From owner-freebsd-current@FreeBSD.ORG Sun May 23 01:25:50 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCD25106566B for ; Sun, 23 May 2010 01:25:50 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-yw0-f175.google.com (mail-yw0-f175.google.com [209.85.211.175]) by mx1.freebsd.org (Postfix) with ESMTP id 92C2E8FC1C for ; Sun, 23 May 2010 01:25:50 +0000 (UTC) Received: by ywh5 with SMTP id 5so1476250ywh.13 for ; Sat, 22 May 2010 18:25:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.13.3 with SMTP id 3mr793215ybm.128.1274577949586; Sat, 22 May 2010 18:25:49 -0700 (PDT) Received: by 10.150.137.17 with HTTP; Sat, 22 May 2010 18:25:49 -0700 (PDT) X-Originating-IP: [128.95.133.151] In-Reply-To: <4BF7F3A7.1060202@jrv.org> References: <4BF24317.8070807@DataIX.net> <4BF7F3A7.1060202@jrv.org> Date: Sat, 22 May 2010 18:25:49 -0700 Message-ID: From: Rob Farmer To: "James R. Van Artsdalen" Content-Type: text/plain; charset=ISO-8859-1 Cc: current@freebsd.org, Garrett Cooper Subject: Re: make release broken 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, 23 May 2010 01:25:50 -0000 On Sat, May 22, 2010 at 8:09 AM, James R. Van Artsdalen wrote: > On 5/18/2010 2:34 AM, jhell wrote: >> On Mon, May 17, 2010 at 10:35 PM, Rob Farmer >> wrote: >>>> make release is broken on current. Seems to be related to the lzma >>>> import. This is on i386: >>>> >>>> cc -static -o boot_crunch boot_crunch.o hostname.lo pwd.lo rm.lo sh.lo >>>> test.lo camcontrol.lo dhclient.lo fsck_ffs.lo ifconfig.lo mount_nfs.lo >>>> newfs.lo route.lo rtsol.lo tunefs.lo cpio.lo find.lo minigzip.lo >>>> sed.lo arp.lo ppp.lo sysinstall.lo usbconfig.lo -ll -ledit -lutil -lmd >>>> -lcrypt -lftpio -lz -lnetgraph -ldialog -lncurses -ldisk -lcam -lsbuf >>>> -lufs -ldevinfo -lbsdxml -larchive -lbz2 -lusb -ljail >>>> /usr/obj/usr/src/tmp/usr/lib/libarchive.a(archive_write_set_compression_xz.o)(.text+0x1e6): >>>> In function `archive_compressor_xz_init': >>>> : undefined reference to `lzma_lzma_preset' >>>> ... >> >> This URL looks to be the problem you are seeing above. >> >> http://docs.freebsd.org/cgi/getmsg.cgi?fetch=20426+0+current/freebsd-current >> > > make release is still broken on amd64 as of svn 208373 (2010-05-21 > 04:52:49 -0500) > > That patch seems unrelated? > That patch is unrelated - it is for building current on RELENG_7 or something like that. What needs done is /src/release/$ARCH/boot_crunch.conf files need the relevant libraries added to the libs section. I haven't tested it, but I think adding -llzma there will fix the problems. -- Rob Farmer From owner-freebsd-current@FreeBSD.ORG Sun May 23 07:27:44 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7627F106566B for ; Sun, 23 May 2010 07:27:44 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-bw0-f54.google.com (mail-bw0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 006E08FC1A for ; Sun, 23 May 2010 07:27:43 +0000 (UTC) Received: by bwz2 with SMTP id 2so581871bwz.13 for ; Sun, 23 May 2010 00:27:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=Bg+TEwA/omogGzF4jceBVvbmFWtvS8cVrsqTXRenpXQ=; b=AWMmQmAe8/wey5Pg53gi5D/s5qmKasBi1zf34o/CTUbje7qUnRuv1oFFUbzjIn3VIf rRRPvR6kkwuEtJ9TB65SQYVFqxQbqRhn9LB3vFjLpucdkbv/2Ip7R6WkBztX6tPL6258 lbZTBKzdooRk2ZkrL7nUsCTweXybRF/GDzoFs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=vCMIjNZYLswqB+8BgK53Lmvfa3TM4mLI9aDI6XX1+5MQuT42LCfoi4HZD8lN1V/OC3 lVtNuvzh3ubQeQsGEGYH/qvKJZBctWJjvegNCw8iIHtpDPpjrkmCSuYEl09lId4F9+pv Bsyp2sgY2WstlGp6x4CoQhkoAEMWgOjCVB/pw= Received: by 10.204.33.149 with SMTP id h21mr1384288bkd.203.1274599662801; Sun, 23 May 2010 00:27:42 -0700 (PDT) Received: from dirtyvegas ([79.126.95.202]) by mx.google.com with ESMTPS id 24sm13047214bkr.12.2010.05.23.00.27.41 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 23 May 2010 00:27:41 -0700 (PDT) Date: Sun, 23 May 2010 07:27:22 +0400 From: Roman Bogorodskiy To: Jeff Roberson Message-ID: <20100523032720.GA89739@dirtyvegas> References: <20100518185201.GA2745@fsol> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: current@freebsd.org Subject: Re: ffs_copyonwrite panics 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, 23 May 2010 07:27:44 -0000 Jeff Roberson wrote: > On Tue, 18 May 2010, Roman Bogorodskiy wrote: > > > Hi, > > > > I've been using -CURRENT last update in February for quite a long time > > and few weeks ago decided to finally update it. The update was quite > > unfortunate as system became very unstable: it just hangs few times a > > day and panics sometimes. > > > > Some things can be reproduced, some cannot. Reproducible ones: > > > > 1. background fsck always makes system hang > > 2. system crashes on operations with nullfs mounts (disabled that for > > now) > > > > The most annoying one is ffs_copyonwrite panic which I cannot reproduce. > > The thing is that if I will run 'startx' on it with some X apps it will > > panic just in few minutes. When I leave the box with nearly no stress > > (just use it as internet gateway for my laptop) it behaves a little > > better but will eventually crash in few hours anyway. > > This may have been my fault. Can you please update and let me know if it > is resolved? There was both a deadlock and a copyonwrite panic as a > result of the softupdates journaling import. I just fixed the deadlock > today. Tried today's -CURRENT and unfortunately the behaviour is still same. Roman Bogorodskiy From owner-freebsd-current@FreeBSD.ORG Mon May 24 02:01:46 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93A321065672 for ; Mon, 24 May 2010 02:01:46 +0000 (UTC) (envelope-from tom@uffner.com) Received: from eris.uffner.com (uffner.com [66.208.243.25]) by mx1.freebsd.org (Postfix) with ESMTP id 1781C8FC12 for ; Mon, 24 May 2010 02:01:44 +0000 (UTC) Received: from kali.uffner.com (static-71-162-143-90.phlapa.fios.verizon.net [71.162.143.90]) (authenticated bits=0) by eris.uffner.com (8.14.3/8.14.3) with ESMTP id o4O240df061729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 23 May 2010 22:04:05 -0400 (EDT) (envelope-from tom@uffner.com) Message-ID: <4BF9CF9E.1000205@uffner.com> Date: Sun, 23 May 2010 21:00:14 -0400 From: Tom Uffner User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.23) Gecko/20090916 SeaMonkey/1.1.18 MIME-Version: 1.0 To: current@freebsd.org References: <20100228095259.GB3536@weongyo> <20100301103240.3a4aac8a.ray@dlink.ua> <20100303082833.GB22865@weongyo> <20100303111014.6564ea1e.ray@dlink.ua> <20100312231333.GZ1295@weongyo> <4BD2201E.3090409@entel.upc.edu> <20100424231755.GI65380@weongyo> <4BD4A928.8020901@entel.upc.edu> <20100506190653.GA31100@weongyo> <58220.88.15.97.205.1273248485.squirrel@webmail.entel.upc.edu> <20100510195622.GA1295@weongyo> In-Reply-To: <20100510195622.GA1295@weongyo> Content-Type: multipart/mixed; boundary="------------050401010107000407030506" Cc: Subject: Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver 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, 24 May 2010 02:01:46 -0000 This is a multi-part message in MIME format. --------------050401010107000407030506 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Weongyo Jeong wrote: > OK. The patch is ready to test. Could you please test it with attached > patch? your patch got rid of the "bwn0: unsupported rate 0" messages on my Dell Inspiron 1150. But it still gives me repeated: bwn0: RX decryption attempted (old 0 keyidx 0x1) and a few of the following: bwn0: need multicast update callback ts_to_ct(1274664456.824638117) = [2010-05-24 01:27:36] please let me know if there is anything you want me to test. --------------050401010107000407030506 Content-Type: text/plain; name="dmesg.boot" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.boot" Copyright (c) 1992-2010 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 is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-STABLE #0: Sun May 16 00:05:17 EDT 2010 tom@zoe.uffner.com:/usr/obj/usr/src/sys/ZOE i386 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0ab6000. Preloaded elf module "/boot/kernel/if_bwn.ko" at 0xc0ab6174. Preloaded elf module "/boot/kernel/siba_bwn.ko" at 0xc0ab6220. Preloaded elf module "/boot/modules/bwn_v4_ucode.ko" at 0xc0ab62d0. Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2597803596 Hz CPU: Intel(R) Celeron(R) CPU 2.60GHz (2597.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Family = f Model = 2 Stepping = 9 Features=0xbfebf9ff Features2=0x4400 Instruction TLB: 4 KB, 2 MB or 4 MB pages, fully associative, 128 entries Data TLB: 4 KB or 4 MB pages, fully associative, 64 entries 1st-level data cache: 8 KB, 4-way set associative, sectored cache, 64 byte line size Trace cache: 12K-uops, 8-way set associative 2nd-level cache: 128 KB, 2-way set associative, sectored cache, 64 byte line size real memory = 1073741824 (1024 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000009efff, 647168 bytes (158 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000000c26000 - 0x000000003ec82fff, 1040568320 bytes (254045 pages) avail memory = 1040355328 (992 MB) bios32: Found BIOS32 Service Directory header at 0xc00ffe80 bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf0000+0xcfae pnpbios: Found PnP BIOS data at 0xc00fe2d0 pnpbios: Entry = f0000:e2f4 Rev = 1.0 pnpbios: Event flag at 4b4 Other BIOS signatures found: x86bios: IVT 0x000000-0x0004ff at 0xc0000000 x86bios: SSEG 0x010000-0x01ffff at 0xc3b74000 x86bios: EBDA 0x09f000-0x09ffff at 0xc009f000 x86bios: ROM 0x0a0000-0x0effff at 0xc00a0000 ULE: setup cpu 0 wlan: <802.11 Link Layer> snd_unit_init() u=0x00ff8000 [512] d=0x00007c00 [32] c=0x000003ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 firmware: 'bwn_v4_ucode' version 0: 0 bytes loaded at 0xc0a8b808 firmware: 'bwn_v4_ucode5' version 0: 22384 bytes loaded at 0xc0a8b808 firmware: 'bwn_v4_ucode11' version 0: 29864 bytes loaded at 0xc0a90f78 firmware: 'bwn_v4_ucode13' version 0: 32232 bytes loaded at 0xc0a98420 firmware: 'bwn_v4_ucode14' version 0: 31384 bytes loaded at 0xc0aa0208 firmware: 'bwn_v4_ucode15' version 0: 30488 bytes loaded at 0xc0aa7ca0 firmware: 'bwn_v4_pcm5' version 0: 1320 bytes loaded at 0xc0aaf3b8 firmware: 'bwn_v4_a0g1initvals5' version 0: 1840 bytes loaded at 0xc0aaf8e0 firmware: 'bwn_v4_a0g0initvals5' version 0: 1840 bytes loaded at 0xc0ab0010 firmware: 'bwn_v4_b0g0initvals5' version 0: 1840 bytes loaded at 0xc0ab0740 firmware: 'bwn_v4_b0g0initvals13' version 0: 2080 bytes loaded at 0xc0ab0e70 firmware: 'bwn_v4_a0g1bsinitvals5' version 0: 158 bytes loaded at 0xc0ab1690 firmware: 'bwn_v4_a0g0bsinitvals5' version 0: 158 bytes loaded at 0xc0ab172e firmware: 'bwn_v4_b0g0bsinitvals5' version 0: 158 bytes loaded at 0xc0ab17cc firmware: 'bwn_v4_lp0initvals13' version 0: 3618 bytes loaded at 0xc0ab186a firmware: 'bwn_v4_lp0initvals14' version 0: 2064 bytes loaded at 0xc0ab268c firmware: 'bwn_v4_lp0initvals15' version 0: 2052 bytes loaded at 0xc0ab2e9c firmware: 'bwn_v4_lp0bsinitvals13' version 0: 158 bytes loaded at 0xc0ab36a0 firmware: 'bwn_v4_lp0bsinitvals14' version 0: 158 bytes loaded at 0xc0ab373e firmware: 'bwn_v4_lp0bsinitvals15' version 0: 158 bytes loaded at 0xc0ab37dc firmware: 'bwn_v4_n0bsinitvals11' version 0: 158 bytes loaded at 0xc0ab387a kbd: new array size 4 kbd1 at kbdmux0 nfslock: pseudo-device mem: Pentium Pro MTRR support enabled null: io: random: ACPI: RSDP 0xfdf00 00014 (v0 DELL ) ACPI: RSDT 0x3fef0000 00028 (v1 DELL CPi R 27D50605 ASL 00000061) ACPI: FACP 0x3fef0400 00074 (v1 DELL CPi R 27D50605 ASL 00000061) ACPI: DSDT 0x3fef0c00 02594 (v1 INT430 SYSFexxx 00001001 MSFT 0100000E) ACPI: FACS 0x3feff800 00040 npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] acpi0: [ITHREAD] acpi0: wakeup code va 0xc3b73000 pa 0x1000 atpic: Programming IRQ9 as level/low pci_open(1): mode 1 addr port (0x0cf8) is 0x80000050 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=35808086) pcibios: BIOS version 2.10 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \\_SB_.PCI0.ISAB.PIR1 -> bus 0 dev 31 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \\_SB_.PCI0.ISAB.PIR2 -> bus 0 dev 31 func 0 acpi0: reservation of 0, 9fc00 (3) failed acpi0: reservation of 100000, 3fdf0000 (3) failed ACPI timer: 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 1/0 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu0: switching to generic Cx mode pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 9 10 11 Validation 0 11 N 0 9 10 11 After Disable 0 255 N 0 9 10 11 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 7 Validation 0 255 N 0 5 7 After Disable 0 255 N 0 5 7 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 9 10 11 Validation 0 11 N 0 9 10 11 After Disable 0 255 N 0 9 10 11 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 5 7 9 10 11 Validation 0 11 N 0 5 7 9 10 11 After Disable 0 255 N 0 5 7 9 10 11 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 3 4 5 6 7 9 10 11 12 14 15 Validation 0 255 N 0 3 4 5 6 7 9 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 14 15 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 6 7 9 10 11 12 14 15 Validation 0 11 N 0 3 4 5 6 7 9 10 11 12 14 15 After Disable 0 255 N 0 3 4 5 6 7 9 10 11 12 14 15 acpi_acad0: on acpi0 battery0: on acpi0 acpi_lid0: on acpi0 acpi_button0: on acpi0 acpi_button1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 ACPI: Found matching pin for 0.31.INTA at func 1: 255 ACPI: Found matching pin for 0.31.INTB at func 5: 11 pci_link1: BIOS IRQ 11 for 0.31.INTB is invalid ACPI: Found matching pin for 0.29.INTA at func 0: 11 ACPI: Found matching pin for 0.29.INTB at func 1: 11 ACPI: Found matching pin for 0.29.INTC at func 2: 11 ACPI: Found matching pin for 0.29.INTD at func 7: 11 ACPI: Found matching pin for 0.2.INTA at func 0: 11 pci0: on pcib0 pci0: domain=0, physical bus=0 found-> vendor=0x8086, dev=0x3580, revid=0x02 domain=0, bus=0, slot=0, func=0 class=06-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0106, statreg=0x3090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x3584, revid=0x02 domain=0, bus=0, slot=0, func=1 class=08-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0006, statreg=0x0080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x3585, revid=0x02 domain=0, bus=0, slot=0, func=3 class=08-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0006, statreg=0x0080, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x3582, revid=0x02 domain=0, bus=0, slot=2, func=0 class=03-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 1 supports D0 D1 D3 current D0 map[10]: type Prefetchable Memory, range 32, base 0xe8000000, size 27, enabled map[14]: type Memory, range 32, base 0xf6f80000, size 19, enabled map[18]: type I/O Port, range 32, base 0xc000, size 3, enabled pcib0: matched entry for 0.2.INTA (src \\_SB_.PCI0.LNKA:0) pcib0: slot 2 INTA routed to irq 11 via \\_SB_.PCI0.LNKA found-> vendor=0x8086, dev=0x3582, revid=0x02 domain=0, bus=0, slot=2, func=1 class=03-80-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0090, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) powerspec 1 supports D0 D1 D3 current D0 map[10]: type Prefetchable Memory, range 32, base 0xe0000000, size 27, enabled map[14]: type Memory, range 32, base 0xf6f00000, size 19, enabled found-> vendor=0x8086, dev=0x24c2, revid=0x01 domain=0, bus=0, slot=29, func=0 class=0c-03-00, hdrtype=0x00, mfdev=1 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[20]: type I/O Port, range 32, base 0xbf80, size 5, enabled pcib0: matched entry for 0.29.INTA (src \\_SB_.PCI0.LNKA:0) pcib0: slot 29 INTA routed to irq 11 via \\_SB_.PCI0.LNKA unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xbf80 found-> vendor=0x8086, dev=0x24c4, revid=0x01 domain=0, bus=0, slot=29, func=1 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 map[20]: type I/O Port, range 32, base 0xbf40, size 5, enabled pcib0: matched entry for 0.29.INTB (src \\_SB_.PCI0.LNKD:0) pcib0: slot 29 INTB routed to irq 11 via \\_SB_.PCI0.LNKD unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xbf40 found-> vendor=0x8086, dev=0x24c7, revid=0x01 domain=0, bus=0, slot=29, func=2 class=0c-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=c, irq=11 map[20]: type I/O Port, range 32, base 0xbf20, size 5, enabled pcib0: matched entry for 0.29.INTC (src \\_SB_.PCI0.LNKC:0) pcib0: slot 29 INTC routed to irq 11 via \\_SB_.PCI0.LNKC unknown: Reserved 0x20 bytes for rid 0x20 type 4 at 0xbf20 found-> vendor=0x8086, dev=0x24cd, revid=0x01 domain=0, bus=0, slot=29, func=7 class=0c-03-20, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=d, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xf6effc00, size 10, enabled pcib0: matched entry for 0.29.INTD (src \\_SB_.PCI0.LNKH:0) pcib0: slot 29 INTD routed to irq 11 via \\_SB_.PCI0.LNKH unknown: Reserved 0x400 bytes for rid 0x10 type 3 at 0xf6effc00 found-> vendor=0x8086, dev=0x2448, revid=0x81 domain=0, bus=0, slot=30, func=0 class=06-04-00, hdrtype=0x01, mfdev=0 cmdreg=0x0107, statreg=0x8880, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x04 (1000 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x24cc, revid=0x01 domain=0, bus=0, slot=31, func=0 class=06-01-00, hdrtype=0x00, mfdev=1 cmdreg=0x010f, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) found-> vendor=0x8086, dev=0x24ca, revid=0x01 domain=0, bus=0, slot=31, func=1 class=01-01-8a, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0280, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=255 map[20]: type I/O Port, range 32, base 0xbfa0, size 4, enabled map[24]: type Memory, range 32, base 0, size 10, memory disabled found-> vendor=0x8086, dev=0x24c5, revid=0x01 domain=0, bus=0, slot=31, func=5 class=04-01-00, hdrtype=0x00, mfdev=0 cmdreg=0x0007, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0xc800, size 8, enabled map[14]: type I/O Port, range 32, base 0xcc40, size 6, enabled map[18]: type Memory, range 32, base 0xf6eff800, size 9, enabled map[1c]: type Memory, range 32, base 0xf6eff400, size 8, enabled pcib0: matched entry for 0.31.INTB (src \\_SB_.PCI0.LNKB:0) pci_link1: Picked IRQ 9 with weight 0 pcib0: slot 31 INTB routed to irq 9 via \\_SB_.PCI0.LNKB found-> vendor=0x8086, dev=0x24c6, revid=0x01 domain=0, bus=0, slot=31, func=6 class=07-03-00, hdrtype=0x00, mfdev=0 cmdreg=0x0005, statreg=0x0290, cachelnsz=0 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=11 powerspec 2 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0xc400, size 8, enabled map[14]: type I/O Port, range 32, base 0xc080, size 7, enabled pcib0: matched entry for 0.31.INTB (src \\_SB_.PCI0.LNKB:0) pcib0: slot 31 INTB routed to irq 9 via \\_SB_.PCI0.LNKB pci0: at device 0.1 (no driver attached) pci0: at device 0.3 (no driver attached) vgapci0: port 0xc000-0xc007 mem 0xe8000000-0xefffffff,0xf6f80000-0xf6ffffff irq 11 at device 2.0 on pci0 agp0: on vgapci0 vgapci0: Reserved 0x8000000 bytes for rid 0x10 type 3 at 0xe8000000 vgapci0: Reserved 0x80000 bytes for rid 0x14 type 3 at 0xf6f80000 agp0: detected 892k stolen memory agp0: aperture size is 128M vgapci1: mem 0xe0000000-0xe7ffffff,0xf6f00000-0xf6f7ffff at device 2.1 on pci0 uhci0: port 0xbf80-0xbf9f irq 11 at device 29.0 on pci0 uhci0: [MPSAFE] uhci0: [ITHREAD] usbus0: on uhci0 uhci1: port 0xbf40-0xbf5f irq 11 at device 29.1 on pci0 uhci1: [MPSAFE] uhci1: [ITHREAD] usbus1: on uhci1 uhci2: port 0xbf20-0xbf3f irq 11 at device 29.2 on pci0 uhci2: [MPSAFE] uhci2: [ITHREAD] usbus2: on uhci2 ehci0: mem 0xf6effc00-0xf6efffff irq 11 at device 29.7 on pci0 ehci0: [MPSAFE] ehci0: [ITHREAD] usbus3: EHCI version 1.0 usbus3: on ehci0 pcib1: at device 30.0 on pci0 pcib1: domain 0 pcib1: secondary bus 2 pcib1: subordinate bus 2 pcib1: I/O decode 0xd000-0xefff pcib1: memory decode 0xf8000000-0xfdffffff pcib1: no prefetched decode pcib1: Subtractively decoded bridge. ACPI: Found matching pin for 2.4.INTA at func 0: 255 ACPI: Found matching pin for 2.2.INTA at func 0: 11 ACPI: Found matching pin for 2.1.INTA at func 0: 11 pci_link1: BIOS IRQ 11 for 2.1.INTA is invalid pci2: on pcib1 pci2: domain=0, physical bus=2 found-> vendor=0x14e4, dev=0x4401, revid=0x01 domain=0, bus=2, slot=1, func=0 class=02-00-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0810, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xfcffe000, size 13, enabled pcib1: requested memory range 0xfcffe000-0xfcffffff: good pcib1: matched entry for 2.1.INTA (src \\_SB_.PCI0.LNKB:0) pcib1: slot 1 INTA routed to irq 9 via \\_SB_.PCI0.LNKB found-> vendor=0x14e4, dev=0x4320, revid=0x03 domain=0, bus=2, slot=2, func=0 class=02-80-00, hdrtype=0x00, mfdev=0 cmdreg=0x0106, statreg=0x0000, cachelnsz=0 (dwords) lattimer=0x20 (960 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=11 map[10]: type Memory, range 32, base 0xfcffc000, size 13, enabled pcib1: requested memory range 0xfcffc000-0xfcffdfff: good pcib1: matched entry for 2.2.INTA (src \\_SB_.PCI0.LNKC:0) pcib1: slot 2 INTA routed to irq 11 via \\_SB_.PCI0.LNKC found-> vendor=0x104c, dev=0xac56, revid=0x00 domain=0, bus=2, slot=4, func=0 class=06-07-00, hdrtype=0x02, mfdev=0 cmdreg=0x0000, statreg=0x0210, cachelnsz=8 (dwords) lattimer=0x20 (960 ns), mingnt=0x40 (16000 ns), maxlat=0x07 (1750 ns) intpin=a, irq=255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0, size 12, memory disabled bfe0: mem 0xfcffe000-0xfcffffff irq 9 at device 1.0 on pci2 bfe0: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfcffe000 miibus0: on bfe0 bmtphy0: PHY 1 on miibus0 bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bfe0: bpf attached bfe0: Ethernet address: 00:11:43:69:8b:52 bfe0: [MPSAFE] bfe0: [ITHREAD] siba_bwn0: mem 0xfcffc000-0xfcffdfff irq 11 at device 2.0 on pci2 siba_bwn0: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfcffc000 bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4306 rev 5) PHY (analog 2 type 2 rev 2) RADIO (manuf 0x17f ver 0x2050 rev 2) bwn0: DMA (30 bits) bwn0: [MPSAFE] bwn0: [FILTER] bwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps bwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps cbb0: at device 4.0 on pci2 pcib1: cbb0 requested memory range 0x0-0xffffffff: good cbb0: Lazy allocation of 0x1000 bytes rid 0x10 type 3 at 0x80000000 cbb0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0x80000000 cardbus0: on cbb0 pccard0: <16-bit PCCard bus> on cbb0 pcib1: matched entry for 2.4.INTA (src \\_SB_.PCI0.LNKA:0) pcib1: slot 4 INTA routed to irq 11 via \\_SB_.PCI0.LNKA cbb0: [MPSAFE] cbb0: [FILTER] cbb0: PCI Configuration space: 0x00: 0xac56104c 0x02100007 0x06070000 0x00022008 0x10: 0x80000000 0x020000a0 0x20040302 0xfffff000 0x20: 0x00000000 0xfffff000 0x00000000 0xfffffffc 0x30: 0x00000000 0xfffffffc 0x00000000 0x0740010b 0x40: 0x017f1028 0x00000001 0x00000000 0x00000000 0x50: 0x00000000 0x00000000 0x00000000 0x00000000 0x60: 0x00000000 0x00000000 0x00000000 0x00000000 0x70: 0x00000000 0x00000000 0x00000000 0x00000000 0x80: 0x08405061 0x00000000 0x00000000 0x00001002 0x90: 0x606482c0 0x00000000 0x00000000 0x00000000 0xa0: 0xfe120001 0x00c00000 0x00000000 0x0000001f 0xb0: 0x00000000 0x00000000 0x00000000 0x00000000 0xc0: 0x00000000 0x00000000 0x00000000 0x00000000 0xd0: 0x00000000 0x00000000 0x00000000 0x00000000 0xe0: 0x00000000 0x00000000 0x00000000 0x00000000 0xf0: 0x00000000 0x00000000 0x00000000 0x00000000 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xbfa0-0xbfaf at device 31.1 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xbfa0 ata0: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1f0 atapci0: Reserved 0x1 bytes for rid 0x14 type 4 at 0x3f6 ata0: reset tp1 mask=03 ostat0=50 ostat1=00 ata0: stat0=0x00 err=0x01 lsb=0x14 msb=0xeb ata0: stat1=0x00 err=0x00 lsb=0x00 msb=0x00 ata0: reset tp2 stat0=00 stat1=00 devices=0x10000 ata0: [MPSAFE] ata0: [ITHREAD] ata1: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x170 atapci0: Reserved 0x1 bytes for rid 0x1c type 4 at 0x376 ata1: reset tp1 mask=03 ostat0=50 ostat1=00 ata1: stat0=0x50 err=0x01 lsb=0x00 msb=0x00 ata1: stat1=0x00 err=0x01 lsb=0x00 msb=0x00 ata1: reset tp2 stat0=50 stat1=00 devices=0x1 ata1: [MPSAFE] ata1: [ITHREAD] pcm0: port 0xc800-0xc8ff,0xcc40-0xcc7f mem 0xf6eff800-0xf6eff9ff,0xf6eff400-0xf6eff4ff irq 9 at device 31.5 on pci0 pcm0: Reserved 0x200 bytes for rid 0x18 type 3 at 0xf6eff800 pcm0: Reserved 0x100 bytes for rid 0x1c type 3 at 0xf6eff400 pcm0: [MPSAFE] pcm0: [ITHREAD] pcm0: pcm0: Codec features headphone, 20 bit DAC, 20 bit ADC, 5 bit master volume, SigmaTel 3D Enhancement pcm0: Primary codec extended features variable rate PCM, AMAP, reserved 4 pcm0: ac97 codec dac ready count: 0 pcm0: Mixer "vol": pcm0: Mixer "pcm": pcm0: Mixer "speaker": pcm0: Mixer "line": pcm0: Mixer "mic": pcm0: Mixer "cd": pcm0: Mixer "rec": pcm0: Mixer "igain": pcm0: Mixer "ogain": pcm0: Mixer "line1": pcm0: Mixer "phin": pcm0: Mixer "phout": pcm0: Mixer "video": pcm0: clone manager: deadline=750ms flags=0x8000001e pcm0: sndbuf_setmap 1e1c000, 4000; 0xe43be000 -> 1e1c000 pcm0: sndbuf_setmap 1e20000, 4000; 0xe43c2000 -> 1e20000 pci0: at device 31.6 (no driver attached) acpi_tz0: on acpi0 psmcpnp0: irq 12 on acpi0 atkbdc0: port 0x60,0x64,0x62,0x66 irq 1 on acpi0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 atkbd0: [GIANT-LOCKED] atkbd0: [ITHREAD] psm0: current command byte:0065 psm0: flags 0x1000 irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: [ITHREAD] psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00001000, flags:00000008, packet size:3 psm0: syncmask:c0, syncbits:00 atrtc0: port 0x70-0x71,0x72-0x77 irq 8 on acpi0 atrtc0: registered as a time-of-day clock (resolution 1000000us) pnp_identify: Trying Read_Port at 203 pnp_identify: Trying Read_Port at 243 pnp_identify: Trying Read_Port at 283 pnp_identify: Trying Read_Port at 2c3 pnp_identify: Trying Read_Port at 303 pnp_identify: Trying Read_Port at 343 pnp_identify: Trying Read_Port at 383 pnp_identify: Trying Read_Port at 3c3 PNP Identify complete isa_probe_children: disabling PnP devices pmtimer0 on isa0 ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it atkbdc: atkbdc0 already exists; skipping it atrtc: atrtc0 already exists; skipping it sc: sc0 already exists; skipping it isa_probe_children: probing non-PnP devices orm0: at iomem 0xc0000-0xcc7ff,0xcc800-0xccfff,0xcd000-0xcd7ff,0xcd800-0xcdfff,0xce000-0xce7ff,0xce800-0xcefff,0xcf000-0xcf7ff,0xcf800-0xcffff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fdc0 failed to probe at port 0x3f0 irq 6 drq 2 on isa0 ppc0 failed to probe at irq 7 on isa0 uart0: failed to probe at port 0x3f8-0x3ff irq 4 on isa0 uart1: failed to probe at port 0x2f8-0x2ff irq 3 on isa0 isa_probe_children: probing PnP devices acpi_perf0: on cpu0 device_attach: acpi_perf0 attach returned 6 acpi_perf0: on cpu0 device_attach: acpi_perf0 attach returned 6 p4tcc0: on cpu0 ichss0: on cpu0 ichss0: enabling SpeedStep support Device configuration finished. procfs registered Timecounter "TSC" frequency 2597803596 Hz quality 800 Timecounters tick every 1.000 msec vlan: initialized, using hash tables with chaining lo0: bpf attached ata0: Identifying devices: 00010000 ata0: New devices: 00010000 usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 12Mbps Full Speed USB v1.0 usbus3: 480Mbps High Speed USB v2.0 acpi_acad0: acline initialization start acpi_acad0: On Line acpi_acad0: acline initialization done, tried 1 times battery0: battery initialization start ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 ugen3.1: at usbus3 uhub3: on usbus3 battery0: battery initialization done, tried 1 times ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire acd0: setting UDMA33 acd0: CDRW drive at ata0 as master acd0: read 4134KB/s (4134KB/s) write 4134KB/s (4134KB/s), 2048KB buffer, UDMA33 acd0: Reads: CDR, CDRW, CDDA stream, DVDROM, DVDR, packet acd0: Writes: CDR, CDRW, test write, burnproof acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc ata1: Identifying devices: 00000001 ata1: New devices: 00000001 ata1-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire ad2: setting UDMA100 ad2: 28615MB at ata1-master UDMA100 ad2: 58605120 sectors [58140C/16H/63S] 16 sectors/interrupt 1 depth queue pcm0: measured ac97 link rate at 48017 Hz, will use 48000 Hz GEOM: new disk ad2 uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered Root mount waiting for: usbus3 Root mount waiting for: usbus3 Root mount waiting for: usbus3 uhub3: 6 ports with 6 removable, self powered Trying to mount root from ufs:/dev/label/rootfs0 ct_to_ts([2010-05-24 01:27:19]) = 1274664439.000000000 start_init: trying /sbin/init wlan0: bpf attached wlan0: bpf attached wlan0: Ethernet address: 00:0b:7d:13:3f:ef bwn0: firmware version (rev 410 patch 2160 date 0x751a time 0x7c0a) wlan0: link state changed to UP bwn0: need multicast update callback --------------050401010107000407030506-- From owner-freebsd-current@FreeBSD.ORG Mon May 24 03:46:35 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A70AB1065672 for ; Mon, 24 May 2010 03:46:35 +0000 (UTC) (envelope-from jroberson@jroberson.net) Received: from mail-px0-f182.google.com (mail-px0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 845578FC15 for ; Mon, 24 May 2010 03:46:35 +0000 (UTC) Received: by pxi7 with SMTP id 7so1532016pxi.13 for ; Sun, 23 May 2010 20:46:35 -0700 (PDT) Received: by 10.143.26.3 with SMTP id d3mr3314388wfj.232.1274672794999; Sun, 23 May 2010 20:46:34 -0700 (PDT) Received: from [10.0.1.198] (udp022762uds.hawaiiantel.net [72.234.79.107]) by mx.google.com with ESMTPS id x34sm752850wfi.16.2010.05.23.20.46.33 (version=SSLv3 cipher=RC4-MD5); Sun, 23 May 2010 20:46:34 -0700 (PDT) Date: Sun, 23 May 2010 17:46:30 -1000 (HST) From: Jeff Roberson X-X-Sender: jroberson@desktop To: Roman Bogorodskiy In-Reply-To: <20100523032720.GA89739@dirtyvegas> Message-ID: References: <20100518185201.GA2745@fsol> <20100523032720.GA89739@dirtyvegas> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: ffs_copyonwrite panics 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, 24 May 2010 03:46:35 -0000 On Sun, 23 May 2010, Roman Bogorodskiy wrote: > Jeff Roberson wrote: > >> On Tue, 18 May 2010, Roman Bogorodskiy wrote: >> >>> Hi, >>> >>> I've been using -CURRENT last update in February for quite a long time >>> and few weeks ago decided to finally update it. The update was quite >>> unfortunate as system became very unstable: it just hangs few times a >>> day and panics sometimes. >>> >>> Some things can be reproduced, some cannot. Reproducible ones: >>> >>> 1. background fsck always makes system hang >>> 2. system crashes on operations with nullfs mounts (disabled that for >>> now) >>> >>> The most annoying one is ffs_copyonwrite panic which I cannot reproduce. >>> The thing is that if I will run 'startx' on it with some X apps it will >>> panic just in few minutes. When I leave the box with nearly no stress >>> (just use it as internet gateway for my laptop) it behaves a little >>> better but will eventually crash in few hours anyway. >> >> This may have been my fault. Can you please update and let me know if it >> is resolved? There was both a deadlock and a copyonwrite panic as a >> result of the softupdates journaling import. I just fixed the deadlock >> today. > > Tried today's -CURRENT and unfortunately the behaviour is still same. Can you give me a full stack trace? Do you have coredumps enabled? I would like to have you look at a few things in a core or send it to me with your kernel. Thanks, Jeff > > Roman Bogorodskiy > From owner-freebsd-current@FreeBSD.ORG Mon May 24 04:49:59 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F62A106566C for ; Mon, 24 May 2010 04:49:59 +0000 (UTC) (envelope-from okuno.kohji@jp.panasonic.com) Received: from smtp.mei.co.jp (smtp.mei.co.jp [133.183.100.20]) by mx1.freebsd.org (Postfix) with ESMTP id D5B858FC14 for ; Mon, 24 May 2010 04:49:58 +0000 (UTC) Received: from mail-gw.jp.panasonic.com ([157.8.1.145]) by smtp.mei.co.jp (8.12.11.20060614/3.7W/kc-maile14) with ESMTP id o4O4nvIm002109 for ; Mon, 24 May 2010 13:49:57 +0900 (JST) Received: from epochmail.jp.panasonic.com (localhost [127.0.0.1]) by mail.jp.panasonic.com (8.11.6p2/3.7W/kc-maili01) with ESMTP id o4O4nuA05108 for ; Mon, 24 May 2010 13:49:56 +0900 (JST) Received: by epochmail.jp.panasonic.com (8.12.11.20060308/3.7W/somla6) id o4O4nvYw006214 for freebsd-current@freebsd.org; Mon, 24 May 2010 13:49:57 +0900 (JST) Received: from localhost by somla6.jp.panasonic.com (8.12.11.20060308/3.7W) with ESMTP id o4O4nuaY006183 for ; Mon, 24 May 2010 13:49:56 +0900 (JST) Date: Mon, 24 May 2010 13:49:55 +0900 (JST) Message-Id: <20100524.134955.2300883222251175323.okuno.kohji@jp.panasonic.com> To: freebsd-current@freebsd.org From: Kohji Okuno Organization: Panasonic Corporation X-Mailer: Mew version 6.3 on Emacs 23.2 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: About 32bit binary on 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: Mon, 24 May 2010 04:49:59 -0000 Hi all, I want to compile 32bit binary on amd64, but I met with the problem. Could you teach me the best solution, please? My environment is FreeBSD 8.1-PRERELEASE #0: Tue May 18 12:01:26 JST 2010. I compiled and executed test.c as below on amd64. -- begin -- test.c ------------------------------------------------------ #include #include #include #include int main() { void *ptr; ptr = mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0); if (ptr == MAP_FAILED) { perror("mmap"); exit(1); } printf("%lx\n", (unsigned long)ptr); munmap(ptr, 4096); exit(0); } -- end -- test.c -------------------------------------------------------- % gcc -m32 -B/usr/lib32 test.c % ./a.out mmap: Invalid argument I disassembled a.out. I think that 'movl $0x0,0x18(%esp)' is needed. This error is occured by 'off_t offset'. 80484ce: 83 ec 34 sub $0x34,%esp 80484d1: c7 44 24 14 00 00 00 movl $0x0,0x14(%esp) 80484d8: 00 80484d9: c7 44 24 10 ff ff ff movl $0xffffffff,0x10(%esp) 80484e0: ff 80484e1: c7 44 24 0c 00 10 00 movl $0x1000,0xc(%esp) 80484e8: 00 80484e9: c7 44 24 08 03 00 00 movl $0x3,0x8(%esp) 80484f0: 00 80484f1: c7 44 24 04 00 10 00 movl $0x1000,0x4(%esp) 80484f8: 00 80484f9: c7 04 24 00 00 00 00 movl $0x0,(%esp) 8048500: e8 43 fe ff ff call 8048348 I found this solution. I modified machine depended header as below. # cd /usr/include/machine # cp /usr/src/sys/i386/include/_types.h _types32.h # patch < _types.h.diff -- begin -- _types.h.diff ------------------------------------------------ --- _types.h.org 2010-05-24 13:34:55.406874258 +0900 +++ _types.h 2010-05-24 13:35:33.790522354 +0900 @@ -36,6 +36,10 @@ * $FreeBSD: src/sys/amd64/include/_types.h,v 1.12.2.1 2009/08/03 08:13:06 kensmith Exp $ */ +#ifdef __i386__ +#include +#else + #ifndef _MACHINE__TYPES_H_ #define _MACHINE__TYPES_H_ @@ -115,3 +119,4 @@ #endif #endif /* !_MACHINE__TYPES_H_ */ +#endif /* __i386__ */ -- end -- _types.h.diff ---------------------------------------------- In this case, 'off_t offset' is set correctly as below. 80484d1: c7 44 24 14 00 00 00 movl $0x0,0x14(%esp) 80484d8: 00 80484d9: c7 44 24 18 00 00 00 movl $0x0,0x18(%esp) 80484e0: 00 80484e1: c7 44 24 10 ff ff ff movl $0xffffffff,0x10(%esp) 80484e8: ff 80484e9: c7 44 24 0c 00 10 00 movl $0x1000,0xc(%esp) 80484f0: 00 80484f1: c7 44 24 08 03 00 00 movl $0x3,0x8(%esp) 80484f8: 00 80484f9: c7 44 24 04 00 10 00 movl $0x1000,0x4(%esp) 8048500: 00 8048501: c7 04 24 00 00 00 00 movl $0x0,(%esp) 8048508: e8 3b fe ff ff call 8048348 How should we deal with this problem? Best reards, Kohji Okuno From owner-freebsd-current@FreeBSD.ORG Mon May 24 06:02:08 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 20DBD106566C for ; Mon, 24 May 2010 06:02:08 +0000 (UTC) (envelope-from james-freebsd-current@jrv.org) Received: from zimbra.jrv.org (adsl-70-243-84-11.dsl.austtx.swbell.net [70.243.84.11]) by mx1.freebsd.org (Postfix) with ESMTP id E08E68FC1A for ; Mon, 24 May 2010 06:02:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zimbra.jrv.org (Postfix) with ESMTP id E8CEB16A079; Mon, 24 May 2010 01:02:05 -0500 (CDT) X-Virus-Scanned: amavisd-new at zimbra.housenet.jrv Received: from zimbra.jrv.org ([127.0.0.1]) by localhost (zimbra.housenet.jrv [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id brnEWeZEWkc0; Mon, 24 May 2010 01:02:05 -0500 (CDT) Received: from [10.0.2.15] (adsl-70-243-84-14.dsl.austtx.swbell.net [70.243.84.14]) by zimbra.jrv.org (Postfix) with ESMTPSA id 14C5B16A048; Mon, 24 May 2010 01:02:05 -0500 (CDT) Message-ID: <4BFA167B.1010902@jrv.org> Date: Mon, 24 May 2010 01:02:35 -0500 From: "James R. Van Artsdalen" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Rob Farmer References: <4BF24317.8070807@DataIX.net> <4BF7F3A7.1060202@jrv.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: current@freebsd.org, Garrett Cooper Subject: Re: make release broken 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, 24 May 2010 06:02:08 -0000 On 5/22/2010 8:25 PM, Rob Farmer wrote: > make release is still broken on amd64 as of svn 208373 (2010-05-21 >> 04:52:49 -0500) >> >> That patch seems unrelated? >> > What needs done is > /src/release/$ARCH/boot_crunch.conf files need the relevant libraries > added to the libs section. I haven't tested it, but I think adding > -llzma there will fix the problems. That works for me, except that I had to add -lcrypto too? I don't know if that's a good idea. Index: release/amd64/boot_crunch.conf =================================================================== --- release/amd64/boot_crunch.conf (revision 208373) +++ release/amd64/boot_crunch.conf (working copy) @@ -41,4 +41,4 @@ libs -ll -ledit -lutil -lmd -lcrypt -lftpio -lz -lnetgraph libs -ldialog -lncurses -ldisk -lcam -lsbuf -lufs -ldevinfo -libs -lbsdxml -larchive -lbz2 -lusb -ljail +libs -lbsdxml -larchive -lbz2 -lusb -ljail -llzma -lcrypto From owner-freebsd-current@FreeBSD.ORG Mon May 24 06:16:38 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E72761065675 for ; Mon, 24 May 2010 06:16:38 +0000 (UTC) (envelope-from rfarmer@predatorlabs.net) Received: from mail-gw0-f54.google.com (mail-gw0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id AAD4F8FC14 for ; Mon, 24 May 2010 06:16:38 +0000 (UTC) Received: by gwj18 with SMTP id 18so703013gwj.13 for ; Sun, 23 May 2010 23:16:38 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.56.33 with SMTP id e33mr5618373yba.423.1274681797806; Sun, 23 May 2010 23:16:37 -0700 (PDT) Received: by 10.150.137.17 with HTTP; Sun, 23 May 2010 23:16:37 -0700 (PDT) X-Originating-IP: [128.95.133.178] In-Reply-To: <4BFA167B.1010902@jrv.org> References: <4BF24317.8070807@DataIX.net> <4BF7F3A7.1060202@jrv.org> <4BFA167B.1010902@jrv.org> Date: Sun, 23 May 2010 23:16:37 -0700 Message-ID: From: Rob Farmer To: "James R. Van Artsdalen" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org, Garrett Cooper Subject: Re: make release broken 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, 24 May 2010 06:16:39 -0000 On Sun, May 23, 2010 at 11:02 PM, James R. Van Artsdalen wrote: > On 5/22/2010 8:25 PM, Rob Farmer wrote: >> make release is still broken on amd64 as of svn 208373 (2010-05-21 >>> 04:52:49 -0500) >>> >>> That patch seems unrelated? >>> >> What needs done is >> /src/release/$ARCH/boot_crunch.conf files need the relevant libraries >> added to the libs section. I haven't tested it, but I think adding >> -llzma there will fix the problems. > > That works for me, except that I had to add -lcrypto too? =A0I don't know > if that's a good idea. Yeah, I found that out too when I tested it. I've submitted a PR with patches for all the archs: http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dmisc/146904 --=20 Rob Farmer > > Index: release/amd64/boot_crunch.conf > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- release/amd64/boot_crunch.conf =A0 =A0 =A0(revision 208373) > +++ release/amd64/boot_crunch.conf =A0 =A0 =A0(working copy) > @@ -41,4 +41,4 @@ > > =A0libs -ll -ledit -lutil -lmd -lcrypt -lftpio -lz -lnetgraph > =A0libs -ldialog -lncurses -ldisk -lcam -lsbuf -lufs -ldevinfo > -libs -lbsdxml -larchive -lbz2 -lusb -ljail > +libs -lbsdxml -larchive -lbz2 -lusb -ljail -llzma -lcrypto > > From owner-freebsd-current@FreeBSD.ORG Mon May 24 09:49:38 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0EBAF1065672 for ; Mon, 24 May 2010 09:49:38 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id C127E8FC1F for ; Mon, 24 May 2010 09:49:37 +0000 (UTC) Received: by gyh20 with SMTP id 20so1853694gyh.13 for ; Mon, 24 May 2010 02:49:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ZPs3lpKo53GRjZBVxSsRExiyos0rUvpv17SBMaR/wbU=; b=cLBxvO+24/6/IXYf1HQy1kKUYrOxjLxTu5U4O1FM9kZsDYI6b9WSuMPeUZlZWI7ISu ZfdQVju153OYAgVPrO7MNYcARcwU4k1h0QC0C4S6q+dlmj3waRpl9pM5o0GWgpELsJvs CZGR/k+kGTCfrHWAzxE/7Y0EfUJpvvoekgFNU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=pTJTLUsqgW7zyRKCrQmnxXLbPyyQqe6PXu8mBgNAoXZmL1rO/cQd59pmgogg7tReZg Y7kolCQ0DpGj6VaTRLV+2S8/yUEyiAUT0UIvyT3rj1R6+BFOCQbV9QSRyksNtPfYLsyD Jq32/34rdaGYpSu4ITR2zj58m0aVP0vGm+MJU= MIME-Version: 1.0 Received: by 10.101.10.34 with SMTP id n34mr5679589ani.109.1274694576748; Mon, 24 May 2010 02:49:36 -0700 (PDT) Received: by 10.100.208.9 with HTTP; Mon, 24 May 2010 02:49:36 -0700 (PDT) In-Reply-To: <20100524.134955.2300883222251175323.okuno.kohji@jp.panasonic.com> References: <20100524.134955.2300883222251175323.okuno.kohji@jp.panasonic.com> Date: Mon, 24 May 2010 13:49:36 +0400 Message-ID: From: pluknet To: Kohji Okuno Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: About 32bit binary on 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: Mon, 24 May 2010 09:49:38 -0000 On 24 May 2010 08:49, Kohji Okuno wrote: > Hi all, > > I want to compile 32bit binary on amd64, but I met with the problem. > Could you teach me the best solution, please? > > > My environment is FreeBSD 8.1-PRERELEASE #0: Tue May 18 12:01:26 JST 2010. > > I compiled and executed test.c as below on amd64. > [...] > > % gcc -m32 -B/usr/lib32 test.c > % ./a.out > mmap: Invalid argument AFAIK, it still doesn't work on FreeBSD. You need something like 32bit chroot environment. There's also about: http://www.freebsd.org/projects/ideas/#p-freebsd-amd64-gcc-m32 -- wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Mon May 24 09:59:10 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E23F106564A for ; Mon, 24 May 2010 09:59:10 +0000 (UTC) (envelope-from okuno.kohji@jp.panasonic.com) Received: from smtp.mei.co.jp (smtp.mei.co.jp [133.183.100.20]) by mx1.freebsd.org (Postfix) with ESMTP id EF81F8FC15 for ; Mon, 24 May 2010 09:59:09 +0000 (UTC) Received: from mail-gw.jp.panasonic.com ([157.8.1.145]) by smtp.mei.co.jp (8.12.11.20060614/3.7W/kc-maile14) with ESMTP id o4O9x8Bc019462; Mon, 24 May 2010 18:59:08 +0900 (JST) Received: from epochmail.jp.panasonic.com (localhost [127.0.0.1]) by mail.jp.panasonic.com (8.11.6p2/3.7W/kc-maili01) with ESMTP id o4O9x6o10708; Mon, 24 May 2010 18:59:06 +0900 (JST) Received: by epochmail.jp.panasonic.com (8.12.11.20060308/3.7W/somla2) id o4O9x8IR006093; Mon, 24 May 2010 18:59:08 +0900 (JST) Received: from localhost by somla2.jp.panasonic.com (8.12.11.20060308/3.7W) with ESMTP id o4O9wvl4005717; Mon, 24 May 2010 18:58:57 +0900 (JST) Date: Mon, 24 May 2010 18:58:56 +0900 (JST) Message-Id: <20100524.185856.2300883222251249895.okuno.kohji@jp.panasonic.com> To: yaneurabeya@gmail.com From: Kohji Okuno In-Reply-To: <3A68039C-BECD-47C0-89EE-45E3FB7C8D90@gmail.com> References: <20100524.134955.2300883222251175323.okuno.kohji@jp.panasonic.com> <3A68039C-BECD-47C0-89EE-45E3FB7C8D90@gmail.com> Organization: Panasonic Corporation X-Mailer: Mew version 6.3 on Emacs 23.2 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Mon_May_24_18_58_56_2010_883)--" Content-Transfer-Encoding: 7bit Cc: pluknet@gmail.com, okuno.kohji@jp.panasonic.com, freebsd-current@freebsd.org Subject: Re: About 32bit binary on 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: Mon, 24 May 2010 09:59:10 -0000 ----Next_Part(Mon_May_24_18_58_56_2010_883)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Thank you for your comments. In my usage, it works good by the patch appended to this mail. > On May 24, 2010, at 2:49 AM, pluknet wrote: > >> On 24 May 2010 08:49, Kohji Okuno wrote: >>> Hi all, >>> >>> I want to compile 32bit binary on amd64, but I met with the problem. >>> Could you teach me the best solution, please? >>> >>> >>> My environment is FreeBSD 8.1-PRERELEASE #0: Tue May 18 12:01:26 JST 2010. >>> >>> I compiled and executed test.c as below on amd64. >>> >> [...] >>> >>> % gcc -m32 -B/usr/lib32 test.c >>> % ./a.out >>> mmap: Invalid argument >> >> AFAIK, it still doesn't work on FreeBSD. You need something like 32bit >> chroot environment. >> There's also about: >> http://www.freebsd.org/projects/ideas/#p-freebsd-amd64-gcc-m32 > > -m32 is busted on FreeBSD; I don't remember the full details but I think it had something to do with the linking stage of things... > Thanks, > -Garrett ----Next_Part(Mon_May_24_18_58_56_2010_883)-- Content-Type: Text/X-Patch; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="machine_amd64.patch" diff -Nur machine.org/_inttypes.h machine/_inttypes.h --- machine.org/_inttypes.h 2009-08-03 17:13:06.000000000 +0900 +++ machine/_inttypes.h 2010-05-24 10:16:12.130753024 +0900 @@ -37,6 +37,9 @@ * $FreeBSD: src/sys/amd64/include/_inttypes.h,v 1.3.34.1 2009/08/03 08:13:06 kensmith Exp $ */ +#ifdef __i386__ +#include +#else #ifndef _MACHINE_INTTYPES_H_ #define _MACHINE_INTTYPES_H_ @@ -218,3 +221,4 @@ #define SCNxPTR "lx" /* uintptr_t */ #endif /* !_MACHINE_INTTYPES_H_ */ +#endif /* __i386__ */ diff -Nur machine.org/_inttypes32.h machine/_inttypes32.h --- machine.org/_inttypes32.h 1970-01-01 09:00:00.000000000 +0900 +++ machine/_inttypes32.h 2010-05-24 10:17:17.382704652 +0900 @@ -0,0 +1,220 @@ +/*- + * Copyright (c) 2001 The NetBSD Foundation, Inc. + * All rights reserved. + * + * This code is derived from software contributed to The NetBSD Foundation + * by Klaus Klein. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. All advertising materials mentioning features or use of this software + * must display the following acknowledgement: + * This product includes software developed by the NetBSD + * Foundation, Inc. and its contributors. + * 4. Neither the name of The NetBSD Foundation nor the names of its + * contributors may be used to endorse or promote products derived + * from this software without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS + * ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED + * TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR + * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS + * BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR + * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF + * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS + * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN + * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) + * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE + * POSSIBILITY OF SUCH DAMAGE. + * + * From: $NetBSD: int_fmtio.h,v 1.2 2001/04/26 16:25:21 kleink Exp $ + * $FreeBSD: src/sys/i386/include/_inttypes.h,v 1.2.36.1 2009/08/03 08:13:06 kensmith Exp $ + */ + +#ifndef _MACHINE_INTTYPES_H_ +#define _MACHINE_INTTYPES_H_ + +/* + * Macros for format specifiers. + */ + +/* fprintf(3) macros for signed integers. */ + +#define PRId8 "d" /* int8_t */ +#define PRId16 "d" /* int16_t */ +#define PRId32 "d" /* int32_t */ +#define PRId64 "lld" /* int64_t */ +#define PRIdLEAST8 "d" /* int_least8_t */ +#define PRIdLEAST16 "d" /* int_least16_t */ +#define PRIdLEAST32 "d" /* int_least32_t */ +#define PRIdLEAST64 "lld" /* int_least64_t */ +#define PRIdFAST8 "d" /* int_fast8_t */ +#define PRIdFAST16 "d" /* int_fast16_t */ +#define PRIdFAST32 "d" /* int_fast32_t */ +#define PRIdFAST64 "lld" /* int_fast64_t */ +#define PRIdMAX "jd" /* intmax_t */ +#define PRIdPTR "d" /* intptr_t */ + +#define PRIi8 "i" /* int8_t */ +#define PRIi16 "i" /* int16_t */ +#define PRIi32 "i" /* int32_t */ +#define PRIi64 "lli" /* int64_t */ +#define PRIiLEAST8 "i" /* int_least8_t */ +#define PRIiLEAST16 "i" /* int_least16_t */ +#define PRIiLEAST32 "i" /* int_least32_t */ +#define PRIiLEAST64 "lli" /* int_least64_t */ +#define PRIiFAST8 "i" /* int_fast8_t */ +#define PRIiFAST16 "i" /* int_fast16_t */ +#define PRIiFAST32 "i" /* int_fast32_t */ +#define PRIiFAST64 "lli" /* int_fast64_t */ +#define PRIiMAX "ji" /* intmax_t */ +#define PRIiPTR "i" /* intptr_t */ + +/* fprintf(3) macros for unsigned integers. */ + +#define PRIo8 "o" /* uint8_t */ +#define PRIo16 "o" /* uint16_t */ +#define PRIo32 "o" /* uint32_t */ +#define PRIo64 "llo" /* uint64_t */ +#define PRIoLEAST8 "o" /* uint_least8_t */ +#define PRIoLEAST16 "o" /* uint_least16_t */ +#define PRIoLEAST32 "o" /* uint_least32_t */ +#define PRIoLEAST64 "llo" /* uint_least64_t */ +#define PRIoFAST8 "o" /* uint_fast8_t */ +#define PRIoFAST16 "o" /* uint_fast16_t */ +#define PRIoFAST32 "o" /* uint_fast32_t */ +#define PRIoFAST64 "llo" /* uint_fast64_t */ +#define PRIoMAX "jo" /* uintmax_t */ +#define PRIoPTR "o" /* uintptr_t */ + +#define PRIu8 "u" /* uint8_t */ +#define PRIu16 "u" /* uint16_t */ +#define PRIu32 "u" /* uint32_t */ +#define PRIu64 "llu" /* uint64_t */ +#define PRIuLEAST8 "u" /* uint_least8_t */ +#define PRIuLEAST16 "u" /* uint_least16_t */ +#define PRIuLEAST32 "u" /* uint_least32_t */ +#define PRIuLEAST64 "llu" /* uint_least64_t */ +#define PRIuFAST8 "u" /* uint_fast8_t */ +#define PRIuFAST16 "u" /* uint_fast16_t */ +#define PRIuFAST32 "u" /* uint_fast32_t */ +#define PRIuFAST64 "llu" /* uint_fast64_t */ +#define PRIuMAX "ju" /* uintmax_t */ +#define PRIuPTR "u" /* uintptr_t */ + +#define PRIx8 "x" /* uint8_t */ +#define PRIx16 "x" /* uint16_t */ +#define PRIx32 "x" /* uint32_t */ +#define PRIx64 "llx" /* uint64_t */ +#define PRIxLEAST8 "x" /* uint_least8_t */ +#define PRIxLEAST16 "x" /* uint_least16_t */ +#define PRIxLEAST32 "x" /* uint_least32_t */ +#define PRIxLEAST64 "llx" /* uint_least64_t */ +#define PRIxFAST8 "x" /* uint_fast8_t */ +#define PRIxFAST16 "x" /* uint_fast16_t */ +#define PRIxFAST32 "x" /* uint_fast32_t */ +#define PRIxFAST64 "llx" /* uint_fast64_t */ +#define PRIxMAX "jx" /* uintmax_t */ +#define PRIxPTR "x" /* uintptr_t */ + +#define PRIX8 "X" /* uint8_t */ +#define PRIX16 "X" /* uint16_t */ +#define PRIX32 "X" /* uint32_t */ +#define PRIX64 "llX" /* uint64_t */ +#define PRIXLEAST8 "X" /* uint_least8_t */ +#define PRIXLEAST16 "X" /* uint_least16_t */ +#define PRIXLEAST32 "X" /* uint_least32_t */ +#define PRIXLEAST64 "llX" /* uint_least64_t */ +#define PRIXFAST8 "X" /* uint_fast8_t */ +#define PRIXFAST16 "X" /* uint_fast16_t */ +#define PRIXFAST32 "X" /* uint_fast32_t */ +#define PRIXFAST64 "llX" /* uint_fast64_t */ +#define PRIXMAX "jX" /* uintmax_t */ +#define PRIXPTR "X" /* uintptr_t */ + +/* fscanf(3) macros for signed integers. */ + +#define SCNd8 "hhd" /* int8_t */ +#define SCNd16 "hd" /* int16_t */ +#define SCNd32 "d" /* int32_t */ +#define SCNd64 "lld" /* int64_t */ +#define SCNdLEAST8 "hhd" /* int_least8_t */ +#define SCNdLEAST16 "hd" /* int_least16_t */ +#define SCNdLEAST32 "d" /* int_least32_t */ +#define SCNdLEAST64 "lld" /* int_least64_t */ +#define SCNdFAST8 "d" /* int_fast8_t */ +#define SCNdFAST16 "d" /* int_fast16_t */ +#define SCNdFAST32 "d" /* int_fast32_t */ +#define SCNdFAST64 "lld" /* int_fast64_t */ +#define SCNdMAX "jd" /* intmax_t */ +#define SCNdPTR "d" /* intptr_t */ + +#define SCNi8 "hhi" /* int8_t */ +#define SCNi16 "hi" /* int16_t */ +#define SCNi32 "i" /* int32_t */ +#define SCNi64 "lli" /* int64_t */ +#define SCNiLEAST8 "hhi" /* int_least8_t */ +#define SCNiLEAST16 "hi" /* int_least16_t */ +#define SCNiLEAST32 "i" /* int_least32_t */ +#define SCNiLEAST64 "lli" /* int_least64_t */ +#define SCNiFAST8 "i" /* int_fast8_t */ +#define SCNiFAST16 "i" /* int_fast16_t */ +#define SCNiFAST32 "i" /* int_fast32_t */ +#define SCNiFAST64 "lli" /* int_fast64_t */ +#define SCNiMAX "ji" /* intmax_t */ +#define SCNiPTR "i" /* intptr_t */ + +/* fscanf(3) macros for unsigned integers. */ + +#define SCNo8 "hho" /* uint8_t */ +#define SCNo16 "ho" /* uint16_t */ +#define SCNo32 "o" /* uint32_t */ +#define SCNo64 "llo" /* uint64_t */ +#define SCNoLEAST8 "hho" /* uint_least8_t */ +#define SCNoLEAST16 "ho" /* uint_least16_t */ +#define SCNoLEAST32 "o" /* uint_least32_t */ +#define SCNoLEAST64 "llo" /* uint_least64_t */ +#define SCNoFAST8 "o" /* uint_fast8_t */ +#define SCNoFAST16 "o" /* uint_fast16_t */ +#define SCNoFAST32 "o" /* uint_fast32_t */ +#define SCNoFAST64 "llo" /* uint_fast64_t */ +#define SCNoMAX "jo" /* uintmax_t */ +#define SCNoPTR "o" /* uintptr_t */ + +#define SCNu8 "hhu" /* uint8_t */ +#define SCNu16 "hu" /* uint16_t */ +#define SCNu32 "u" /* uint32_t */ +#define SCNu64 "llu" /* uint64_t */ +#define SCNuLEAST8 "hhu" /* uint_least8_t */ +#define SCNuLEAST16 "hu" /* uint_least16_t */ +#define SCNuLEAST32 "u" /* uint_least32_t */ +#define SCNuLEAST64 "llu" /* uint_least64_t */ +#define SCNuFAST8 "u" /* uint_fast8_t */ +#define SCNuFAST16 "u" /* uint_fast16_t */ +#define SCNuFAST32 "u" /* uint_fast32_t */ +#define SCNuFAST64 "llu" /* uint_fast64_t */ +#define SCNuMAX "ju" /* uintmax_t */ +#define SCNuPTR "u" /* uintptr_t */ + +#define SCNx8 "hhx" /* uint8_t */ +#define SCNx16 "hx" /* uint16_t */ +#define SCNx32 "x" /* uint32_t */ +#define SCNx64 "llx" /* uint64_t */ +#define SCNxLEAST8 "hhx" /* uint_least8_t */ +#define SCNxLEAST16 "hx" /* uint_least16_t */ +#define SCNxLEAST32 "x" /* uint_least32_t */ +#define SCNxLEAST64 "llx" /* uint_least64_t */ +#define SCNxFAST8 "x" /* uint_fast8_t */ +#define SCNxFAST16 "x" /* uint_fast16_t */ +#define SCNxFAST32 "x" /* uint_fast32_t */ +#define SCNxFAST64 "llx" /* uint_fast64_t */ +#define SCNxMAX "jx" /* uintmax_t */ +#define SCNxPTR "x" /* uintptr_t */ + +#endif /* !_MACHINE_INTTYPES_H_ */ diff -Nur machine.org/_limits.h machine/_limits.h --- machine.org/_limits.h 2009-08-03 17:13:06.000000000 +0900 +++ machine/_limits.h 2010-05-24 10:16:45.623585129 +0900 @@ -30,6 +30,9 @@ * $FreeBSD: src/sys/amd64/include/_limits.h,v 1.11.10.1 2009/08/03 08:13:06 kensmith Exp $ */ +#ifdef __i386__ +#include +#else #ifndef _MACHINE__LIMITS_H_ #define _MACHINE__LIMITS_H_ @@ -90,3 +93,4 @@ #define __MINSIGSTKSZ (512 * 4) #endif /* !_MACHINE__LIMITS_H_ */ +#endif diff -Nur machine.org/_limits32.h machine/_limits32.h --- machine.org/_limits32.h 1970-01-01 09:00:00.000000000 +0900 +++ machine/_limits32.h 2010-05-24 10:17:25.631931374 +0900 @@ -0,0 +1,103 @@ +/*- + * Copyright (c) 1988, 1993 + * The Regents of the University of California. All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 4. Neither the name of the University nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + * @(#)limits.h 8.3 (Berkeley) 1/4/94 + * $FreeBSD: src/sys/i386/include/_limits.h,v 1.28.10.1 2009/08/03 08:13:06 kensmith Exp $ + */ + +#ifndef _MACHINE__LIMITS_H_ +#define _MACHINE__LIMITS_H_ + +/* + * According to ANSI (section 2.2.4.2), the values below must be usable by + * #if preprocessing directives. Additionally, the expression must have the + * same type as would an expression that is an object of the corresponding + * type converted according to the integral promotions. The subtraction for + * INT_MIN, etc., is so the value is not unsigned; e.g., 0x80000000 is an + * unsigned int for 32-bit two's complement ANSI compilers (section 3.1.3.2). + * These numbers are for the default configuration of gcc. They work for + * some other compilers as well, but this should not be depended on. + */ + +#define __CHAR_BIT 8 /* number of bits in a char */ + +#define __SCHAR_MAX 0x7f /* max value for a signed char */ +#define __SCHAR_MIN (-0x7f - 1) /* min value for a signed char */ + +#define __UCHAR_MAX 0xff /* max value for an unsigned char */ + +#define __USHRT_MAX 0xffff /* max value for an unsigned short */ +#define __SHRT_MAX 0x7fff /* max value for a short */ +#define __SHRT_MIN (-0x7fff - 1) /* min value for a short */ + +#define __UINT_MAX 0xffffffffU /* max value for an unsigned int */ +#define __INT_MAX 0x7fffffff /* max value for an int */ +#define __INT_MIN (-0x7fffffff - 1) /* min value for an int */ + +/* Bad hack for gcc configured to give 64-bit longs. */ +#ifdef _LARGE_LONG +#define __ULONG_MAX 0xffffffffffffffffUL +#define __LONG_MAX 0x7fffffffffffffffL +#define __LONG_MIN (-0x7fffffffffffffffL - 1) +#else +#define __ULONG_MAX 0xffffffffUL /* max value for an unsigned long */ +#define __LONG_MAX 0x7fffffffL /* max value for a long */ +#define __LONG_MIN (-0x7fffffffL - 1) /* min value for a long */ +#endif + + /* max value for an unsigned long long */ +#define __ULLONG_MAX 0xffffffffffffffffULL +#define __LLONG_MAX 0x7fffffffffffffffLL /* max value for a long long */ +#define __LLONG_MIN (-0x7fffffffffffffffLL - 1) /* min for a long long */ + +#define __SSIZE_MAX __INT_MAX /* max value for a ssize_t */ + +#define __SIZE_T_MAX __UINT_MAX /* max value for a size_t */ + +#define __OFF_MAX __LLONG_MAX /* max value for an off_t */ +#define __OFF_MIN __LLONG_MIN /* min value for an off_t */ + +/* Quads and long longs are the same size. Ensure they stay in sync. */ +#define __UQUAD_MAX __ULLONG_MAX /* max value for a uquad_t */ +#define __QUAD_MAX __LLONG_MAX /* max value for a quad_t */ +#define __QUAD_MIN __LLONG_MIN /* min value for a quad_t */ + +#ifdef _LARGE_LONG +#define __LONG_BIT 64 +#else +#define __LONG_BIT 32 +#endif +#define __WORD_BIT 32 + +/* + * Minimum signal stack size. The current signal frame + * for i386 is 408 bytes large. + */ +#define __MINSIGSTKSZ (512 * 4) + +#endif /* !_MACHINE__LIMITS_H_ */ diff -Nur machine.org/_stdint.h machine/_stdint.h --- machine.org/_stdint.h 2009-08-03 17:13:06.000000000 +0900 +++ machine/_stdint.h 2010-05-24 10:18:36.849061766 +0900 @@ -37,6 +37,9 @@ * $FreeBSD: src/sys/amd64/include/_stdint.h,v 1.3.30.1 2009/08/03 08:13:06 kensmith Exp $ */ +#ifdef __i386__ +#include +#else #ifndef _MACHINE__STDINT_H_ #define _MACHINE__STDINT_H_ @@ -169,3 +172,4 @@ #endif /* !defined(__cplusplus) || defined(__STDC_LIMIT_MACROS) */ #endif /* !_MACHINE__STDINT_H_ */ +#endif /* __i386__ */ diff -Nur machine.org/_stdint32.h machine/_stdint32.h --- machine.org/_stdint32.h 1970-01-01 09:00:00.000000000 +0900 +++ machine/_stdint32.h 2010-05-24 10:17:35.331631317 +0900 @@ -0,0 +1,171 @@ +/*- + * Copyright (c) 2001, 2002 Mike Barcroft + * Copyright (c) 2001 The NetBSD Foundation, Inc. + * All rights reserved. + * + * This code is derived from software contributed to The NetBSD Foundation + * by Klaus Klein. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. All advertising materials mentioning features or use of this software + * must display the following acknowledgement: + * This product includes software developed by the NetBSD + * Foundation, Inc. and its contributors. + * 4. Neither the name of The NetBSD Foundation nor the names of its + * contributors may be used to endorse or promote products derived + * from this software without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE NETBSD FOUNDATION, INC. AND CONTRIBUTORS + * ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED + * TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR + * PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE FOUNDATION OR CONTRIBUTORS + * BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR + * CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF + * SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS + * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN + * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) + * ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE + * POSSIBILITY OF SUCH DAMAGE. + * + * $FreeBSD: src/sys/i386/include/_stdint.h,v 1.2.30.1 2009/08/03 08:13:06 kensmith Exp $ + */ + +#ifndef _MACHINE__STDINT_H_ +#define _MACHINE__STDINT_H_ + +#if !defined(__cplusplus) || defined(__STDC_CONSTANT_MACROS) + +#define INT8_C(c) (c) +#define INT16_C(c) (c) +#define INT32_C(c) (c) +#define INT64_C(c) (c ## LL) + +#define UINT8_C(c) (c) +#define UINT16_C(c) (c) +#define UINT32_C(c) (c ## U) +#define UINT64_C(c) (c ## ULL) + +#define INTMAX_C(c) (c ## LL) +#define UINTMAX_C(c) (c ## ULL) + +#endif /* !defined(__cplusplus) || defined(__STDC_CONSTANT_MACROS) */ + +#if !defined(__cplusplus) || defined(__STDC_LIMIT_MACROS) + +/* + * ISO/IEC 9899:1999 + * 7.18.2.1 Limits of exact-width integer types + */ +/* Minimum values of exact-width signed integer types. */ +#define INT8_MIN (-0x7f-1) +#define INT16_MIN (-0x7fff-1) +#define INT32_MIN (-0x7fffffff-1) +#define INT64_MIN (-0x7fffffffffffffffLL-1) + +/* Maximum values of exact-width signed integer types. */ +#define INT8_MAX 0x7f +#define INT16_MAX 0x7fff +#define INT32_MAX 0x7fffffff +#define INT64_MAX 0x7fffffffffffffffLL + +/* Maximum values of exact-width unsigned integer types. */ +#define UINT8_MAX 0xff +#define UINT16_MAX 0xffff +#define UINT32_MAX 0xffffffffU +#define UINT64_MAX 0xffffffffffffffffULL + +/* + * ISO/IEC 9899:1999 + * 7.18.2.2 Limits of minimum-width integer types + */ +/* Minimum values of minimum-width signed integer types. */ +#define INT_LEAST8_MIN INT8_MIN +#define INT_LEAST16_MIN INT16_MIN +#define INT_LEAST32_MIN INT32_MIN +#define INT_LEAST64_MIN INT64_MIN + +/* Maximum values of minimum-width signed integer types. */ +#define INT_LEAST8_MAX INT8_MAX +#define INT_LEAST16_MAX INT16_MAX +#define INT_LEAST32_MAX INT32_MAX +#define INT_LEAST64_MAX INT64_MAX + +/* Maximum values of minimum-width unsigned integer types. */ +#define UINT_LEAST8_MAX UINT8_MAX +#define UINT_LEAST16_MAX UINT16_MAX +#define UINT_LEAST32_MAX UINT32_MAX +#define UINT_LEAST64_MAX UINT64_MAX + +/* + * ISO/IEC 9899:1999 + * 7.18.2.3 Limits of fastest minimum-width integer types + */ +/* Minimum values of fastest minimum-width signed integer types. */ +#define INT_FAST8_MIN INT32_MIN +#define INT_FAST16_MIN INT32_MIN +#define INT_FAST32_MIN INT32_MIN +#define INT_FAST64_MIN INT64_MIN + +/* Maximum values of fastest minimum-width signed integer types. */ +#define INT_FAST8_MAX INT32_MAX +#define INT_FAST16_MAX INT32_MAX +#define INT_FAST32_MAX INT32_MAX +#define INT_FAST64_MAX INT64_MAX + +/* Maximum values of fastest minimum-width unsigned integer types. */ +#define UINT_FAST8_MAX UINT32_MAX +#define UINT_FAST16_MAX UINT32_MAX +#define UINT_FAST32_MAX UINT32_MAX +#define UINT_FAST64_MAX UINT64_MAX + +/* + * ISO/IEC 9899:1999 + * 7.18.2.4 Limits of integer types capable of holding object pointers + */ +#define INTPTR_MIN INT32_MIN +#define INTPTR_MAX INT32_MAX +#define UINTPTR_MAX UINT32_MAX + +/* + * ISO/IEC 9899:1999 + * 7.18.2.5 Limits of greatest-width integer types + */ +#define INTMAX_MIN INT64_MIN +#define INTMAX_MAX INT64_MAX +#define UINTMAX_MAX UINT64_MAX + +/* + * ISO/IEC 9899:1999 + * 7.18.3 Limits of other integer types + */ +/* Limits of ptrdiff_t. */ +#define PTRDIFF_MIN INT32_MIN +#define PTRDIFF_MAX INT32_MAX + +/* Limits of sig_atomic_t. */ +#define SIG_ATOMIC_MIN INT32_MIN +#define SIG_ATOMIC_MAX INT32_MAX + +/* Limit of size_t. */ +#define SIZE_MAX UINT32_MAX + +#ifndef WCHAR_MIN /* Also possibly defined in */ +/* Limits of wchar_t. */ +#define WCHAR_MIN INT32_MIN +#define WCHAR_MAX INT32_MAX +#endif + +/* Limits of wint_t. */ +#define WINT_MIN INT32_MIN +#define WINT_MAX INT32_MAX + +#endif /* !defined(__cplusplus) || defined(__STDC_LIMIT_MACROS) */ + +#endif /* !_MACHINE__STDINT_H_ */ diff -Nur machine.org/_types.h machine/_types.h --- machine.org/_types.h 2009-08-03 17:13:06.000000000 +0900 +++ machine/_types.h 2010-05-24 10:11:23.812330967 +0900 @@ -36,6 +36,9 @@ * $FreeBSD: src/sys/amd64/include/_types.h,v 1.12.2.1 2009/08/03 08:13:06 kensmith Exp $ */ +#ifdef __i386__ +#include +#else #ifndef _MACHINE__TYPES_H_ #define _MACHINE__TYPES_H_ @@ -115,3 +118,4 @@ #endif #endif /* !_MACHINE__TYPES_H_ */ +#endif /* __i386__*/ diff -Nur machine.org/_types32.h machine/_types32.h --- machine.org/_types32.h 1970-01-01 09:00:00.000000000 +0900 +++ machine/_types32.h 2010-05-24 10:10:21.118585714 +0900 @@ -0,0 +1,134 @@ +/*- + * Copyright (c) 2002 Mike Barcroft + * Copyright (c) 1990, 1993 + * The Regents of the University of California. All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. All advertising materials mentioning features or use of this software + * must display the following acknowledgement: + * This product includes software developed by the University of + * California, Berkeley and its contributors. + * 4. Neither the name of the University nor the names of its contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + * From: @(#)ansi.h 8.2 (Berkeley) 1/4/94 + * From: @(#)types.h 8.3 (Berkeley) 1/5/94 + * $FreeBSD: src/sys/i386/include/_types.h,v 1.15.2.1 2009/08/03 08:13:06 kensmith Exp $ + */ + +#ifndef _MACHINE__TYPES_H_ +#define _MACHINE__TYPES_H_ + +#ifndef _SYS_CDEFS_H_ +#error this file needs sys/cdefs.h as a prerequisite +#endif + +#define __NO_STRICT_ALIGNMENT + +/* + * Basic types upon which most other types are built. + */ +typedef __signed char __int8_t; +typedef unsigned char __uint8_t; +typedef short __int16_t; +typedef unsigned short __uint16_t; +typedef int __int32_t; +typedef unsigned int __uint32_t; + +#if defined(lint) +/* LONGLONG */ +typedef long long __int64_t; +/* LONGLONG */ +typedef unsigned long long __uint64_t; +#elif defined(__GNUCLIKE_ATTRIBUTE_MODE_DI) +typedef int __attribute__((__mode__(__DI__))) __int64_t; +typedef unsigned int __attribute__((__mode__(__DI__))) __uint64_t; +#else +/* LONGLONG */ +typedef long long __int64_t; +/* LONGLONG */ +typedef unsigned long long __uint64_t; +#endif + +/* + * Standard type definitions. + */ +typedef unsigned long __clock_t; /* clock()... */ +typedef unsigned int __cpumask_t; +typedef __int32_t __critical_t; +typedef long double __double_t; +typedef long double __float_t; +typedef __int32_t __intfptr_t; +typedef __int64_t __intmax_t; +typedef __int32_t __intptr_t; +typedef __int32_t __int_fast8_t; +typedef __int32_t __int_fast16_t; +typedef __int32_t __int_fast32_t; +typedef __int64_t __int_fast64_t; +typedef __int8_t __int_least8_t; +typedef __int16_t __int_least16_t; +typedef __int32_t __int_least32_t; +typedef __int64_t __int_least64_t; +typedef __int32_t __ptrdiff_t; /* ptr1 - ptr2 */ +typedef __int32_t __register_t; +typedef __int32_t __segsz_t; /* segment size (in pages) */ +typedef __uint32_t __size_t; /* sizeof() */ +typedef __int32_t __ssize_t; /* byte count or error */ +typedef __int32_t __time_t; /* time()... */ +typedef __uint32_t __uintfptr_t; +typedef __uint64_t __uintmax_t; +typedef __uint32_t __uintptr_t; +typedef __uint32_t __uint_fast8_t; +typedef __uint32_t __uint_fast16_t; +typedef __uint32_t __uint_fast32_t; +typedef __uint64_t __uint_fast64_t; +typedef __uint8_t __uint_least8_t; +typedef __uint16_t __uint_least16_t; +typedef __uint32_t __uint_least32_t; +typedef __uint64_t __uint_least64_t; +typedef __uint32_t __u_register_t; +typedef __uint32_t __vm_offset_t; +typedef __int64_t __vm_ooffset_t; +#ifdef PAE +typedef __uint64_t __vm_paddr_t; +#else +typedef __uint32_t __vm_paddr_t; +#endif +typedef __uint64_t __vm_pindex_t; +typedef __uint32_t __vm_size_t; + +/* + * Unusual type definitions. + */ +#ifdef __GNUCLIKE_BUILTIN_VARARGS +typedef __builtin_va_list __va_list; /* internally known to gcc */ +#else +typedef char * __va_list; +#endif /* __GNUCLIKE_BUILTIN_VARARGS */ +#if defined(__GNUC_VA_LIST_COMPATIBILITY) && !defined(__GNUC_VA_LIST) \ + && !defined(__NO_GNUC_VA_LIST) +#define __GNUC_VA_LIST +typedef __va_list __gnuc_va_list; /* compatibility w/GNU headers*/ +#endif + +#endif /* !_MACHINE__TYPES_H_ */ diff -Nur machine.org/setjmp.h machine/setjmp.h --- machine.org/setjmp.h 2009-08-03 17:13:06.000000000 +0900 +++ machine/setjmp.h 2010-05-24 10:10:49.662301925 +0900 @@ -29,6 +29,9 @@ * $FreeBSD: src/sys/amd64/include/setjmp.h,v 1.10.10.1 2009/08/03 08:13:06 kensmith Exp $ */ +#ifdef __i386__ +#include +#else #ifndef _MACHINE_SETJMP_H_ #define _MACHINE_SETJMP_H_ @@ -48,3 +51,4 @@ typedef struct _jmp_buf { long _jb[_JBLEN]; } jmp_buf[1]; #endif /* !_MACHINE_SETJMP_H_ */ +#endif /* __i386__ */ diff -Nur machine.org/setjmp32.h machine/setjmp32.h --- machine.org/setjmp32.h 1970-01-01 09:00:00.000000000 +0900 +++ machine/setjmp32.h 2010-05-24 10:11:42.720873864 +0900 @@ -0,0 +1,50 @@ +/*- + * Copyright (c) 1998 John Birrell . + * All rights reserved. + * + * Redistribution and use in source and binary forms, with or without + * modification, are permitted provided that the following conditions + * are met: + * 1. Redistributions of source code must retain the above copyright + * notice, this list of conditions and the following disclaimer. + * 2. Redistributions in binary form must reproduce the above copyright + * notice, this list of conditions and the following disclaimer in the + * documentation and/or other materials provided with the distribution. + * 3. Neither the name of the author nor the names of any co-contributors + * may be used to endorse or promote products derived from this software + * without specific prior written permission. + * + * THIS SOFTWARE IS PROVIDED BY JOHN BIRRELL AND CONTRIBUTORS ``AS IS'' AND + * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE + * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE + * ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE + * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL + * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS + * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) + * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT + * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY + * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF + * SUCH DAMAGE. + * + * $FreeBSD: src/sys/i386/include/setjmp.h,v 1.8.10.1 2009/08/03 08:13:06 kensmith Exp $ + */ + +#ifndef _MACHINE_SETJMP_H_ +#define _MACHINE_SETJMP_H_ + +#include + +#define _JBLEN 11 /* Size of the jmp_buf on x86. */ + +/* + * jmp_buf and sigjmp_buf are encapsulated in different structs to force + * compile-time diagnostics for mismatches. The structs are the same + * internally to avoid some run-time errors for mismatches. + */ +#if __BSD_VISIBLE || __POSIX_VISIBLE || __XSI_VISIBLE +typedef struct _sigjmp_buf { int _sjb[_JBLEN + 1]; } sigjmp_buf[1]; +#endif + +typedef struct _jmp_buf { int _jb[_JBLEN + 1]; } jmp_buf[1]; + +#endif /* !_MACHINE_SETJMP_H_ */ ----Next_Part(Mon_May_24_18_58_56_2010_883)---- From owner-freebsd-current@FreeBSD.ORG Mon May 24 10:36:25 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C12BD1065742 for ; Mon, 24 May 2010 10:36:25 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 60B318FC1B for ; Mon, 24 May 2010 10:36:24 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o4OAaYTA051665 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 May 2010 13:36:34 +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.14.4/8.14.4) with ESMTP id o4OAaLFW063787; Mon, 24 May 2010 13:36:21 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o4OAaLcx063786; Mon, 24 May 2010 13:36:21 +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: Mon, 24 May 2010 13:36:21 +0300 From: Kostik Belousov To: Kohji Okuno Message-ID: <20100524103621.GH83316@deviant.kiev.zoral.com.ua> References: <20100524.134955.2300883222251175323.okuno.kohji@jp.panasonic.com> <3A68039C-BECD-47C0-89EE-45E3FB7C8D90@gmail.com> <20100524.185856.2300883222251249895.okuno.kohji@jp.panasonic.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="K2ilJF7ocWQIPRKZ" Content-Disposition: inline In-Reply-To: <20100524.185856.2300883222251249895.okuno.kohji@jp.panasonic.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_20, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: pluknet@gmail.com, yaneurabeya@gmail.com, freebsd-current@freebsd.org Subject: Re: About 32bit binary on 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: Mon, 24 May 2010 10:36:25 -0000 --K2ilJF7ocWQIPRKZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, May 24, 2010 at 06:58:56PM +0900, Kohji Okuno wrote: > Thank you for your comments. >=20 > In my usage, it works good by the patch appended to this mail. The patch is probably a start in the right direction. But, it would be much better to install sys/i386/include to e.g. /usr/include/machine32 and use the pristine i386 files instead of copying them. Are you interested in going further with the approach ? Thanks. >=20 > > On May 24, 2010, at 2:49 AM, pluknet wrote: > >=20 > >> On 24 May 2010 08:49, Kohji Okuno wrote: > >>> Hi all, > >>>=20 > >>> I want to compile 32bit binary on amd64, but I met with the problem. > >>> Could you teach me the best solution, please? > >>>=20 > >>>=20 > >>> My environment is FreeBSD 8.1-PRERELEASE #0: Tue May 18 12:01:26 JST = 2010. > >>>=20 > >>> I compiled and executed test.c as below on amd64. > >>>=20 > >> [...] > >>>=20 > >>> % gcc -m32 -B/usr/lib32 test.c > >>> % ./a.out > >>> mmap: Invalid argument > >>=20 > >> AFAIK, it still doesn't work on FreeBSD. You need something like 32bit > >> chroot environment. > >> There's also about: > >> http://www.freebsd.org/projects/ideas/#p-freebsd-amd64-gcc-m32 > >=20 > > -m32 is busted on FreeBSD; I don't remember the full details but I thin= k it had something to do with the linking stage of things... > > Thanks, > > -Garrett > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" --K2ilJF7ocWQIPRKZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkv6VqQACgkQC3+MBN1Mb4i+CwCgkyBodZh0lO0ek4cf4YDQsJwF IoYAoJHBxpqjuBRbSnn7PgMhBd+cdgjy =t8UG -----END PGP SIGNATURE----- --K2ilJF7ocWQIPRKZ-- From owner-freebsd-current@FreeBSD.ORG Mon May 24 10:15:09 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EB53A1065762 for ; Mon, 24 May 2010 10:15:09 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pz0-f175.google.com (mail-pz0-f175.google.com [209.85.222.175]) by mx1.freebsd.org (Postfix) with ESMTP id BB6048FC0C for ; Mon, 24 May 2010 10:15:09 +0000 (UTC) Received: by pzk5 with SMTP id 5so1548629pzk.14 for ; Mon, 24 May 2010 03:15:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=kLWN/O5/1+nFa7CZkdxMU0q7nYUgZST4+DxENa5Cxbw=; b=Gt/aaY9rU9m8S8nzF5whPX62FBy1ZRLzt3VOZLVX8EnyCtRN65Xk3LNI73ntQ1rXVt KUDIXysZiOA/m1AUKS19VwJ4mexVKeQtEHRHjB5eE5gDySgwxC33/LohiPAIV3of03zr PyeXr43cVE21USVEY5mjQ3ZlvGpQwaT345VfE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=m0iZfFCAxEV8PeA1C9kMq1oKzSG3GTt3868jHkx2fGW6lrT8OSBnXE/EnMfgBlnjDG Oy3zrB1zXKVSlQ1mZ3pgSaRh1nIzdL8cDJCVvI44JG4PHOXF1fmG0OzeGN2OiCexrlON j6o1BnNZsX3/Kbz9mzdZDkcDjGHcXyu0HMZKM= Received: by 10.115.117.38 with SMTP id u38mr4639651wam.168.1274694686755; Mon, 24 May 2010 02:51:26 -0700 (PDT) Received: from [192.168.0.204] (deviant.freebsdgirl.com [173.8.183.73]) by mx.google.com with ESMTPS id c22sm37041181wam.18.2010.05.24.02.51.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 24 May 2010 02:51:25 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Garrett Cooper In-Reply-To: Date: Mon, 24 May 2010 02:51:23 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <3A68039C-BECD-47C0-89EE-45E3FB7C8D90@gmail.com> References: <20100524.134955.2300883222251175323.okuno.kohji@jp.panasonic.com> To: pluknet X-Mailer: Apple Mail (2.1078) X-Mailman-Approved-At: Mon, 24 May 2010 11:14:22 +0000 Cc: freebsd-current@freebsd.org, Kohji Okuno Subject: Re: About 32bit binary on 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: Mon, 24 May 2010 10:15:10 -0000 On May 24, 2010, at 2:49 AM, pluknet wrote: > On 24 May 2010 08:49, Kohji Okuno = wrote: >> Hi all, >>=20 >> I want to compile 32bit binary on amd64, but I met with the problem. >> Could you teach me the best solution, please? >>=20 >>=20 >> My environment is FreeBSD 8.1-PRERELEASE #0: Tue May 18 12:01:26 JST = 2010. >>=20 >> I compiled and executed test.c as below on amd64. >>=20 > [...] >>=20 >> % gcc -m32 -B/usr/lib32 test.c >> % ./a.out >> mmap: Invalid argument >=20 > AFAIK, it still doesn't work on FreeBSD. You need something like 32bit > chroot environment. > There's also about: > http://www.freebsd.org/projects/ideas/#p-freebsd-amd64-gcc-m32 -m32 is busted on FreeBSD; I don't remember the full details but I think = it had something to do with the linking stage of things... Thanks, -Garrett= From owner-freebsd-current@FreeBSD.ORG Mon May 24 11:24:19 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 03ADC1065675 for ; Mon, 24 May 2010 11:24:19 +0000 (UTC) (envelope-from bogorodskiy@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 7FCF38FC15 for ; Mon, 24 May 2010 11:24:18 +0000 (UTC) Received: by fxm4 with SMTP id 4so3140842fxm.13 for ; Mon, 24 May 2010 04:24:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:references:mime-version:content-type:content-disposition :in-reply-to:user-agent; bh=fWPZ+IcRBWlbRF47dBIuMnLffQL0zQgGDZ+iEYWRCjc=; b=gkD2eM2EX8xTHnUHRjmXKeG4CZJd5FyyZXCtBNvGdbEQBohKL9Swq7j0Zf+hiPzeSw j62JCZBfUgzPZy8YII5ErlN6nSkpnzXtPgYVrwk+l7ioDIRSHRTVIVelPkO3/erbHTih uo/sy/sFkR7khmpF8LqLehUPqJIhJwYApkWc0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=oLjgZVb+Un012zLPFHAKg8chz3Lvgsl1zl0b/JQr+ldkyDDTBKN11k3XJ/HSafwx3p zRKIUmiUTpK3sRx/Jsp85dHd5hzg4BfSiKF4vDFjXlzfj5UF1DSjh/iOnhzyVPjmnfRd sDJeVgudFpO6rtsap+YuSmomXy2WZLb957NQM= Received: by 10.103.81.29 with SMTP id i29mr4219264mul.109.1274700257295; Mon, 24 May 2010 04:24:17 -0700 (PDT) Received: from rbogorodskiy ([91.207.133.2]) by mx.google.com with ESMTPS id j6sm14759338mue.44.2010.05.24.04.24.15 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 24 May 2010 04:24:16 -0700 (PDT) Date: Mon, 24 May 2010 15:21:41 +0400 From: Roman Bogorodskiy To: Jeff Roberson Message-ID: <20100524112140.GB18511@rbogorodskiy> References: <20100518185201.GA2745@fsol> <20100523032720.GA89739@dirtyvegas> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VV4b6MQE+OnNyhkM" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: current@freebsd.org Subject: Re: ffs_copyonwrite panics 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, 24 May 2010 11:24:19 -0000 --VV4b6MQE+OnNyhkM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Jeff Roberson wrote: > >Tried today's -CURRENT and unfortunately the behaviour is still same. >=20 > Can you give me a full stack trace? Do you have coredumps enabled? > I would like to have you look at a few things in a core or send it > to me with your kernel. I am not sure how to save coredump as when the system boots after the crash and starts saving coredump from swap partition to disk the system crashes again. Generally, the system is almost unusable and in order to try a new kernel I cross-compile it on my i386 laptop and copy in using livefs cdrom. Do you have an idea how to save a trace? Thanks, Roman Bogorodskiy --VV4b6MQE+OnNyhkM Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iJwEAQECAAYFAkv6YUQACgkQgHRbOB2qykbvjgP/XiQ+40VDGq55HL4VaQk62kln B7yMgkYelccZzNffwbtwYEYdi9Z2gtMOkMRmdNnypE6dNwNMxcIQyfMGMlLi+c5/ PdImIXaOCS5dc2gT9kVXIVrgqDLfL0JbN/I+3nU4PoHvY1n5Xp1urB19xWxDgFBO ZZcHI/4tJQrNGOa+gaM= =+WbG -----END PGP SIGNATURE----- --VV4b6MQE+OnNyhkM-- From owner-freebsd-current@FreeBSD.ORG Mon May 24 21:09:32 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5729106567A for ; Mon, 24 May 2010 21:09:32 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6A7688FC1B for ; Mon, 24 May 2010 21:09:32 +0000 (UTC) Received: by pvh11 with SMTP id 11so703563pvh.13 for ; Mon, 24 May 2010 14:09:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:from:date:to:cc :subject:message-id:reply-to:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent:organization:x-operation-sytem; bh=9DILI48DIPwJ3TN9BDyU5OeYlYWBwLf1oshvQR9/NI0=; b=YVVIXlGEmgq7b0Bc7C2yFRVtls/E/57QH2YAu0coSwZz2CtcN4SgrK3B8US3ZllXz7 LwiX2ugJAK2YccqoKit0WV2D0rBHxFTnv7X9gzvuvfV3QekZRa5//zvRrWfxQsgQ7jIr toznX3XUkuDP4tedtO4JUPP+qPpnLwnwlVZUU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:mail-followup-to :references:mime-version:content-type:content-disposition :in-reply-to:user-agent:organization:x-operation-sytem; b=FUe2ZCfzm37dZelBywbZTfhed8pgIMiW5eqqtafwVxDcvLqF/Qn1L3wpdb6TmCxhwf 5JYslUbijUURFgDAb/XxjpBvpw50MImQNV9j4WMyyq+UfB9+3if5QWRH3kTKc4dAmn5W w7FMRl6zN7IRd4z44KNsyjXkPYeSVnzZDx69c= Received: by 10.143.26.28 with SMTP id d28mr3758532wfj.103.1274735371851; Mon, 24 May 2010 14:09:31 -0700 (PDT) Received: from weongyo ([174.35.1.224]) by mx.google.com with ESMTPS id e16sm1139025wfg.2.2010.05.24.14.09.29 (version=SSLv3 cipher=RC4-MD5); Mon, 24 May 2010 14:09:29 -0700 (PDT) Received: by weongyo (sSMTP sendmail emulation); Mon, 24 May 2010 14:09:46 -0700 From: Weongyo Jeong Date: Mon, 24 May 2010 14:09:46 -0700 To: Gustau P??rez Message-ID: <20100524210945.GE1295@weongyo> Mail-Followup-To: Gustau P??rez , current@freebsd.org, Ian FREISLICH References: <20100303082833.GB22865@weongyo> <20100303111014.6564ea1e.ray@dlink.ua> <20100312231333.GZ1295@weongyo> <4BD2201E.3090409@entel.upc.edu> <20100424231755.GI65380@weongyo> <4BD4A928.8020901@entel.upc.edu> <20100506190653.GA31100@weongyo> <58220.88.15.97.205.1273248485.squirrel@webmail.entel.upc.edu> <20100510195622.GA1295@weongyo> <4BF54F93.9000409@entel.upc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4BF54F93.9000409@entel.upc.edu> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: Ian FREISLICH , current@freebsd.org Subject: Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Weongyo Jeong List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 May 2010 21:09:32 -0000 On Thu, May 20, 2010 at 05:04:51PM +0200, Gustau P??rez wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > En/na Weongyo Jeong ha escrit: > > On Fri, May 07, 2010 at 06:08:05PM +0200, Gustavo Perez Querol wrote: > >>> Hello Gustau, I'm so sorry for belated response that I had no time to > >>> read and work email and wireless stuffs. > >>> > >>> Could you please test this symptom with attached patch? It looks in > >>> CURRENT it missed to initialize a ratectl when it associates with AP. > >>> > >> The patch made the machine to panic. I think it happened when launching > >> the supplicant. In fact, right now it works by putting the RF switch to > >> OFF. As soon as I change it to ON the machine panics. > >> > >> It get a trap 12, with two reasons : page fault and "bufwrite, buffer is > >> not busy?" > >> > >> I'm running 9.0/AMD64 from 1 of May (don't know exact svn revision). > >> > >> Do you want me to test anything else ? > > > > OK. The patch is ready to test. Could you please test it with attached > > patch? > > > > regards, > > Weongyo Jeong > > > I've just updated to FreeBSD 8.1 PRERELEASE and I see the > unsupported rate problem again. I applied the patch for CURRENT and it > works. So I guess the patch was not MFC in the 8.1 branch. It's MFCed today. > However it still works slow (betwenn 200 and 300 kbytes/s). I tried > using a rum dongle with the same AP (which is a 8.0-STABLE system with > an Atheros card) and works great when uploading (2Mb sustained). Umm. I have no clue why this is happened currently. When I found any hints I'll let you know. Thank you. > In my laptop I see now messages like these : > > bwn0: RX decryption attempted (old 0 keyidx 0x1) You could ignore this messages because bwn(4) doesn't support H/W crypto and it looks it's harmless. > If you want me to try anything, let me know. Regards, Weongyo Jeong From owner-freebsd-current@FreeBSD.ORG Tue May 25 04:11:10 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2A0D01065672; Tue, 25 May 2010 04:11:10 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id EA2B08FC18; Tue, 25 May 2010 04:11:09 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o4P4B9KF050616; Tue, 25 May 2010 00:11:09 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o4P4B8mS050605; Tue, 25 May 2010 04:11:08 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 25 May 2010 04:11:08 GMT Message-Id: <201005250411.o4P4B8mS050605@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2010 04:11:10 -0000 TB --- 2010-05-25 02:40:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-05-25 02:40:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2010-05-25 02:40:00 - cleaning the object tree TB --- 2010-05-25 02:40:22 - cvsupping the source tree TB --- 2010-05-25 02:40:22 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2010-05-25 02:45:58 - building world TB --- 2010-05-25 02:45:58 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-25 02:45:58 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-25 02:45:58 - TARGET=pc98 TB --- 2010-05-25 02:45:58 - TARGET_ARCH=i386 TB --- 2010-05-25 02:45:58 - TZ=UTC TB --- 2010-05-25 02:45:58 - __MAKE_CONF=/dev/null TB --- 2010-05-25 02:45:58 - cd /src TB --- 2010-05-25 02:45:58 - /usr/bin/make -B buildworld >>> World build started on Tue May 25 02:45:58 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue May 25 03:43:41 UTC 2010 TB --- 2010-05-25 03:43:41 - generating LINT kernel config TB --- 2010-05-25 03:43:41 - cd /src/sys/pc98/conf TB --- 2010-05-25 03:43:41 - /usr/bin/make -B LINT TB --- 2010-05-25 03:43:41 - building LINT kernel TB --- 2010-05-25 03:43:41 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-25 03:43:41 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-25 03:43:41 - TARGET=pc98 TB --- 2010-05-25 03:43:41 - TARGET_ARCH=i386 TB --- 2010-05-25 03:43:41 - TZ=UTC TB --- 2010-05-25 03:43:41 - __MAKE_CONF=/dev/null TB --- 2010-05-25 03:43:41 - cd /src TB --- 2010-05-25 03:43:41 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue May 25 03:43:41 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Tue May 25 04:05:23 UTC 2010 TB --- 2010-05-25 04:05:23 - building GENERIC kernel TB --- 2010-05-25 04:05:23 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-25 04:05:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-25 04:05:23 - TARGET=pc98 TB --- 2010-05-25 04:05:23 - TARGET_ARCH=i386 TB --- 2010-05-25 04:05:23 - TZ=UTC TB --- 2010-05-25 04:05:23 - __MAKE_CONF=/dev/null TB --- 2010-05-25 04:05:23 - cd /src TB --- 2010-05-25 04:05:23 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue May 25 04:05:24 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] :> hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=/usr/bin/make sh /src/sys/conf/newvers.sh GENERIC cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror vers.c linking kernel.debug mca.o(.text+0x1627): In function `mca_init': /src/sys/i386/i386/mca.c:786: undefined reference to `lapic_enable_cmc' *** Error code 1 Stop in /obj/pc98/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-05-25 04:11:08 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-05-25 04:11:08 - ERROR: failed to build GENERIC kernel TB --- 2010-05-25 04:11:08 - 3968.38 user 831.76 system 5468.48 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Tue May 25 08:45:56 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BBE4E1065674; Tue, 25 May 2010 08:45:56 +0000 (UTC) (envelope-from decke@FreeBSD.org) Received: from mail.itac.at (unknown [IPv6:2002:5bc2:5ac8:d:20c:29ff:fe19:7b2]) by mx1.freebsd.org (Postfix) with ESMTP id 1D7608FC34; Tue, 25 May 2010 08:45:56 +0000 (UTC) Received: from [91.205.172.21] (helo=webmail.bluelife.at) by mail.itac.at with esmtpa (Exim 4.63) (envelope-from ) id 1OGplr-0002HB-4B; Tue, 25 May 2010 10:45:55 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Date: Tue, 25 May 2010 10:45:56 +0200 From: Bernhard Froehlich To: Mario Sergio Fujikawa Ferreira In-Reply-To: <20100521020553.80602.qmail@exxodus.fedaykin.here> References: <20100521020553.80602.qmail@exxodus.fedaykin.here> Message-ID: X-Sender: decke@FreeBSD.org User-Agent: RoundCube Webmail/0.4-beta X-Spam-Score: 0.2 (/) X-Spam-Report: Spam detection software, running on the system "mail.itac.at", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: On Thu, 20 May 2010 23:05:53 -0300, Mario Sergio Fujikawa Ferreira wrote: > Hi, > > I recently reinstalled my FreeBSD 8-STABLE box to move from > i386 to amd64. The hardware hasn't changed (except for an increase > from 4GB to 8GB ram). > > There have been some hiccups and I am still trying to tidy > up things together. > > One of the problems I am having is building virtualbox-ose > which previously built nicely on i386. > > I am running a vanilla 8-STABLE world (no special COPTFLAGS) from May > 17th. > > $ uname -a > FreeBSD exxodus.fedaykin.here 8.0-STABLE FreeBSD 8.0-STABLE #2: Mon May 17 > 19:53:30 BRT 2010 lioux@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 > > I have a clean and up to date ports tree from today. > All ports upgraded using portupgrade. > > I am trying to build the virtualbox-ose port with vanilla cflags. > > $ make -V CFLAGS > -O2 -pipe -fno-strict-aliasing > > The relevant message follows: > > --------- > > kBuild: Installing VBoxControl => > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/bin/additions/VBoxControl > kmk[2]: *** > [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h] > Segmentation fault: 11 (core dumped) > kmk[2]: *** Deleting file > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h' > kmk[2]: Leaving directory > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE' > kmk[1]: *** [pass_binaries_this] Error 2 > kmk[1]: Leaving directory > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE' > kmk: *** [pass_binaries_order] Error 2 > *** Error code 2 > > --------- > > The complete build log can be found at > > http://people.freebsd.org/~lioux/virtualbox-ose_3.1.8_build.log.bz2 > > My virtualbox-ose work directory can be found at > (you need archivers/xz to extract it) > > http://people.freebsd.org/~lioux/virtualbox-ose__work.tar.xz > > Let me know if there is anything I can do [...] Content analysis details: (0.2 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP 1.6 AWL AWL: From: address is in the auto white-list Cc: freebsd-current@freebsd.org, vbox@FreeBSD.org Subject: gcc segfault: Cannot build virtualbox-ose on 8-STABLE 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: Tue, 25 May 2010 08:45:56 -0000 On Thu, 20 May 2010 23:05:53 -0300, Mario Sergio Fujikawa Ferreira wrote: > Hi, > > I recently reinstalled my FreeBSD 8-STABLE box to move from > i386 to amd64. The hardware hasn't changed (except for an increase > from 4GB to 8GB ram). > > There have been some hiccups and I am still trying to tidy > up things together. > > One of the problems I am having is building virtualbox-ose > which previously built nicely on i386. > > I am running a vanilla 8-STABLE world (no special COPTFLAGS) from May > 17th. > > $ uname -a > FreeBSD exxodus.fedaykin.here 8.0-STABLE FreeBSD 8.0-STABLE #2: Mon May 17 > 19:53:30 BRT 2010 lioux@exxodus:/usr/obj/usr/src/sys/LIOUX amd64 > > I have a clean and up to date ports tree from today. > All ports upgraded using portupgrade. > > I am trying to build the virtualbox-ose port with vanilla cflags. > > $ make -V CFLAGS > -O2 -pipe -fno-strict-aliasing > > The relevant message follows: > > --------- > > kBuild: Installing VBoxControl => > /usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/bin/additions/VBoxControl > kmk[2]: *** > [/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h] > Segmentation fault: 11 (core dumped) > kmk[2]: *** Deleting file > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE/out/freebsd.amd64/release/obj/VMM/tstVMStructRC.h' > kmk[2]: Leaving directory > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE' > kmk[1]: *** [pass_binaries_this] Error 2 > kmk[1]: Leaving directory > `/usr/ports/emulators/virtualbox-ose/work/VirtualBox-3.1.8_OSE' > kmk: *** [pass_binaries_order] Error 2 > *** Error code 2 > > --------- > > The complete build log can be found at > > http://people.freebsd.org/~lioux/virtualbox-ose_3.1.8_build.log.bz2 > > My virtualbox-ose work directory can be found at > (you need archivers/xz to extract it) > > http://people.freebsd.org/~lioux/virtualbox-ose__work.tar.xz > > Let me know if there is anything I can do to help. > > Regards, > > ps: virtualbox-ose-kmod builds without a problem as well as my other > 1482 ports. :) Segmentation fault: 11 comes from gcc so this is likely to be a compiler bug and i'm not sure if we can help in this case so I cc'd current@. Could you try to get a backtrace from the core file that it has dumped? -- Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-current@FreeBSD.ORG Tue May 25 09:21:23 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A56A106564A for ; Tue, 25 May 2010 09:21:23 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from mail.haruhiism.net (mail.fujibayashi.jp [IPv6:2001:470:9954:ffff::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6D9688FC14 for ; Tue, 25 May 2010 09:21:22 +0000 (UTC) Received: from [IPv6:2001:470:9f2d:0:1::1] (omoikane.gensokyo.fujibayashi.jp [IPv6:2001:470:9f2d:0:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.haruhiism.net (Postfix) with ESMTPSA id 5C3FA195A58 for ; Tue, 25 May 2010 18:21:20 +0900 (JST) Message-ID: <4BFB968C.40108@haruhiism.net> Date: Tue, 25 May 2010 13:21:16 +0400 From: Kamigishi Rei User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 ThunderBrowse/3.2.8.1 MIME-Version: 1.0 To: FreeBSD Current X-Enigmail-Version: 1.0.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigEEE2592C7CE1A4B5E8CAA4CA" Subject: MROUTING issues (r200287) with multicast routing daemons 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, 25 May 2010 09:21:23 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigEEE2592C7CE1A4B5E8CAA4CA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, hope you're having a nice day, I have a problem with my single-core amd64 system running FreeBSD 8.0-STABLE #1 r200287; if I try running XORP (or igmpproxy) to route multicast packets, the system traps after a while - usually less than a hour since the start of xorp process. This is, basically, easily reproductable for me. The routing daemon is configured to route multicast from the external interface re0, which is currently not connected ('no carrier'). Traps seemingly occur within ip_mroute.c. The process in which the crash occurs varies; it might be xorp's FEA subprocess, or the system's interrupt handler, for example (I witnessed both). The following lines were added to the kernel config file: device pf device pflog device pfsync options ALTQ options ALTQ_HFSC options DEVICE_POLLING options MROUTING FreeBSD gw.gensokyo.fujibayashi.jp 8.0-STABLE FreeBSD 8.0-STABLE #1 r200287: Tue May 4 13:33:08 MSD 2010 =20 root@gw.gensokyo.fujibayashi.jp:/usr/obj/usr/src/sys/Eientei amd64 Some of core.txt contents follow: Fatal trap 12: page fault while in kernel mode cpuid =3D 0; apic id =3D 00 fault virtual address =3D 0x10 fault code =3D supervisor read data, page not present instruction pointer =3D 0x20:0xffffffff806c866f stack pointer =3D 0x28:0xffffff80698d9840 frame pointer =3D 0x28:0xffffff80698d98c0 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 1634 (xorp_fea) trap number =3D 12 panic: page fault cpuid =3D 0 Uptime: 10m22s (kgdb) #0 doadump () at pcpu.h:223 #1 0xffffffff805c24f9 in boot (howto=3D260) at /usr/src/sys/kern/kern_shutdown.c:416 #2 0xffffffff805c292c in panic (fmt=3D0xffffffff80973cac "%s") at /usr/src/sys/kern/kern_shutdown.c:579 #3 0xffffffff808ab298 in trap_fatal (frame=3D0xffffff0082149720, eva=3DVariable "eva" is not available. ) at /usr/src/sys/amd64/amd64/trap.c:857 #4 0xffffffff808ab664 in trap_pfault (frame=3D0xffffff80698d9790, usermo= de=3D0) at /usr/src/sys/amd64/amd64/trap.c:773 #5 0xffffffff808abfe2 in trap (frame=3D0xffffff80698d9790) at /usr/src/sys/amd64/amd64/trap.c:499 #6 0xffffffff808921c3 in calltrap () at /usr/src/sys/amd64/amd64/exception.S:224 #7 0xffffffff806c866f in ip_mdq (m=3D0x0, ifp=3D0xffffff0001de62b0, rt=3D0xffffff0001de6200, xmt_vif=3D65535) at /usr/src/sys/netinet/ip_mroute.c:1471 #8 0xffffffff806caf67 in X_ip_mrouter_set (so=3DVariable "so" is not available. ) at /usr/src/sys/netinet/ip_mroute.c:1093 #9 0xffffffff806cf03a in rip_ctloutput (so=3D0xffffff00c15de2a8, sopt=3D0xffffff80698d9ad0) at /usr/src/sys/netinet/raw_ip.c:662 #10 0xffffffff80621132 in sosetopt (so=3D0xffffff00c15de2a8, sopt=3D0xffffff80698d9ad0) at /usr/src/sys/kern/uipc_socket.c:2379 #11 0xffffffff806279f0 in kern_setsockopt (td=3D0xffffff0082149720, s=3D3= 3, level=3DVariable "level" is not available. ) at /usr/src/sys/kern/uipc_syscalls.c:1331 #12 0xffffffff80627a62 in setsockopt (td=3DVariable "td" is not available= =2E ) at /usr/src/sys/kern/uipc_syscalls.c:1286 #13 0xffffffff808ab8d6 in syscall (frame=3D0xffffff80698d9c80) at /usr/src/sys/amd64/amd64/trap.c:989 #14 0xffffffff808924a1 in Xfast_syscall () at /usr/src/sys/amd64/amd64/exception.S:373 #15 0x000000080144232c in ?? () Previous frame inner to this frame (corrupt stack?) --=20 Kamigishi Rei KREI-RIPE --------------enigEEE2592C7CE1A4B5E8CAA4CA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJL+5aPAAoJEPAgyqbDpP+eEiUH+gK0nnfc98+Xco4WxcwNVPUC Ly6ry+jCzY6UTz9yW70U8zCOnFFcfPKDo0mfl8wF65yr2ClkSzR5WLCf1NDxErIq 256NPXB1oPTd/msId0USnsTBNgIil5nvEA7kPlk/lSBFnqxfl9FQ7FhNFSeA6hDW XVb3j5Lr7Op6a6hwVUXK1SIHwrWGlPQH2F9ZfDwNXltM69LIoe/WfWSsU4ypR8ww 20PrZMSGGIDhVuyxxYotdeZdS0ygrwr5ve43iEvDmHpQMsR6kHUtSO5YOy+9/Y+v IEAvsImd+07IaYHR42a+yIQtdV3Z9fdHZTuF8MsUuG/9+sB0pKT6LhcDl23Z3D4= =j8u9 -----END PGP SIGNATURE----- --------------enigEEE2592C7CE1A4B5E8CAA4CA-- From owner-freebsd-current@FreeBSD.ORG Tue May 25 10:04:12 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 058E9106566C for ; Tue, 25 May 2010 10:04:12 +0000 (UTC) (envelope-from rvdp@rvdp.org) Received: from kirk.rvdp.org (kirk.rvdp.org [IPv6:2001:610:108:87::2]) by mx1.freebsd.org (Postfix) with ESMTP id 6F22C8FC1C for ; Tue, 25 May 2010 10:04:11 +0000 (UTC) Received: from kirk.rvdp.org (localhost [127.0.0.1]) by kirk.rvdp.org (8.14.3/8.14.3) with ESMTP id o4PA4A2s099392 for ; Tue, 25 May 2010 12:04:10 +0200 (CEST) (envelope-from rvdp@kirk.rvdp.org) Received: (from rvdp@localhost) by kirk.rvdp.org (8.14.3/8.14.3/Submit) id o4PA4Avp099391 for freebsd-current@freebsd.org; Tue, 25 May 2010 12:04:10 +0200 (CEST) (envelope-from rvdp) Date: Tue, 25 May 2010 12:04:04 +0200 From: Ronald van der Pol To: freebsd-current@freebsd.org Message-ID: <20100525100404.GF287@rvdp.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Subject: panic: lapic_enable_cmc: missing APIC 0 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, 25 May 2010 10:04:12 -0000 I am trying to move to current from 8.1-PRERELEASE. After buildworld, buildkernel, installkernel and rebooting I get: panic: lapic_enable_cmc: missing APIC 0 cpuid = 0 KDB: enter : panic while the kernel is booting. This is some boot info from 8.1-PRERELEASE: CPU: Intel(R) Xeon(R) CPU X5550 @ 2.67GHz (2660.02-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x106a5 Family = 6 Model = 1a Stepping = 5 Features=0xbfebfbff Features2=0x9ce3bd AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant real memory = 6442450944 (6144 MB) avail memory = 6172110848 (5886 MB) ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 16 cpu1 (AP): APIC ID: 17 cpu2 (AP): APIC ID: 18 cpu3 (AP): APIC ID: 19 cpu4 (AP): APIC ID: 20 cpu5 (AP): APIC ID: 21 cpu6 (AP): APIC ID: 22 cpu7 (AP): APIC ID: 23 ioapic1: Changing APIC ID to 1 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 32-55 on motherboard kbd1 at kbdmux0 acpi0: on motherboard acpi0: [ITHREAD] acpi0: Power Button (fixed) Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 900 rvdp From owner-freebsd-current@FreeBSD.ORG Tue May 25 11:25:16 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0ABFF106568C; Tue, 25 May 2010 11:25:16 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea]) by mx1.freebsd.org (Postfix) with ESMTP id C953E8FC14; Tue, 25 May 2010 11:25:15 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id A07FE71F0E; Tue, 25 May 2010 11:25:14 +0000 (UTC) From: Stefan Bethke Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Tue, 25 May 2010 13:25:12 +0200 Message-Id: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> To: Robert Watson Mime-Version: 1.0 (Apple Message framework v1078) X-Mailer: Apple Mail (2.1078) Cc: freebsd-current Current Subject: AppleTalk status 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, 25 May 2010 11:25:16 -0000 Hi, I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when that = comes out the next couple of days), and I'm wondering what state = AppleTalk support is in these days. Is anybody still using it, or would = now be the time to make all AppleTalk support in that port optional, and = just focus on the file server component? I haven't used AppleTalk for at least eight years now, and I don't quite = see which setting it still would be used in nowadays... Thanks, Stefan --=20 Stefan Bethke Fon +49 151 14070811 From owner-freebsd-current@FreeBSD.ORG Tue May 25 11:41:21 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6DE5A1065674; Tue, 25 May 2010 11:41:21 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id DADB58FC18; Tue, 25 May 2010 11:41:20 +0000 (UTC) Received: from ur.dons.net.au (ppp121-45-159-148.lns6.adl6.internode.on.net [121.45.159.148]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id o4PBfAuR007920 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 25 May 2010 21:11:17 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> Date: Tue, 25 May 2010 21:11:10 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: <13F8E068-61AE-4670-86B8-B09C3BC00B86@gsoft.com.au> References: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> To: Stefan Bethke X-Mailer: Apple Mail (2.1078) X-Spam-Score: 0.163 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-current Current , Robert Watson Subject: Re: AppleTalk status 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, 25 May 2010 11:41:21 -0000 On 25/05/2010, at 20:55, Stefan Bethke wrote: > I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when = that comes out the next couple of days), and I'm wondering what state = AppleTalk support is in these days. Is anybody still using it, or would = now be the time to make all AppleTalk support in that port optional, and = just focus on the file server component? >=20 > I haven't used AppleTalk for at least eight years now, and I don't = quite see which setting it still would be used in nowadays... I use it so I can back my Macbook Pro to my FreeBSD server on a ZFS = partition.. (But that is all) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-current@FreeBSD.ORG Tue May 25 12:28:41 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BCED51065675 for ; Tue, 25 May 2010 12:28:41 +0000 (UTC) (envelope-from gerd@truschinski.de) Received: from mo-p00-ob.rzone.de (mo-p00-ob.rzone.de [81.169.146.161]) by mx1.freebsd.org (Postfix) with ESMTP id 4523F8FC1E for ; Tue, 25 May 2010 12:28:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1274790519; l=510; s=domk; d=truschinski.de; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=Rt1LrocL1usqBZjjgQcHc2asv9c=; b=t+gS+X7KV8veJgAYPd0iDhX72a2aCh81ki/973wEkRFp0XbF9OsoyVqqj59x9YkxRCK o9i7mLQRpzhUONRfX8RilclyrNjTohS+Jf3oGCn72Bz6C20GKxFTPwaUGmB+kR0Fis3C5 fKSC5+emrGzqAk6Lhdv6gQfSue6XuT+/dws= X-RZG-AUTH: :K2kWcWC8aeptqAZ2mRDu0s07mmH1zFKQdF0lCrKer4N5IzlbYCUfXh+UU9cpFXAUAYM= X-RZG-CLASS-ID: mo00 Received: from [192.168.10.105] (dslb-188-103-110-107.pools.arcor-ip.net [188.103.110.107]) by post.strato.de (jimi mo46) (RZmta 23.2) with ESMTP id D0032bm4PBnczJ for ; Tue, 25 May 2010 14:17:38 +0200 (MEST) Message-ID: <4BFBC027.8090504@truschinski.de> Date: Tue, 25 May 2010 14:18:47 +0200 From: Gerd Truschinski User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20091109) MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: No internet with snapshots 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, 25 May 2010 12:28:41 -0000 Hi there, I tried to install the latest FreeBSD-9.0-CURRENT-201005-amd64-bootonly.iso. FreeBSD is starting, sysinstall is running. I want to install from ftp.freebsd.org. Therefor I try to set the _Media Typ_ in the _Options Editor_. I select the only Network Interface, a nfe, no IP6 but DHCP. I get an IP address from my Router and then I get a "Cannot resolv hostname ftp.freebsd.org". This seems to happen with older snapshots also. What could I do. What information did you need? /gT/ From owner-freebsd-current@FreeBSD.ORG Tue May 25 12:35:17 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7946F1065676; Tue, 25 May 2010 12:35:17 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea]) by mx1.freebsd.org (Postfix) with ESMTP id 3F98D8FC15; Tue, 25 May 2010 12:35:17 +0000 (UTC) Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id AA3A071125; Tue, 25 May 2010 12:35:15 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Stefan Bethke In-Reply-To: <13F8E068-61AE-4670-86B8-B09C3BC00B86@gsoft.com.au> Date: Tue, 25 May 2010 14:35:13 +0200 Content-Transfer-Encoding: quoted-printable Message-Id: References: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> <13F8E068-61AE-4670-86B8-B09C3BC00B86@gsoft.com.au> To: "Daniel O'Connor" X-Mailer: Apple Mail (2.1078) Cc: freebsd-current Current , Robert Watson Subject: Re: AppleTalk status 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, 25 May 2010 12:35:17 -0000 Am 25.05.2010 um 13:41 schrieb Daniel O'Connor: > On 25/05/2010, at 20:55, Stefan Bethke wrote: >> I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when = that comes out the next couple of days), and I'm wondering what state = AppleTalk support is in these days. Is anybody still using it, or would = now be the time to make all AppleTalk support in that port optional, and = just focus on the file server component? >>=20 >> I haven't used AppleTalk for at least eight years now, and I don't = quite see which setting it still would be used in nowadays... >=20 > I use it so I can back my Macbook Pro to my FreeBSD server on a ZFS = partition.. > (But that is all) You're using the sys/netatalk AppleTalk protocol for that, or TCP? The = netatalk port's afpd (Apple File Protocol daemon) can speak AFP over = both DDP/ASP and TCP, and I'll keep afpd working over TCP of course. = I'm talking about disabling AppleTalk protocol support. Stefan --=20 Stefan Bethke Fon +49 151 14070811 From owner-freebsd-current@FreeBSD.ORG Tue May 25 12:55:22 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 616EF1065677 for ; Tue, 25 May 2010 12:55:22 +0000 (UTC) (envelope-from gljennjohn@googlemail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id DCE588FC1C for ; Tue, 25 May 2010 12:55:21 +0000 (UTC) Received: by fxm17 with SMTP id 17so349519fxm.13 for ; Tue, 25 May 2010 05:55:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:cc:subject :message-id:in-reply-to:references:reply-to:x-mailer:mime-version :content-type:content-transfer-encoding; bh=S2Hyc61YokJmhEElZCmnPisAyRYYSaEkSh55H93DlWk=; b=VMX9iLIKhPe8HrbAzplrIexBnDz/tuJjFZAjsjOV5t1DpiFangAruoE2VPdy+B6oyT 0NYH1SnZ9beoElP5OujzEW4rhXeRAtiDyCbV+Gabo3y+U55VeuoglUcW7L5smG3MsEbC wc5E9jmfoI8EZIoGUCN42OTgn1I6yEpMgI/xM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :x-mailer:mime-version:content-type:content-transfer-encoding; b=uWtCpPXnuiNhgQmLh+bQxTMwxfJG/lDyDGzj9aDftTL3D0nsLsjaqVQ+8HeJZWvKrV BJZgfA4VyUx5ofE4OyaFzi8mHjjoKXqQNzGCnGHUCpaa4vF7j5jlBuNDvXvQMLgDcur8 lT0ew7d6GAYOI6ClnoLF9475wBKqr7kfba9/c= Received: by 10.223.99.78 with SMTP id t14mr2442407fan.85.1274792120761; Tue, 25 May 2010 05:55:20 -0700 (PDT) Received: from ernst.jennejohn.org (p578E2D21.dip.t-dialin.net [87.142.45.33]) by mx.google.com with ESMTPS id g10sm24717635fai.0.2010.05.25.05.55.19 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 25 May 2010 05:55:20 -0700 (PDT) Date: Tue, 25 May 2010 14:55:18 +0200 From: Gary Jennejohn To: Gerd Truschinski Message-ID: <20100525145518.7dbb6e91@ernst.jennejohn.org> In-Reply-To: <4BFBC027.8090504@truschinski.de> References: <4BFBC027.8090504@truschinski.de> X-Mailer: Claws Mail 3.7.5 (GTK+ 2.18.7; amd64-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: No internet with snapshots X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gljennjohn@googlemail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2010 12:55:22 -0000 On Tue, 25 May 2010 14:18:47 +0200 Gerd Truschinski wrote: > I tried to install the latest > FreeBSD-9.0-CURRENT-201005-amd64-bootonly.iso. > FreeBSD is starting, sysinstall is running. > I want to install from ftp.freebsd.org. Therefor I try to set the _Media > Typ_ in the _Options Editor_. > I select the only Network Interface, a nfe, no IP6 but DHCP. I get an IP > address from my Router and then I get a > "Cannot resolv hostname ftp.freebsd.org". > > This seems to happen with older snapshots also. > > What could I do. What information did you need? > Looks like there's no name server, although the router should have passed that info with the other DHCP data. Look whether there's an option to set a name server (I haven't done an install for a long time so I can't remember). If there is you could use 8.8.8.8, which is a Google name server which works quite well (and it's easy to remember). -- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Tue May 25 13:12:02 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7FD6A1065673; Tue, 25 May 2010 13:12:02 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id EC51E8FC1A; Tue, 25 May 2010 13:12:01 +0000 (UTC) Received: from ur.dons.net.au (ppp121-45-159-148.lns6.adl6.internode.on.net [121.45.159.148]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id o4PDBreN010613 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 25 May 2010 22:41:59 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: Date: Tue, 25 May 2010 22:41:53 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: <00019AED-1A3A-4350-890D-7D4FA62F0EF9@gsoft.com.au> References: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> <13F8E068-61AE-4670-86B8-B09C3BC00B86@gsoft.com.au> To: Stefan Bethke X-Mailer: Apple Mail (2.1078) X-Spam-Score: 0.163 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-current Current , Robert Watson Subject: Re: AppleTalk status 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, 25 May 2010 13:12:02 -0000 On 25/05/2010, at 22:05, Stefan Bethke wrote: > You're using the sys/netatalk AppleTalk protocol for that, or TCP? = The netatalk port's afpd (Apple File Protocol daemon) can speak AFP over = both DDP/ASP and TCP, and I'll keep afpd working over TCP of course. = I'm talking about disabling AppleTalk protocol support. Ahh, sorry, yes I am using TCP! -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-current@FreeBSD.ORG Tue May 25 13:16:37 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 592AD106566B; Tue, 25 May 2010 13:16:37 +0000 (UTC) (envelope-from rwatson@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 332F28FC12; Tue, 25 May 2010 13:16:37 +0000 (UTC) Received: from [192.168.2.105] (host86-162-158-86.range86-162.btcentralplus.com [86.162.158.86]) by cyrus.watson.org (Postfix) with ESMTPSA id 5648746B5C; Tue, 25 May 2010 09:16:36 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: "Robert N. M. Watson" In-Reply-To: <4BFBCCDE.6050900@freebsd.org> Date: Tue, 25 May 2010 14:16:34 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> <4BFBCCDE.6050900@freebsd.org> To: Nathan Whitehorn X-Mailer: Apple Mail (2.1078) Cc: freebsd-current Current , Stefan Bethke Subject: Re: AppleTalk status 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, 25 May 2010 13:16:37 -0000 On 25 May 2010, at 14:13, Nathan Whitehorn wrote: >> I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when = that comes out the next couple of days), and I'm wondering what state = AppleTalk support is in these days. Is anybody still using it, or would = now be the time to make all AppleTalk support in that port optional, and = just focus on the file server component? >>=20 >> I haven't used AppleTalk for at least eight years now, and I don't = quite see which setting it still would be used in nowadays... > I use it successfully on a router to connect my antique AppleTalk-only = laser printer. It seems to work quite well still. I can confirm that whenever kernel netatalk gets broken, I get bug = reports. :-) However, it hasn't gotten broken in a year or two so I've = not polled recently. Robert= From owner-freebsd-current@FreeBSD.ORG Tue May 25 13:18:10 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C25AA1065677 for ; Tue, 25 May 2010 13:18:10 +0000 (UTC) (envelope-from gerd@truschinski.de) Received: from mo-p00-ob.rzone.de (mo-p00-ob.rzone.de [81.169.146.162]) by mx1.freebsd.org (Postfix) with ESMTP id 4D30F8FC24 for ; Tue, 25 May 2010 13:18:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1274793489; l=1136; s=domk; d=truschinski.de; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References: Subject:CC:To:MIME-Version:From:Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=4lEVeWH0l8BS8tbwKruZCxI0GfQ=; b=STUlGdED9HA++TxWFRltm4lTyzBP7HkHUDDKUHAvYUOI4uh8d4eNjGjWGQxW/parvzA 0XRMA28VVtL2RIuxf+JkIcgvR5E+rmkzlf0pe6wj8HIUHb9I/1pNKXlz0+b9oEFDs/8yI QV4Lx4sFWgL8uMkUwd5L+ANvzbvzEnIzLYQ= X-RZG-AUTH: :K2kWcWC8aeptqAZ2mRDu0s07mmH1zFKQdF0lCrKer4N5IzlbYCUfXh+UU9cpFXAUAYM= X-RZG-CLASS-ID: mo00 Received: from [192.168.10.105] (dslb-188-103-110-107.pools.arcor-ip.net [188.103.110.107]) by post.strato.de (jimi mo45) (RZmta 23.2) with ESMTP id 60032cm4PC36i1 ; Tue, 25 May 2010 15:06:42 +0200 (MEST) Message-ID: <4BFBCBA7.8080904@truschinski.de> Date: Tue, 25 May 2010 15:07:51 +0200 From: Gerd Truschinski User-Agent: Mozilla-Thunderbird 2.0.0.22 (X11/20091109) MIME-Version: 1.0 To: gljennjohn@googlemail.com References: <4BFBC027.8090504@truschinski.de> <20100525145518.7dbb6e91@ernst.jennejohn.org> In-Reply-To: <20100525145518.7dbb6e91@ernst.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: No internet with snapshots 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, 25 May 2010 13:18:10 -0000 Gary Jennejohn wrote: > On Tue, 25 May 2010 14:18:47 +0200 > Gerd Truschinski wrote: > > >> I tried to install the latest >> FreeBSD-9.0-CURRENT-201005-amd64-bootonly.iso. >> FreeBSD is starting, sysinstall is running. >> I want to install from ftp.freebsd.org. Therefor I try to set the _Media >> Typ_ in the _Options Editor_. >> I select the only Network Interface, a nfe, no IP6 but DHCP. I get an IP >> address from my Router and then I get a >> "Cannot resolv hostname ftp.freebsd.org". >> >> This seems to happen with older snapshots also. >> >> What could I do. What information did you need? >> >> > > Looks like there's no name server, although the router should have passed > that info with the other DHCP data. > > Look whether there's an option to set a name server (I haven't done an > install for a long time so I can't remember). If there is you could use > 8.8.8.8, which is a Google name server which works quite well (and it's > easy to remember). > > No, I get the correct gateway and name server address from the router. But thank you for the 8.8.8.8 :-) /gT/ From owner-freebsd-current@FreeBSD.ORG Tue May 25 13:42:44 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 511F71065673 for ; Tue, 25 May 2010 13:42:44 +0000 (UTC) (envelope-from nwhitehorn@freebsd.org) Received: from mail.icecube.wisc.edu (trout.icecube.wisc.edu [128.104.255.119]) by mx1.freebsd.org (Postfix) with ESMTP id 278928FC15 for ; Tue, 25 May 2010 13:42:43 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.icecube.wisc.edu (Postfix) with ESMTP id B5DD1582A6; Tue, 25 May 2010 08:13:04 -0500 (CDT) X-Virus-Scanned: amavisd-new at icecube.wisc.edu Received: from mail.icecube.wisc.edu ([127.0.0.1]) by localhost (trout.icecube.wisc.edu [127.0.0.1]) (amavisd-new, port 10030) with ESMTP id 2i4TKu29fLgB; Tue, 25 May 2010 08:13:04 -0500 (CDT) Received: from wanderer.tachypleus.net (adsl-76-233-145-159.dsl.mdsnwi.sbcglobal.net [76.233.145.159]) by mail.icecube.wisc.edu (Postfix) with ESMTP id 32D2A58267; Tue, 25 May 2010 08:13:04 -0500 (CDT) Message-ID: <4BFBCCDE.6050900@freebsd.org> Date: Tue, 25 May 2010 08:13:02 -0500 From: Nathan Whitehorn User-Agent: Thunderbird 2.0.0.24 (X11/20100504) MIME-Version: 1.0 To: Stefan Bethke References: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> In-Reply-To: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current Current , Robert Watson Subject: Re: AppleTalk status 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, 25 May 2010 13:42:44 -0000 Stefan Bethke wrote: > Hi, > > I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when that comes out the next couple of days), and I'm wondering what state AppleTalk support is in these days. Is anybody still using it, or would now be the time to make all AppleTalk support in that port optional, and just focus on the file server component? > > I haven't used AppleTalk for at least eight years now, and I don't quite see which setting it still would be used in nowadays... > > > Thanks, > Stefan > > I use it successfully on a router to connect my antique AppleTalk-only laser printer. It seems to work quite well still. -Nathan From owner-freebsd-current@FreeBSD.ORG Tue May 25 15:13:05 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B79451065670; Tue, 25 May 2010 15:13:05 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 86B388FC1D; Tue, 25 May 2010 15:13:05 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o4PFD4k8071381; Tue, 25 May 2010 11:13:04 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o4PFD490071374; Tue, 25 May 2010 15:13:04 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 25 May 2010 15:13:04 GMT Message-Id: <201005251513.o4PFD490071374@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 May 2010 15:13:05 -0000 TB --- 2010-05-25 13:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-05-25 13:30:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2010-05-25 13:30:00 - cleaning the object tree TB --- 2010-05-25 13:30:24 - cvsupping the source tree TB --- 2010-05-25 13:30:24 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2010-05-25 13:47:17 - building world TB --- 2010-05-25 13:47:17 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-25 13:47:17 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-25 13:47:17 - TARGET=pc98 TB --- 2010-05-25 13:47:17 - TARGET_ARCH=i386 TB --- 2010-05-25 13:47:17 - TZ=UTC TB --- 2010-05-25 13:47:17 - __MAKE_CONF=/dev/null TB --- 2010-05-25 13:47:17 - cd /src TB --- 2010-05-25 13:47:17 - /usr/bin/make -B buildworld >>> World build started on Tue May 25 13:47:17 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Tue May 25 14:45:12 UTC 2010 TB --- 2010-05-25 14:45:12 - generating LINT kernel config TB --- 2010-05-25 14:45:12 - cd /src/sys/pc98/conf TB --- 2010-05-25 14:45:12 - /usr/bin/make -B LINT TB --- 2010-05-25 14:45:12 - building LINT kernel TB --- 2010-05-25 14:45:12 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-25 14:45:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-25 14:45:12 - TARGET=pc98 TB --- 2010-05-25 14:45:12 - TARGET_ARCH=i386 TB --- 2010-05-25 14:45:12 - TZ=UTC TB --- 2010-05-25 14:45:12 - __MAKE_CONF=/dev/null TB --- 2010-05-25 14:45:12 - cd /src TB --- 2010-05-25 14:45:12 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Tue May 25 14:45:12 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for LINT completed on Tue May 25 15:07:19 UTC 2010 TB --- 2010-05-25 15:07:19 - building GENERIC kernel TB --- 2010-05-25 15:07:19 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-25 15:07:19 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-25 15:07:19 - TARGET=pc98 TB --- 2010-05-25 15:07:19 - TARGET_ARCH=i386 TB --- 2010-05-25 15:07:19 - TZ=UTC TB --- 2010-05-25 15:07:19 - __MAKE_CONF=/dev/null TB --- 2010-05-25 15:07:19 - cd /src TB --- 2010-05-25 15:07:19 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Tue May 25 15:07:19 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] :> hack.c cc -shared -nostdlib hack.c -o hack.So rm -f hack.c MAKE=/usr/bin/make sh /src/sys/conf/newvers.sh GENERIC cc -c -O -pipe -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror vers.c linking kernel.debug mca.o(.text+0x1627): In function `mca_init': /src/sys/i386/i386/mca.c:786: undefined reference to `lapic_enable_cmc' *** Error code 1 Stop in /obj/pc98/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-05-25 15:13:04 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-05-25 15:13:04 - ERROR: failed to build GENERIC kernel TB --- 2010-05-25 15:13:04 - 3968.60 user 817.78 system 6183.70 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Tue May 25 15:36:37 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A85A1065670; Tue, 25 May 2010 15:36:37 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-gx0-f226.google.com (mail-gx0-f226.google.com [209.85.217.226]) by mx1.freebsd.org (Postfix) with ESMTP id F03F58FC19; Tue, 25 May 2010 15:36:36 +0000 (UTC) Received: by gxk26 with SMTP id 26so2443297gxk.13 for ; Tue, 25 May 2010 08:36:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=FSBdzgaSdMGsfm0EZrVSysl9JjYKZ4VlncFUmvgGWhw=; b=E15Jv/jyh1Z35SEw8LHLbVch95rHj8AAzXV4Y1GPJ1PzxyByT5v8FPWOdiO8d49V0u jU2VYRPoB30H/EyimhcmTH4VkALgX0LZEav/kp7688OZGVnY/RXCzDIa1zXdigAuvP8g zBqmGHyr/VBu2zQgsSg9Rf99wkA612lSB044k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ajuTQkKNapIljR7POodw0wOi1SGUd7T/LvPiXYOeCGorwhzUYgpfWGe901oX5ReqcU d5PP47f1HzhEVLZHFxJFcRiajhfKkAM1xNnhdfxIZ/VOX54WrCPvk/UsqeDfE8J/Bj7T lkWmUO5I8avoOGkhld8RqQCWEFa3aGdVgT1HQ= MIME-Version: 1.0 Received: by 10.101.131.14 with SMTP id i14mr8602817ann.63.1274801796073; Tue, 25 May 2010 08:36:36 -0700 (PDT) Received: by 10.100.208.9 with HTTP; Tue, 25 May 2010 08:36:36 -0700 (PDT) In-Reply-To: <201005251513.o4PFD490071374@freebsd-current.sentex.ca> References: <201005251513.o4PFD490071374@freebsd-current.sentex.ca> Date: Tue, 25 May 2010 19:36:36 +0400 Message-ID: From: pluknet To: FreeBSD Tinderbox Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org, i386@freebsd.org Subject: Re: [head tinderbox] failure on i386/pc98 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, 25 May 2010 15:36:37 -0000 On 25 May 2010 19:13, FreeBSD Tinderbox wrote: > TB --- 2010-05-25 13:30:00 - tinderbox 2.6 running on freebsd-current.sen= tex.ca > TB --- 2010-05-25 13:30:00 - starting HEAD tinderbox run for i386/pc98 > TB --- 2010-05-25 13:30:00 - cleaning the object tree > TB --- 2010-05-25 13:30:24 - cvsupping the source tree > TB --- 2010-05-25 13:30:24 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sente= x.ca /tinderbox/HEAD/i386/pc98/supfile > TB --- 2010-05-25 13:47:17 - building world > TB --- 2010-05-25 13:47:17 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2010-05-25 13:47:17 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2010-05-25 13:47:17 - TARGET=3Dpc98 > TB --- 2010-05-25 13:47:17 - TARGET_ARCH=3Di386 > TB --- 2010-05-25 13:47:17 - TZ=3DUTC > TB --- 2010-05-25 13:47:17 - __MAKE_CONF=3D/dev/null > TB --- 2010-05-25 13:47:17 - cd /src > TB --- 2010-05-25 13:47:17 - /usr/bin/make -B buildworld >>>> World build started on Tue May 25 13:47:17 UTC 2010 >>>> Rebuilding the temporary build tree >>>> stage 1.1: legacy release compatibility shims >>>> stage 1.2: bootstrap tools >>>> stage 2.1: cleaning up the object tree >>>> stage 2.2: rebuilding the object tree >>>> stage 2.3: build tools >>>> stage 3: cross tools >>>> stage 4.1: building includes >>>> stage 4.2: building libraries >>>> stage 4.3: make dependencies >>>> stage 4.4: building everything >>>> World build completed on Tue May 25 14:45:12 UTC 2010 > TB --- 2010-05-25 14:45:12 - generating LINT kernel config > TB --- 2010-05-25 14:45:12 - cd /src/sys/pc98/conf > TB --- 2010-05-25 14:45:12 - /usr/bin/make -B LINT > TB --- 2010-05-25 14:45:12 - building LINT kernel > TB --- 2010-05-25 14:45:12 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2010-05-25 14:45:12 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2010-05-25 14:45:12 - TARGET=3Dpc98 > TB --- 2010-05-25 14:45:12 - TARGET_ARCH=3Di386 > TB --- 2010-05-25 14:45:12 - TZ=3DUTC > TB --- 2010-05-25 14:45:12 - __MAKE_CONF=3D/dev/null > TB --- 2010-05-25 14:45:12 - cd /src > TB --- 2010-05-25 14:45:12 - /usr/bin/make -B buildkernel KERNCONF=3DLINT >>>> Kernel build for LINT started on Tue May 25 14:45:12 UTC 2010 >>>> stage 1: configuring the kernel >>>> stage 2.1: cleaning up the object tree >>>> stage 2.2: rebuilding the object tree >>>> stage 2.3: build tools >>>> stage 3.1: making dependencies >>>> stage 3.2: building everything >>>> Kernel build for LINT completed on Tue May 25 15:07:19 UTC 2010 > TB --- 2010-05-25 15:07:19 - building GENERIC kernel > TB --- 2010-05-25 15:07:19 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2010-05-25 15:07:19 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2010-05-25 15:07:19 - TARGET=3Dpc98 > TB --- 2010-05-25 15:07:19 - TARGET_ARCH=3Di386 > TB --- 2010-05-25 15:07:19 - TZ=3DUTC > TB --- 2010-05-25 15:07:19 - __MAKE_CONF=3D/dev/null > TB --- 2010-05-25 15:07:19 - cd /src > TB --- 2010-05-25 15:07:19 - /usr/bin/make -B buildkernel KERNCONF=3DGENE= RIC >>>> Kernel build for GENERIC started on Tue May 25 15:07:19 UTC 2010 >>>> stage 1: configuring the kernel >>>> stage 2.1: cleaning up the object tree >>>> stage 2.2: rebuilding the object tree >>>> stage 2.3: build tools >>>> stage 3.1: making dependencies >>>> stage 3.2: building everything > [...] > :> hack.c > cc -shared -nostdlib hack.c -o hack.So > rm -f hack.c > MAKE=3D/usr/bin/make sh /src/sys/conf/newvers.sh GENERIC > cc -c -O -pipe =A0-std=3Dc99 -g -Wall -Wredundant-decls -Wnested-externs = -Wstrict-prototypes =A0-Wmissing-prototypes -Wpointer-arith -Winline -Wcast= -qual =A0-Wundef -Wno-pointer-sign -fformat-extensions -nostdinc =A0-I. -I/= src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -inc= lude opt_global.h -fno-common -finline-limit=3D8000 --param inline-unit-gro= wth=3D100 --param large-function-growth=3D1000 =A0-mno-align-long-strings -= mpreferred-stack-boundary=3D2 =A0-mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mn= o-sse3 -ffreestanding -fstack-protector -Werror =A0vers.c > linking kernel.debug > mca.o(.text+0x1627): In function `mca_init': > /src/sys/i386/i386/mca.c:786: undefined reference to `lapic_enable_cmc' > *** Error code 1 > > Stop in /obj/pc98/src/sys/GENERIC. Just wonder why apic is still commented out in pc98's GENERIC. Is there a reason to keep things intact? It was inherited from i386 port in time when it was commented out. --=20 wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Tue May 25 16:43:02 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4480A106566B; Tue, 25 May 2010 16:43:02 +0000 (UTC) (envelope-from millenia2000@hotmail.com) Received: from bay0-omc3-s3.bay0.hotmail.com (bay0-omc3-s3.bay0.hotmail.com [65.54.190.141]) by mx1.freebsd.org (Postfix) with ESMTP id 281B88FC22; Tue, 25 May 2010 16:43:01 +0000 (UTC) Received: from BAY126-W9 ([65.54.190.189]) by bay0-omc3-s3.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 25 May 2010 09:31:02 -0700 Message-ID: X-Originating-IP: [153.31.113.21] From: Sean Cavanaugh To: , Date: Tue, 25 May 2010 12:31:01 -0400 Importance: Normal In-Reply-To: References: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de>, <13F8E068-61AE-4670-86B8-B09C3BC00B86@gsoft.com.au>, MIME-Version: 1.0 X-OriginalArrivalTime: 25 May 2010 16:31:02.0184 (UTC) FILETIME=[AA233A80:01CAFC27] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: "freebsd-current@freebsd.org" , rwatson@freebsd.org Subject: RE: AppleTalk status 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, 25 May 2010 16:43:02 -0000 > > On 25/05/2010=2C at 20:55=2C Stefan Bethke wrote: > >> I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when tha= t comes out the next couple of days)=2C and I'm wondering what state AppleT= alk support is in these days. Is anybody still using it=2C or would now be = the time to make all AppleTalk support in that port optional=2C and just fo= cus on the file server component? > >>=20 > >> I haven't used AppleTalk for at least eight years now=2C and I don't q= uite see which setting it still would be used in nowadays... > >=20 > > I use it so I can back my Macbook Pro to my FreeBSD server on a ZFS par= tition.. > > (But that is all) >=20 > You're using the sys/netatalk AppleTalk protocol for that=2C or TCP? The = netatalk port's afpd (Apple File Protocol daemon) can speak AFP over both D= DP/ASP and TCP=2C and I'll keep afpd working over TCP of course. I'm talkin= g about disabling AppleTalk protocol support. >=20 >=20 I think that making it optional would be smartest choice. I think only peop= le with older equipment that cannot do TCP would need it and that most like= ly is a select few. definitely better than flat out removing completely. =20 _________________________________________________________________ The New Busy is not the too busy. Combine all your e-mail accounts with Hot= mail. http://www.windowslive.com/campaign/thenewbusy?tile=3Dmultiaccount&ocid=3DP= ID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4= From owner-freebsd-current@FreeBSD.ORG Tue May 25 16:48:33 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 69573106564A; Tue, 25 May 2010 16:48:33 +0000 (UTC) (envelope-from julian@elischer.org) Received: from out-0.mx.aerioconnect.net (outj.internet-mail-service.net [216.240.47.233]) by mx1.freebsd.org (Postfix) with ESMTP id 488058FC22; Tue, 25 May 2010 16:48:33 +0000 (UTC) Received: from idiom.com (postfix@mx0.idiom.com [216.240.32.160]) by out-0.mx.aerioconnect.net (8.13.8/8.13.8) with ESMTP id o4PGmVpU007392; Tue, 25 May 2010 09:48:32 -0700 X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e X-Client-Authorized: MaGic Cook1e Received: from julian-mac.elischer.org (h-67-100-89-137.snfccasy.static.covad.net [67.100.89.137]) by idiom.com (Postfix) with ESMTP id 1E0782D601B; Tue, 25 May 2010 09:48:30 -0700 (PDT) Message-ID: <4BFBFF6A.1090807@elischer.org> Date: Tue, 25 May 2010 09:48:42 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Stefan Bethke References: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> In-Reply-To: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 216.240.47.51 Cc: freebsd-current Current , Robert Watson Subject: Re: AppleTalk status 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, 25 May 2010 16:48:33 -0000 On 5/25/10 4:25 AM, Stefan Bethke wrote: > Hi, > > I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when > that comes out the next couple of days), and I'm wondering what > state AppleTalk support is in these days. Is anybody still using > it, or would now be the time to make all AppleTalk support in that > port optional, and just focus on the file server component? > > I haven't used AppleTalk for at least eight years now, and I don't > quite see which setting it still would be used in nowadays... I did the original port to freeBSD (from a netbsd port from memory) I haven't checked recently but it was used by several companies running legacy stuff in some industrial control situations. In any case it's good having a working example of another protocol as the world is getting a bit too focused on IP these days and having a different protocol in the sources keeps us honest. > Thanks, > Stefan > From owner-freebsd-current@FreeBSD.ORG Tue May 25 16:50:03 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A80BC1065674 for ; Tue, 25 May 2010 16:50:03 +0000 (UTC) (envelope-from rwatson@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 81AFF8FC16 for ; Tue, 25 May 2010 16:50:03 +0000 (UTC) Received: from [192.168.33.146] (lapwing-gw-1.csx.cam.ac.uk [131.111.1.66]) by cyrus.watson.org (Postfix) with ESMTPSA id 6F11F46B53; Tue, 25 May 2010 12:50:02 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: "Robert N. M. Watson" In-Reply-To: <4BFBFF6A.1090807@elischer.org> Date: Tue, 25 May 2010 17:50:00 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> <4BFBFF6A.1090807@elischer.org> To: Julian Elischer X-Mailer: Apple Mail (2.1078) Cc: freebsd-current Current , Stefan Bethke Subject: Re: AppleTalk status 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, 25 May 2010 16:50:03 -0000 On 25 May 2010, at 17:48, Julian Elischer wrote: >> I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when >> that comes out the next couple of days), and I'm wondering what >> state AppleTalk support is in these days. Is anybody still using >> it, or would now be the time to make all AppleTalk support in that >> port optional, and just focus on the file server component? >>=20 >> I haven't used AppleTalk for at least eight years now, and I don't >> quite see which setting it still would be used in nowadays... >=20 > I did the original port to freeBSD (from a netbsd port from memory) > I haven't checked recently but it was used by several companies = running legacy stuff in some industrial control situations. > In any case it's good having a working example of another protocol > as the world is getting a bit too focused on IP these days > and having a different protocol in the sources keeps us honest. FWIW, I have no intention of removing the kernel support for appletalk = (or, perhaps more properly, ethertalk). It does want to be changed to = use our link layer improvements in 8.x, but what is there today works = fine and should continue to work fine for the forseeable future. = Virtualizing for VIMAGE will probably take someone a couple of = afternoons, and I tentatively plan to do it "at some point" before 9.0. Robert= From owner-freebsd-current@FreeBSD.ORG Tue May 25 17:39:53 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 734791065670 for ; Tue, 25 May 2010 17:39:53 +0000 (UTC) (envelope-from super_bisquit@yahoo.com) Received: from n5-vm0.bullet.mail.gq1.yahoo.com (n5-vm0.bullet.mail.gq1.yahoo.com [67.195.8.62]) by mx1.freebsd.org (Postfix) with SMTP id 40F3E8FC18 for ; Tue, 25 May 2010 17:39:53 +0000 (UTC) Received: from [67.195.9.81] by n5.bullet.mail.gq1.yahoo.com with NNFMP; 25 May 2010 17:26:19 -0000 Received: from [98.137.27.216] by t1.bullet.mail.gq1.yahoo.com with NNFMP; 25 May 2010 17:26:19 -0000 Received: from [127.0.0.1] by omp126.mail.gq1.yahoo.com with NNFMP; 25 May 2010 17:26:19 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 755557.82436.bm@omp126.mail.gq1.yahoo.com Received: (qmail 64791 invoked by uid 60001); 25 May 2010 17:26:19 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1274808379; bh=FM2bV20knigEYLjeHSVMS0kgLpVo60xA2P/QgdfxL1g=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=ug0IvYwe3orUMnuN+fzQW8Ka0E1wIXhSGSCH7yz4iTGRNRseeLD7knc2ooF8F2wYQxMnGwf3OGxvqupz0kML0SWtxZYtizXjmLUS89YGCltMzySnjZnSHdvW7nboa/iGIOSK1t0UH0oI9eb3dHiebZyEeAsCF7sWOnnwCLIMAxI= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=B33J6KFcpunKBt7EzIQs2dqfo/GT7NBcH6UdI48cAFdNMBz2x0mt4w38RkWEBe7wSwSC2piKqfpFATEo0Z67y+ILUsGF6BITK2tDmxepQWUpgOKGkcvliVEz+IPkCkIdQCLjW2qjn6qY22HWXvulORmRdRsF36l2Bfv0ssHB+bo=; Message-ID: <632584.63233.qm@web110101.mail.gq1.yahoo.com> X-YMail-OSG: TwnpShcVM1nC.EqowN3W0mAFpqyiQmZYCmUC19Ue0MQV.77 BPiju17R2Ctk3SEhwyudE2eqD9jHoM3gxej_JB50NJXPYVvZqjExcHhq_kWY wzW2t1ZUMbMPUUMa77TDVMIDSEqBgkzLOzaaIbZco_X5bpkFmG0XZ58zLuXe myWifaJPL2jMKGlcpSy7X6GsyRhcCEQPrWmRoCebFaBslFk4jP2k7LIHp1Yx swVtvtMg0RWMadDERxdJssn2HLN8v82t0kPxXaHrVGTniWhVOLk0jmhUlWNH 4LrjtQmI- Received: from [98.252.40.146] by web110101.mail.gq1.yahoo.com via HTTP; Tue, 25 May 2010 10:26:19 PDT X-Mailer: YahooMailClassic/11.0.8 YahooMailWebService/0.8.103.269680 Date: Tue, 25 May 2010 10:26:19 -0700 (PDT) From: Super Biscuit To: Gerd Truschinski In-Reply-To: <4BFBC027.8090504@truschinski.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org Subject: Re: No internet with snapshots 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, 25 May 2010 17:39:53 -0000 --- On Tue, 5/25/10, Gerd Truschinski wrote: From: Gerd Truschinski Subject: No internet with snapshots To: current@freebsd.org Date: Tuesday, May 25, 2010, 12:18 PM Hi there, I tried to install the latest FreeBSD-9.0-CURRENT-201005-amd64-bootonly.iso. FreeBSD is starting, sysinstall is running. I want to install from ftp.freebsd.org. Therefor I try to set the _Media Typ_ in the _Options Editor_. I select the only Network Interface, a nfe, no IP6 but DHCP. I get an IP address from my Router and then I get a "Cannot resolv hostname ftp.freebsd.org". This seems to happen with older snapshots also. What could I do. What information did you need? /gT/ _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" I usually bring up the interface and do the base install from the CD. You can then do what you need- users, root, basic services- and then reboot without the media in the machine. Use mount -t cd9660 -o /dev/mount /soft/mount and extract with sh path/binary.sh. I did this with a PowerPC snapshot and it worked. From owner-freebsd-current@FreeBSD.ORG Tue May 25 17:42:51 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 614BF1065670 for ; Tue, 25 May 2010 17:42:51 +0000 (UTC) (envelope-from super_bisquit@yahoo.com) Received: from n4.bullet.mail.gq1.yahoo.com (n4.bullet.mail.gq1.yahoo.com [67.195.9.84]) by mx1.freebsd.org (Postfix) with SMTP id 30B3C8FC16 for ; Tue, 25 May 2010 17:42:51 +0000 (UTC) Received: from [67.195.9.83] by n4.bullet.mail.gq1.yahoo.com with NNFMP; 25 May 2010 17:30:22 -0000 Received: from [98.137.27.209] by t3.bullet.mail.gq1.yahoo.com with NNFMP; 25 May 2010 17:30:22 -0000 Received: from [127.0.0.1] by omp119.mail.gq1.yahoo.com with NNFMP; 25 May 2010 17:30:22 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 251026.24811.bm@omp119.mail.gq1.yahoo.com Received: (qmail 29463 invoked by uid 60001); 25 May 2010 17:30:22 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1274808622; bh=3pXoSip5YgHI+iIs7TArsh95t8j5BLJCHPsqIMszIx0=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=ncIsA3Tb6DAiWuCDJm5ygZxLnsa0MgaR2vFzRNLxU4rlUfChqZsMETJP1edxl5oJ/lQU0X+ghifmQmumyW+MKlax7Vzmk3Vwi20UWf/3gXQDCt76O2lJIHp5Kz2I2KisRW2J57nm6r0Cu3os2G44fh9Ehi/B4WRbxwDQgnkvKPg= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=fAzHvqg1D0Q8+QdbmEYu2B3gPqcsP+fvwwiszsdmtwxbWP6IRj6OFRFbbIZFpjSgFWlkQMqdUbPL0k8Uk73ypI7ONpmf54AqXVWCjhTurEb0Aob81NwRApq+9sxaaevr2IK1VChDEK7mENEF1FWWgkmi2rEk3HgDli3mBPYbsEk=; Message-ID: <59130.28866.qm@web110109.mail.gq1.yahoo.com> X-YMail-OSG: .EF7SeIVM1kZAunyGhDuH8f0QEStSABLi._ICJpwv8xZL10 a4xHgCFVZqtbJ5RLAt4KJcOjwpYykjTNB8..QkZLIDJ_cSWF72.OM8mRd1yO Z7uiSeVeSZFpBogOXrvN9XwqqFWtKA.N7LZZ67pBDLzBCFTCktm4roPTo7PM p2PbmwhsMgHZQLqf8KqPR6rRMMR9i2.DUi3m1AOw1IyA7Y3VrTs1eIOF5qhA jOzfAVNzeQ_v.kTctmG6vd6ib4S.p7x1z.EQ7KkhM4xlxX2HgvxN4LhP.B.r zp0nsZHM- Received: from [98.252.40.146] by web110109.mail.gq1.yahoo.com via HTTP; Tue, 25 May 2010 10:30:21 PDT X-Mailer: YahooMailClassic/11.0.8 YahooMailWebService/0.8.103.269680 Date: Tue, 25 May 2010 10:30:21 -0700 (PDT) From: Super Biscuit To: Gerd Truschinski In-Reply-To: <4BFBC027.8090504@truschinski.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org Subject: Re: No internet with snapshots 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, 25 May 2010 17:42:51 -0000 --- On Tue, 5/25/10, Gerd Truschinski wrote: From: Gerd Truschinski Subject: No internet with snapshots To: current@freebsd.org Date: Tuesday, May 25, 2010, 12:18 PM Hi there, I tried to install the latest FreeBSD-9.0-CURRENT-201005-amd64-bootonly.iso. FreeBSD is starting, sysinstall is running. I want to install from ftp.freebsd.org. Therefor I try to set the _Media Typ_ in the _Options Editor_. I select the only Network Interface, a nfe, no IP6 but DHCP. I get an IP address from my Router and then I get a "Cannot resolv hostname ftp.freebsd.org". This seems to happen with older snapshots also. What could I do. What information did you need? /gT/ _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" I forgot to add. Use CD1 for a base system. You will also need to go into sysinstall and choose ftp passive mode. This can be done with the first reboot. From owner-freebsd-current@FreeBSD.ORG Tue May 25 21:00:29 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 84FF5106564A; Tue, 25 May 2010 21:00:29 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 184528FC12; Tue, 25 May 2010 21:00:28 +0000 (UTC) Received: by qyk11 with SMTP id 11so8318558qyk.13 for ; Tue, 25 May 2010 14:00:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:cc:content-type; bh=vdr4DHOhNrs8NOJMxLaBA1CPSQsA3XJHl6HGtNvrdWc=; b=MalzczYB+HhB47H7tW00lbdJrqM4cXMmU6QYdkyFA7SJo+haMQBcNGEDOel4F7DRLM lgPzyc48Le6HBqEOMZY6T42bwYv+96jdmKvFGIo58JDDeg9RFulWO1dg8O2jHKahMFt/ zuQQQynwXpL9XPDodhzqx/KjfirOx/1Cpb9lc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=LUALN0ImTeI+n5Nz7AS55NzB3CPhzeMvC5mWsHRysA6jKgptBdK81I0Hp3wOxgZHIY sbgVJ9a2+AZU12gnnwpfjhEDD6DD+EhiGVPyCYim4PeUGvTBJXT8iAWPDy3xg8qZC69c 9hGu6KkkgTyxsglklL3vYNhLl5MN9An64+j8o= MIME-Version: 1.0 Received: by 10.229.28.74 with SMTP id l10mr1675899qcc.142.1274821227509; Tue, 25 May 2010 14:00:27 -0700 (PDT) Received: by 10.229.190.83 with HTTP; Tue, 25 May 2010 14:00:27 -0700 (PDT) Date: Tue, 25 May 2010 14:00:27 -0700 Message-ID: From: Garrett Cooper To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Cc: alc@freebsd.org, Konstantin Belousov Subject: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 25 May 2010 21:00:29 -0000 Just reporting the fact that nvidia-driver 195.22 is horribly broken between r206173 and r208486 (my machine consistency livelocks at X11 startup); the latest driver is still broken as well with the same symptoms. I realize that's a huge revision difference, and I'll definitely try and track down the root cause via a binary search, but I wanted to make sure that other folks knew of the issue and don't upgrade and their systems break horribly as well. I suspect that the locking changes are causing the issue, but I don't have any hard data to backup my claim at this time. Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Tue May 25 22:48:57 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7B90106566B for ; Tue, 25 May 2010 22:48:57 +0000 (UTC) (envelope-from vrachil@gmail.com) Received: from mail-fx0-f54.google.com (mail-fx0-f54.google.com [209.85.161.54]) by mx1.freebsd.org (Postfix) with ESMTP id 74D9B8FC0C for ; Tue, 25 May 2010 22:48:57 +0000 (UTC) Received: by fxm17 with SMTP id 17so981236fxm.13 for ; Tue, 25 May 2010 15:48:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=ZtqWeuqOBQR5D+HSPKRxPJu90eAfHaub7nTaX/z1+f4=; b=mkvGOZt42KOVmkR4Wm6Tw8nz8hYjJMq8vPteEbX81PJ/fA9PF9Hz4LafTshl3q6O0b +saIZbnjH2Cpl6765C1x8Nf3wLINpBN6rmp/HWIgtg6kW5kF0smDNYiQnbFZy12L9yoo 7WTkr/EEQbuOmO7tmSxmfMjtrJH/1ftR9nrdo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=BOoBQuSUEmJcq6PqU0PYCrw95IyKyVqg7DH17g8PcdgpbFzBUVpAzk3XMG6LOcH60u PN84NMqY511/r9fGT5+Mj5yxV4sS9e35f37OaTHWM/qrinmzuKh4u0gzc/C93uvQ4yjN q2+Kg4avNYWgWMsUa7RMoY19q/ExRALbi9c8I= Received: by 10.223.98.24 with SMTP id o24mr6807715fan.29.1274826004292; Tue, 25 May 2010 15:20:04 -0700 (PDT) Received: from [192.168.2.64] (77.49.1.2.dsl.dyn.forthnet.gr [77.49.1.2]) by mx.google.com with ESMTPS id 2sm26850877fav.1.2010.05.25.15.20.02 (version=SSLv3 cipher=RC4-MD5); Tue, 25 May 2010 15:20:03 -0700 (PDT) Message-ID: <4BFC4DB2.6030106@gmail.com> Date: Wed, 26 May 2010 01:22:42 +0300 From: Vrachnis Ilias-Dimitrios User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100330 Shredder/3.0.4 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: In-Reply-To: X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 25 May 2010 22:48:58 -0000 On 05/26/2010 12:00 AM, Garrett Cooper wrote: > Just reporting the fact that nvidia-driver 195.22 is horribly > broken between r206173 and r208486 (my machine consistency livelocks > at X11 startup); the latest driver is still broken as well with the > same symptoms. I realize that's a huge revision difference, and I'll > definitely try and track down the root cause via a binary search, but > I wanted to make sure that other folks knew of the issue and don't > upgrade and their systems break horribly as well. > I suspect that the locking changes are causing the issue, but I > don't have any hard data to backup my claim at this time. > Thanks, > -Garrett same goes for nvidia-driver-96. nv seems unaffected though. (thankfully i rarely need X on that machine) From owner-freebsd-current@FreeBSD.ORG Tue May 25 23:17:42 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1C621065674 for ; Tue, 25 May 2010 23:17:42 +0000 (UTC) (envelope-from marcelorossi@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 5C64E8FC18 for ; Tue, 25 May 2010 23:17:42 +0000 (UTC) Received: by qyk11 with SMTP id 11so8512939qyk.13 for ; Tue, 25 May 2010 16:17:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=ltQfpwRLrcXk03L+mI9ZBRx5P4wK47OdqeR/M5Xb0qE=; b=h0Rwzz3F51V0KawdJS5sHUacTQzxTgZP+gWZSMU+FS7ncRSzGRWp8u/MB+WrL+rngv rv1XxfVEM3FacRlOmtpZqTnOXohS/FWXKFJG8RZGfot63i+0YzYuk3ud+BKXDjCspKRg Rm0u5iyUNqHARifB2JrSp2dcqAa3C8x6hZN2A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=gL9dJtKReXMEL9+nxcM82vlGBoVyiwT8FfpLu1OweQWE9f7W59TwUPdlMWUNT35yk3 40CsEYox4Ut9O2Vpa3XKj0kdJe5DOoAo5wdcUTklsWk3IZJrsMbsmsSdHWsYfEGb1j17 eO2aA4TJUkPDq2/bddgiAi5avLtT67UvR4BrY= MIME-Version: 1.0 Received: by 10.229.187.135 with SMTP id cw7mr1698403qcb.15.1274827779868; Tue, 25 May 2010 15:49:39 -0700 (PDT) Received: by 10.229.80.6 with HTTP; Tue, 25 May 2010 15:49:39 -0700 (PDT) In-Reply-To: References: Date: Tue, 25 May 2010 19:49:39 -0300 Message-ID: From: "Marcelo/Porks" To: Jeff Roberson Content-Type: text/plain; charset=ISO-8859-1 Cc: current@freebsd.org Subject: Re: SUJ Changes 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, 25 May 2010 23:17:42 -0000 On 5/17/10, Jeff Roberson wrote: > I fixed the sparse inode tunefs bug and changed the tunefs behavior based > on discussions here on current@. Hopefully this works for everyone. Hi! I tested the r208241 and it's seems to be ok but this calls my atention to other thing: Could I disable de SU when the SUJ is enabled? I did some tests and seems that I can do this (logs bellow). But will SUJ work properly with SU disabled? Thanks. ========== logs ============ BARAD-DUR# uname -a FreeBSD BARAD-DUR.BUTECO 9.0-CURRENT FreeBSD 9.0-CURRENT #11 r208366: Thu May 20 21:52:36 BRT 2010 porks@BARAD-DUR.BUTECO:/usr/obj/usr/src/sys/BARAD-DUR i386 BARAD-DUR# df -h /dev/ad2s1d Filesystem Size Used Avail Capacity Mounted on /dev/ad2s1d 72G 54G 12G 82% BARAD-DUR# df -h | grep /dev/ad2s1d BARAD-DUR# tunefs -p /dev/ad2s1d tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) disabled tunefs: gjournal: (-J) disabled tunefs: maximum blocks per file in a cylinder group: (-e) 2048 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: optimization preference: (-o) time tunefs: volume label: (-L) BARAD-DUR# tunefs -j enable /dev/ad2s1d Using inode 13 in cg 0 for 33554432 byte journal tunefs: soft updates journaling set BARAD-DUR# tunefs -p /dev/ad2s1d tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) enabled tunefs: soft update journaling: (-j) enabled tunefs: gjournal: (-J) disabled tunefs: maximum blocks per file in a cylinder group: (-e) 2048 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: optimization preference: (-o) time tunefs: volume label: (-L) BARAD-DUR# tunefs -n disable /dev/ad2s1d tunefs: soft updates cleared BARAD-DUR# tunefs -p /dev/ad2s1d tunefs: POSIX.1e ACLs: (-a) disabled tunefs: NFSv4 ACLs: (-N) disabled tunefs: MAC multilabel: (-l) disabled tunefs: soft updates: (-n) disabled tunefs: soft update journaling: (-j) enabled tunefs: gjournal: (-J) disabled tunefs: maximum blocks per file in a cylinder group: (-e) 2048 tunefs: average file size: (-f) 16384 tunefs: average number of files in a directory: (-s) 64 tunefs: minimum percentage of free space: (-m) 8% tunefs: optimization preference: (-o) time tunefs: volume label: (-L) BARAD-DUR# mount /dev/ad2s1d BARAD-DUR# df -h | grep /dev/ad2s1d /dev/ad2s1d 72G 54G 12G 82% /mnt/ad2s1d BARAD-DUR# ls -lah /mnt/ad2s1d/test.log ls: /mnt/ad2s1d/test.log: No such file or directory BARAD-DUR# echo "test data" >> /mnt/ad2s1d/test.log BARAD-DUR# ls -lah /mnt/ad2s1d/test.log -rw-r--r-- 1 root wheel 10B May 25 19:36 /mnt/ad2s1d/test.log BARAD-DUR# cat /mnt/ad2s1d/test.log test data BARAD-DUR# > I have one bad perf bug and one journal overflow bug left to resolve. > Please keeps the reports coming and thank you for your help. > > Thanks, > Jeff > > ---------- Forwarded message ---------- > Date: Tue, 18 May 2010 01:45:28 +0000 (UTC) > From: Jeff Roberson > To: src-committers@freebsd.org, svn-src-all@freebsd.org, > svn-src-head@freebsd.org > Subject: svn commit: r208241 - head/sbin/tunefs > > Author: jeff > Date: Tue May 18 01:45:28 2010 > New Revision: 208241 > URL: http://svn.freebsd.org/changeset/base/208241 > > Log: > - Round up the journal size to the block size so we don't confuse fsck. > > Reported by: Mikolaj Golub > > - Only require 256k of blocks per-cg when trying to allocate contiguous > journal blocks. The storage may not actually be contiguous but is at > least within one cg. > - When disabling SUJ leave SU enabled and report this to the user. It > is expected that users will upgrade SU filesystems to SUJ and want > a similar downgrade path. > > Modified: > head/sbin/tunefs/tunefs.c > > Modified: head/sbin/tunefs/tunefs.c > ============================================================================== > --- head/sbin/tunefs/tunefs.c Tue May 18 00:46:15 2010 (r208240) > +++ head/sbin/tunefs/tunefs.c Tue May 18 01:45:28 2010 (r208241) > @@ -358,10 +358,12 @@ main(int argc, char *argv[]) > warnx("%s remains unchanged as disabled", name); > } else { > journal_clear(); > - sblock.fs_flags &= ~(FS_DOSOFTDEP | FS_SUJ); > + sblock.fs_flags &= ~FS_SUJ; > sblock.fs_sujfree = 0; > - warnx("%s cleared, " > - "remove .sujournal to reclaim space", name); > + warnx("%s cleared but soft updates still set.", > + name); > + > + warnx("remove .sujournal to reclaim space"); > } > } > } > @@ -546,7 +548,7 @@ journal_balloc(void) > * Try to minimize fragmentation by requiring a minimum > * number of blocks present. > */ > - if (cgp->cg_cs.cs_nbfree > 128 * 1024 * 1024) > + if (cgp->cg_cs.cs_nbfree > 256 * 1024) > break; > if (contig == 0 && cgp->cg_cs.cs_nbfree) > break; > @@ -906,6 +908,8 @@ journal_alloc(int64_t size) > if (size / sblock.fs_fsize > sblock.fs_fpg) > size = sblock.fs_fpg * sblock.fs_fsize; > size = MAX(SUJ_MIN, size); > + /* fsck does not support fragments in journal files. */ > + size = roundup(size, sblock.fs_bsize); > } > resid = blocks = size / sblock.fs_bsize; > if (sblock.fs_cstotal.cs_nbfree < blocks) { > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Marcelo Rossi "This e-mail is provided "AS IS" with no warranties, and confers no rights." From owner-freebsd-current@FreeBSD.ORG Wed May 26 05:17:27 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3DD2D106564A for ; Wed, 26 May 2010 05:17:27 +0000 (UTC) (envelope-from kientzle@freebsd.org) Received: from monday.kientzle.com (kientzle.com [66.166.149.50]) by mx1.freebsd.org (Postfix) with ESMTP id 3CFC08FC21 for ; Wed, 26 May 2010 05:17:25 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.3/8.14.3) id o4Q5Hg4w009410 for current@freebsd.org; Wed, 26 May 2010 05:17:42 GMT (envelope-from kientzle@freebsd.org) Received: from horton.x.kientzle.com (fw2.kientzle.com [10.123.1.2]) by kientzle.com with SMTP id bzvhqrkm9cmipe7esnap358brs; for current@freebsd.org; Wed, 26 May 2010 05:17:41 +0000 (UTC) (envelope-from kientzle@freebsd.org) Message-ID: <4BFCAEE2.2030601@freebsd.org> Date: Tue, 25 May 2010 22:17:22 -0700 From: Tim Kientzle User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.8.1.23) Gecko/20100314 SeaMonkey/1.1.18 MIME-Version: 1.0 To: "'current@FreeBSD.org'" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: SUJ Rocks! 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, 26 May 2010 05:17:27 -0000 After seeing Kirk's presentation on SUJ at BSDCan, I decided to give it a try. Wow. The reality of being able to pull the plug (or watch an experimental kernel patch go down in flames) and simply power back on and have a running system with a sane clean filesystem almost immediately is truly amazing. Kudos to Jeff for his work on this. Tim From owner-freebsd-current@FreeBSD.ORG Wed May 26 10:22:05 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18B2A1065670 for ; Wed, 26 May 2010 10:22:05 +0000 (UTC) (envelope-from spambox@haruhiism.net) Received: from mail.haruhiism.net (mail.fujibayashi.jp [IPv6:2001:470:9954:ffff::2]) by mx1.freebsd.org (Postfix) with ESMTP id C51428FC21 for ; Wed, 26 May 2010 10:22:04 +0000 (UTC) Received: from [IPv6:2001:470:9f2d:0:1::1] (omoikane.gensokyo.fujibayashi.jp [IPv6:2001:470:9f2d:0:1::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.haruhiism.net (Postfix) with ESMTPSA id B8BE9196CA0 for ; Wed, 26 May 2010 19:22:02 +0900 (JST) Message-ID: <4BFCF64A.1030709@haruhiism.net> Date: Wed, 26 May 2010 14:22:02 +0400 From: Kamigishi Rei User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.10) Gecko/20100512 Lightning/1.0b1 Thunderbird/3.0.5 ThunderBrowse/3.2.8.1 MIME-Version: 1.0 To: FreeBSD Current References: <4BFB968C.40108@haruhiism.net> In-Reply-To: <4BFB968C.40108@haruhiism.net> X-Enigmail-Version: 1.0.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA3BF501EA3F747A128819722" Subject: Re: MROUTING issues (r200287) with multicast routing daemons 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, 26 May 2010 10:22:05 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA3BF501EA3F747A128819722 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 25.05.2010 13:21, Kamigishi Rei wrote > device pf > device pflog > device pfsync > options ALTQ > options ALTQ_HFSC > options DEVICE_POLLING > options MROUTING > =20 Tried reproducing with options KDB options DDB options KDB_UNATTENDED options WITNESS options WITNESS_SKIPSPIN options INVARIANTS options INVARIANT_SUPPORT and without FLOWTABLE. Instead of fatal trap 12 I get trap 9, general protection fault now (same for the three attempts I made), and the vmcore file seems unusable:= remilia@gw ~ % sudo kgdb /usr/obj/usr/src/sys/Eientei/kernel.debug /var/crash/vmcore.1 (skip) This GDB was configured as "amd64-marcel-freebsd"... Cannot access memory at address 0xfff08de9ff6d62dc (kgdb) bt #0 0x0000000000000000 in ?? () Cannot access memory at address 0x0 Can someone suggest a way to properly debug this? --=20 Kamigishi Rei KREI-RIPE --------------enigA3BF501EA3F747A128819722 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJL/PZLAAoJEPAgyqbDpP+ekzoIALr6sIg0HZ2Ku43L+Wtc/1qH rwhwVYDm3q2FiZHNnU6EGsHZWV8+rJGVi+2ZeO76nZ8aGhmpC+yCiDge7gusLdg1 hTv0DMErSr30YtVkJi/WDK/wkOOcLmp/jZq7uXOudJYwixPiMTCD71J6b4zDFSie 9KRgmvmuBQC6u6XVGFYSA3Fwt4UuzeINEmUt9GpJ3tF6cZftQv5rg71YM6atKgb/ mp689YJiXV3bUKwL3saQ1Fy3lFXFK9+DGhH/ap7Umrk75w251g+NBNEVjIPaVR5l WqY69JcabS9Z269P9SM4ejMnjxzFraN/6138QgxHE/3/prs7eackoYckskpb8SE= =l/4M -----END PGP SIGNATURE----- --------------enigA3BF501EA3F747A128819722-- From owner-freebsd-current@FreeBSD.ORG Wed May 26 11:12:14 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C63D1065670 for ; Wed, 26 May 2010 11:12:14 +0000 (UTC) (envelope-from nyan@jp.FreeBSD.org) Received: from sakura.ccs.furiru.org (sakura.ccs.furiru.org [IPv6:2001:2f0:104:8060::1]) by mx1.freebsd.org (Postfix) with ESMTP id CC9588FC15 for ; Wed, 26 May 2010 11:12:13 +0000 (UTC) Received: from localhost (authenticated bits=0) by sakura.ccs.furiru.org (unknown) with ESMTP id o4QBC8A5053119; Wed, 26 May 2010 20:12:11 +0900 (JST) (envelope-from nyan@jp.FreeBSD.org) Date: Wed, 26 May 2010 20:12:08 +0900 (JST) Message-Id: <20100526.201208.27863135.nyan@jp.FreeBSD.org> To: pluknet@gmail.com From: TAKAHASHI Yoshihiro In-Reply-To: References: <201005251513.o4PFD490071374@freebsd-current.sentex.ca> X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: current@freebsd.org Subject: Re: [head tinderbox] failure on i386/pc98 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, 26 May 2010 11:12:14 -0000 In article pluknet writes: > Just wonder why apic is still commented out in pc98's GENERIC. > Is there a reason to keep things intact? > It was inherited from i386 port in time when it was commented out. Because, most of pc98 does not have APIC. In addition, SMP support on pc98 is broken. --- TAKAHASHI Yoshihiro From owner-freebsd-current@FreeBSD.ORG Wed May 26 14:22:03 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B175A1065677 for ; Wed, 26 May 2010 14:22:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 834A98FC1E for ; Wed, 26 May 2010 14:22:03 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 33C8D46B45; Wed, 26 May 2010 10:22:03 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 639FF8A021; Wed, 26 May 2010 10:22:02 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 26 May 2010 08:26:30 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <20100525100404.GF287@rvdp.org> In-Reply-To: <20100525100404.GF287@rvdp.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201005260826.30963.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 26 May 2010 10:22:02 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Ronald van der Pol Subject: Re: panic: lapic_enable_cmc: missing APIC 0 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, 26 May 2010 14:22:03 -0000 On Tuesday 25 May 2010 6:04:04 am Ronald van der Pol wrote: > I am trying to move to current from 8.1-PRERELEASE. After > buildworld, buildkernel, installkernel and rebooting I get: > > panic: lapic_enable_cmc: missing APIC 0 > cpuid = 0 > KDB: enter : panic Try this patch: Index: i386/i386/mca.c =================================================================== --- i386/i386/mca.c (revision 208556) +++ i386/i386/mca.c (working copy) @@ -812,6 +812,19 @@ load_cr4(rcr4() | CR4_MCE); } +/* + * The machine check registers for the BSP cannot be initialized until + * the local APIC is initialized. This happens at SI_SUB_CPU, + * SI_ORDER_SECOND. + */ +static void +mca_init_bsp(void *arg __unused) +{ + + mca_init(); +} +SYSINIT(mca_init_bsp, SI_SUB_CPU, SI_ORDER_ANY, mca_init_bsp, NULL); + /* Called when a machine check exception fires. */ int mca_intr(void) Index: i386/i386/machdep.c =================================================================== --- i386/i386/machdep.c (revision 208545) +++ i386/i386/machdep.c (working copy) @@ -328,7 +328,6 @@ #ifndef XEN cpu_setregs(); #endif - mca_init(); } /* Index: amd64/amd64/mca.c =================================================================== --- amd64/amd64/mca.c (revision 208545) +++ amd64/amd64/mca.c (working copy) @@ -789,6 +789,19 @@ load_cr4(rcr4() | CR4_MCE); } +/* + * The machine check registers for the BSP cannot be initialized until + * the local APIC is initialized. This happens at SI_SUB_CPU, + * SI_ORDER_SECOND. + */ +static void +mca_init_bsp(void *arg __unused) +{ + + mca_init(); +} +SYSINIT(mca_init_bsp, SI_SUB_CPU, SI_ORDER_ANY, mca_init_bsp, NULL); + /* Called when a machine check exception fires. */ int mca_intr(void) Index: amd64/amd64/machdep.c =================================================================== --- amd64/amd64/machdep.c (revision 208545) +++ amd64/amd64/machdep.c (working copy) @@ -285,7 +285,6 @@ vm_pager_bufferinit(); cpu_setregs(); - mca_init(); } /* -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed May 26 16:11:01 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 86A7D106564A for ; Wed, 26 May 2010 16:11:01 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 48F918FC0A for ; Wed, 26 May 2010 16:11:00 +0000 (UTC) Received: by pva4 with SMTP id 4so918166pva.13 for ; Wed, 26 May 2010 09:11:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id :disposition-notification-to:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=lHU4Ivxl8I/46w5fl9h5APkofDlOeUOdAAcaGDTPfQY=; b=eEwTl3wT5uzeJt1QcQGsrTgybQKR4qK2ydtiu/uToaG9R0aG1yUV008kBM26uUC2Ah tJlaJC5ohNO5rcJSpeDGChgTaa3TG5Mb5EaPhgu+/R4jvsshoTmIP+wMbzz4LrLa6cgU ORPd9UGahKKoZ9STPSJwj+iC/gkMDzgQUAm8c= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:disposition-notification-to:date:from:user-agent :mime-version:to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; b=LGTRN82TueWOpoqcOoFMzN3cvOTwmKzqNgihdTZBVU5uT+QrTYppEm0G+rrowDDiyz s6UEX7s1DAM5N+NiA8fPdhPVXCBREjOQIx+zTw8z10en9Ka+Gk4cCZ+et+ut0ASwotLA BU3ylAibdUKtkpK5Igh0XYZRyNHkqBm6o2NIc= Received: by 10.142.201.12 with SMTP id y12mr104290wff.174.1274890260473; Wed, 26 May 2010 09:11:00 -0700 (PDT) Received: from beastie.micom.mng.net ([202.179.21.129]) by mx.google.com with ESMTPS id d16sm1813804wam.0.2010.05.26.09.10.49 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 26 May 2010 09:10:53 -0700 (PDT) Message-ID: <4BFD4806.8070001@gmail.com> Date: Thu, 27 May 2010 00:10:46 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.23 (X11/20091011) MIME-Version: 1.0 To: PseudoCylon References: <16641.96608.qm@web51806.mail.re2.yahoo.com> <4B9FA3E0.4050702@micom.mng.net> <633929.41041.qm@web51802.mail.re2.yahoo.com> <4BA22B8D.9030700@micom.mng.net> <375331.74876.qm@web51804.mail.re2.yahoo.com> <4BA38B26.6050208@micom.mng.net> <989377.89740.qm@web51802.mail.re2.yahoo.com> <4BAE01AC.7000509@gmail.com> <623907.37074.qm@web51803.mail.re2.yahoo.com> <4BB3575D.4040506@gmail.com> <87836.79143.qm@web51804.mail.re2.yahoo.com> <4BBB372C.1060302@gmail.com> <665283.95271.qm@web51802.mail.re2.yahoo.com> <4BBDEC8F.9050803@gmail.com> <490521.32714.qm@web51804.mail.re2.yahoo.com> <4BD307DE.5080507@gmail.com> <332448.8676.qm@web51801.mail.re2.yahoo.com> <4BD3F2D4.8000007@gmail.com> <702632.81988.qm@web51803.mail.re2.yahoo.com> <4BDEE393.4080206@gmail.com> <660085.11669.qm@web51802.mail.re2.yahoo.com> In-Reply-To: <660085.11669.qm@web51802.mail.re2.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Ganbold Tsagaankhuu , freebsd-current@freebsd.org Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless 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, 26 May 2010 16:11:01 -0000 AK-san, Did you test run driver in bridge mode? I have following setup: # ifconfig arge0: flags=8943 metric 0 mtu 1500 options=80000 ether 00:15:6d:c1:c7:77 inet 192.168.1.41 netmask 0xffffff00 broadcast 192.168.1.255 media: Ethernet autoselect (100baseTX ) status: active run0: flags=8a43 metric 0 mtu 2290 ether 00:22:cf:03:e0:30 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running wlan0: flags=8943 metric 0 mtu 1500 ether 00:22:cf:03:e0:30 inet 192.168.1.42 netmask 0xffffff00 broadcast 192.168.1.255 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: running ssid bsd channel 6 (2437 MHz 11g) bssid 00:22:cf:03:e0:30 country US authmode WPA1+WPA2/802.11i privacy MIXED deftxkey 3 TKIP 2:128-bit TKIP 3:128-bit txpower 0 scanvalid 60 protmode CTS wme dtimperiod 1 -dfs bridge0: flags=8843 metric 0 mtu 1500 ether 36:7d:f9:e1:56:c9 inet 192.168.1.43 netmask 0xffffff00 broadcast 192.168.1.255 id 00:15:6d:c1:c7:77 priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200 root id 00:15:6d:c1:c7:77 priority 32768 ifcost 0 port 0 member: arge0 flags=1e7 ifmaxaddr 0 port 1 priority 128 path cost 200000 proto rstp role designated state forwarding member: wlan0 flags=167 ifmaxaddr 0 port 9 priority 128 path cost 370370 proto rstp role designated state forwarding It looks like either bridge or wlan/run driver is not forwarding/allowing incoming arp request for wireless client behind this access point. Wireless client is not getting any arp request and after sending several arp request to wireless client ADSL modem stops responding (had to restart modem). Any idea? thanks, Ganbold PseudoCylon wrote: > ----- Original Message ---- > >> From: Ganbold >> To: PseudoCylon >> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu >> Sent: Mon, May 3, 2010 8:54:11 AM >> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless >> >> Thanks a lot, works no problem so far here with bridge (no >> auth/hostapd/WPA2). >> > > >> rspro# uname -an FreeBSD rspro 9.0-CURRENT FreeBSD 9.0-CURRENT #64 r207140M: Mon May 3 >> 21:49:50 ULAT 2010 >> tsgan@beastie:/usr/obj/mips/usr/mysrc/sys/RSPRO_AR71XX mips >> > > > Yes! finally. I'm so happy to hear. > > If there are any other bugs, please report. I'll wait a few days before submit the changes just to make sure every thing is fine on your routerstation. > > Thank you for testing the driver several times and your patient. > > AK > > > > > -- I wouldn't be so paranoid if you weren't all out to get me!! From owner-freebsd-current@FreeBSD.ORG Wed May 26 16:23:13 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D36C106567B; Wed, 26 May 2010 16:23:13 +0000 (UTC) (envelope-from alc@cs.rice.edu) Received: from mail.cs.rice.edu (mail.cs.rice.edu [128.42.1.31]) by mx1.freebsd.org (Postfix) with ESMTP id 1BE0D8FC16; Wed, 26 May 2010 16:23:12 +0000 (UTC) Received: from mail.cs.rice.edu (localhost.localdomain [127.0.0.1]) by mail.cs.rice.edu (Postfix) with ESMTP id 8B4362C2D0C; Wed, 26 May 2010 11:23:12 -0500 (CDT) X-Virus-Scanned: by amavis-2.4.0 at mail.cs.rice.edu Received: from mail.cs.rice.edu ([127.0.0.1]) by mail.cs.rice.edu (mail.cs.rice.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 5P-GSZKG0gPp; Wed, 26 May 2010 11:23:04 -0500 (CDT) Received: from adsl-216-63-78-18.dsl.hstntx.swbell.net (adsl-216-63-78-18.dsl.hstntx.swbell.net [216.63.78.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cs.rice.edu (Postfix) with ESMTP id 699C22C2BF0; Wed, 26 May 2010 11:23:04 -0500 (CDT) Message-ID: <4BFD4AE6.5040105@cs.rice.edu> Date: Wed, 26 May 2010 11:23:02 -0500 From: Alan Cox User-Agent: Thunderbird 2.0.0.24 (X11/20100501) MIME-Version: 1.0 To: Garrett Cooper References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, FreeBSD Current , Konstantin Belousov Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 26 May 2010 16:23:13 -0000 Garrett Cooper wrote: > Just reporting the fact that nvidia-driver 195.22 is horribly > broken between r206173 and r208486 (my machine consistency livelocks > at X11 startup); the latest driver is still broken as well with the > same symptoms. I realize that's a huge revision difference, and I'll > definitely try and track down the root cause via a binary search, but > I wanted to make sure that other folks knew of the issue and don't > upgrade and their systems break horribly as well. > I suspect that the locking changes are causing the issue, but I > don't have any hard data to backup my claim at this time. > I'm sure they are. The Nvidia driver directly accesses low-level virtual memory structures on which the synchronization rules have changed. (In contrast, the Xorg dri drivers in our source tree are using higher-level interfaces that have remained stable.) I don't think that a binary search is needed. The lock assertion failures should indicate most if not all of the changes that are needed in the driver. When Kip got this process started, he bumped FreeBSD_version, so it should be possible to condition the locking changes in the driver. Good luck! Alan From owner-freebsd-current@FreeBSD.ORG Wed May 26 16:51:48 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25E691065674; Wed, 26 May 2010 16:51:48 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 92C548FC08; Wed, 26 May 2010 16:51:47 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o4QGpsKi008710 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 May 2010 19:51:54 +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.14.4/8.14.4) with ESMTP id o4QGpfLP086183; Wed, 26 May 2010 19:51:41 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o4QGpfwn086182; Wed, 26 May 2010 19:51:41 +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, 26 May 2010 19:51:41 +0300 From: Kostik Belousov To: Alan Cox Message-ID: <20100526165141.GF83316@deviant.kiev.zoral.com.ua> References: <4BFD4AE6.5040105@cs.rice.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="qbWslfj5jix8J1iW" Content-Disposition: inline In-Reply-To: <4BFD4AE6.5040105@cs.rice.edu> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: alc@freebsd.org, Garrett Cooper , FreeBSD Current Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 26 May 2010 16:51:48 -0000 --qbWslfj5jix8J1iW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 26, 2010 at 11:23:02AM -0500, Alan Cox wrote: > Garrett Cooper wrote: > > Just reporting the fact that nvidia-driver 195.22 is horribly > >broken between r206173 and r208486 (my machine consistency livelocks > >at X11 startup); the latest driver is still broken as well with the > >same symptoms. I realize that's a huge revision difference, and I'll > >definitely try and track down the root cause via a binary search, but > >I wanted to make sure that other folks knew of the issue and don't > >upgrade and their systems break horribly as well. > > I suspect that the locking changes are causing the issue, but I > >don't have any hard data to backup my claim at this time. > > =20 >=20 > I'm sure they are. The Nvidia driver directly accesses low-level=20 > virtual memory structures on which the synchronization rules have=20 > changed. (In contrast, the Xorg dri drivers in our source tree are=20 > using higher-level interfaces that have remained stable.) >=20 > I don't think that a binary search is needed. The lock assertion=20 > failures should indicate most if not all of the changes that are needed= =20 > in the driver. When Kip got this process started, he bumped=20 > FreeBSD_version, so it should be possible to condition the locking=20 > changes in the driver. >=20 > Good luck! I did a quick glance over the driver, try this: http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch I did not even compiled the patched driver. --qbWslfj5jix8J1iW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkv9UZwACgkQC3+MBN1Mb4jx+ACfcqwH2Tj17rNp/JhcVogezvoz cYAAnjS5f1sblFbGHuH/u3Xry7N2lqKt =bT4i -----END PGP SIGNATURE----- --qbWslfj5jix8J1iW-- From owner-freebsd-current@FreeBSD.ORG Wed May 26 17:42:00 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 853AC106564A; Wed, 26 May 2010 17:42:00 +0000 (UTC) (envelope-from alc@cs.rice.edu) Received: from mail.cs.rice.edu (mail.cs.rice.edu [128.42.1.31]) by mx1.freebsd.org (Postfix) with ESMTP id 4A1128FC1F; Wed, 26 May 2010 17:42:00 +0000 (UTC) Received: from mail.cs.rice.edu (localhost.localdomain [127.0.0.1]) by mail.cs.rice.edu (Postfix) with ESMTP id BE6902C2D08; Wed, 26 May 2010 12:41:59 -0500 (CDT) X-Virus-Scanned: by amavis-2.4.0 at mail.cs.rice.edu Received: from mail.cs.rice.edu ([127.0.0.1]) by mail.cs.rice.edu (mail.cs.rice.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id aLVfEFp7fcah; Wed, 26 May 2010 12:41:52 -0500 (CDT) Received: from adsl-216-63-78-18.dsl.hstntx.swbell.net (adsl-216-63-78-18.dsl.hstntx.swbell.net [216.63.78.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cs.rice.edu (Postfix) with ESMTP id BCFA62C2C59; Wed, 26 May 2010 12:41:51 -0500 (CDT) Message-ID: <4BFD5D5F.8090106@cs.rice.edu> Date: Wed, 26 May 2010 12:41:51 -0500 From: Alan Cox User-Agent: Thunderbird 2.0.0.24 (X11/20100501) MIME-Version: 1.0 To: Kostik Belousov References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> In-Reply-To: <20100526165141.GF83316@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, Garrett Cooper , FreeBSD Current Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 26 May 2010 17:42:00 -0000 Kostik Belousov wrote: > On Wed, May 26, 2010 at 11:23:02AM -0500, Alan Cox wrote: > >> Garrett Cooper wrote: >> >>> Just reporting the fact that nvidia-driver 195.22 is horribly >>> broken between r206173 and r208486 (my machine consistency livelocks >>> at X11 startup); the latest driver is still broken as well with the >>> same symptoms. I realize that's a huge revision difference, and I'll >>> definitely try and track down the root cause via a binary search, but >>> I wanted to make sure that other folks knew of the issue and don't >>> upgrade and their systems break horribly as well. >>> I suspect that the locking changes are causing the issue, but I >>> don't have any hard data to backup my claim at this time. >>> >>> >> I'm sure they are. The Nvidia driver directly accesses low-level >> virtual memory structures on which the synchronization rules have >> changed. (In contrast, the Xorg dri drivers in our source tree are >> using higher-level interfaces that have remained stable.) >> >> I don't think that a binary search is needed. The lock assertion >> failures should indicate most if not all of the changes that are needed >> in the driver. When Kip got this process started, he bumped >> FreeBSD_version, so it should be possible to condition the locking >> changes in the driver. >> >> Good luck! >> > > I did a quick glance over the driver, try this: > http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch > I did not even compiled the patched driver. > The second snippet looks weird to me, specifically, seeing an explicit unwiring before a kmem_free() call. Should the corresponding allocation be using kmem_alloc_attr()? Alan From owner-freebsd-current@FreeBSD.ORG Wed May 26 17:58:24 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0899F106564A for ; Wed, 26 May 2010 17:58:24 +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 ESMTP id A3F8B8FC13 for ; Wed, 26 May 2010 17:58:23 +0000 (UTC) Received: (qmail 29123 invoked by uid 399); 26 May 2010 17:58:22 -0000 Received: from localhost (HELO ?192.168.0.145?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 26 May 2010 17:58:22 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4BFD613B.6050508@FreeBSD.org> Date: Wed, 26 May 2010 10:58:19 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Kostik Belousov References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> In-Reply-To: <20100526165141.GF83316@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, Garrett Cooper , FreeBSD Current , Alan Cox Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 26 May 2010 17:58:24 -0000 On 5/26/2010 9:51 AM, Kostik Belousov wrote: > > I did a quick glance over the driver, try this: > http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch > I did not even compiled the patched driver. Kostik, Thanks for taking a look at this! I sent the following to Alexey recently in regards to his query about whether or not the new version of the driver works. Maybe it will assist you: Good news, it was a simple version bump to upgrade to 195.36.24. Bad news, no improvement. Under very light load (X11 using openbox, Alpine mail client) it lasted about an hour. As soon as I started adding more stress (firefox, flash, etc.) it wedged after about 30 minutes (total uptime, 90 minutes). This was still on the old kernel that I've been using in combination with 195.22: FreeBSD dougb.net 9.0-CURRENT FreeBSD 9.0-CURRENT #3 r207134: Thu Apr 29 23:14:20 PDT 2010 i386 The combination of the r207134 kernel and the 195.22 version of the driver has been very stable for me. If I try to go newer than that in either category I get lockups and/or panics. hth, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Wed May 26 18:56:54 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6181E106566B; Wed, 26 May 2010 18:56:54 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id EE2FD8FC18; Wed, 26 May 2010 18:56:53 +0000 (UTC) Received: by qyk11 with SMTP id 11so10003081qyk.13 for ; Wed, 26 May 2010 11:56:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=bagglSD+YaR3pD8h0/2OEZ58Hn6kS7jIDGZM0rKLp3I=; b=KuGbFFSvN/5CR9RsICouFA65t9Xg5gqlFZWGYDWh+tjM2RHIwdDV8f2Vn1yIAR0Gqd Q8BDBIG3EjSYsgAZpwu+tnY7znd8+ZIezjY1z6qfMIdEx5jRRs5S+RKnLmjNTP72Is+2 4xCHq+rMbx38JPpugXTKMNKADAtQHthHaV/UI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Rx3a1MJHPdFg6o3Jtol3+sme0SyNDMVRGtvkViiFYUpUVLV/EkcOPoVoojfS32c5Fj wiikNWO6tWc2fzCLrcEyBH58I+JewcX9+aL9sKr+RwZZK/vYNoaVprKNZGLzghEtihts Rn+sU50KSfGQVvPH7dbHPP6NM/MXogz+g76vY= MIME-Version: 1.0 Received: by 10.224.35.89 with SMTP id o25mr5141486qad.209.1274900206714; Wed, 26 May 2010 11:56:46 -0700 (PDT) Received: by 10.229.190.83 with HTTP; Wed, 26 May 2010 11:56:46 -0700 (PDT) In-Reply-To: <4BFD5D5F.8090106@cs.rice.edu> References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> <4BFD5D5F.8090106@cs.rice.edu> Date: Wed, 26 May 2010 11:56:46 -0700 Message-ID: From: Garrett Cooper To: Alan Cox Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Kostik Belousov , alc@freebsd.org, FreeBSD Current Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 26 May 2010 18:56:54 -0000 On Wed, May 26, 2010 at 10:41 AM, Alan Cox wrote: > Kostik Belousov wrote: >> >> On Wed, May 26, 2010 at 11:23:02AM -0500, Alan Cox wrote: >> >>> >>> Garrett Cooper wrote: >>> >>>> >>>> =A0 Just reporting the fact that nvidia-driver 195.22 is horribly >>>> broken between r206173 and r208486 (my machine consistency livelocks >>>> at X11 startup); the latest driver is still broken as well with the >>>> same symptoms. I realize that's a huge revision difference, and I'll >>>> definitely try and track down the root cause via a binary search, but >>>> I wanted to make sure that other folks knew of the issue and don't >>>> upgrade and their systems break horribly as well. >>>> =A0 I suspect that the locking changes are causing the issue, but I >>>> don't have any hard data to backup my claim at this time. >>>> >>> >>> I'm sure they are. =A0The Nvidia driver directly accesses low-level vir= tual >>> memory structures on which the synchronization rules have changed. =A0(= In >>> contrast, the Xorg dri drivers in our source tree are using higher-leve= l >>> interfaces that have remained stable.) >>> >>> I don't think that a binary search is needed. =A0The lock assertion >>> failures should indicate most if not all of the changes that are needed= in >>> the driver. =A0When Kip got this process started, he bumped FreeBSD_ver= sion, >>> so it should be possible to condition the locking changes in the driver= . >>> >>> Good luck! >>> >> >> I did a quick glance over the driver, try this: >> http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch >> I did not even compiled the patched driver. >> > > The second snippet looks weird to me, specifically, seeing an explicit > unwiring before a kmem_free() call. =A0Should the corresponding allocatio= n be > using kmem_alloc_attr()? I'm by no means an expert in this area, but isn't removing the locking on free a bad thing? Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Wed May 26 19:24:32 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CE2C8106564A; Wed, 26 May 2010 19:24:32 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 692EA8FC15; Wed, 26 May 2010 19:24:31 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o4QJObwS020994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 May 2010 22:24:37 +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.14.4/8.14.4) with ESMTP id o4QJOOYg098525; Wed, 26 May 2010 22:24:24 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o4QJONb1098524; Wed, 26 May 2010 22:24:23 +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, 26 May 2010 22:24:23 +0300 From: Kostik Belousov To: Alan Cox Message-ID: <20100526192423.GI83316@deviant.kiev.zoral.com.ua> References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> <4BFD5D5F.8090106@cs.rice.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gqUrV6DUXoHnB0ku" Content-Disposition: inline In-Reply-To: <4BFD5D5F.8090106@cs.rice.edu> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: alc@freebsd.org, Garrett Cooper , FreeBSD Current Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 26 May 2010 19:24:33 -0000 --gqUrV6DUXoHnB0ku Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, May 26, 2010 at 12:41:51PM -0500, Alan Cox wrote: > Kostik Belousov wrote: > >On Wed, May 26, 2010 at 11:23:02AM -0500, Alan Cox wrote: > > =20 > >>Garrett Cooper wrote: > >> =20 > >>> Just reporting the fact that nvidia-driver 195.22 is horribly > >>>broken between r206173 and r208486 (my machine consistency livelocks > >>>at X11 startup); the latest driver is still broken as well with the > >>>same symptoms. I realize that's a huge revision difference, and I'll > >>>definitely try and track down the root cause via a binary search, but > >>>I wanted to make sure that other folks knew of the issue and don't > >>>upgrade and their systems break horribly as well. > >>> I suspect that the locking changes are causing the issue, but I > >>>don't have any hard data to backup my claim at this time. > >>>=20 > >>> =20 > >>I'm sure they are. The Nvidia driver directly accesses low-level=20 > >>virtual memory structures on which the synchronization rules have=20 > >>changed. (In contrast, the Xorg dri drivers in our source tree are=20 > >>using higher-level interfaces that have remained stable.) > >> > >>I don't think that a binary search is needed. The lock assertion=20 > >>failures should indicate most if not all of the changes that are needed= =20 > >>in the driver. When Kip got this process started, he bumped=20 > >>FreeBSD_version, so it should be possible to condition the locking=20 > >>changes in the driver. > >> > >>Good luck! > >> =20 > > > >I did a quick glance over the driver, try this: > >http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch > >I did not even compiled the patched driver. > > =20 >=20 > The second snippet looks weird to me, specifically, seeing an explicit=20 > unwiring before a kmem_free() call. Should the corresponding allocation= =20 > be using kmem_alloc_attr()? I have no idea about lifecycle of the unmanaged pages in nvidia driver. The weird thing is that the pages are wired explicitely by a call to vm_page_wire(9) at all. The pages are allocated by contigmapping(9), that already wires the region. Possibly this is done to signify two references to the page, second one is by sg list that is stuffed with the pages immediately after. My goal was to fix an obvious misusage of the KPI. --gqUrV6DUXoHnB0ku Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkv9dWcACgkQC3+MBN1Mb4g/mACgssoSAXdMO04ZozaB32rEVnzz lXgAoOsdiRkILJZcqFL019XiOqj4q2zy =G5bi -----END PGP SIGNATURE----- --gqUrV6DUXoHnB0ku-- From owner-freebsd-current@FreeBSD.ORG Wed May 26 19:56:10 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F2927106566C for ; Wed, 26 May 2010 19:56:10 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5CD7B8FC15 for ; Wed, 26 May 2010 19:56:10 +0000 (UTC) Received: by wyj26 with SMTP id 26so1762357wyj.13 for ; Wed, 26 May 2010 12:56:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=0ZY6C6+6sPeVzR/xIAbNruXgyymB4spcMnH/h5VTk+M=; b=ZpLY5Rn2R2DEpvjATKKvPQsog4ah0axjCHHigjpnLVAQ6gYS45FojOhaoGgos3CPdB DJPnkhuzWv2vomq0OncrikrwHtsnidYi+4bGu71NBgVwL5vzH5XyKxbPlKX6cOoXQHnA X/d+g5f40PmTZUYn2laqpJdCLJicRTXWogunc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LNRbkBn/+TNrCUg28DgXNOS5Ie7glHwJA1gyjEoTmQCySgAseqb9kkE/RISOHDulZb f9SeUUyuzTS1EBO5NWzAl5LP+sipdSNR2O9NZFHBsxNtfvuEWOz3l4fFSdaheTzVRcH1 Q2Q7cwA9vIkdii2KsY/WF7F/DBrDFIt7+1bfU= MIME-Version: 1.0 Received: by 10.227.141.201 with SMTP id n9mr9114205wbu.31.1274903769364; Wed, 26 May 2010 12:56:09 -0700 (PDT) Received: by 10.216.36.135 with HTTP; Wed, 26 May 2010 12:56:09 -0700 (PDT) In-Reply-To: References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> <4BFD5D5F.8090106@cs.rice.edu> Date: Wed, 26 May 2010 15:56:09 -0400 Message-ID: From: Ryan Stone To: Garrett Cooper Content-Type: text/plain; charset=ISO-8859-1 Cc: Kostik Belousov , alc@freebsd.org, FreeBSD Current , Alan Cox Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 26 May 2010 19:56:11 -0000 > I'm by no means an expert in this area, but isn't removing the locking > on free a bad thing? Looking at the code, it seems that vm_page_unwire() only requires the page to be locked if it is managed. As it was acquired by contigmalloc, the page should be unmanaged so that should be ok. I am confused as to why vm_page_unwire() does not require the page to be locked if the page is unmanaged. What is synchronizing the accesses to m->wire_count? From owner-freebsd-current@FreeBSD.ORG Wed May 26 21:01:57 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD88A1065686 for ; Wed, 26 May 2010 21:01:57 +0000 (UTC) (envelope-from yr.retarded@gmail.com) Received: from mail-pz0-f183.google.com (mail-pz0-f183.google.com [209.85.222.183]) by mx1.freebsd.org (Postfix) with ESMTP id A13038FC36 for ; Wed, 26 May 2010 21:01:57 +0000 (UTC) Received: by pzk13 with SMTP id 13so5189284pzk.13 for ; Wed, 26 May 2010 14:01:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:cc:content-type :content-transfer-encoding; bh=crlaGvNOQEk2K0QGpJVKuS8Yz4HYm5Re7MRwn6JXwq8=; b=pSl16scxadg3UpfmqjG3NJBSOzA9vBo3eOHjXD9Kyadrk8FGg4teIlTh36LJSVXQ+9 nFtBPK+D3y7hslknvRwMonHNWYexbckg/uJ338X9T8h84xTKNsTzFZkfzDYA4OfiW4nM lco+0W4MS4klcLx8bqV8jlEjQzYkuhLY+yrEc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:cc :content-type:content-transfer-encoding; b=bgQ/CVNQh2pefVGIfuW2Iv/CsWPeX8NlZQz+gz5EH5BZ8vjFqdjQyPNzoiKZ6VCsO7 lAAkypmSXWQu1JzLtr/CliF9uMlmLS709r4vrAcz+YwduImyNd8gNH/v1VugRm7ZUAHD QUaS4daTuqV1ohRxjueHAvnRyoy05cwWlrb7A= MIME-Version: 1.0 Received: by 10.143.27.3 with SMTP id e3mr6347400wfj.224.1274907716715; Wed, 26 May 2010 14:01:56 -0700 (PDT) Received: by 10.142.49.1 with HTTP; Wed, 26 May 2010 14:01:56 -0700 (PDT) In-Reply-To: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> References: <7DB9656A-44DF-4A37-B9A4-652451234FEE@lassitu.de> Date: Wed, 26 May 2010 16:01:56 -0500 Message-ID: From: Chris Ruiz Cc: freebsd-current Current Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: AppleTalk status 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, 26 May 2010 21:01:57 -0000 On Tue, May 25, 2010 at 6:25 AM, Stefan Bethke wrote: > Hi, > > I'm working on updating net/netatalk to version 2.1 (or 2.1.1 when that c= omes out the next couple of days), and I'm wondering what state AppleTalk s= upport is in these days. =A0Is anybody still using it, or would now be the = time to make all AppleTalk support in that port optional, and just focus on= the file server component? > > I haven't used AppleTalk for at least eight years now, and I don't quite = see which setting it still would be used in nowadays... Snow Leopard (10.6) dropped support for AppleTalk, so I think that making it compile-time optional would be the best way to go. Just my 2c. Thanks -- Chris ----------------------------------------- http://twitter.com/chrisattack http://chrisattack.com From owner-freebsd-current@FreeBSD.ORG Wed May 26 21:55:09 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C98B1106564A; Wed, 26 May 2010 21:55:09 +0000 (UTC) (envelope-from alc@cs.rice.edu) Received: from mail.cs.rice.edu (mail.cs.rice.edu [128.42.1.31]) by mx1.freebsd.org (Postfix) with ESMTP id 9CE838FC19; Wed, 26 May 2010 21:55:09 +0000 (UTC) Received: from mail.cs.rice.edu (localhost.localdomain [127.0.0.1]) by mail.cs.rice.edu (Postfix) with ESMTP id 449D32C2CB6; Wed, 26 May 2010 16:55:09 -0500 (CDT) X-Virus-Scanned: by amavis-2.4.0 at mail.cs.rice.edu Received: from mail.cs.rice.edu ([127.0.0.1]) by mail.cs.rice.edu (mail.cs.rice.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id NHgp+Smg0BR0; Wed, 26 May 2010 16:55:01 -0500 (CDT) Received: from [10.209.194.87] (unknown [10.209.194.87]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.cs.rice.edu (Postfix) with ESMTP id 692DC2C2C59; Wed, 26 May 2010 16:55:01 -0500 (CDT) Message-ID: <4BFD98AF.9030503@cs.rice.edu> Date: Wed, 26 May 2010 16:54:55 -0500 From: Alan Cox User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Ryan Stone References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> <4BFD5D5F.8090106@cs.rice.edu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Kostik Belousov , Garrett Cooper , FreeBSD Current , alc@freebsd.org Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 26 May 2010 21:55:09 -0000 On 5/26/2010 2:56 PM, Ryan Stone wrote: >> I'm by no means an expert in this area, but isn't removing the locking >> on free a bad thing? >> > Looking at the code, it seems that vm_page_unwire() only requires the > page to be locked if it is managed. As it was acquired by > contigmalloc, the page should be unmanaged so that should be ok. > > I am confused as to why vm_page_unwire() does not require the page to > be locked if the page is unmanaged. What is synchronizing the > accesses to m->wire_count? > You can think of unmanaged pages as being private. Not necessarily private to a thread or processor, but private to some entity, such as a particular process's page table. So, no one else, such as the page daemon, is going to be concurrently accessing the wire count field of the page, and thus, no page or page queues locking is needed. Alan From owner-freebsd-current@FreeBSD.ORG Wed May 26 22:52:18 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 321BC106567F for ; Wed, 26 May 2010 22:52:18 +0000 (UTC) (envelope-from marcelorossi@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id E08D88FC21 for ; Wed, 26 May 2010 22:52:17 +0000 (UTC) Received: by qyk11 with SMTP id 11so10342455qyk.13 for ; Wed, 26 May 2010 15:52:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=YgcVfk6peu2omgbfhWYI7iq+bjty5r/hRF6kcjshobg=; b=a5QEwwgKhyiyQs1omnYEVfqLfIQG972wGQD7yBDlgJ5dAU/xZKMIXbkwfzm5ilpk5d ITyaL1R2X//0HWnUNZ5GxjBtCn5EnghJos1tnnW15kGjzU1BZus5DBtwIEFWDtLjOZnq 1ganzhwMN1+U7QNIjSXJAgNVLz8J/Zoegj/9Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=LOs7qtlZNTWbzePMs1BH57CqVH0QMFfuOzmrdfuPIpIgIEt8cjXAHHmVlpvKNPJ6Aj TLOug7Ehby3ZG3Etx1yzFqwKu03cbpgsn0bGFHZcHmXdP/ctir1UzKY8wS87jI5cIOLK +J1Mnka+3sXVEFIMKRNodM7ggkuRoosWwHskc= MIME-Version: 1.0 Received: by 10.224.116.75 with SMTP id l11mr5189246qaq.300.1274914337325; Wed, 26 May 2010 15:52:17 -0700 (PDT) Received: by 10.229.80.6 with HTTP; Wed, 26 May 2010 15:52:17 -0700 (PDT) In-Reply-To: References: Date: Wed, 26 May 2010 19:52:17 -0300 Message-ID: From: "Marcelo/Porks" To: Jeff Roberson Content-Type: text/plain; charset=ISO-8859-1 Cc: current@freebsd.org Subject: Re: SUJ Changes 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, 26 May 2010 22:52:18 -0000 On 5/25/10, Marcelo/Porks wrote: > Hi! I tested the r208241 and it's seems to be ok but this calls my > atention to other thing: Could I disable de SU when the SUJ is > enabled? > > I did some tests and seems that I can do this (logs bellow). > > But will SUJ work properly with SU disabled? Hi guys. I'm not sure if I could call this a problem but I can disable SU when SUJ is enabled, so SUJ will remain enabled and SU will be disabled. #tunefs -j enable /dev/device #tunefs -n disable /dev/device I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the user disable SU. Maybe this will be useful for some of you. Thanks. Index: sbin/tunefs/tunefs.c =================================================================== --- sbin/tunefs/tunefs.c (revision 208580) +++ sbin/tunefs/tunefs.c (working copy) @@ -460,6 +460,14 @@ if ((~sblock.fs_flags & FS_DOSOFTDEP) == FS_DOSOFTDEP) warnx("%s remains unchanged as disabled", name); else { + /* also disable SUJ */ + if ((sblock.fs_flags & FS_SUJ) == FS_SUJ) { + warnx("soft updates journaling will be disabled too"); + journal_clear(); + sblock.fs_flags &= ~FS_SUJ; + sblock.fs_sujfree = 0; + warnx("remove .sujournal to reclaim space"); + } sblock.fs_flags &= ~FS_DOSOFTDEP; warnx("%s cleared", name); } -- Marcelo Rossi "This e-mail is provided "AS IS" with no warranties, and confers no rights." From owner-freebsd-current@FreeBSD.ORG Wed May 26 23:56:25 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7429A106566B for ; Wed, 26 May 2010 23:56:25 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 2757A8FC13 for ; Wed, 26 May 2010 23:56:24 +0000 (UTC) Received: by qyk11 with SMTP id 11so10430123qyk.13 for ; Wed, 26 May 2010 16:56:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=XWQD+UBwzJ38PCfXLQg69iTYKk+2KzJ+lhl1U0c7FWQ=; b=exM8RJF7ERVho8kT30d0b/ovYGh4EFII/UlsvK9rykx0cdlJUD3djsQM/b2F1nlTDh rfRz0gwr5gZl5H4dLj1HW73K4uf7/kP3vy7X3dUZPnvivixH8ZEC+KaNnUI0s69iIKuw HoAxhgRK3HNqGSy2n59LOXH0b0OSvFiAEtLd8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=pLzgjUw8mQQg7z6BZX6WNRQc+rtDNLmXtwS7EbAN2Ivb+6L2Io69QvPh+AANDp4S1E qWflDScx/xQomnFO1T6oiszhycN0gOnFicq26/xfaHKXYMsnhYFEGituppSAEbM5j7ti TtvECifdk9h5QylzQFLIPxZO0WvqCwd3aUndQ= MIME-Version: 1.0 Received: by 10.224.64.72 with SMTP id d8mr5517296qai.109.1274918184249; Wed, 26 May 2010 16:56:24 -0700 (PDT) Received: by 10.229.190.83 with HTTP; Wed, 26 May 2010 16:56:24 -0700 (PDT) In-Reply-To: References: Date: Wed, 26 May 2010 16:56:24 -0700 Message-ID: From: Garrett Cooper To: "Marcelo/Porks" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Jeff Roberson , current@freebsd.org Subject: Re: SUJ Changes 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, 26 May 2010 23:56:25 -0000 On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks wro= te: > On 5/25/10, Marcelo/Porks wrote: >> Hi! I tested the r208241 and it's seems to be ok but this calls my >> atention to other thing: Could I disable de SU when the SUJ is >> enabled? >> >> I did some tests and seems that I can do this (logs bellow). >> >> But will SUJ work properly with SU disabled? > > Hi guys. I'm not sure if I could call this a problem but I can disable > SU when SUJ is enabled, so SUJ will remain enabled and SU will be > disabled. > > #tunefs -j enable /dev/device > #tunefs -n disable /dev/device > > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the user > disable SU. Maybe this will be useful for some of you. > > Thanks. > > > Index: sbin/tunefs/tunefs.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(revision 208580) > +++ sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(working copy) > @@ -460,6 +460,14 @@ > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if ((~sblock.fs_flags & FS= _DOSOFTDEP) =3D=3D FS_DOSOFTDEP) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("%s = remains unchanged as disabled", name); > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0else { > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* also dis= able SUJ */ > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if ((sblock= .fs_flags & FS_SUJ) =3D=3D FS_SUJ) { > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 warnx("soft updates journaling > will be disabled too"); > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 journal_clear(); > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 sblock.fs_flags &=3D ~FS_SUJ; > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 sblock.fs_sujfree =3D 0; > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0= =A0 warnx("remove .sujournal to > reclaim space"); > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0sblock.fs_= flags &=3D ~FS_DOSOFTDEP; > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("%s = cleared", name); > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0} I think that it makes sense to have this as a force option as someone may want to retain their journal instead of disposing of it automatically. I think that the 2nd warnx should be the first warnx, and the 2nd warnx can be removed as it'll be quickly followed up by cleared. Changing `remove' to `removing' and changing `.sujournal' to journal would a) make the action more correct and b) make the concept more straightforward as to what's being removed, as Jeff or someone else may decide to remove or rename .sujournal in the future, and it's just another thing that users don't have to understand that aren't familiar with FreeBSD or SUJ. Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Thu May 27 00:59:33 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AE56C106566C for ; Thu, 27 May 2010 00:59:33 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-gx0-f224.google.com (mail-gx0-f224.google.com [209.85.217.224]) by mx1.freebsd.org (Postfix) with ESMTP id 4AE3D8FC0A for ; Thu, 27 May 2010 00:59:33 +0000 (UTC) Received: by gxk24 with SMTP id 24so3904974gxk.3 for ; Wed, 26 May 2010 17:59:32 -0700 (PDT) Received: by 10.150.183.11 with SMTP id g11mr126555ybf.66.1274921972241; Wed, 26 May 2010 17:59:32 -0700 (PDT) Received: from papi.localnet ([189.70.227.237]) by mx.google.com with ESMTPS id u2sm5371454ybh.15.2010.05.26.17.59.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 26 May 2010 17:59:31 -0700 (PDT) From: Mario Lobo To: freebsd-current@freebsd.org, current@freebsd.org Date: Wed, 26 May 2010 21:59:27 +0000 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201005262159.27350.lobo@bsd.com.br> Cc: Subject: Re: SUJ Changes 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, 27 May 2010 00:59:33 -0000 On Wednesday 26 May 2010 23:56:24 Garrett Cooper wrote: > On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks wrote: > > On 5/25/10, Marcelo/Porks wrote: > >> Hi! I tested the r208241 and it's seems to be ok but this calls my > >> atention to other thing: Could I disable de SU when the SUJ is > >> enabled? > >> > >> I did some tests and seems that I can do this (logs bellow). > >> > >> But will SUJ work properly with SU disabled? > > > > Hi guys. I'm not sure if I could call this a problem but I can disable > > SU when SUJ is enabled, so SUJ will remain enabled and SU will be > > disabled. > > > > #tunefs -j enable /dev/device > > #tunefs -n disable /dev/device > > > > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the user > > disable SU. Maybe this will be useful for some of you. > > > > Thanks. > > > > > > Index: sbin/tunefs/tunefs.c > > =================================================================== > > --- sbin/tunefs/tunefs.c (revision 208580) > > +++ sbin/tunefs/tunefs.c (working copy) > > @@ -460,6 +460,14 @@ > > if ((~sblock.fs_flags & FS_DOSOFTDEP) == > > FS_DOSOFTDEP) warnx("%s remains unchanged as disabled", name); else { > > + /* also disable SUJ */ > > + if ((sblock.fs_flags & FS_SUJ) == FS_SUJ) > > { + warnx("soft updates journaling > > will be disabled too"); > > + journal_clear(); > > + sblock.fs_flags &= ~FS_SUJ; > > + sblock.fs_sujfree = 0; > > + warnx("remove .sujournal to > > reclaim space"); > > + } > > sblock.fs_flags &= ~FS_DOSOFTDEP; > > warnx("%s cleared", name); > > } > > I think that it makes sense to have this as a force option as someone > may want to retain their journal instead of disposing of it > automatically. > > I think that the 2nd warnx should be the first warnx, and the 2nd > warnx can be removed as it'll be quickly followed up by > cleared. Changing `remove' to `removing' and changing `.sujournal' to > journal would a) make the action more correct and b) make the concept > more straightforward as to what's being removed, as Jeff or someone > else may decide to remove or rename .sujournal in the future, and it's > just another thing that users don't have to understand that aren't > familiar with FreeBSD or SUJ. > > Thanks, > -Garrett > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Is this available in 8-STABLE? Can it be? Can this be activated on my current installation without loosing data? Thanks, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] (99% winfoes FREE) From owner-freebsd-current@FreeBSD.ORG Thu May 27 01:25:34 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EBC711065672 for ; Thu, 27 May 2010 01:25:33 +0000 (UTC) (envelope-from lobo@bsd.com.br) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id AEE398FC14 for ; Thu, 27 May 2010 01:25:33 +0000 (UTC) Received: by gyh20 with SMTP id 20so4602201gyh.13 for ; Wed, 26 May 2010 18:25:33 -0700 (PDT) Received: by 10.150.183.11 with SMTP id g11mr126555ybf.66.1274921972241; Wed, 26 May 2010 17:59:32 -0700 (PDT) Received: from papi.localnet ([189.70.227.237]) by mx.google.com with ESMTPS id u2sm5371454ybh.15.2010.05.26.17.59.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 26 May 2010 17:59:31 -0700 (PDT) From: Mario Lobo To: freebsd-current@freebsd.org, current@freebsd.org Date: Wed, 26 May 2010 21:59:27 +0000 User-Agent: KMail/1.12.4 (FreeBSD/8.0-STABLE; KDE/4.3.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201005262159.27350.lobo@bsd.com.br> Cc: Subject: Re: SUJ Changes 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, 27 May 2010 01:25:34 -0000 On Wednesday 26 May 2010 23:56:24 Garrett Cooper wrote: > On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks wrote: > > On 5/25/10, Marcelo/Porks wrote: > >> Hi! I tested the r208241 and it's seems to be ok but this calls my > >> atention to other thing: Could I disable de SU when the SUJ is > >> enabled? > >> > >> I did some tests and seems that I can do this (logs bellow). > >> > >> But will SUJ work properly with SU disabled? > > > > Hi guys. I'm not sure if I could call this a problem but I can disable > > SU when SUJ is enabled, so SUJ will remain enabled and SU will be > > disabled. > > > > #tunefs -j enable /dev/device > > #tunefs -n disable /dev/device > > > > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the user > > disable SU. Maybe this will be useful for some of you. > > > > Thanks. > > > > > > Index: sbin/tunefs/tunefs.c > > =================================================================== > > --- sbin/tunefs/tunefs.c (revision 208580) > > +++ sbin/tunefs/tunefs.c (working copy) > > @@ -460,6 +460,14 @@ > > if ((~sblock.fs_flags & FS_DOSOFTDEP) == > > FS_DOSOFTDEP) warnx("%s remains unchanged as disabled", name); else { > > + /* also disable SUJ */ > > + if ((sblock.fs_flags & FS_SUJ) == FS_SUJ) > > { + warnx("soft updates journaling > > will be disabled too"); > > + journal_clear(); > > + sblock.fs_flags &= ~FS_SUJ; > > + sblock.fs_sujfree = 0; > > + warnx("remove .sujournal to > > reclaim space"); > > + } > > sblock.fs_flags &= ~FS_DOSOFTDEP; > > warnx("%s cleared", name); > > } > > I think that it makes sense to have this as a force option as someone > may want to retain their journal instead of disposing of it > automatically. > > I think that the 2nd warnx should be the first warnx, and the 2nd > warnx can be removed as it'll be quickly followed up by > cleared. Changing `remove' to `removing' and changing `.sujournal' to > journal would a) make the action more correct and b) make the concept > more straightforward as to what's being removed, as Jeff or someone > else may decide to remove or rename .sujournal in the future, and it's > just another thing that users don't have to understand that aren't > familiar with FreeBSD or SUJ. > > Thanks, > -Garrett > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > Is this available in 8-STABLE? Can it be? Can this be activated on my current installation without loosing data? Thanks, -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio.... YET!!] (99% winfoes FREE) From owner-freebsd-current@FreeBSD.ORG Thu May 27 01:57:22 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04CEE106564A for ; Thu, 27 May 2010 01:57:22 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id AF7438FC0A for ; Thu, 27 May 2010 01:57:21 +0000 (UTC) Received: by qyk11 with SMTP id 11so10592362qyk.13 for ; Wed, 26 May 2010 18:57:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=TZ1syBdi5942HR1LR9wJSMw4Y5qYNp02Dowiq9jHqr4=; b=oq+Fs3i56T2shC+IaFWcCsOIUCotlk8QpdUstus8mBGawm0l9zFUYDrWqcfeRwIpL4 /gA/3K8D96XtN69FCzMzA1oeYcJ4/uucpJgP62NVq1sG8Uix7CSpuN8T4DtPgDv926my wat/aPfJ5tuUyvJRpLNJH9vwTD2qFfxj5EqMI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mn3QRSdnQ5x3Q7AFEYM2Ks/WdEK0LLsT/PwE3i7CL/n4X48qh6BdJo68U6FbQx8pCd k8a2pl6KJ8+boWrcjrdPJAR0gOaHcvREhA7sQCDrIlmxXaqwWr/dCSFG/xrP0t7uDG3t Zadp/Yf0EYlefG9H303ulSjjQFG6Habt4FDA4= MIME-Version: 1.0 Received: by 10.229.95.137 with SMTP id d9mr2089125qcn.125.1274925440993; Wed, 26 May 2010 18:57:20 -0700 (PDT) Received: by 10.229.190.83 with HTTP; Wed, 26 May 2010 18:57:20 -0700 (PDT) In-Reply-To: <201005262159.27350.lobo@bsd.com.br> References: <201005262159.27350.lobo@bsd.com.br> Date: Wed, 26 May 2010 18:57:20 -0700 Message-ID: From: Garrett Cooper To: Mario Lobo Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: FreeBSD Current Subject: Re: SUJ Changes 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, 27 May 2010 01:57:22 -0000 On Wed, May 26, 2010 at 2:59 PM, Mario Lobo wrote: > On Wednesday 26 May 2010 23:56:24 Garrett Cooper wrote: >> On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks > wrote: >> > On 5/25/10, Marcelo/Porks wrote: >> >> Hi! I tested the r208241 and it's seems to be ok but this calls my >> >> atention to other thing: Could I disable de SU when the SUJ is >> >> enabled? >> >> >> >> I did some tests and seems that I can do this (logs bellow). >> >> >> >> But will SUJ work properly with SU disabled? >> > >> > Hi guys. I'm not sure if I could call this a problem but I can disable >> > SU when SUJ is enabled, so SUJ will remain enabled and SU will be >> > disabled. >> > >> > #tunefs -j enable /dev/device >> > #tunefs -n disable /dev/device >> > >> > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the user >> > disable SU. Maybe this will be useful for some of you. >> > >> > Thanks. >> > >> > >> > Index: sbin/tunefs/tunefs.c >> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> > --- sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(revision 208580) >> > +++ sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(working copy) >> > @@ -460,6 +460,14 @@ >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if ((~sblock.fs_flags &= FS_DOSOFTDEP) =3D=3D >> > FS_DOSOFTDEP) warnx("%s remains unchanged as disabled", name); else { >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* also = disable SUJ */ >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if ((sbl= ock.fs_flags & FS_SUJ) =3D=3D FS_SUJ) >> > { + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 warnx("soft updates journaling >> > will be disabled too"); >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 journal_clear(); >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 sblock.fs_flags &=3D ~FS_SUJ; >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 sblock.fs_sujfree =3D 0; >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 warnx("remove .sujournal to >> > reclaim space"); >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0sblock.= fs_flags &=3D ~FS_DOSOFTDEP; >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("= %s cleared", name); >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0} >> >> I think that it makes sense to have this as a force option as someone >> may want to retain their journal instead of disposing of it >> automatically. >> >> I think that the 2nd warnx should be the first warnx, and the 2nd >> warnx can be removed as it'll be quickly followed up by >> cleared. Changing `remove' to `removing' and changing `.sujournal' to >> journal would a) make the action more correct and b) make the concept >> more straightforward as to what's being removed, as Jeff or someone >> else may decide to remove or rename .sujournal in the future, and it's >> just another thing that users don't have to understand that aren't >> familiar with FreeBSD or SUJ. >> > Is this available in 8-STABLE? Nope. > Can it be? Not sure (fs@ folks should make the call), but definitely not before 8.= 1. > Can this be activated on my current installation without loosing data? I suggest looking for SUJ in the current archives in the past 2 months. There are a number of threads that discuss how SUJ should be enabled. HTH, -Garrett From owner-freebsd-current@FreeBSD.ORG Thu May 27 02:31:59 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFB3D106564A for ; Thu, 27 May 2010 02:31:59 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 8D1DD8FC08 for ; Thu, 27 May 2010 02:31:59 +0000 (UTC) Received: by qyk11 with SMTP id 11so10638317qyk.13 for ; Wed, 26 May 2010 19:31:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=UjkCwPxNRLBjEIXNBHpRQqxJRGr8H75vvsJ94I58NUY=; b=s8ejCdUa3Mcr4esIeoYN9PaXJCs7N3D4/3Ts9Bj1yb3kWeJ5BIfRlWIMoo5xgFYEFY 0C45+uqkSE+McxUwcIIAmSwRzoy6Y4Z2sKYtN1kC3BNC4iPHM9dhklKWbhSJjwEWQr7w gSwdIFf920yGEWT0Rz0rmxwkObLdcCf+U4QqE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=RlCikuCLGA6vtk1Ee0ayXbxunSeQF91W1G+qsv+6TkZyBjK2218AqnSb1W9jNfFk00 P3oN20yrBBDgtzdo5BMpSgkW9A+Vm6fVFp1znPeiP+N8lz2DdnsHZNMrQWEou86cfBFA AAcuGqWxAU89qGQEl2xbl1sG7iM6p526uzYyw= MIME-Version: 1.0 Received: by 10.229.250.206 with SMTP id mp14mr2126302qcb.62.1274927518658; Wed, 26 May 2010 19:31:58 -0700 (PDT) Received: by 10.229.190.83 with HTTP; Wed, 26 May 2010 19:31:58 -0700 (PDT) Date: Wed, 26 May 2010 19:31:58 -0700 Message-ID: From: Garrett Cooper To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Subject: NIS crankiness at bootup 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, 27 May 2010 02:31:59 -0000 Hi folks, I've been booting from NIS off a development machine at work and I've noticed the following behavior: 1. Booting with nisdomainname, nis_client_enable, nis_client_flags set at boot makes the machine inaccessible (I have to reboot the machine, get into singleuser, comment out the vars, and boot again). 2. Booting with the variables unset, uncommenting them, booting up, and finally enabling all of the amd and NIS bits works. So I was wondering if there was some secret sauce in the mix or some monkeying that I needed to do (similar to ntpdate to ensure that the interface is up and functional) to determine that NIS is sane and functional for use, or is there some option I can specify in nsswitch.conf to fallback to the system account data)? Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Thu May 27 08:49:54 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D47D91065673 for ; Thu, 27 May 2010 08:49:54 +0000 (UTC) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.freebsd.org (Postfix) with ESMTP id 900D98FC15 for ; Thu, 27 May 2010 08:49:54 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by solfertje.student.utwente.nl (Postfix) with SMTP id E005A8050 for ; Thu, 27 May 2010 10:49:52 +0200 (CEST) Received: from hollewijn.internal (hollewijn.internal [10.236.150.4]) by solfertje.student.utwente.nl (Postfix) with ESMTP id AEDE88034 for ; Thu, 27 May 2010 10:49:44 +0200 (CEST) From: Alban Hertroys Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Date: Thu, 27 May 2010 10:49:44 +0200 Message-Id: <16DEFF8A-DBBB-4F4F-9C0E-FAFBF444E7FE@solfertje.student.utwente.nl> To: FreeBSD Current Mime-Version: 1.0 (Apple Message framework v1078) X-Mailer: Apple Mail (2.1078) X-DSPAM-Result: Innocent X-DSPAM-Processed: Thu May 27 10:49:52 2010 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 930,4bfe323010414002918410 X-DSPAM-Factors: 27, but, 0.40000, but, 0.40000, From*Alban, 0.40000, preferred+boot, 0.40000, yet+I, 0.40000, Mime-Version*Message, 0.40000, Message-Id*DBBB+4F4F, 0.40000, solve, 0.40000, not+very, 0.40000, Date*May, 0.40000, the+preferred, 0.40000, an, 0.40000, didn't+put, 0.40000, manager+but, 0.40000, from, 0.40000, from, 0.40000, to+boot, 0.40000, to+boot, 0.40000, of, 0.40000, of, 0.40000, have+that, 0.40000, as+I, 0.40000, (my, 0.40000, the+BIOS, 0.40000, the+BIOS, 0.40000, in+short, 0.40000, Received*ESMTP, 0.40000 Cc: Subject: GPT on amd64 and boot managers 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, 27 May 2010 08:49:54 -0000 Good day, Yesterday I finally changed my FreeBSD disk to use GPT instead of a traditional MBR, but I hadn't realised that the FreeBSD boot manager doesn't understand GPT partitions (my CURRENT is from early January, if that matters). I used to have that disk set up in the BIOS as the preferred boot disk and the boot manager on it allowed me to boot one of the other disks containing Windows 7 [1]. I googled around and noticed that other people with this problem were told to use Grub as a boot manager, but trying to install that from ports I found out that Grub is only for x86, while I run amd64. So in short, I can't use the FreeBSD boot manager as I have my disk partitioned with GPT, and I can't use Grub as it's not compatible with amd64, yet I do want a boot manager. How do I solve this? Currently I have to choose which OS to boot by changing the boot sequence of my disks in the BIOS - not very convenient. [1] I didn't put a boot manager on the Windows disk on purpose, as Microsoft overwrites it with every reinstall anyway. Alban Hertroys -- Screwing up is an excellent way to attach something to the ceiling. !DSPAM:930,4bfe323010414002918410! From owner-freebsd-current@FreeBSD.ORG Thu May 27 09:57:38 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C93E01065672 for ; Thu, 27 May 2010 09:57:38 +0000 (UTC) (envelope-from moonlightakkiy@yahoo.ca) Received: from web51807.mail.re2.yahoo.com (web51807.mail.re2.yahoo.com [206.190.38.238]) by mx1.freebsd.org (Postfix) with SMTP id 767028FC0C for ; Thu, 27 May 2010 09:57:38 +0000 (UTC) Received: (qmail 37834 invoked by uid 60001); 27 May 2010 09:57:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.ca; s=s1024; t=1274954257; bh=s2++l0k0IyXPIHZ/+o8PMeqlm7M6xcBZJTRdeNy0mic=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=CuaK6Pg2Si0luXnkFmYlEFtB/92LStrMOtkZ7Ka+wDbE09qYtR+pL6ao+7GORJBS33V8C358yMgbqMqP69p7QOZPWo0zWCWRURNXRZccIFn1rAx0+bPwKsfRp6SXQuuHNGXvyc/z0bS7f1T8BFRQ1qA+cz91cewIq4bO1+OLCKo= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.ca; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=qwANQ5JZFeQKQn70XPRPZbG7x1xriPxD9jApTbhcuMNqQlQYac7yHSA7JZlqImPrV5Dox9pCbye4ZIscCwFTBm1CLCEsv/FgN6/56l0UCXqtrXW0fWoax/E1uQGODPnaaBYriJ+Pkf+Kk11/MZBbKRA2WzstqVl1GYIu1JsqIZI=; Message-ID: <618770.37649.qm@web51807.mail.re2.yahoo.com> X-YMail-OSG: rSOICq8VM1lfOkrfLrVKo.x_2QmF.2gW.ht0eRazvoFUqrR zHku7v0LDlxI60Mk63mEjyQ9YNZPt_fYneRZ0thfKZ4Gq4hLPt2rTiFU.HrX HsU4HEEuzrong4clyqsf6KpflqfO_AwEdZAl5nEVgoOlesbnDmjkCZU6ctcF MZkHbQJroT0VdgUa0dNo0xOQZyYxdMT2X1f8wwBaTZDylEAHzDB.Hj_aBdq0 NPCr4vWkSK_0JjFYAOlucVV_s.e6fNQNIj8Aar3lX.YY8wKj9MLGrKky6kVL PKqN4yvFxzW.lzNZ9gvAJkFezv8dIpUDvX3MGeh0x1dzXRjUXUcOWBEzxaY9 j.1z1SYcH19Onekb6 Received: from [173.183.132.20] by web51807.mail.re2.yahoo.com via HTTP; Thu, 27 May 2010 02:57:37 PDT X-Mailer: YahooMailRC/374.4 YahooMailWebService/0.8.103.269680 References: <16641.96608.qm@web51806.mail.re2.yahoo.com> <4B9FA3E0.4050702@micom.mng.net> <633929.41041.qm@web51802.mail.re2.yahoo.com> <4BA22B8D.9030700@micom.mng.net> <375331.74876.qm@web51804.mail.re2.yahoo.com> <4BA38B26.6050208@micom.mng.net> <989377.89740.qm@web51802.mail.re2.yahoo.com> <4BAE01AC.7000509@gmail.com> <623907.37074.qm@web51803.mail.re2.yahoo.com> <4BB3575D.4040506@gmail.com> <87836.79143.qm@web51804.mail.re2.yahoo.com> <4BBB372C.1060302@gmail.com> <665283.95271.qm@web51802.mail.re2.yahoo.com> <4BBDEC8F.9050803@gmail.com> <490521.32714.qm@web51804.mail.re2.yahoo.com> <4BD307DE.5080507@gmail.com> <332448.8676.qm@web51801.mail.re2.yahoo.com> <4BD3F2D4.8000007@gmail.com> <702632.81988.qm@web51803.mail.re2.yahoo.com> <4BDEE393.4080206@gmail.com> <660085.11669.qm@web51802.mail.re2.yahoo.com> <4BFD4806.8070001@gmail.com> Date: Thu, 27 May 2010 02:57:37 -0700 (PDT) From: PseudoCylon To: Ganbold In-Reply-To: <4BFD4806.8070001@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Ganbold Tsagaankhuu , freebsd-current@freebsd.org Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless 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, 27 May 2010 09:57:39 -0000 ----- Original Message ---- > From: Ganbold > To: PseudoCylon > Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu > Sent: Wed, May 26, 2010 10:10:46 AM > Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless > > It looks like either bridge or wlan/run driver is not > forwarding/allowing incoming arp request for wireless client behind this > access point. > Wireless client is not getting any arp request and after sending several > arp request to wireless client ADSL modem stops responding (had to > restart modem). > Any idea? > > thanks, > > Ganbold Hello again Ganbold, This time I can reproduce the problem on my computer. Please try attached patch. (patch to if_run.c) I suppose arp is for during dhcp negotiation. So, client does associate but cannot get IP address. The device won't talk with other devices until 2-way handshake has happens. I thought it happens after 4-way handshake, but hostapd with -d option shows it happens several minutes later. I added code to set some registers ahead of it. So, no need to wait renegotiation happens. -- patch begin -- diff --git a/dev/usb/wlan/if_run.c b/dev/usb/wlan/if_run.c index 61784d9..9beb582 100644 --- a/dev/usb/wlan/if_run.c +++ b/dev/usb/wlan/if_run.c @@ -2053,6 +2053,17 @@ run_key_set_cb(void *arg) attr = (attr & ~0xf) | (mode << 1) | RT2860_RX_PKEY_EN; if(run_write(sc, RT2860_WCID_ATTR(wcid), attr)) return; + +if(vap->iv_opmode == IEEE80211_M_HOSTAP){ +if(run_read(sc, RT2860_SKEY_MODE_0_7, &attr)) +return; +attr &= ~(0xf << (1 * 4)); +attr &= ~(0xf << (2 * 4)); +attr |= mode << (1 * 4); +attr |= mode << (2 * 4); +if(run_write(sc, RT2860_SKEY_MODE_0_7, attr)) +return; +} } /* TODO create a pass-thru key entry? */ -- patch end -- From owner-freebsd-current@FreeBSD.ORG Thu May 27 10:02:14 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F2CF1065673; Thu, 27 May 2010 10:02:14 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id C0D248FC1B; Thu, 27 May 2010 10:02:13 +0000 (UTC) Received: by pwj4 with SMTP id 4so123085pwj.13 for ; Thu, 27 May 2010 03:02:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=W0u2Yhb0qtOyJVC5RB1SpyhaRmalWt+Mw7/1pd8fP2g=; b=MYiHiW3vNVBrHDSfpy05zMUAqO4sY8xuBNLMTW5IoJRwjwFSOQ6ZQi75v4D6pogcEA TSnz7PmQWNvbIcX90MLNVjdLNe4kpY+W+4wMWZ9T6hGJ4Bb2re/wW0AS4juIoZ9ny4Wh IXdeb64MkvGqTFm4s6iX64H+pwrX7/FUUWVZY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=U1yRwg58LWNu1Z+EU/j80hSzUPo7MWtGKxa/WEXEqvnCfM3YQhlGtRYaYluHWw4ZAY S1P+rbqGCnroEKQ4yZP3XPz3dBc7ZT2PRYi7bKg5xMNF7jXQ4rTLufehIdMpNjWyZhpq PVKjQOk0uz0nza2xg6LSnjf96Qc2zGINBMMdE= MIME-Version: 1.0 Received: by 10.141.14.8 with SMTP id r8mr7671538rvi.271.1274954533046; Thu, 27 May 2010 03:02:13 -0700 (PDT) Received: by 10.140.247.13 with HTTP; Thu, 27 May 2010 03:02:12 -0700 (PDT) In-Reply-To: <618770.37649.qm@web51807.mail.re2.yahoo.com> References: <16641.96608.qm@web51806.mail.re2.yahoo.com> <4B9FA3E0.4050702@micom.mng.net> <633929.41041.qm@web51802.mail.re2.yahoo.com> <4BA22B8D.9030700@micom.mng.net> <375331.74876.qm@web51804.mail.re2.yahoo.com> <4BA38B26.6050208@micom.mng.net> <989377.89740.qm@web51802.mail.re2.yahoo.com> <4BAE01AC.7000509@gmail.com> <623907.37074.qm@web51803.mail.re2.yahoo.com> <4BB3575D.4040506@gmail.com> <87836.79143.qm@web51804.mail.re2.yahoo.com> <4BBB372C.1060302@gmail.com> <665283.95271.qm@web51802.mail.re2.yahoo.com> <4BBDEC8F.9050803@gmail.com> <490521.32714.qm@web51804.mail.re2.yahoo.com> <4BD307DE.5080507@gmail.com> <332448.8676.qm@web51801.mail.re2.yahoo.com> <4BD3F2D4.8000007@gmail.com> <702632.81988.qm@web51803.mail.re2.yahoo.com> <4BDEE393.4080206@gmail.com> <660085.11669.qm@web51802.mail.re2.yahoo.com> <4BFD4806.8070001@gmail.com> <618770.37649.qm@web51807.mail.re2.yahoo.com> Date: Thu, 27 May 2010 18:02:12 +0800 Message-ID: From: Ganbold Tsagaankhuu To: PseudoCylon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Qing Li , Ganbold Tsagaankhuu , freebsd-current@freebsd.org Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless 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, 27 May 2010 10:02:14 -0000 AK-san, On Thu, May 27, 2010 at 5:57 PM, PseudoCylon wrote: > ----- Original Message ---- > > From: Ganbold > > To: PseudoCylon > > Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu > > > Sent: Wed, May 26, 2010 10:10:46 AM > > Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless > > > > It looks like either bridge or wlan/run driver is not > > forwarding/allowing incoming arp request for wireless client behind this > > access point. > > Wireless client is not getting any arp request and after sending several > > arp request to wireless client ADSL modem stops responding (had to > > restart modem). > > Any idea? > > > > thanks, > > > > Ganbold > > > Hello again Ganbold, > > This time I can reproduce the problem on my computer. Please try attached > patch. (patch to if_run.c) I suppose arp is for during dhcp negotiation. So, > client does associate but cannot get IP address. > > The device won't talk with other devices until 2-way handshake has happens. > I thought it happens after 4-way handshake, but hostapd with -d option shows > it happens several minutes later. I added code to set some registers ahead > of it. So, no need to wait renegotiation happens. > I didn't try DHCP on client, just used static IP. Anyhow I will try your patch later tonight and let you know. thanks a lot, Ganbold > > > -- patch begin -- > > diff --git a/dev/usb/wlan/if_run.c b/dev/usb/wlan/if_run.c > index 61784d9..9beb582 100644 > --- a/dev/usb/wlan/if_run.c > +++ b/dev/usb/wlan/if_run.c > @@ -2053,6 +2053,17 @@ run_key_set_cb(void *arg) > attr = (attr & ~0xf) | (mode << 1) | RT2860_RX_PKEY_EN; > if(run_write(sc, RT2860_WCID_ATTR(wcid), attr)) > return; > + > +if(vap->iv_opmode == IEEE80211_M_HOSTAP){ > +if(run_read(sc, RT2860_SKEY_MODE_0_7, &attr)) > +return; > +attr &= ~(0xf << (1 * 4)); > +attr &= ~(0xf << (2 * 4)); > +attr |= mode << (1 * 4); > +attr |= mode << (2 * 4); > +if(run_write(sc, RT2860_SKEY_MODE_0_7, attr)) > +return; > +} > } > > /* TODO create a pass-thru key entry? */ > > -- patch end -- > > > From owner-freebsd-current@FreeBSD.ORG Thu May 27 10:21:15 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1C621065672 for ; Thu, 27 May 2010 10:21:15 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.9]) by mx1.freebsd.org (Postfix) with ESMTP id AC8298FC15 for ; Thu, 27 May 2010 10:21:15 +0000 (UTC) Received: from frontend1.mail.m-online.net (unknown [192.168.8.180]) by mail-out.m-online.net (Postfix) with ESMTP id 426261C160F5; Thu, 27 May 2010 12:02:42 +0200 (CEST) Received: from mail.reifenberger.com (ppp-93-104-99-102.dynamic.mnet-online.de [93.104.99.102]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.mnet-online.de (Postfix) with ESMTPS id 2967D1C000F1; Thu, 27 May 2010 12:02:42 +0200 (CEST) Received: by mail.reifenberger.com (Postfix, from userid 1001) id 8463D14AD0; Thu, 27 May 2010 12:02:41 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.reifenberger.com (Postfix) with ESMTP id 6D03014ACD; Thu, 27 May 2010 12:02:41 +0200 (CEST) Date: Thu, 27 May 2010 12:02:40 +0200 (CEST) From: Michael Reifenberger To: Alban Hertroys In-Reply-To: <16DEFF8A-DBBB-4F4F-9C0E-FAFBF444E7FE@solfertje.student.utwente.nl> Message-ID: References: <16DEFF8A-DBBB-4F4F-9C0E-FAFBF444E7FE@solfertje.student.utwente.nl> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Current Subject: Re: GPT on amd64 and boot managers 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, 27 May 2010 10:21:16 -0000 On Thu, 27 May 2010, Alban Hertroys wrote: > Date: Thu, 27 May 2010 10:49:44 +0200 > From: Alban Hertroys > To: FreeBSD Current > Subject: GPT on amd64 and boot managers > > Good day, > > Yesterday I finally changed my FreeBSD disk to use GPT instead of a traditional MBR, but I hadn't realised that the FreeBSD boot manager doesn't understand GPT partitions (my CURRENT is from early January, if that matters). > I used to have that disk set up in the BIOS as the preferred boot disk and the boot manager on it allowed me to boot one of the other disks containing Windows 7 [1]. > FreeBSD boots just fine from GPT. See the examples section of gpart(8). Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com From owner-freebsd-current@FreeBSD.ORG Thu May 27 10:55:32 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 863121065675 for ; Thu, 27 May 2010 10:55:32 +0000 (UTC) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.freebsd.org (Postfix) with ESMTP id 3AFBA8FC0A for ; Thu, 27 May 2010 10:55:31 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by solfertje.student.utwente.nl (Postfix) with SMTP id 6898F8034 for ; Thu, 27 May 2010 12:55:30 +0200 (CEST) Received: from hollewijn.internal (hollewijn.internal [10.236.150.4]) by solfertje.student.utwente.nl (Postfix) with ESMTP id 93FF98050; Thu, 27 May 2010 12:55:23 +0200 (CEST) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Alban Hertroys In-Reply-To: Date: Thu, 27 May 2010 12:55:23 +0200 Content-Transfer-Encoding: 8bit Message-Id: References: <16DEFF8A-DBBB-4F4F-9C0E-FAFBF444E7FE@solfertje.student.utwente.nl> To: Michael Reifenberger X-Mailer: Apple Mail (2.1078) X-DSPAM-Result: Innocent X-DSPAM-Processed: Thu May 27 12:55:30 2010 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 930,4bfe4fa210412299192489 X-DSPAM-Factors: 27, To*Michael, 0.40000, Date*55+23, 0.40000, but, 0.40000, but, 0.40000, From*Alban, 0.40000, preferred+boot, 0.40000, just, 0.40000, just, 0.40000, May+2010, 0.40000, May+2010, 0.40000, Mime-Version*Message, 0.40000, To* Subject: Re: GPT on amd64 and boot managers 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, 27 May 2010 10:55:32 -0000 On 27 May 2010, at 12:02, Michael Reifenberger wrote: > On Thu, 27 May 2010, Alban Hertroys wrote: >> Good day, >> >> Yesterday I finally changed my FreeBSD disk to use GPT instead of a traditional MBR, but I hadn't realised that the FreeBSD boot manager doesn't understand GPT partitions (my CURRENT is from early January, if that matters). >> I used to have that disk set up in the BIOS as the preferred boot disk and the boot manager on it allowed me to boot one of the other disks containing Windows 7 [1]. >> > > FreeBSD boots just fine from GPT. > See the examples section of gpart(8). You appear to have missed the point; I was talking about the boot manager - the thing that lets you choose which OS to boot, not the boot loader. I can boot FreeBSD just fine off GPT, but I have to select in the BIOS whether I want to boot FreeBSD or Windows (by means of changing the boot sequence). A working boot manager would be so much more convenient for that. Alban Hertroys -- If you can't see the forest for the trees, cut the trees and you'll see there is no forest. !DSPAM:930,4bfe4fa210412299192489! From owner-freebsd-current@FreeBSD.ORG Thu May 27 11:33:48 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45A08106566C for ; Thu, 27 May 2010 11:33:48 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 85ABF8FC0A for ; Thu, 27 May 2010 11:33:47 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA17964; Thu, 27 May 2010 14:33:40 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4BFE5893.5090609@icyb.net.ua> Date: Thu, 27 May 2010 14:33:39 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100517) MIME-Version: 1.0 To: Alban Hertroys References: <16DEFF8A-DBBB-4F4F-9C0E-FAFBF444E7FE@solfertje.student.utwente.nl> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: GPT on amd64 and boot managers 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, 27 May 2010 11:33:48 -0000 on 27/05/2010 13:55 Alban Hertroys said the following: > On 27 May 2010, at 12:02, Michael Reifenberger wrote: > >> On Thu, 27 May 2010, Alban Hertroys wrote: >>> Good day, >>> >>> Yesterday I finally changed my FreeBSD disk to use GPT instead of a >>> traditional MBR, but I hadn't realised that the FreeBSD boot manager >>> doesn't understand GPT partitions (my CURRENT is from early January, if >>> that matters). I used to have that disk set up in the BIOS as the preferred >>> boot disk and the boot manager on it allowed me to boot one of the other >>> disks containing Windows 7 [1]. >>> >> FreeBSD boots just fine from GPT. See the examples section of gpart(8). > > > You appear to have missed the point; I was talking about the boot manager - the > thing that lets you choose which OS to boot, not the boot loader. > > I can boot FreeBSD just fine off GPT, but I have to select in the BIOS whether > I want to boot FreeBSD or Windows (by means of changing the boot sequence). A > working boot manager would be so much more convenient for that. Right. OTOH I have standard GPT installation (pmbr + gptzfsboot) and during boot I am presented with a choice which _hard disk_ to boot from. I didn't do anything special for that. Not exactly a boot manager, but OK for me. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Thu May 27 14:02:11 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 236031065672; Thu, 27 May 2010 14:02:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D37748FC13; Thu, 27 May 2010 14:02:10 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 84B3746B66; Thu, 27 May 2010 10:02:10 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id D6D5F8A021; Thu, 27 May 2010 10:02:09 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 27 May 2010 09:33:42 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201005270933.42760.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 27 May 2010 10:02:09 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Marcelo/Porks , Garrett Cooper , Jeff Roberson , current@freebsd.org Subject: Re: SUJ Changes 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, 27 May 2010 14:02:11 -0000 On Wednesday 26 May 2010 7:56:24 pm Garrett Cooper wrote: > On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks wrote: > > On 5/25/10, Marcelo/Porks wrote: > >> Hi! I tested the r208241 and it's seems to be ok but this calls my > >> atention to other thing: Could I disable de SU when the SUJ is > >> enabled? > >> > >> I did some tests and seems that I can do this (logs bellow). > >> > >> But will SUJ work properly with SU disabled? > > > > Hi guys. I'm not sure if I could call this a problem but I can disable > > SU when SUJ is enabled, so SUJ will remain enabled and SU will be > > disabled. > > > > #tunefs -j enable /dev/device > > #tunefs -n disable /dev/device > > > > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the user > > disable SU. Maybe this will be useful for some of you. > > > > Thanks. > > > > > > Index: sbin/tunefs/tunefs.c > > =================================================================== > > --- sbin/tunefs/tunefs.c (revision 208580) > > +++ sbin/tunefs/tunefs.c (working copy) > > @@ -460,6 +460,14 @@ > > if ((~sblock.fs_flags & FS_DOSOFTDEP) == FS_DOSOFTDEP) > > warnx("%s remains unchanged as disabled", name); > > else { > > + /* also disable SUJ */ > > + if ((sblock.fs_flags & FS_SUJ) == FS_SUJ) { > > + warnx("soft updates journaling > > will be disabled too"); > > + journal_clear(); > > + sblock.fs_flags &= ~FS_SUJ; > > + sblock.fs_sujfree = 0; > > + warnx("remove .sujournal to > > reclaim space"); > > + } > > sblock.fs_flags &= ~FS_DOSOFTDEP; > > warnx("%s cleared", name); > > } > > I think that it makes sense to have this as a force option as someone > may want to retain their journal instead of disposing of it > automatically. I'm not sure that really makes sense. As as you do any update to the filesystem the journal becomes out of date, and attempting to replay it could corrupt the filesystem. Instead, I think that attempting to disable SU if SUJ is enabled should just fail with an error message. The sysadmin can then choose to disable both SUJ and SU if desired. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu May 27 14:02:11 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 236031065672; Thu, 27 May 2010 14:02:11 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id D37748FC13; Thu, 27 May 2010 14:02:10 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 84B3746B66; Thu, 27 May 2010 10:02:10 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id D6D5F8A021; Thu, 27 May 2010 10:02:09 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 27 May 2010 09:33:42 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201005270933.42760.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 27 May 2010 10:02:09 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Marcelo/Porks , Garrett Cooper , Jeff Roberson , current@freebsd.org Subject: Re: SUJ Changes 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, 27 May 2010 14:02:11 -0000 On Wednesday 26 May 2010 7:56:24 pm Garrett Cooper wrote: > On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks wrote: > > On 5/25/10, Marcelo/Porks wrote: > >> Hi! I tested the r208241 and it's seems to be ok but this calls my > >> atention to other thing: Could I disable de SU when the SUJ is > >> enabled? > >> > >> I did some tests and seems that I can do this (logs bellow). > >> > >> But will SUJ work properly with SU disabled? > > > > Hi guys. I'm not sure if I could call this a problem but I can disable > > SU when SUJ is enabled, so SUJ will remain enabled and SU will be > > disabled. > > > > #tunefs -j enable /dev/device > > #tunefs -n disable /dev/device > > > > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the user > > disable SU. Maybe this will be useful for some of you. > > > > Thanks. > > > > > > Index: sbin/tunefs/tunefs.c > > =================================================================== > > --- sbin/tunefs/tunefs.c (revision 208580) > > +++ sbin/tunefs/tunefs.c (working copy) > > @@ -460,6 +460,14 @@ > > if ((~sblock.fs_flags & FS_DOSOFTDEP) == FS_DOSOFTDEP) > > warnx("%s remains unchanged as disabled", name); > > else { > > + /* also disable SUJ */ > > + if ((sblock.fs_flags & FS_SUJ) == FS_SUJ) { > > + warnx("soft updates journaling > > will be disabled too"); > > + journal_clear(); > > + sblock.fs_flags &= ~FS_SUJ; > > + sblock.fs_sujfree = 0; > > + warnx("remove .sujournal to > > reclaim space"); > > + } > > sblock.fs_flags &= ~FS_DOSOFTDEP; > > warnx("%s cleared", name); > > } > > I think that it makes sense to have this as a force option as someone > may want to retain their journal instead of disposing of it > automatically. I'm not sure that really makes sense. As as you do any update to the filesystem the journal becomes out of date, and attempting to replay it could corrupt the filesystem. Instead, I think that attempting to disable SU if SUJ is enabled should just fail with an error message. The sysadmin can then choose to disable both SUJ and SU if desired. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu May 27 14:14:02 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BC896106564A; Thu, 27 May 2010 14:14:02 +0000 (UTC) (envelope-from marcelorossi@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 879A78FC0A; Thu, 27 May 2010 14:14:01 +0000 (UTC) Received: by pwj4 with SMTP id 4so19421pwj.13 for ; Thu, 27 May 2010 07:14:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=6JFc8q61MC5MtryN5s0a980SsdHu82aqr8q3WKn4BMo=; b=W3/vsSNk2KsVX9zWaBoMsIHK5QihGRsdOb4kaBOkIjxQyNr0SL6MiRbs73OC2EKGSR nlx9yTcKAeMXZ+Rd+TFxHPnr/xdhJ4pQcsRDKnfCjqcJZp3b7kGsthyfuucPw6tV5kfc wuOTcZHJ64i0sgdTrdSNyfwsGoBJJZzLv1/KE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=YP8IFM69ABdZHs+4fyxA7+wmk5khwYotb8F864vY4OjNbzNF2vH68t1ioMDYoV9/Ve MyD+rThz7d9zGZSuF/VZrkg5rV4oU0wQb9+ui8mobfhp/YfwzmZ/rfTJTAxnbn53qjXQ Z+KKKWvC8TrL7Qfd0TsB7FEEt4g1vU74kgU7E= Received: by 10.229.191.3 with SMTP id dk3mr2269638qcb.25.1274969640095; Thu, 27 May 2010 07:14:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.80.6 with HTTP; Thu, 27 May 2010 07:13:38 -0700 (PDT) In-Reply-To: <201005270933.42760.jhb@freebsd.org> References: <201005270933.42760.jhb@freebsd.org> From: "Marcelo/Porks" Date: Thu, 27 May 2010 11:13:38 -0300 Message-ID: To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Garrett Cooper , freebsd-current@freebsd.org, Jeff Roberson , current@freebsd.org Subject: Re: SUJ Changes 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, 27 May 2010 14:14:02 -0000 On Thu, May 27, 2010 at 10:33 AM, John Baldwin wrote: > On Wednesday 26 May 2010 7:56:24 pm Garrett Cooper wrote: >> On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks = wrote: >> > >> > Hi guys. I'm not sure if I could call this a problem but I can disable >> > SU when SUJ is enabled, so SUJ will remain enabled and SU will be >> > disabled. >> > >> > #tunefs -j enable /dev/device >> > #tunefs -n disable /dev/device >> > >> > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the user >> > disable SU. Maybe this will be useful for some of you. >> > >> > Thanks. >> > >> > >> > Index: sbin/tunefs/tunefs.c >> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> > --- sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(revision 208580) >> > +++ sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(working copy) >> > @@ -460,6 +460,14 @@ >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if ((~sblock.fs_flags &= FS_DOSOFTDEP) =3D=3D > FS_DOSOFTDEP) >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("= %s remains unchanged as disabled", > name); >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0else { >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* also = disable SUJ */ >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if ((sbl= ock.fs_flags & FS_SUJ) =3D=3D FS_SUJ) > { >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 warnx("soft updates journaling >> > will be disabled too"); >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 journal_clear(); >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 sblock.fs_flags &=3D ~FS_SUJ; >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 sblock.fs_sujfree =3D 0; >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 warnx("remove .sujournal to >> > reclaim space"); >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0sblock.= fs_flags &=3D ~FS_DOSOFTDEP; >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("= %s cleared", name); >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0} >> > I think that attempting to disable SU if SUJ > is enabled should just fail with an error message. =A0The sysadmin can th= en > choose to disable both SUJ and SU if desired. If SU is disabled and One tries to enable SUJ then SU will be automatically enabled. So Why not automatically disable SUJ when One tries to disable SU? --=20 Marcelo Rossi "This e-mail is provided "AS IS" with no warranties, and confers no rights.= " From owner-freebsd-current@FreeBSD.ORG Thu May 27 14:27:17 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4F001065677 for ; Thu, 27 May 2010 14:27:17 +0000 (UTC) (envelope-from mike@reifenberger.com) Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.9]) by mx1.freebsd.org (Postfix) with ESMTP id 9DCB58FC18 for ; Thu, 27 May 2010 14:27:17 +0000 (UTC) Received: from frontend1.mail.m-online.net (unknown [192.168.8.180]) by mail-out.m-online.net (Postfix) with ESMTP id EFAC21C16159; Thu, 27 May 2010 16:27:15 +0200 (CEST) Received: from mail.reifenberger.com (ppp-93-104-99-102.dynamic.mnet-online.de [93.104.99.102]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.mnet-online.de (Postfix) with ESMTPS id DC2AB1C00140; Thu, 27 May 2010 16:27:15 +0200 (CEST) Received: by mail.reifenberger.com (Postfix, from userid 1001) id 84F5214B7D; Thu, 27 May 2010 16:27:15 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mail.reifenberger.com (Postfix) with ESMTP id 6E4E814B7A; Thu, 27 May 2010 16:27:15 +0200 (CEST) Date: Thu, 27 May 2010 16:27:15 +0200 (CEST) From: Michael Reifenberger To: Alban Hertroys In-Reply-To: Message-ID: References: <16DEFF8A-DBBB-4F4F-9C0E-FAFBF444E7FE@solfertje.student.utwente.nl> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: FreeBSD Current Subject: Re: GPT on amd64 and boot managers 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, 27 May 2010 14:27:18 -0000 On Thu, 27 May 2010, Alban Hertroys wrote: ... > You appear to have missed the point; I was talking about the boot manager - the thing that lets you choose which OS to boot, not the boot loader. > > I can boot FreeBSD just fine off GPT, but I have to select in the BIOS whether I want to boot FreeBSD or Windows (by means of changing the boot sequence). A working boot manager would be so much more convenient for that. > Ah. I see. Sorry, can't help here. On all servers I use GPT for FreeBSD/ZFS exclusively. On the Notebooks I stay with MBR... Bye/2 --- Michael Reifenberger Michael@Reifenberger.com http://www.Reifenberger.com From owner-freebsd-current@FreeBSD.ORG Thu May 27 14:36:58 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8A2C3106566C for ; Thu, 27 May 2010 14:36:58 +0000 (UTC) (envelope-from marcelorossi@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 5BDD68FC19 for ; Thu, 27 May 2010 14:36:58 +0000 (UTC) Received: by pvh1 with SMTP id 1so4040pvh.13 for ; Thu, 27 May 2010 07:36:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=6JFc8q61MC5MtryN5s0a980SsdHu82aqr8q3WKn4BMo=; b=W3/vsSNk2KsVX9zWaBoMsIHK5QihGRsdOb4kaBOkIjxQyNr0SL6MiRbs73OC2EKGSR nlx9yTcKAeMXZ+Rd+TFxHPnr/xdhJ4pQcsRDKnfCjqcJZp3b7kGsthyfuucPw6tV5kfc wuOTcZHJ64i0sgdTrdSNyfwsGoBJJZzLv1/KE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; b=YP8IFM69ABdZHs+4fyxA7+wmk5khwYotb8F864vY4OjNbzNF2vH68t1ioMDYoV9/Ve MyD+rThz7d9zGZSuF/VZrkg5rV4oU0wQb9+ui8mobfhp/YfwzmZ/rfTJTAxnbn53qjXQ Z+KKKWvC8TrL7Qfd0TsB7FEEt4g1vU74kgU7E= Received: by 10.229.191.3 with SMTP id dk3mr2269638qcb.25.1274969640095; Thu, 27 May 2010 07:14:00 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.80.6 with HTTP; Thu, 27 May 2010 07:13:38 -0700 (PDT) In-Reply-To: <201005270933.42760.jhb@freebsd.org> References: <201005270933.42760.jhb@freebsd.org> From: "Marcelo/Porks" Date: Thu, 27 May 2010 11:13:38 -0300 Message-ID: To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Garrett Cooper , freebsd-current@freebsd.org, Jeff Roberson , current@freebsd.org Subject: Re: SUJ Changes 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, 27 May 2010 14:36:58 -0000 On Thu, May 27, 2010 at 10:33 AM, John Baldwin wrote: > On Wednesday 26 May 2010 7:56:24 pm Garrett Cooper wrote: >> On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks = wrote: >> > >> > Hi guys. I'm not sure if I could call this a problem but I can disable >> > SU when SUJ is enabled, so SUJ will remain enabled and SU will be >> > disabled. >> > >> > #tunefs -j enable /dev/device >> > #tunefs -n disable /dev/device >> > >> > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the user >> > disable SU. Maybe this will be useful for some of you. >> > >> > Thanks. >> > >> > >> > Index: sbin/tunefs/tunefs.c >> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> > --- sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(revision 208580) >> > +++ sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(working copy) >> > @@ -460,6 +460,14 @@ >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if ((~sblock.fs_flags &= FS_DOSOFTDEP) =3D=3D > FS_DOSOFTDEP) >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("= %s remains unchanged as disabled", > name); >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0else { >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* also = disable SUJ */ >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if ((sbl= ock.fs_flags & FS_SUJ) =3D=3D FS_SUJ) > { >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 warnx("soft updates journaling >> > will be disabled too"); >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 journal_clear(); >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 sblock.fs_flags &=3D ~FS_SUJ; >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 sblock.fs_sujfree =3D 0; >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 warnx("remove .sujournal to >> > reclaim space"); >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0sblock.= fs_flags &=3D ~FS_DOSOFTDEP; >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("= %s cleared", name); >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0} >> > I think that attempting to disable SU if SUJ > is enabled should just fail with an error message. =A0The sysadmin can th= en > choose to disable both SUJ and SU if desired. If SU is disabled and One tries to enable SUJ then SU will be automatically enabled. So Why not automatically disable SUJ when One tries to disable SU? --=20 Marcelo Rossi "This e-mail is provided "AS IS" with no warranties, and confers no rights.= " From owner-freebsd-current@FreeBSD.ORG Thu May 27 14:52:42 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CBD8E1065675 for ; Thu, 27 May 2010 14:52:42 +0000 (UTC) (envelope-from vova@parallels.com) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id 16E9C8FC12 for ; Thu, 27 May 2010 14:52:39 +0000 (UTC) Received: from vbook.fbsd.ru ([10.30.1.111]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id o4REqVJZ029338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 May 2010 18:52:35 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.71 (FreeBSD)) (envelope-from ) id 1OHeRj-0000oX-Ha; Thu, 27 May 2010 18:52:31 +0400 From: Vladimir Grebenschikov To: Jeff Roberson In-Reply-To: References: <1272780607.2720.89.camel@localhost> Content-Type: text/plain; charset="KOI8-R" Content-Transfer-Encoding: quoted-printable Date: Thu, 27 May 2010 18:52:31 +0400 Message-ID: <1274971951.2209.12.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.30.1.2 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: current@freebsd.org Subject: Re: SUJ update - new panic - "ffs_copyonwrite: recursive call" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 14:52:42 -0000 Hi Jeff=20 > I checked in a fix for this at revision 207742. If you can verify that i= t=20 > works for you it would be appreciated. Sorry for long delay, finally, I've updated to recent sources, looks like n= o more such panics so far. Will test under more load. > Thanks! > Jeff --=20 Vladimir B. Grebenschikov vova@fbsd.ru From owner-freebsd-current@FreeBSD.ORG Thu May 27 15:07:09 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BE2F91065670 for ; Thu, 27 May 2010 15:07:09 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mail-pw0-f54.google.com (mail-pw0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 82C218FC0C for ; Thu, 27 May 2010 15:07:09 +0000 (UTC) Received: by pwj4 with SMTP id 4so65379pwj.13 for ; Thu, 27 May 2010 08:07:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Hl4HWMl4AXZu94UTYK4Pr4QbiRplfrj0GLc1Wx7QNHs=; b=c82CMrTD4dZC7RTPheQ8uS/6rkGqbK9a+wctEa5+G3wuXq+tX0wNAMhafhXt3bn4IC 2Cwj6wSyAAjXUfNdukGI9bsgZeqfHMpsTb6SeXRPm2f3hwrRZy7hWGWLDi9meN9LIyi4 rsaKuroACg70iI3vimO5Lv3Q9D4H4w6ICGe1M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=rR7zpR8mL0OBOS/CrgPoeKa0APJAn4pjvR+v9mutGr0gLIO/kTe6wjE/z+QD3jFATA juA1qspn0GHobWMPpDpFjhU20TIKOp7g7z65ztJHxodfGYdYZMNiuOA6TYiyES4euwAB VuuvQGeXEPfLyKJtnsGskkKVnAmZd9eiFcQ98= Received: by 10.115.81.37 with SMTP id i37mr9128775wal.95.1274972828916; Thu, 27 May 2010 08:07:08 -0700 (PDT) Received: from beastie.micom.mng.net ([202.179.21.130]) by mx.google.com with ESMTPS id n32sm10777404wae.22.2010.05.27.08.07.04 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 27 May 2010 08:07:06 -0700 (PDT) Message-ID: <4BFE8A8E.2050607@gmail.com> Date: Thu, 27 May 2010 23:06:54 +0800 From: Ganbold User-Agent: Thunderbird 2.0.0.23 (X11/20091011) MIME-Version: 1.0 To: PseudoCylon References: <16641.96608.qm@web51806.mail.re2.yahoo.com> <4B9FA3E0.4050702@micom.mng.net> <633929.41041.qm@web51802.mail.re2.yahoo.com> <4BA22B8D.9030700@micom.mng.net> <375331.74876.qm@web51804.mail.re2.yahoo.com> <4BA38B26.6050208@micom.mng.net> <989377.89740.qm@web51802.mail.re2.yahoo.com> <4BAE01AC.7000509@gmail.com> <623907.37074.qm@web51803.mail.re2.yahoo.com> <4BB3575D.4040506@gmail.com> <87836.79143.qm@web51804.mail.re2.yahoo.com> <4BBB372C.1060302@gmail.com> <665283.95271.qm@web51802.mail.re2.yahoo.com> <4BBDEC8F.9050803@gmail.com> <490521.32714.qm@web51804.mail.re2.yahoo.com> <4BD307DE.5080507@gmail.com> <332448.8676.qm@web51801.mail.re2.yahoo.com> <4BD3F2D4.8000007@gmail.com> <702632.81988.qm@web51803.mail.re2.yahoo.com> <4BDEE393.4080206@gmail.com> <660085.11669.qm@web51802.mail.re2.yahoo.com> <4BFD4806.8070001@gmail.com> <618770.37649.qm@web51807.mail.re2.yahoo.com> In-Reply-To: <618770.37649.qm@web51807.mail.re2.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Ganbold Tsagaankhuu , freebsd-current@freebsd.org Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless 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, 27 May 2010 15:07:09 -0000 AK-san, PseudoCylon wrote: > ----- Original Message ---- > >> From: Ganbold >> To: PseudoCylon >> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu >> Sent: Wed, May 26, 2010 10:10:46 AM >> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless >> >> It looks like either bridge or wlan/run driver is not >> forwarding/allowing incoming arp request for wireless client behind this >> access point. >> Wireless client is not getting any arp request and after sending several >> arp request to wireless client ADSL modem stops responding (had to >> restart modem). >> Any idea? >> >> thanks, >> >> Ganbold >> > > > Hello again Ganbold, > > This time I can reproduce the problem on my computer. Please try attached patch. (patch to if_run.c) I suppose arp is for during dhcp negotiation. So, client does associate but cannot get IP address. > > The device won't talk with other devices until 2-way handshake has happens. I thought it happens after 4-way handshake, but hostapd with -d option shows it happens several minutes later. I added code to set some registers ahead of it. So, no need to wait renegotiation happens. > Just tested the patch, still it has same problem. (FreeBSD rspro 9.0-CURRENT FreeBSD 9.0-CURRENT #67 r208541M: Thu May 27 22:46:36 ULAT 2010 tsgan@beastie:/usr/obj/mips/usr/mysrc/sys/RSPRO_AR71XX mips) thanks, Ganbold > > -- patch begin -- > > diff --git a/dev/usb/wlan/if_run.c b/dev/usb/wlan/if_run.c > index 61784d9..9beb582 100644 > --- a/dev/usb/wlan/if_run.c > +++ b/dev/usb/wlan/if_run.c > @@ -2053,6 +2053,17 @@ run_key_set_cb(void *arg) > attr = (attr & ~0xf) | (mode << 1) | RT2860_RX_PKEY_EN; > if(run_write(sc, RT2860_WCID_ATTR(wcid), attr)) > return; > + > +if(vap->iv_opmode == IEEE80211_M_HOSTAP){ > +if(run_read(sc, RT2860_SKEY_MODE_0_7, &attr)) > +return; > +attr &= ~(0xf << (1 * 4)); > +attr &= ~(0xf << (2 * 4)); > +attr |= mode << (1 * 4); > +attr |= mode << (2 * 4); > +if(run_write(sc, RT2860_SKEY_MODE_0_7, attr)) > +return; > +} > } > > /* TODO create a pass-thru key entry? */ > > -- patch end -- > > > > -- A pessimist is a man who has been compelled to live with an optimist. -- Elbert Hubbard From owner-freebsd-current@FreeBSD.ORG Thu May 27 15:30:21 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D47D2106566B for ; Thu, 27 May 2010 15:30:21 +0000 (UTC) (envelope-from cpghost@cordula.ws) Received: from mail-ew0-f209.google.com (mail-ew0-f209.google.com [209.85.219.209]) by mx1.freebsd.org (Postfix) with ESMTP id 740F98FC12 for ; Thu, 27 May 2010 15:30:21 +0000 (UTC) Received: by ewy1 with SMTP id 1so27077ewy.13 for ; Thu, 27 May 2010 08:30:20 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.17.81 with SMTP id r17mr2089751eba.50.1274972534682; Thu, 27 May 2010 08:02:14 -0700 (PDT) Received: by 10.213.28.76 with HTTP; Thu, 27 May 2010 08:02:14 -0700 (PDT) X-Originating-IP: [93.203.30.113] In-Reply-To: <16DEFF8A-DBBB-4F4F-9C0E-FAFBF444E7FE@solfertje.student.utwente.nl> References: <16DEFF8A-DBBB-4F4F-9C0E-FAFBF444E7FE@solfertje.student.utwente.nl> Date: Thu, 27 May 2010 17:02:14 +0200 Message-ID: From: "C. P. Ghost" To: Alban Hertroys Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current Subject: Re: GPT on amd64 and boot managers 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, 27 May 2010 15:30:21 -0000 On Thu, May 27, 2010 at 10:49 AM, Alban Hertroys wrote: > I googled around and noticed that other people with this problem > were told to use Grub as a boot manager, but trying to install that > from ports I found out that Grub is only for x86, while I run amd64. Maybe you'll have more luck with grub2 instead of legacy grub? I've compiled the bzr version of grub2 on amd64: all I had to do was to add -L /usr/lib32 at the end stage of linking. However, there's currently a bug in grub2 which prevents it from interpreting and recognizing BSD partitions correctly. It's currently being worked on. http://www.mail-archive.com/grub-devel@gnu.org/msg15595.html http://www.mail-archive.com/grub-devel@gnu.org/msg15644.html http://www.mail-archive.com/grub-devel@gnu.org/msg15661.html http://www.mail-archive.com/grub-devel@gnu.org/msg15715.html -cpghost. -- Cordula's Web. http://www.cordula.ws/ From owner-freebsd-current@FreeBSD.ORG Thu May 27 15:57:19 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E4C6106564A for ; Thu, 27 May 2010 15:57:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 6E9EE8FC0A for ; Thu, 27 May 2010 15:57:19 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 2117C46B2D; Thu, 27 May 2010 11:57:19 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 280338A01F; Thu, 27 May 2010 11:57:18 -0400 (EDT) From: John Baldwin To: "Marcelo/Porks" Date: Thu, 27 May 2010 11:47:20 -0400 User-Agent: KMail/1.12.1 (FreeBSD/7.3-CBSD-20100217; KDE/4.3.1; amd64; ; ) References: <201005270933.42760.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201005271147.20155.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 27 May 2010 11:57:18 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Garrett Cooper , freebsd-current@freebsd.org, Jeff Roberson Subject: Re: SUJ Changes 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, 27 May 2010 15:57:19 -0000 On Thursday 27 May 2010 10:13:38 am Marcelo/Porks wrote: > On Thu, May 27, 2010 at 10:33 AM, John Baldwin wrote: > > On Wednesday 26 May 2010 7:56:24 pm Garrett Cooper wrote: > >> On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks wrote: > >> > > >> > Hi guys. I'm not sure if I could call this a problem but I can disable > >> > SU when SUJ is enabled, so SUJ will remain enabled and SU will be > >> > disabled. > >> > > >> > #tunefs -j enable /dev/device > >> > #tunefs -n disable /dev/device > >> > > >> > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the user > >> > disable SU. Maybe this will be useful for some of you. > >> > > >> > Thanks. > >> > > >> > > >> > Index: sbin/tunefs/tunefs.c > >> > =================================================================== > >> > --- sbin/tunefs/tunefs.c (revision 208580) > >> > +++ sbin/tunefs/tunefs.c (working copy) > >> > @@ -460,6 +460,14 @@ > >> > if ((~sblock.fs_flags & FS_DOSOFTDEP) == > > FS_DOSOFTDEP) > >> > warnx("%s remains unchanged as disabled", > > name); > >> > else { > >> > + /* also disable SUJ */ > >> > + if ((sblock.fs_flags & FS_SUJ) == FS_SUJ) > > { > >> > + warnx("soft updates journaling > >> > will be disabled too"); > >> > + journal_clear(); > >> > + sblock.fs_flags &= ~FS_SUJ; > >> > + sblock.fs_sujfree = 0; > >> > + warnx("remove .sujournal to > >> > reclaim space"); > >> > + } > >> > sblock.fs_flags &= ~FS_DOSOFTDEP; > >> > warnx("%s cleared", name); > >> > } > >> > > I think that attempting to disable SU if SUJ > > is enabled should just fail with an error message. The sysadmin can then > > choose to disable both SUJ and SU if desired. > > If SU is disabled and One tries to enable SUJ then SU will be > automatically enabled. > So Why not automatically disable SUJ when One tries to disable SU? I'm probably not a big fan of either really. :) For something as rarely done as tunefs I would prefer to err on the side of caution and require the admin to explicitly specify everything. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu May 27 18:54:31 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 11E671065673 for ; Thu, 27 May 2010 18:54:31 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id AC18C8FC15 for ; Thu, 27 May 2010 18:54:30 +0000 (UTC) Received: (qmail 19367 invoked by uid 399); 27 May 2010 18:54:29 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 27 May 2010 18:54:29 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4BFEBFE3.9030606@FreeBSD.org> Date: Thu, 27 May 2010 11:54:27 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: Kostik Belousov References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> In-Reply-To: <20100526165141.GF83316@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, Garrett Cooper , FreeBSD Current , Alan Cox Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 27 May 2010 18:54:31 -0000 On 05/26/10 09:51, Kostik Belousov wrote: > I did a quick glance over the driver, try this: > http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch > I did not even compiled the patched driver. cc -pipe -g -g -g -DNV_VERSION_STRING=\"195.36.15\" -D__KERNEL__ -DNVRM -O -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I/src -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -c nvidia_subr.c cc1: warnings being treated as errors nvidia_subr.c: In function 'nv_alloc_system_pages': nvidia_subr.c:1306: warning: implicit declaration of function 'vm_page_lock' nvidia_subr.c:1306: warning: nested extern declaration of 'vm_page_lock' nvidia_subr.c:1308: warning: implicit declaration of function 'vm_page_unlock' nvidia_subr.c:1308: warning: nested extern declaration of 'vm_page_unlock' *** Error code 1 FYI, Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Thu May 27 19:13:10 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0A7DA1065674; Thu, 27 May 2010 19:13:10 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 95CAD8FC14; Thu, 27 May 2010 19:13:09 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id o4RJDCMZ054725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 May 2010 22:13:12 +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.14.4/8.14.4) with ESMTP id o4RJCxAE025146; Thu, 27 May 2010 22:12:59 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id o4RJCwab025145; Thu, 27 May 2010 22:12:58 +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: Thu, 27 May 2010 22:12:58 +0300 From: Kostik Belousov To: Doug Barton Message-ID: <20100527191258.GQ83316@deviant.kiev.zoral.com.ua> References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> <4BFEBFE3.9030606@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4CM1oNDqiDLyatGS" Content-Disposition: inline In-Reply-To: <4BFEBFE3.9030606@FreeBSD.org> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-2.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_50, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: alc@freebsd.org, Garrett Cooper , FreeBSD Current , Alan Cox Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 27 May 2010 19:13:10 -0000 --4CM1oNDqiDLyatGS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, May 27, 2010 at 11:54:27AM -0700, Doug Barton wrote: > On 05/26/10 09:51, Kostik Belousov wrote: > >I did a quick glance over the driver, try this: > >http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch > >I did not even compiled the patched driver. >=20 > cc -pipe -g -g -g -DNV_VERSION_STRING=3D\"195.36.15\" -D__KERNEL__ -DNVRM= =20 > -O -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I/src -I. -I@=20 > -I@/contrib/altq -finline-limit=3D8000 --param inline-unit-growth=3D100= =20 > --param large-function-growth=3D1000 -fno-common -g=20 > -mno-align-long-strings -mpreferred-stack-boundary=3D2 -mno-mmx=20 > -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector= =20 > -std=3Diso9899:1999 -fstack-protector -Wall -Wredundant-decls=20 > -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes=20 > -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign=20 > -fformat-extensions -c nvidia_subr.c > cc1: warnings being treated as errors > nvidia_subr.c: In function 'nv_alloc_system_pages': > nvidia_subr.c:1306: warning: implicit declaration of function 'vm_page_lo= ck' > nvidia_subr.c:1306: warning: nested extern declaration of 'vm_page_lock' > nvidia_subr.c:1308: warning: implicit declaration of function=20 > 'vm_page_unlock' > nvidia_subr.c:1308: warning: nested extern declaration of 'vm_page_unlock' > *** Error code 1 I think you have stale/wrong includes used by the build. I just checked that driver indeed builds with my patch. vm_page_lock() and vm_page_unlock() are the macros defined in vm/vm_page.h that are present since first Kip commit. Look at the target of the "@" symlink in the driver directory. --4CM1oNDqiDLyatGS Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkv+xDoACgkQC3+MBN1Mb4ha2QCgr3XueFjnCt6Twhi7IXS+O6SV pZIAn3XdbQIIdiNV8BujFcwx98xraksl =ZTn0 -----END PGP SIGNATURE----- --4CM1oNDqiDLyatGS-- From owner-freebsd-current@FreeBSD.ORG Thu May 27 19:35:00 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D6F8A1065676 for ; Thu, 27 May 2010 19:35:00 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 563F58FC14 for ; Thu, 27 May 2010 19:35:00 +0000 (UTC) Received: (qmail 22353 invoked by uid 399); 27 May 2010 19:34:59 -0000 Received: from localhost (HELO ?192.168.0.145?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 27 May 2010 19:34:59 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4BFEC960.6060402@FreeBSD.org> Date: Thu, 27 May 2010 12:34:56 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: Kostik Belousov References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> <4BFEBFE3.9030606@FreeBSD.org> <20100527191258.GQ83316@deviant.kiev.zoral.com.ua> In-Reply-To: <20100527191258.GQ83316@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, Garrett Cooper , FreeBSD Current , Alan Cox Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 27 May 2010 19:35:00 -0000 On 5/27/2010 12:12 PM, Kostik Belousov wrote: > I think you have stale/wrong includes used by the build. I just checked > that driver indeed builds with my patch. vm_page_lock() and vm_page_unlock() > are the macros defined in vm/vm_page.h that are present since first > Kip commit. As I reported earlier, I am using an older kernel atm for stability reasons. I will try again with a more up to date kernel when time allows. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Thu May 27 21:42:30 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 660851065672; Thu, 27 May 2010 21:42:30 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 318728FC18; Thu, 27 May 2010 21:42:29 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o4RLgTnV068903; Thu, 27 May 2010 17:42:29 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o4RLgTBg068895; Thu, 27 May 2010 21:42:29 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 27 May 2010 21:42:29 GMT Message-Id: <201005272142.o4RLgTBg068895@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 21:42:30 -0000 TB --- 2010-05-27 20:25:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-05-27 20:25:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2010-05-27 20:25:00 - cleaning the object tree TB --- 2010-05-27 20:25:26 - cvsupping the source tree TB --- 2010-05-27 20:25:26 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2010-05-27 20:31:24 - building world TB --- 2010-05-27 20:31:24 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 20:31:24 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 20:31:24 - TARGET=pc98 TB --- 2010-05-27 20:31:24 - TARGET_ARCH=i386 TB --- 2010-05-27 20:31:24 - TZ=UTC TB --- 2010-05-27 20:31:24 - __MAKE_CONF=/dev/null TB --- 2010-05-27 20:31:24 - cd /src TB --- 2010-05-27 20:31:24 - /usr/bin/make -B buildworld >>> World build started on Thu May 27 20:31:25 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu May 27 21:31:25 UTC 2010 TB --- 2010-05-27 21:31:25 - generating LINT kernel config TB --- 2010-05-27 21:31:25 - cd /src/sys/pc98/conf TB --- 2010-05-27 21:31:25 - /usr/bin/make -B LINT TB --- 2010-05-27 21:31:25 - building LINT kernel TB --- 2010-05-27 21:31:25 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 21:31:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 21:31:25 - TARGET=pc98 TB --- 2010-05-27 21:31:25 - TARGET_ARCH=i386 TB --- 2010-05-27 21:31:25 - TZ=UTC TB --- 2010-05-27 21:31:25 - __MAKE_CONF=/dev/null TB --- 2010-05-27 21:31:25 - cd /src TB --- 2010-05-27 21:31:25 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu May 27 21:31:25 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_subs.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_nfsiod.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_vfsops.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_vnops.c /src/sys/nfsclient/nfs_vnops.c: In function 'nfs_lookup': /src/sys/nfsclient/nfs_vnops.c:977: error: 'vp' undeclared (first use in this function) /src/sys/nfsclient/nfs_vnops.c:977: error: (Each undeclared identifier is reported only once /src/sys/nfsclient/nfs_vnops.c:977: error: for each function it appears in.) *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-05-27 21:42:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-05-27 21:42:29 - ERROR: failed to build lint kernel TB --- 2010-05-27 21:42:29 - 3203.16 user 705.91 system 4648.17 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Thu May 27 21:55:07 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3AA181065676; Thu, 27 May 2010 21:55:07 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id E3A5E8FC16; Thu, 27 May 2010 21:55:06 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o4RLt6Bn005654; Thu, 27 May 2010 17:55:06 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o4RLt6i8005653; Thu, 27 May 2010 21:55:06 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 27 May 2010 21:55:06 GMT Message-Id: <201005272155.o4RLt6i8005653@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 21:55:07 -0000 TB --- 2010-05-27 20:25:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-05-27 20:25:00 - starting HEAD tinderbox run for i386/i386 TB --- 2010-05-27 20:25:00 - cleaning the object tree TB --- 2010-05-27 20:25:29 - cvsupping the source tree TB --- 2010-05-27 20:25:29 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2010-05-27 20:41:13 - building world TB --- 2010-05-27 20:41:13 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 20:41:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 20:41:13 - TARGET=i386 TB --- 2010-05-27 20:41:13 - TARGET_ARCH=i386 TB --- 2010-05-27 20:41:13 - TZ=UTC TB --- 2010-05-27 20:41:13 - __MAKE_CONF=/dev/null TB --- 2010-05-27 20:41:13 - cd /src TB --- 2010-05-27 20:41:13 - /usr/bin/make -B buildworld >>> World build started on Thu May 27 20:41:13 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu May 27 21:42:26 UTC 2010 TB --- 2010-05-27 21:42:26 - generating LINT kernel config TB --- 2010-05-27 21:42:26 - cd /src/sys/i386/conf TB --- 2010-05-27 21:42:26 - /usr/bin/make -B LINT TB --- 2010-05-27 21:42:26 - building LINT kernel TB --- 2010-05-27 21:42:26 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 21:42:26 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 21:42:26 - TARGET=i386 TB --- 2010-05-27 21:42:26 - TARGET_ARCH=i386 TB --- 2010-05-27 21:42:26 - TZ=UTC TB --- 2010-05-27 21:42:26 - __MAKE_CONF=/dev/null TB --- 2010-05-27 21:42:26 - cd /src TB --- 2010-05-27 21:42:26 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu May 27 21:42:26 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_subs.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_nfsiod.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_vfsops.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_vnops.c /src/sys/nfsclient/nfs_vnops.c: In function 'nfs_lookup': /src/sys/nfsclient/nfs_vnops.c:977: error: 'vp' undeclared (first use in this function) /src/sys/nfsclient/nfs_vnops.c:977: error: (Each undeclared identifier is reported only once /src/sys/nfsclient/nfs_vnops.c:977: error: for each function it appears in.) *** Error code 1 Stop in /obj/i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-05-27 21:55:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-05-27 21:55:06 - ERROR: failed to build lint kernel TB --- 2010-05-27 21:55:06 - 3317.41 user 707.73 system 5405.21 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Thu May 27 22:22:18 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A4BAF106567A; Thu, 27 May 2010 22:22:18 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 753188FC20; Thu, 27 May 2010 22:22:18 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o4RMMHEE038738; Thu, 27 May 2010 18:22:17 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o4RMMHsd038737; Thu, 27 May 2010 22:22:17 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 27 May 2010 22:22:17 GMT Message-Id: <201005272222.o4RMMHsd038737@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 22:22:18 -0000 TB --- 2010-05-27 20:25:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-05-27 20:25:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2010-05-27 20:25:00 - cleaning the object tree TB --- 2010-05-27 20:25:30 - cvsupping the source tree TB --- 2010-05-27 20:25:30 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile TB --- 2010-05-27 20:41:46 - building world TB --- 2010-05-27 20:41:46 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 20:41:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 20:41:46 - TARGET=amd64 TB --- 2010-05-27 20:41:46 - TARGET_ARCH=amd64 TB --- 2010-05-27 20:41:46 - TZ=UTC TB --- 2010-05-27 20:41:46 - __MAKE_CONF=/dev/null TB --- 2010-05-27 20:41:46 - cd /src TB --- 2010-05-27 20:41:46 - /usr/bin/make -B buildworld >>> World build started on Thu May 27 20:41:47 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Thu May 27 22:10:10 UTC 2010 TB --- 2010-05-27 22:10:10 - generating LINT kernel config TB --- 2010-05-27 22:10:10 - cd /src/sys/amd64/conf TB --- 2010-05-27 22:10:10 - /usr/bin/make -B LINT TB --- 2010-05-27 22:10:10 - building LINT kernel TB --- 2010-05-27 22:10:10 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 22:10:10 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 22:10:10 - TARGET=amd64 TB --- 2010-05-27 22:10:10 - TARGET_ARCH=amd64 TB --- 2010-05-27 22:10:10 - TZ=UTC TB --- 2010-05-27 22:10:10 - __MAKE_CONF=/dev/null TB --- 2010-05-27 22:10:10 - cd /src TB --- 2010-05-27 22:10:10 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu May 27 22:10:10 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_subs.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_nfsiod.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_vfsops.c cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-sse -mno-sse2 -mno-sse3 -mno-mmx -mno-3dnow -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/nfsclient/nfs_vnops.c /src/sys/nfsclient/nfs_vnops.c: In function 'nfs_lookup': /src/sys/nfsclient/nfs_vnops.c:977: error: 'vp' undeclared (first use in this function) /src/sys/nfsclient/nfs_vnops.c:977: error: (Each undeclared identifier is reported only once /src/sys/nfsclient/nfs_vnops.c:977: error: for each function it appears in.) *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-05-27 22:22:17 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-05-27 22:22:17 - ERROR: failed to build lint kernel TB --- 2010-05-27 22:22:17 - 4496.03 user 988.98 system 7036.71 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Thu May 27 22:44:41 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF0B6106566C; Thu, 27 May 2010 22:44:41 +0000 (UTC) (envelope-from marcelorossi@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.221.175]) by mx1.freebsd.org (Postfix) with ESMTP id 4FACE8FC08; Thu, 27 May 2010 22:44:41 +0000 (UTC) Received: by qyk5 with SMTP id 5so827935qyk.3 for ; Thu, 27 May 2010 15:44:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=aYX4tonMSe9CVGYVUjcaDJ4d/CE2k6n5PJqbwh7c5HI=; b=gKxQbghcKXQYMKSQuSb4cT+9du3nuqFCHEy22Wghtwr1auEfJSFkgkFhyYt6caBYEz d1gvEBgYcYK+L8qyGG7O6DO4ngiVwnnsLznTMN6Kazq8T2fIfXpi6AjhRYYbhxI4ZGnR 2PXGi4+B153Jpiaf5zeWDjiQh8HioHgbcw+wQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=ZRIAUXHlzcnY1DD/fkfwOcmCDKRaQJ5LcNFtP+IlmhO1SzSbyr2yiH3HJqPJgYW+Uj 5jTqZ3C5yOhCSkquaLOU2nSX/aZOh2qMqcT8AQGAojCNyEK3sfD2SU4Oji2mo55d1TVo hA8FMBkB6PvhO7N/UEwpmTPk58zwxFP9+KpuA= MIME-Version: 1.0 Received: by 10.229.228.208 with SMTP id jf16mr2498791qcb.43.1275000280645; Thu, 27 May 2010 15:44:40 -0700 (PDT) Received: by 10.229.80.6 with HTTP; Thu, 27 May 2010 15:44:40 -0700 (PDT) In-Reply-To: <201005271147.20155.jhb@freebsd.org> References: <201005270933.42760.jhb@freebsd.org> <201005271147.20155.jhb@freebsd.org> Date: Thu, 27 May 2010 19:44:40 -0300 Message-ID: From: "Marcelo/Porks" To: John Baldwin Content-Type: multipart/mixed; boundary=00163630f223d1052104879b224b Cc: Garrett Cooper , freebsd-current@freebsd.org, Jeff Roberson Subject: Re: SUJ Changes 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, 27 May 2010 22:44:41 -0000 --00163630f223d1052104879b224b Content-Type: text/plain; charset=ISO-8859-1 On 5/27/10, John Baldwin wrote: > On Thursday 27 May 2010 10:13:38 am Marcelo/Porks wrote: >> On Thu, May 27, 2010 at 10:33 AM, John Baldwin wrote: >> > On Wednesday 26 May 2010 7:56:24 pm Garrett Cooper wrote: >> >> On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks >> >> > wrote: >> >> > >> >> > Hi guys. I'm not sure if I could call this a problem but I can >> >> > disable >> >> > SU when SUJ is enabled, so SUJ will remain enabled and SU will be >> >> > disabled. >> >> > >> >> > #tunefs -j enable /dev/device >> >> > #tunefs -n disable /dev/device >> >> > >> >> > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the user >> >> > disable SU. Maybe this will be useful for some of you. >> >> > >> >> > Thanks. >> >> > >> >> > >> >> > Index: sbin/tunefs/tunefs.c >> >> > =================================================================== >> >> > --- sbin/tunefs/tunefs.c (revision 208580) >> >> > +++ sbin/tunefs/tunefs.c (working copy) >> >> > @@ -460,6 +460,14 @@ >> >> > if ((~sblock.fs_flags & FS_DOSOFTDEP) == >> > FS_DOSOFTDEP) >> >> > warnx("%s remains unchanged as > disabled", >> > name); >> >> > else { >> >> > + /* also disable SUJ */ >> >> > + if ((sblock.fs_flags & FS_SUJ) == > FS_SUJ) >> > { >> >> > + warnx("soft updates >> >> > journaling >> >> > will be disabled too"); >> >> > + journal_clear(); >> >> > + sblock.fs_flags &= ~FS_SUJ; >> >> > + sblock.fs_sujfree = 0; >> >> > + warnx("remove .sujournal to >> >> > reclaim space"); >> >> > + } >> >> > sblock.fs_flags &= ~FS_DOSOFTDEP; >> >> > warnx("%s cleared", name); >> >> > } >> >> >> > I think that attempting to disable SU if SUJ >> > is enabled should just fail with an error message. The sysadmin can >> > then >> > choose to disable both SUJ and SU if desired. >> >> If SU is disabled and One tries to enable SUJ then SU will be >> automatically enabled. >> So Why not automatically disable SUJ when One tries to disable SU? > > I'm probably not a big fan of either really. :) For something as rarely > done > as tunefs I would prefer to err on the side of caution and require the admin > to explicitly specify everything. Hi John. I agree with you, I do prefer a fail of tunefs in this situation. Before of I have posted the first patch I have done another one that fails to enable SUJ when SU is disabled and fails to disable SU when SUJ is enabled. Now this patch is bellow and attached. *All the stuff that I will say bellow is based on the attached patch* The attached patch fails to disable SU when SUJ is enabled. And it fails to enable SUJ when SU is disabled. Earlier I decided to not post the patch because it will cause confusion when SU and SUJ is disabled and you try to do something such as: # tunefs -j enable -n enable /dev/ad2s1d The flags's processing order is alphabetically, so It will try to enable SUJ first (and it will fail) and after it will enable SU. We could resolve this by processing '-n' (SU) first and after '-j' (SUJ) but this schema will make to fail the following command: # tunefs -j disable -n disable /dev/ad2s1d So I think we could create a function for each flag to be processed and the main() calls this functions as necessary (and main() disabled the relative flag so the function will not be called again). But I'm just a curious doing trivial patches, You can talk about this with more experience and knowlege. =========patch========== Index: sbin/tunefs/tunefs.c =================================================================== --- sbin/tunefs/tunefs.c (revision 208584) +++ sbin/tunefs/tunefs.c (working copy) @@ -341,16 +341,19 @@ if (jflag) { name = "soft updates journaling"; if (strcmp(jvalue, "enable") == 0) { - if ((sblock.fs_flags & (FS_DOSOFTDEP | FS_SUJ)) == - (FS_DOSOFTDEP | FS_SUJ)) { + if ((sblock.fs_flags & FS_SUJ) == FS_SUJ) { warnx("%s remains unchanged as enabled", name); + } else if ((sblock.fs_flags & FS_DOSOFTDEP) != + FS_DOSOFTDEP) { + warnx("%s cannot be enabled until soft updates is enabled", + name); } else if (sblock.fs_clean == 0) { warnx("%s cannot be enabled until fsck is run", name); } else if (journal_alloc(Svalue) != 0) { warnx("%s can not be enabled", name); } else { - sblock.fs_flags |= FS_DOSOFTDEP | FS_SUJ; + sblock.fs_flags |= FS_SUJ; warnx("%s set", name); } } else if (strcmp(jvalue, "disable") == 0) { @@ -459,6 +462,9 @@ } else if (strcmp(nvalue, "disable") == 0) { if ((~sblock.fs_flags & FS_DOSOFTDEP) == FS_DOSOFTDEP) warnx("%s remains unchanged as disabled", name); + else if ((sblock.fs_flags & FS_SUJ) == FS_SUJ) + warnx("%s cannot be enabled until soft updates \ +journaling is disabled", name); else { sblock.fs_flags &= ~FS_DOSOFTDEP; warnx("%s cleared", name); -- Marcelo Rossi "This e-mail is provided "AS IS" with no warranties, and confers no rights." --00163630f223d1052104879b224b Content-Type: application/octet-stream; name="tunefs.diff" Content-Disposition: attachment; filename="tunefs.diff" Content-Transfer-Encoding: base64 X-Attachment-Id: file1 SW5kZXg6IHNiaW4vdHVuZWZzL3R1bmVmcy5jCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIHNiaW4vdHVuZWZzL3R1 bmVmcy5jCShyZXZpc2lvbiAyMDg1ODQpCisrKyBzYmluL3R1bmVmcy90dW5lZnMuYwkod29ya2lu ZyBjb3B5KQpAQCAtMzQxLDE2ICszNDEsMTkgQEAKIAlpZiAoamZsYWcpIHsKICAJCW5hbWUgPSAi c29mdCB1cGRhdGVzIGpvdXJuYWxpbmciOwogIAkJaWYgKHN0cmNtcChqdmFsdWUsICJlbmFibGUi KSA9PSAwKSB7Ci0JCQlpZiAoKHNibG9jay5mc19mbGFncyAmIChGU19ET1NPRlRERVAgfCBGU19T VUopKSA9PQotCQkJICAgIChGU19ET1NPRlRERVAgfCBGU19TVUopKSB7CisJCQlpZiAoKHNibG9j ay5mc19mbGFncyAmIEZTX1NVSikgPT0gRlNfU1VKKSB7CiAJCQkJd2FybngoIiVzIHJlbWFpbnMg dW5jaGFuZ2VkIGFzIGVuYWJsZWQiLCBuYW1lKTsKKwkJCX0gZWxzZSBpZiAoKHNibG9jay5mc19m bGFncyAmIEZTX0RPU09GVERFUCkgIT0KKwkJCQlGU19ET1NPRlRERVApIHsKKwkJCQl3YXJueCgi JXMgY2Fubm90IGJlIGVuYWJsZWQgdW50aWwgc29mdCB1cGRhdGVzIGlzIGVuYWJsZWQiLAorCQkJ CQluYW1lKTsKIAkJCX0gZWxzZSBpZiAoc2Jsb2NrLmZzX2NsZWFuID09IDApIHsKIAkJCQl3YXJu eCgiJXMgY2Fubm90IGJlIGVuYWJsZWQgdW50aWwgZnNjayBpcyBydW4iLAogCQkJCSAgICBuYW1l KTsKIAkJCX0gZWxzZSBpZiAoam91cm5hbF9hbGxvYyhTdmFsdWUpICE9IDApIHsKIAkJCQl3YXJu eCgiJXMgY2FuIG5vdCBiZSBlbmFibGVkIiwgbmFtZSk7CiAJCQl9IGVsc2UgewotIAkJCQlzYmxv Y2suZnNfZmxhZ3MgfD0gRlNfRE9TT0ZUREVQIHwgRlNfU1VKOworIAkJCQlzYmxvY2suZnNfZmxh Z3MgfD0gRlNfU1VKOwogIAkJCQl3YXJueCgiJXMgc2V0IiwgbmFtZSk7CiAJCQl9CiAgCQl9IGVs c2UgaWYgKHN0cmNtcChqdmFsdWUsICJkaXNhYmxlIikgPT0gMCkgewpAQCAtNDU5LDYgKzQ2Miw5 IEBACiAgCQl9IGVsc2UgaWYgKHN0cmNtcChudmFsdWUsICJkaXNhYmxlIikgPT0gMCkgewogCQkJ aWYgKCh+c2Jsb2NrLmZzX2ZsYWdzICYgRlNfRE9TT0ZUREVQKSA9PSBGU19ET1NPRlRERVApCiAJ CQkJd2FybngoIiVzIHJlbWFpbnMgdW5jaGFuZ2VkIGFzIGRpc2FibGVkIiwgbmFtZSk7CisJCQll bHNlIGlmICgoc2Jsb2NrLmZzX2ZsYWdzICYgRlNfU1VKKSA9PSBGU19TVUopCisJCQkJd2Fybngo IiVzIGNhbm5vdCBiZSBlbmFibGVkIHVudGlsIHNvZnQgdXBkYXRlcyBcCitqb3VybmFsaW5nIGlz IGRpc2FibGVkIiwgbmFtZSk7CiAJCQllbHNlIHsKICAJCQkJc2Jsb2NrLmZzX2ZsYWdzICY9IH5G U19ET1NPRlRERVA7CiAgCQkJCXdhcm54KCIlcyBjbGVhcmVkIiwgbmFtZSk7Cg== --00163630f223d1052104879b224b-- From owner-freebsd-current@FreeBSD.ORG Thu May 27 22:49:24 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D602F106566B; Thu, 27 May 2010 22:49:24 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id A3B128FC0A; Thu, 27 May 2010 22:49:24 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o4RMnNTQ067728; Thu, 27 May 2010 18:49:23 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o4RMnNeW067723; Thu, 27 May 2010 22:49:23 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 27 May 2010 22:49:23 GMT Message-Id: <201005272249.o4RMnNeW067723@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 22:49:24 -0000 TB --- 2010-05-27 21:15:03 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-05-27 21:15:03 - starting HEAD tinderbox run for ia64/ia64 TB --- 2010-05-27 21:15:03 - cleaning the object tree TB --- 2010-05-27 21:15:24 - cvsupping the source tree TB --- 2010-05-27 21:15:24 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2010-05-27 21:15:51 - building world TB --- 2010-05-27 21:15:51 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 21:15:51 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 21:15:51 - TARGET=ia64 TB --- 2010-05-27 21:15:51 - TARGET_ARCH=ia64 TB --- 2010-05-27 21:15:51 - TZ=UTC TB --- 2010-05-27 21:15:51 - __MAKE_CONF=/dev/null TB --- 2010-05-27 21:15:51 - cd /src TB --- 2010-05-27 21:15:51 - /usr/bin/make -B buildworld >>> World build started on Thu May 27 21:15:52 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu May 27 22:34:34 UTC 2010 TB --- 2010-05-27 22:34:34 - generating LINT kernel config TB --- 2010-05-27 22:34:34 - cd /src/sys/ia64/conf TB --- 2010-05-27 22:34:34 - /usr/bin/make -B LINT TB --- 2010-05-27 22:34:34 - building LINT kernel TB --- 2010-05-27 22:34:34 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 22:34:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 22:34:34 - TARGET=ia64 TB --- 2010-05-27 22:34:34 - TARGET_ARCH=ia64 TB --- 2010-05-27 22:34:34 - TZ=UTC TB --- 2010-05-27 22:34:34 - __MAKE_CONF=/dev/null TB --- 2010-05-27 22:34:34 - cd /src TB --- 2010-05-27 22:34:34 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu May 27 22:34:34 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/nfsclient/nfs_subs.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/nfsclient/nfs_nfsiod.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/nfsclient/nfs_vfsops.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/nfsclient/nfs_vnops.c /src/sys/nfsclient/nfs_vnops.c: In function 'nfs_lookup': /src/sys/nfsclient/nfs_vnops.c:977: error: 'vp' undeclared (first use in this function) /src/sys/nfsclient/nfs_vnops.c:977: error: (Each undeclared identifier is reported only once /src/sys/nfsclient/nfs_vnops.c:977: error: for each function it appears in.) *** Error code 1 Stop in /obj/ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-05-27 22:49:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-05-27 22:49:23 - ERROR: failed to build lint kernel TB --- 2010-05-27 22:49:23 - 4491.11 user 692.59 system 5660.56 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Thu May 27 23:07:13 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FB3B1065672; Thu, 27 May 2010 23:07:13 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 008D28FC0A; Thu, 27 May 2010 23:07:12 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o4RN7CAi003153; Thu, 27 May 2010 19:07:12 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o4RN7CYu003147; Thu, 27 May 2010 23:07:12 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 27 May 2010 23:07:12 GMT Message-Id: <201005272307.o4RN7CYu003147@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 23:07:13 -0000 TB --- 2010-05-27 21:55:06 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-05-27 21:55:06 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2010-05-27 21:55:06 - cleaning the object tree TB --- 2010-05-27 21:55:25 - cvsupping the source tree TB --- 2010-05-27 21:55:25 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2010-05-27 21:55:52 - building world TB --- 2010-05-27 21:55:52 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 21:55:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 21:55:52 - TARGET=powerpc TB --- 2010-05-27 21:55:52 - TARGET_ARCH=powerpc TB --- 2010-05-27 21:55:52 - TZ=UTC TB --- 2010-05-27 21:55:52 - __MAKE_CONF=/dev/null TB --- 2010-05-27 21:55:52 - cd /src TB --- 2010-05-27 21:55:52 - /usr/bin/make -B buildworld >>> World build started on Thu May 27 21:55:53 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu May 27 22:57:15 UTC 2010 TB --- 2010-05-27 22:57:15 - generating LINT kernel config TB --- 2010-05-27 22:57:15 - cd /src/sys/powerpc/conf TB --- 2010-05-27 22:57:15 - /usr/bin/make -B LINT TB --- 2010-05-27 22:57:15 - building LINT kernel TB --- 2010-05-27 22:57:15 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 22:57:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 22:57:15 - TARGET=powerpc TB --- 2010-05-27 22:57:15 - TARGET_ARCH=powerpc TB --- 2010-05-27 22:57:15 - TZ=UTC TB --- 2010-05-27 22:57:15 - __MAKE_CONF=/dev/null TB --- 2010-05-27 22:57:15 - cd /src TB --- 2010-05-27 22:57:15 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu May 27 22:57:15 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_subs.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_nfsiod.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_vfsops.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_vnops.c /src/sys/nfsclient/nfs_vnops.c: In function 'nfs_lookup': /src/sys/nfsclient/nfs_vnops.c:977: error: 'vp' undeclared (first use in this function) /src/sys/nfsclient/nfs_vnops.c:977: error: (Each undeclared identifier is reported only once /src/sys/nfsclient/nfs_vnops.c:977: error: for each function it appears in.) *** Error code 1 Stop in /obj/powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-05-27 23:07:12 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-05-27 23:07:12 - ERROR: failed to build lint kernel TB --- 2010-05-27 23:07:12 - 3323.52 user 646.73 system 4325.94 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Thu May 27 23:29:34 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 586581065674; Thu, 27 May 2010 23:29:34 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 26AA28FC1D; Thu, 27 May 2010 23:29:33 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o4RNTXii096184; Thu, 27 May 2010 19:29:33 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o4RNTXfq096182; Thu, 27 May 2010 23:29:33 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 27 May 2010 23:29:33 GMT Message-Id: <201005272329.o4RNTXfq096182@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 23:29:34 -0000 TB --- 2010-05-27 22:22:17 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-05-27 22:22:17 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2010-05-27 22:22:17 - cleaning the object tree TB --- 2010-05-27 22:22:33 - cvsupping the source tree TB --- 2010-05-27 22:22:33 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2010-05-27 22:23:01 - building world TB --- 2010-05-27 22:23:01 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 22:23:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 22:23:01 - TARGET=sparc64 TB --- 2010-05-27 22:23:01 - TARGET_ARCH=sparc64 TB --- 2010-05-27 22:23:01 - TZ=UTC TB --- 2010-05-27 22:23:01 - __MAKE_CONF=/dev/null TB --- 2010-05-27 22:23:01 - cd /src TB --- 2010-05-27 22:23:01 - /usr/bin/make -B buildworld >>> World build started on Thu May 27 22:23:01 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu May 27 23:19:18 UTC 2010 TB --- 2010-05-27 23:19:18 - generating LINT kernel config TB --- 2010-05-27 23:19:18 - cd /src/sys/sparc64/conf TB --- 2010-05-27 23:19:18 - /usr/bin/make -B LINT TB --- 2010-05-27 23:19:18 - building LINT kernel TB --- 2010-05-27 23:19:18 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 23:19:18 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 23:19:18 - TARGET=sparc64 TB --- 2010-05-27 23:19:18 - TARGET_ARCH=sparc64 TB --- 2010-05-27 23:19:18 - TZ=UTC TB --- 2010-05-27 23:19:18 - __MAKE_CONF=/dev/null TB --- 2010-05-27 23:19:18 - cd /src TB --- 2010-05-27 23:19:18 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu May 27 23:19:18 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_subs.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_nfsiod.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_vfsops.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_vnops.c /src/sys/nfsclient/nfs_vnops.c: In function 'nfs_lookup': /src/sys/nfsclient/nfs_vnops.c:977: error: 'vp' undeclared (first use in this function) /src/sys/nfsclient/nfs_vnops.c:977: error: (Each undeclared identifier is reported only once /src/sys/nfsclient/nfs_vnops.c:977: error: for each function it appears in.) *** Error code 1 Stop in /obj/sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-05-27 23:29:33 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-05-27 23:29:33 - ERROR: failed to build lint kernel TB --- 2010-05-27 23:29:33 - 3162.41 user 625.45 system 4035.51 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Thu May 27 23:38:58 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3779106564A; Thu, 27 May 2010 23:38:58 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id B1A8F8FC17; Thu, 27 May 2010 23:38:58 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.4/8.14.3) with ESMTP id o4RNcvb4011476; Thu, 27 May 2010 19:38:57 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.4/8.14.3/Submit) id o4RNcvd5011475; Thu, 27 May 2010 23:38:57 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 27 May 2010 23:38:57 GMT Message-Id: <201005272338.o4RNcvd5011475@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Precedence: bulk Cc: Subject: [head tinderbox] failure on sparc64/sun4v X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 May 2010 23:38:59 -0000 TB --- 2010-05-27 22:33:14 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2010-05-27 22:33:14 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2010-05-27 22:33:14 - cleaning the object tree TB --- 2010-05-27 22:33:27 - cvsupping the source tree TB --- 2010-05-27 22:33:27 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2010-05-27 22:33:52 - building world TB --- 2010-05-27 22:33:52 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 22:33:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 22:33:52 - TARGET=sun4v TB --- 2010-05-27 22:33:52 - TARGET_ARCH=sparc64 TB --- 2010-05-27 22:33:52 - TZ=UTC TB --- 2010-05-27 22:33:52 - __MAKE_CONF=/dev/null TB --- 2010-05-27 22:33:52 - cd /src TB --- 2010-05-27 22:33:52 - /usr/bin/make -B buildworld >>> World build started on Thu May 27 22:33:52 UTC 2010 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Thu May 27 23:28:32 UTC 2010 TB --- 2010-05-27 23:28:32 - generating LINT kernel config TB --- 2010-05-27 23:28:32 - cd /src/sys/sun4v/conf TB --- 2010-05-27 23:28:32 - /usr/bin/make -B LINT TB --- 2010-05-27 23:28:32 - building LINT kernel TB --- 2010-05-27 23:28:32 - MAKEOBJDIRPREFIX=/obj TB --- 2010-05-27 23:28:32 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2010-05-27 23:28:32 - TARGET=sun4v TB --- 2010-05-27 23:28:32 - TARGET_ARCH=sparc64 TB --- 2010-05-27 23:28:32 - TZ=UTC TB --- 2010-05-27 23:28:32 - __MAKE_CONF=/dev/null TB --- 2010-05-27 23:28:32 - cd /src TB --- 2010-05-27 23:28:32 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu May 27 23:28:32 UTC 2010 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_subs.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_nfsiod.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_vfsops.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/nfsclient/nfs_vnops.c /src/sys/nfsclient/nfs_vnops.c: In function 'nfs_lookup': /src/sys/nfsclient/nfs_vnops.c:977: error: 'vp' undeclared (first use in this function) /src/sys/nfsclient/nfs_vnops.c:977: error: (Each undeclared identifier is reported only once /src/sys/nfsclient/nfs_vnops.c:977: error: for each function it appears in.) *** Error code 1 Stop in /obj/sun4v/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2010-05-27 23:38:57 - WARNING: /usr/bin/make returned exit code 1 TB --- 2010-05-27 23:38:57 - ERROR: failed to build lint kernel TB --- 2010-05-27 23:38:57 - 3158.31 user 617.74 system 3943.23 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Fri May 28 01:31:08 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A83E6106564A; Fri, 28 May 2010 01:31:08 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 4ADE88FC12; Fri, 28 May 2010 01:31:07 +0000 (UTC) Received: by qyk11 with SMTP id 11so999447qyk.13 for ; Thu, 27 May 2010 18:31:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=xRDhLJ0XL4ljDTsZrDgyFhtuIZD21CyfXZNmtbh524A=; b=tZDNJwcq3xgYZejBZNtqBseRmH5GwDoesXLc7lHvSnDxb1Imxi0mDzfaYugETGLfeT jQvYr3RsQ0iVKRy+QHSjx36IXyWAWpMYBCthvEZYpJZ0Mz/0EYRV1i1rXOydV7RfV1mx 0zfpvUNAZmeGV1nA1chqZK3L7KybwE/DS/J/Q= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Dcy5VZ5CcuCHxOO/7YcPtU8q9gaDX15tNxny6lulej6rc1eU3oyjhToULZo+H7rSTj KkHcqzcrd2vJuW4Db1NKSctDjdrtJ6Ch6US6OraDNdumyy0DdCyyCiMMi4jzsAYul/mD XhYfHb9EpZuvjYb+xVHzYDDVw4wKIydOJh4/A= MIME-Version: 1.0 Received: by 10.224.29.208 with SMTP id r16mr5602560qac.212.1275010266745; Thu, 27 May 2010 18:31:06 -0700 (PDT) Received: by 10.229.190.83 with HTTP; Thu, 27 May 2010 18:31:06 -0700 (PDT) In-Reply-To: References: <201005270933.42760.jhb@freebsd.org> <201005271147.20155.jhb@freebsd.org> Date: Thu, 27 May 2010 18:31:06 -0700 Message-ID: From: Garrett Cooper To: "Marcelo/Porks" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Jeff Roberson Subject: Re: SUJ Changes 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, 28 May 2010 01:31:08 -0000 On Thu, May 27, 2010 at 3:44 PM, Marcelo/Porks wro= te: > On 5/27/10, John Baldwin wrote: >> On Thursday 27 May 2010 10:13:38 am Marcelo/Porks wrote: >>> On Thu, May 27, 2010 at 10:33 AM, John Baldwin wrote: >>> > On Wednesday 26 May 2010 7:56:24 pm Garrett Cooper wrote: >>> >> On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks >>> >> >> wrote: >>> >> > >>> >> > Hi guys. I'm not sure if I could call this a problem but I can >>> >> > disable >>> >> > SU when SUJ is enabled, so SUJ will remain enabled and SU will be >>> >> > disabled. >>> >> > >>> >> > #tunefs -j enable /dev/device >>> >> > #tunefs -n disable /dev/device >>> >> > >>> >> > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the u= ser >>> >> > disable SU. Maybe this will be useful for some of you. >>> >> > >>> >> > Thanks. >>> >> > >>> >> > >>> >> > Index: sbin/tunefs/tunefs.c >>> >> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>> >> > --- sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(revision 208580) >>> >> > +++ sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(working copy) >>> >> > @@ -460,6 +460,14 @@ >>> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if ((~sblock.fs_fla= gs & FS_DOSOFTDEP) =3D=3D >>> > FS_DOSOFTDEP) >>> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0war= nx("%s remains unchanged as >> disabled", >>> > name); >>> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0else { >>> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* a= lso disable SUJ */ >>> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if (= (sblock.fs_flags & FS_SUJ) =3D=3D >> FS_SUJ) >>> > { >>> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 warnx("soft updates >>> >> > journaling >>> >> > will be disabled too"); >>> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 journal_clear(); >>> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 sblock.fs_flags &=3D ~FS_SUJ; >>> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 sblock.fs_sujfree =3D 0; >>> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 warnx("remove .sujournal to >>> >> > reclaim space"); >>> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } >>> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0sbl= ock.fs_flags &=3D ~FS_DOSOFTDEP; >>> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0war= nx("%s cleared", name); >>> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0} >>> >> >>> > I think that attempting to disable SU if SUJ >>> > is enabled should just fail with an error message. =A0The sysadmin ca= n >>> > then >>> > choose to disable both SUJ and SU if desired. >>> >>> If SU is disabled and One tries to enable SUJ then SU will be >>> automatically enabled. >>> So Why not automatically disable SUJ when One tries to disable SU? >> >> I'm probably not a big fan of either really. :) =A0For something as rare= ly >> done >> as tunefs I would prefer to err on the side of caution and require the a= dmin >> to explicitly specify everything. > > Hi John. I agree with you, I do prefer a fail of tunefs in this > situation. Before of I have posted the first patch I have done another > one that fails to enable SUJ when SU is disabled and fails to disable > SU when SUJ is enabled. Now this patch is bellow and attached. > > *All the stuff that I will say bellow is based on the attached patch* > > The attached patch fails to disable SU when SUJ is enabled. > And it fails to enable SUJ when SU is disabled. > > Earlier I decided to not post the patch because it will cause > confusion when SU and SUJ is disabled and you try to do something such > as: > # tunefs -j enable -n enable /dev/ad2s1d > > The flags's processing order is alphabetically, so It will try to > enable SUJ first (and it will fail) and after it will enable SU. We > could resolve this by processing '-n' (SU) first and after '-j' (SUJ) > but this schema will make to fail the following command: > # tunefs -j disable -n disable /dev/ad2s1d > > So I think we could create a function for each flag to be processed > and the main() calls this functions as necessary (and main() disabled > the relative flag so the function will not be called again). > > But I'm just a curious doing trivial patches, You can talk about this > with more experience and knowlege. > > =3D=3D=3D=3D=3D=3D=3D=3D=3Dpatch=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > > Index: sbin/tunefs/tunefs.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- sbin/tunefs/tunefs.c =A0 =A0(revision 208584) > +++ sbin/tunefs/tunefs.c =A0 =A0(working copy) > @@ -341,16 +341,19 @@ > =A0 =A0if (jflag) { > =A0 =A0 =A0 =A0name =3D "soft updates journaling"; > =A0 =A0 =A0 =A0if (strcmp(jvalue, "enable") =3D=3D 0) { > - =A0 =A0 =A0 =A0 =A0 if ((sblock.fs_flags & (FS_DOSOFTDEP | FS_SUJ)) =3D= =3D > - =A0 =A0 =A0 =A0 =A0 =A0 =A0 (FS_DOSOFTDEP | FS_SUJ)) { > + =A0 =A0 =A0 =A0 =A0 if ((sblock.fs_flags & FS_SUJ) =3D=3D FS_SUJ) { > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("%s remains unchanged as enabled", n= ame); > + =A0 =A0 =A0 =A0 =A0 } else if ((sblock.fs_flags & FS_DOSOFTDEP) !=3D > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 FS_DOSOFTDEP) { > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 warnx("%s cannot be enabled until soft upda= tes is enabled", > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 name); > =A0 =A0 =A0 =A0 =A0 =A0} else if (sblock.fs_clean =3D=3D 0) { > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("%s cannot be enabled until fsck is = run", > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0name); > =A0 =A0 =A0 =A0 =A0 =A0} else if (journal_alloc(Svalue) !=3D 0) { > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("%s can not be enabled", name); > =A0 =A0 =A0 =A0 =A0 =A0} else { > - =A0 =A0 =A0 =A0 =A0 =A0 =A0 sblock.fs_flags |=3D FS_DOSOFTDEP | FS_SUJ; > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 sblock.fs_flags |=3D FS_SUJ; I assume FS_DOSOFTDEP is being set elsewhere in the code? > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("%s set", name); > =A0 =A0 =A0 =A0 =A0 =A0} > =A0 =A0 =A0 =A0} else if (strcmp(jvalue, "disable") =3D=3D 0) { > @@ -459,6 +462,9 @@ > =A0 =A0 =A0 =A0} else if (strcmp(nvalue, "disable") =3D=3D 0) { > =A0 =A0 =A0 =A0 =A0 =A0if ((~sblock.fs_flags & FS_DOSOFTDEP) =3D=3D FS_DO= SOFTDEP) > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("%s remains unchanged as disabled", = name); > + =A0 =A0 =A0 =A0 =A0 else if ((sblock.fs_flags & FS_SUJ) =3D=3D FS_SUJ) > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 warnx("%s cannot be enabled until soft upda= tes \ > +journaling is disabled", name); This message doesn't make sense (enable vs disable). > =A0 =A0 =A0 =A0 =A0 =A0else { > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0sblock.fs_flags &=3D ~FS_DOSOFTDEP; > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warnx("%s cleared", name); Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Fri May 28 01:31:32 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA3FD1065745; Fri, 28 May 2010 01:31:32 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 7E69E8FC21; Fri, 28 May 2010 01:31:32 +0000 (UTC) Received: by mail-qy0-f181.google.com with SMTP id 11so999447qyk.13 for ; Thu, 27 May 2010 18:31:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Mr6sE69zWHRnMN9cln/Z3gCtuHbY57k/a27uDioRpsc=; b=KTpYgnLoeqczzX/Fhb77NNfUsduigMKaJRN9U6iiTxKQxtr9//3GDi9ikF2xvH19N7 rLUTNWIP0xG82IVDo3sK01KasRO5879YRzQwV8d5SZCrLYmZGyavJg9MoOVuQZCo+N2j 2/RkWCNCpIPPevVXlth5YAozFjJ3zUvjaPVG8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=eDPxq4I5d/4w9jfEugj1j1gkRUG/sVABRnKpFiKItPwYLEKuK2XGMWRwkxf1buqygM GKc6HS7rWoV08pp0l6CZtTowNjkrBIyyAIpVLSwbUQUoTm4b9ALI/w3Vu+ewL0DMctUy HSEfA0lXfJFdRJUlDNGzWkfus3UlGhnX9TVKs= MIME-Version: 1.0 Received: by 10.229.38.148 with SMTP id b20mr2509781qce.139.1275010292268; Thu, 27 May 2010 18:31:32 -0700 (PDT) Received: by 10.229.190.83 with HTTP; Thu, 27 May 2010 18:31:32 -0700 (PDT) In-Reply-To: <201005271147.20155.jhb@freebsd.org> References: <201005270933.42760.jhb@freebsd.org> <201005271147.20155.jhb@freebsd.org> Date: Thu, 27 May 2010 18:31:32 -0700 Message-ID: From: Garrett Cooper To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Marcelo/Porks , freebsd-current@freebsd.org, Jeff Roberson Subject: Re: SUJ Changes 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, 28 May 2010 01:31:32 -0000 On Thu, May 27, 2010 at 8:47 AM, John Baldwin wrote: > On Thursday 27 May 2010 10:13:38 am Marcelo/Porks wrote: >> On Thu, May 27, 2010 at 10:33 AM, John Baldwin wrote: >> > On Wednesday 26 May 2010 7:56:24 pm Garrett Cooper wrote: >> >> On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks > wrote: >> >> > >> >> > Hi guys. I'm not sure if I could call this a problem but I can disa= ble >> >> > SU when SUJ is enabled, so SUJ will remain enabled and SU will be >> >> > disabled. >> >> > >> >> > #tunefs -j enable /dev/device >> >> > #tunefs -n disable /dev/device >> >> > >> >> > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the us= er >> >> > disable SU. Maybe this will be useful for some of you. >> >> > >> >> > Thanks. >> >> > >> >> > >> >> > Index: sbin/tunefs/tunefs.c >> >> > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> >> > --- sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(revision 208580) >> >> > +++ sbin/tunefs/tunefs.c =A0 =A0 =A0 =A0(working copy) >> >> > @@ -460,6 +460,14 @@ >> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0if ((~sblock.fs_flag= s & FS_DOSOFTDEP) =3D=3D >> > FS_DOSOFTDEP) >> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warn= x("%s remains unchanged as > disabled", >> > name); >> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0else { >> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 /* al= so disable SUJ */ >> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 if ((= sblock.fs_flags & FS_SUJ) =3D=3D > FS_SUJ) >> > { >> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 warnx("soft updates journaling >> >> > will be disabled too"); >> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 journal_clear(); >> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 sblock.fs_flags &=3D ~FS_SUJ; >> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 sblock.fs_sujfree =3D 0; >> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 = =A0 =A0 =A0 warnx("remove .sujournal to >> >> > reclaim space"); >> >> > + =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 } >> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0sblo= ck.fs_flags &=3D ~FS_DOSOFTDEP; >> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0warn= x("%s cleared", name); >> >> > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0} >> >> >> > I think that attempting to disable SU if SUJ >> > is enabled should just fail with an error message. =A0The sysadmin can= then >> > choose to disable both SUJ and SU if desired. >> >> If SU is disabled and One tries to enable SUJ then SU will be >> automatically enabled. >> So Why not automatically disable SUJ when One tries to disable SU? > > I'm probably not a big fan of either really. :) =A0For something as rarel= y done > as tunefs I would prefer to err on the side of caution and require the ad= min > to explicitly specify everything. Yeah... I suppose that makes more functional sense. -Garrett From owner-freebsd-current@FreeBSD.ORG Fri May 28 02:04:18 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 715631065675 for ; Fri, 28 May 2010 02:04:18 +0000 (UTC) (envelope-from marcelorossi@gmail.com) Received: from mail-qy0-f181.google.com (mail-qy0-f181.google.com [209.85.221.181]) by mx1.freebsd.org (Postfix) with ESMTP id 297D88FC14 for ; Fri, 28 May 2010 02:04:17 +0000 (UTC) Received: by qyk11 with SMTP id 11so1043633qyk.13 for ; Thu, 27 May 2010 19:04:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=jI3q6rqO4n7CTPiHWIOwUqPuQK1YnTQS2gGmxuDezr4=; b=BOZE2AmheRrXFZewcByvLmKvAdolFn6IReCNwSFEawhH5PGUhYRg4ZR8Xme47iaCOo GVo5HohjYLVVUzaJgtL3FxaaZL+ghkwFEXZLyzWW1h5EVcGi2HfuFk6INxDKdGiScHXj JvuyXjuXAJTJQ1TI04yU6EouyfyNyqpix1TBQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=lA6iJ0CXxT0+n0qltHE2klqJ2sfXdGkD5xPMyj73kMlMYBZCQVeuuRcqb+jCW+mE1o hae8BPrY5rKGOZaP7sdHE7+ykEB0DkI8CXp8RyQ8HHyhz0BEPSKlLmaRMd32HRSoS7BK pI8qDFMUtHrwV0dCus2X+DFtb7z+HPmSXN+2w= MIME-Version: 1.0 Received: by 10.229.182.1 with SMTP id ca1mr2493665qcb.158.1275012257281; Thu, 27 May 2010 19:04:17 -0700 (PDT) Received: by 10.229.80.6 with HTTP; Thu, 27 May 2010 19:04:16 -0700 (PDT) In-Reply-To: References: <201005270933.42760.jhb@freebsd.org> <201005271147.20155.jhb@freebsd.org> Date: Thu, 27 May 2010 23:04:16 -0300 Message-ID: From: "Marcelo/Porks" To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: SUJ Changes 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, 28 May 2010 02:04:18 -0000 On 5/27/10, Garrett Cooper wrote: > On Thu, May 27, 2010 at 3:44 PM, Marcelo/Porks > wrote: >> On 5/27/10, John Baldwin wrote: >>> On Thursday 27 May 2010 10:13:38 am Marcelo/Porks wrote: >>>> On Thu, May 27, 2010 at 10:33 AM, John Baldwin wrote: >>>> > On Wednesday 26 May 2010 7:56:24 pm Garrett Cooper wrote: >>>> >> On Wed, May 26, 2010 at 3:52 PM, Marcelo/Porks >>>> >> >>>> >> >>> wrote: >>>> >> > >>>> >> > Hi guys. I'm not sure if I could call this a problem but I can >>>> >> > disable >>>> >> > SU when SUJ is enabled, so SUJ will remain enabled and SU will be >>>> >> > disabled. >>>> >> > >>>> >> > #tunefs -j enable /dev/device >>>> >> > #tunefs -n disable /dev/device >>>> >> > >>>> >> > I did a patch for sbin/tunefs/tunefs.c that disable SUJ when the >>>> >> > user >>>> >> > disable SU. Maybe this will be useful for some of you. >>>> >> > >>>> >> > Thanks. >>>> >> > >>>> >> > >>>> >> > Index: sbin/tunefs/tunefs.c >>>> >> > =================================================================== >>>> >> > --- sbin/tunefs/tunefs.c (revision 208580) >>>> >> > +++ sbin/tunefs/tunefs.c (working copy) >>>> >> > @@ -460,6 +460,14 @@ >>>> >> > if ((~sblock.fs_flags & FS_DOSOFTDEP) == >>>> > FS_DOSOFTDEP) >>>> >> > warnx("%s remains unchanged as >>> disabled", >>>> > name); >>>> >> > else { >>>> >> > + /* also disable SUJ */ >>>> >> > + if ((sblock.fs_flags & FS_SUJ) == >>> FS_SUJ) >>>> > { >>>> >> > + warnx("soft updates >>>> >> > journaling >>>> >> > will be disabled too"); >>>> >> > + journal_clear(); >>>> >> > + sblock.fs_flags &= ~FS_SUJ; >>>> >> > + sblock.fs_sujfree = 0; >>>> >> > + warnx("remove .sujournal to >>>> >> > reclaim space"); >>>> >> > + } >>>> >> > sblock.fs_flags &= ~FS_DOSOFTDEP; >>>> >> > warnx("%s cleared", name); >>>> >> > } >>>> >> >>>> > I think that attempting to disable SU if SUJ >>>> > is enabled should just fail with an error message. The sysadmin can >>>> > then >>>> > choose to disable both SUJ and SU if desired. >>>> >>>> If SU is disabled and One tries to enable SUJ then SU will be >>>> automatically enabled. >>>> So Why not automatically disable SUJ when One tries to disable SU? >>> >>> I'm probably not a big fan of either really. :) For something as rarely >>> done >>> as tunefs I would prefer to err on the side of caution and require the >>> admin >>> to explicitly specify everything. >> >> Hi John. I agree with you, I do prefer a fail of tunefs in this >> situation. Before of I have posted the first patch I have done another >> one that fails to enable SUJ when SU is disabled and fails to disable >> SU when SUJ is enabled. Now this patch is bellow and attached. >> >> *All the stuff that I will say bellow is based on the attached patch* >> >> The attached patch fails to disable SU when SUJ is enabled. >> And it fails to enable SUJ when SU is disabled. >> >> Earlier I decided to not post the patch because it will cause >> confusion when SU and SUJ is disabled and you try to do something such >> as: >> # tunefs -j enable -n enable /dev/ad2s1d >> >> The flags's processing order is alphabetically, so It will try to >> enable SUJ first (and it will fail) and after it will enable SU. We >> could resolve this by processing '-n' (SU) first and after '-j' (SUJ) >> but this schema will make to fail the following command: >> # tunefs -j disable -n disable /dev/ad2s1d >> >> So I think we could create a function for each flag to be processed >> and the main() calls this functions as necessary (and main() disabled >> the relative flag so the function will not be called again). >> >> But I'm just a curious doing trivial patches, You can talk about this >> with more experience and knowlege. >> >> =========patch========== >> >> Index: sbin/tunefs/tunefs.c >> =================================================================== >> --- sbin/tunefs/tunefs.c (revision 208584) >> +++ sbin/tunefs/tunefs.c (working copy) >> @@ -341,16 +341,19 @@ >> if (jflag) { >> name = "soft updates journaling"; >> if (strcmp(jvalue, "enable") == 0) { >> - if ((sblock.fs_flags & (FS_DOSOFTDEP | FS_SUJ)) == >> - (FS_DOSOFTDEP | FS_SUJ)) { >> + if ((sblock.fs_flags & FS_SUJ) == FS_SUJ) { >> warnx("%s remains unchanged as enabled", name); >> + } else if ((sblock.fs_flags & FS_DOSOFTDEP) != >> + FS_DOSOFTDEP) { >> + warnx("%s cannot be enabled until soft updates is >> enabled", >> + name); >> } else if (sblock.fs_clean == 0) { >> warnx("%s cannot be enabled until fsck is run", >> name); >> } else if (journal_alloc(Svalue) != 0) { >> warnx("%s can not be enabled", name); >> } else { >> - sblock.fs_flags |= FS_DOSOFTDEP | FS_SUJ; >> + sblock.fs_flags |= FS_SUJ; > > I assume FS_DOSOFTDEP is being set elsewhere in the code? > >> warnx("%s set", name); >> } >> } else if (strcmp(jvalue, "disable") == 0) { >> @@ -459,6 +462,9 @@ >> } else if (strcmp(nvalue, "disable") == 0) { >> if ((~sblock.fs_flags & FS_DOSOFTDEP) == FS_DOSOFTDEP) >> warnx("%s remains unchanged as disabled", name); >> + else if ((sblock.fs_flags & FS_SUJ) == FS_SUJ) >> + warnx("%s cannot be enabled until soft updates \ >> +journaling is disabled", name); > > This message doesn't make sense (enable vs disable). Oh for god shake, I'm sorry. The correct message was supposed to be: warnx("%s cannot be disabled until soft updates journaling is disabled", name); Sorry... -- Marcelo Rossi "This e-mail is provided "AS IS" with no warranties, and confers no rights." From owner-freebsd-current@FreeBSD.ORG Fri May 28 10:58:19 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 913551065676 for ; Fri, 28 May 2010 10:58:19 +0000 (UTC) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.freebsd.org (Postfix) with ESMTP id 46B898FC0C for ; Fri, 28 May 2010 10:58:19 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by solfertje.student.utwente.nl (Postfix) with SMTP id C162F8051 for ; Fri, 28 May 2010 12:58:17 +0200 (CEST) Received: from bommel.internal (bommel.internal [10.236.150.2]) by solfertje.student.utwente.nl (Postfix) with ESMTP id 304A78050; Fri, 28 May 2010 12:58:11 +0200 (CEST) Message-ID: <4BFFA1C3.3050901@solfertje.student.utwente.nl> Date: Fri, 28 May 2010 12:58:11 +0200 From: Alban Hertroys User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.9) Gecko/20100527 Thunderbird/3.0.4 MIME-Version: 1.0 To: Andriy Gapon References: <16DEFF8A-DBBB-4F4F-9C0E-FAFBF444E7FE@solfertje.student.utwente.nl> <4BFE5893.5090609@icyb.net.ua> In-Reply-To: <4BFE5893.5090609@icyb.net.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Fri May 28 12:58:17 2010 X-DSPAM-Confidence: 1.0000 X-DSPAM-Probability: 0.0023 X-DSPAM-Signature: 930,4bffa1c910415538290380 X-DSPAM-Factors: 27, gpart+show, 0.40000, but, 0.40000, but, 0.40000, presented, 0.40000, From*Alban, 0.40000, 2097152+2, 0.40000, anything+>, 0.40000, just, 0.40000, 18874530+1024000, 0.40000, boot+from, 0.40000, 1024000, 0.40000, 625142381, 0.40000, References* Subject: Re: GPT on amd64 and boot managers 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, 28 May 2010 10:58:19 -0000 On 05/27/10 13:33, Andriy Gapon wrote: > on 27/05/2010 13:55 Alban Hertroys said the following: >> I can boot FreeBSD just fine off GPT, but I have to select in the BIOS whether >> I want to boot FreeBSD or Windows (by means of changing the boot sequence). A >> working boot manager would be so much more convenient for that. > > Right. > OTOH I have standard GPT installation (pmbr + gptzfsboot) and during boot I am > presented with a choice which _hard disk_ to boot from. I didn't do anything > special for that. Not exactly a boot manager, but OK for me. I'd be quite happy to have something like that, do you have any idea what's doing that for you? I suspect it is your BIOS, as I don't get that choice and AFAIK I also have a standard GPT installation - I literally followed the examples in man gpart up to the point where freebsd-ufs partitions are added. This is my partition layout: dalroi:bommel > gpart show ada0 => 34 625142381 ada0 GPT (298G) 34 128 1 freebsd-boot (64K) 162 2097152 2 freebsd-ufs (1.0G) 2097314 16777216 3 freebsd-swap (8.0G) 18874530 1024000 4 freebsd-ufs (500M) 19898530 2097152 5 freebsd-ufs (1.0G) 21995682 41943040 6 freebsd-ufs (20G) 63938722 561203693 7 freebsd-ufs (268G) !DSPAM:930,4bffa1c910415538290380! From owner-freebsd-current@FreeBSD.ORG Fri May 28 11:29:14 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64EB01065673 for ; Fri, 28 May 2010 11:29:14 +0000 (UTC) (envelope-from dalroi@solfertje.student.utwente.nl) Received: from solfertje.student.utwente.nl (solfertje.student.utwente.nl [130.89.167.40]) by mx1.freebsd.org (Postfix) with ESMTP id EF9D18FC1D for ; Fri, 28 May 2010 11:29:13 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by solfertje.student.utwente.nl (Postfix) with SMTP id 98DAD8050 for ; Fri, 28 May 2010 13:29:12 +0200 (CEST) Received: from bommel.internal (bommel.internal [10.236.150.2]) by solfertje.student.utwente.nl (Postfix) with ESMTP id B67378034 for ; Fri, 28 May 2010 13:29:03 +0200 (CEST) Message-ID: <4BFFA8FF.2030405@solfertje.student.utwente.nl> Date: Fri, 28 May 2010 13:29:03 +0200 From: Alban Hertroys User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.9) Gecko/20100527 Thunderbird/3.0.4 MIME-Version: 1.0 To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DSPAM-Result: Innocent X-DSPAM-Processed: Fri May 28 13:29:12 2010 X-DSPAM-Confidence: 0.9899 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 930,4bffa90810411104319959 X-DSPAM-Factors: 27, but, 0.01000, but, 0.01000, From*Alban, 0.01000, Date*May, 0.01000, from, 0.01000, of, 0.01000, of, 0.01000, Received*ESMTP, 0.01000, that, 0.01000, Received*May+2010, 0.01000, Date*2010, 0.01000, From*Hertroys, 0.01000, From*solfertje.student.utwente.nl>, 0.01000, in, 0.01000, in, 0.01000, Received*May, 0.01000, Received*with, 0.01000, Received*id, 0.01000, Received*ESMTP+id, 0.01000, Received*2010, 0.01000, From*Hertroys+ List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 May 2010 11:29:14 -0000 Hello, I see this message a couple of times in my dmesg every time I boot and I'm wondering from which device these messages originate and whether they might be harmful in some way? They don't seem to cause any trouble, but it's probably better if they weren't there. Below are the relevant section of my dmesg and the output of usbconfig: ugen5.4: at usbus5 ums0: on usbus5 ums0: 3 buttons and [XYZ] coordinates ID=0 Root mount waiting for: usbus5 Root mount waiting for: usbus5 ugen5.5: at usbus5 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 uhid1: on usbus5 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 hid_get_item: Number of items truncated to 255 ugen5.6: at usbus5 ukbd0: on usbus5 kbd2 at ukbd0 uhid2: on usbus5 ugen0.1: at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen1.1: at usbus1, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen2.1: at usbus2, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen3.1: at usbus3, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen4.1: at usbus4, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen5.1: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON ugen1.2: at usbus1, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen5.2: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen5.3: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen5.4: at usbus5, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON ugen5.5: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON ugen5.6: at usbus5, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON I found that vendor 0x05ac is Apple Computer Inc and therefore I suspect the device that's causing these errors could be the brightness control in my Apple Cinema display. The first of below devices is probably the USB-hub in the display and the second the brightness control, but it could be the other way around. ugen5.3: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE ugen5.5: at usbus5, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON The other unrecognised device, in case someone wants to add it somewhere: ugen5.2: at usbus5, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE This is a Belkin n52te game-controller (http://www.belkin.com/IWCatProductPage.process?Product_Id=390404) !DSPAM:930,4bffa90810411104319959! From owner-freebsd-current@FreeBSD.ORG Fri May 28 16:52:16 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 745D61065673 for ; Fri, 28 May 2010 16:52:16 +0000 (UTC) (envelope-from avg@icyb.net.ua) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id AFCE58FC17 for ; Fri, 28 May 2010 16:52:15 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id TAA15207; Fri, 28 May 2010 19:52:09 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4BFFF4B8.9010203@icyb.net.ua> Date: Fri, 28 May 2010 19:52:08 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.24 (X11/20100517) MIME-Version: 1.0 To: Alban Hertroys References: <16DEFF8A-DBBB-4F4F-9C0E-FAFBF444E7FE@solfertje.student.utwente.nl> <4BFE5893.5090609@icyb.net.ua> <4BFFA1C3.3050901@solfertje.student.utwente.nl> In-Reply-To: <4BFFA1C3.3050901@solfertje.student.utwente.nl> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: GPT on amd64 and boot managers 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, 28 May 2010 16:52:16 -0000 on 28/05/2010 13:58 Alban Hertroys said the following: > On 05/27/10 13:33, Andriy Gapon wrote: >> on 27/05/2010 13:55 Alban Hertroys said the following: >>> I can boot FreeBSD just fine off GPT, but I have to select in the >>> BIOS whether >>> I want to boot FreeBSD or Windows (by means of changing the boot >>> sequence). A >>> working boot manager would be so much more convenient for that. >> >> Right. >> OTOH I have standard GPT installation (pmbr + gptzfsboot) and during >> boot I am >> presented with a choice which _hard disk_ to boot from. I didn't do >> anything >> special for that. Not exactly a boot manager, but OK for me. > > I'd be quite happy to have something like that, do you have any idea > what's doing that for you? I suspect it is your BIOS, as I don't get > that choice and AFAIK I also have a standard GPT installation - I > literally followed the examples in man gpart up to the point where > freebsd-ufs partitions are added. Looks like I was confused - this was on a system where ZFS was installed in a slice and boot0 was used as MBR. Sorry for misleading you. I wonder if it's possible to cram both disk selection support and GPT support in 512 bytes by throwing out something... Or perhaps add boot manager functions to gptboot, that sounds easier. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Fri May 28 17:17:43 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id 86A4B1065674; Fri, 28 May 2010 17:17:42 +0000 (UTC) (envelope-from nork@FreeBSD.org) Date: Sat, 29 May 2010 02:17:41 +0900 From: Norikatsu Shigemura To: Roman Divacky Message-Id: <20100529021741.674bf85f.nork@FreeBSD.org> X-Mailer: Sylpheed 3.0.2 (GTK+ 2.20.1; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: clangBSD build error on r208621 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, 28 May 2010 17:17:43 -0000 Hi rdivacky. I svn updated latest clangBSD: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ svn info Path: . URL: file:///home/nork/.svk/local/freebsd/base/projects/clangbsd Repository Root: file:///home/nork/.svk/local Repository UUID: c867b0bc-624e-df11-a429-00248c1b55b2 Revision: 208621 Node Kind: directory Schedule: normal Last Changed Author: rdivacky Last Changed Rev: 208621 Last Changed Date: 2010-05-29 00:45:17 +0900 (Sat, 29 May 2010) - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - But I got following error: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -------------------------------------------------------------- >>> stage 4.2: building libraries -------------------------------------------------------------- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj MACHINE_ARCH=amd64 MACHINE=amd64 CPUTYPE= GROFF_BIN_PATH=/usr/obj/usr/src/tmp/legacy/usr/bin GROFF_FONT_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/groff_font GROFF_TMAC_PATH=/usr/obj/usr/src/tmp/legacy/usr/share/tmac _SHLIBDIRPREFIX=/usr/obj/usr/src/tmp VERSION="FreeBSD 9.0-CURRENT amd64 900010" INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/bin CC="clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/" CXX="clang++ -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/" NO_CTF=1 make -f Makefile.inc1 DESTDIR=/usr/obj/usr/src/tmp -DNO_FSCHG -DWITHOUT_HTML -DWITHOUT_INFO -DNO_LINT -DWITHOUT_MAN -DWITHOUT_PROFILE libraries cd /usr/src; make -f Makefile.inc1 _prereq_libs; make -f Makefile.inc1 _startup_libs; make -f Makefile.inc1 _prebuild_libs; make -f Makefile.inc1 _generic_libs; ===> gnu/lib/libssp/libssp_nonshared (obj,depend,all,install) rm -f .depend CC='clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/' mkdep -f .depend -a -DHAVE_CONFIG_H -I/usr/src/gnu/lib/libssp/libssp_nonshared/.. -I/usr/src/gnu/lib/libssp/libssp_nonshared/../../../../contrib/gcclibs/libssp -I/usr/src/gnu/lib/libssp/libssp_nonshared/../../../../contrib/gcclibs/include -DPIC /usr/src/gnu/lib/libssp/libssp_nonshared/../../../../contrib/gcclibs/libssp/ssp-local.c error: unknown argument: '-ferror-limit' mkdep: compile failed *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Do you have any idea? Of cause I set following environment: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ cat /etc/src.conf NO_WERROR= WERROR= - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- Norikatsu Shigemura From owner-freebsd-current@FreeBSD.ORG Fri May 28 20:18:25 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F85E106564A for ; Fri, 28 May 2010 20:18:25 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 334298FC0A for ; Fri, 28 May 2010 20:18:24 +0000 (UTC) Received: (qmail 24933 invoked by uid 399); 28 May 2010 20:18:22 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 28 May 2010 20:18:22 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C00250D.10603@FreeBSD.org> Date: Fri, 28 May 2010 13:18:21 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: wpi not working on today's current (r208626) 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, 28 May 2010 20:18:25 -0000 I am trying to update -current in order to try kib's patch for the nvidia driver, and the wpi driver won't establish a connection. I'm using r207134 right now without any problems, but that's a long time back to try and do a binary search. I don't see any changes to wpi or wpa_supplicant between then and now, anyone have an idea of where to look? My WAP is using WPA2 with AES if that's any help. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Fri May 28 22:03:55 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C5BC31065672 for ; Fri, 28 May 2010 22:03:55 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 5972A8FC17 for ; Fri, 28 May 2010 22:03:55 +0000 (UTC) Received: (qmail 11548 invoked by uid 399); 28 May 2010 22:03:54 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 28 May 2010 22:03:54 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C003DC9.3010603@FreeBSD.org> Date: Fri, 28 May 2010 15:03:53 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org References: <4C00250D.10603@FreeBSD.org> In-Reply-To: <4C00250D.10603@FreeBSD.org> X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)) 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, 28 May 2010 22:03:55 -0000 On 05/28/10 13:18, Doug Barton wrote: > I am trying to update -current in order to try kib's patch for the > nvidia driver, and the wpi driver won't establish a connection. I'm > using r207134 right now without any problems, but that's a long time > back to try and do a binary search. > > I don't see any changes to wpi or wpa_supplicant between then and now, > anyone have an idea of where to look? My WAP is using WPA2 with AES if > that's any help. Correction, the problem seems to be more generally with wpa_supplicant. I tried with the new kernel and my ath PCMCIA card (AR5416 mac 13.10 RF2133 phy 8.1) and it doesn't work with the latest kernel either. However, the same card is working fine with the older kernel (I'm using it now). Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Fri May 28 23:50:05 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF3E2106566B; Fri, 28 May 2010 23:50:05 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id 312208FC16; Fri, 28 May 2010 23:50:04 +0000 (UTC) Received: by wwb34 with SMTP id 34so550834wwb.13 for ; Fri, 28 May 2010 16:50:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to:date :message-id:subject:from:to:cc:content-type; bh=nPlzlDGV1P5W/NcFm37uBlNlnDX8OtU/cRZOWbdmRmI=; b=wrYoud6oFSsK1L1SzESYNSNf83UCWA2wRVWA80KKxvtXQKdMqWZ+4THyTY42YpyCs4 oqQMBLK+rcksy2Bds0QgvWhv1Mb3aP4QfsspWNdzEVHlHJOp/uvhhqF6FPuI8QijZEX7 FwFWCh64k2tQYi1DSB/s7u1yqI022pbhLbHaU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:cc :content-type; b=OnvDXz+YrH+6eFH6M2WODBNT704QW5guRJXymEDqGCgE2dm/MU4yf/Vj4+HvFCZBBi 5b/5gz/L4XgzJXIw4TDH4v/bB0qkj3A00ttirhj1ueXjKwT+/gCLE2tcvrMFZTvZNx7O zBOBk+5u3W+xNjuXboAQaN2MR/EgjILrlOABM= MIME-Version: 1.0 Received: by 10.216.185.209 with SMTP id u59mr2090042wem.112.1275090603353; Fri, 28 May 2010 16:50:03 -0700 (PDT) Received: by 10.216.158.146 with HTTP; Fri, 28 May 2010 16:50:03 -0700 (PDT) Date: Fri, 28 May 2010 19:50:03 -0400 Message-ID: From: "b. f." To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: dougb@FreeBSD.org Subject: Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@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, 28 May 2010 23:50:05 -0000 >On 05/28/10 13:18, Doug Barton wrote: >> I am trying to update -current in order to try kib's patch for the >> nvidia driver, and the wpi driver won't establish a connection. I'm >> using r207134 right now without any problems, but that's a long time >> back to try and do a binary search. >> >> I don't see any changes to wpi or wpa_supplicant between then and now, >> anyone have an idea of where to look? My WAP is using WPA2 with AES if >> that's any help. > >Correction, the problem seems to be more generally with wpa_supplicant. >I tried with the new kernel and my ath PCMCIA card (AR5416 mac 13.10 >RF2133 phy 8.1) and it doesn't work with the latest kernel either. >However, the same card is working fine with the older kernel (I'm using >it now). I can't see any problems when using WPA2 with AES on r208606 i386 with uath(4). I'm updating this machine to r208630 tonight, and if I encounter problems with the later revision, I'll let you know. Are you saying that you experienced problems when trying to use a r207134 base with a r208626 kernel? If that's the case, I would recommend updating the base to the same revision as the kernel, and then retesting. b. From owner-freebsd-current@FreeBSD.ORG Sat May 29 02:59:57 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8950B1065676 for ; Sat, 29 May 2010 02:59:57 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 180CB8FC13 for ; Sat, 29 May 2010 02:59:56 +0000 (UTC) Received: (qmail 24118 invoked by uid 399); 29 May 2010 02:59:56 -0000 Received: from localhost (HELO ?192.168.0.145?) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 29 May 2010 02:59:56 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C00832A.4030102@FreeBSD.org> Date: Fri, 28 May 2010 19:59:54 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: bf1783@gmail.com References: In-Reply-To: X-Enigmail-Version: 1.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, "b. f." Subject: Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)) 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, 29 May 2010 02:59:57 -0000 On 5/28/2010 4:50 PM, b. f. wrote: > > I can't see any problems when using WPA2 with AES on r208606 i386 with > uath(4). I'm updating this machine to r208630 tonight, and if I > encounter problems with the later revision, I'll let you know. Ok, thanks. > Are > you saying that you experienced problems when trying to use a r207134 > base with a r208626 kernel? If that's the case, I would recommend > updating the base to the same revision as the kernel, and then > retesting. Yes, that's what I'm doing I actually tried running the newly built wpa_supplicant but that didn't work. I'm kind of hesitant to do the full upgrade since I'm having kernel problems with the nvidia driver, but if I'm sure wpa_supplicant will work then I suppose I can bite the bullet. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Sat May 29 04:39:26 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9AE1E106566C; Sat, 29 May 2010 04:39:26 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 08E318FC15; Sat, 29 May 2010 04:39:25 +0000 (UTC) Received: by wyj26 with SMTP id 26so384095wyj.13 for ; Fri, 28 May 2010 21:39:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=TPOR6A7iD7j1QuSIqpv9Dg2vOmQLKVlh0DVOXh3gE4Q=; b=GVpUjJVj6hGLX/jvjxbKO9iiadbPxRlC8AMHi1J+UZXLwsIxjxWG8N0qRkMpocphzZ 6SgqsqP6a39LuNk+adBkyV+csr6kqbm1yX6rxr1liQ//7MzQVKTEtz0pOub8IQAyEExN 7uaCgWANN7CG3CkTPP5qSBKwPSdCGRM2Jff2Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=ifgsajTYtx1hc7q4yd0cumVJdDpZCf39+hnfd3taXfMwJgM6iO5/TroMOtwzKeP4nE c5s7Ysh7tTb4rgHZ1Xlesg1F99YFz9DMZHLKhH0jTtzuouC3SvaJqlnb9RwlMgB1aUtg sUfVWJGUP9hZ6spEuwg3e1wMIyChux2DQGQvA= MIME-Version: 1.0 Received: by 10.216.179.200 with SMTP id h50mr2155723wem.73.1275107964940; Fri, 28 May 2010 21:39:24 -0700 (PDT) Received: by 10.216.158.146 with HTTP; Fri, 28 May 2010 21:39:24 -0700 (PDT) In-Reply-To: <4C00832A.4030102@FreeBSD.org> References: <4C00832A.4030102@FreeBSD.org> Date: Sat, 29 May 2010 00:39:24 -0400 Message-ID: From: "b. f." To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@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: Sat, 29 May 2010 04:39:26 -0000 On 5/28/10, Doug Barton wrote: > On 5/28/2010 4:50 PM, b. f. wrote: >> >> I can't see any problems when using WPA2 with AES on r208606 i386 with >> uath(4). I'm updating this machine to r208630 tonight, and if I >> encounter problems with the later revision, I'll let you know. > > Ok, thanks. > >> Are >> you saying that you experienced problems when trying to use a r207134 >> base with a r208626 kernel? If that's the case, I would recommend >> updating the base to the same revision as the kernel, and then >> retesting. > > Yes, that's what I'm doing I actually tried running the newly built > wpa_supplicant but that didn't work. I'm kind of hesitant to do the full > upgrade since I'm having kernel problems with the nvidia driver, but if > I'm sure wpa_supplicant will work then I suppose I can bite the bullet. > It appears that something is wrong. My wireless stick no longer associates with the network with r208630. I'll do some tinkering. b. From owner-freebsd-current@FreeBSD.ORG Sat May 29 07:47:13 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 26013106567B for ; Sat, 29 May 2010 07:47:13 +0000 (UTC) (envelope-from areilly@bigpond.net.au) Received: from nschwmtas06p.mx.bigpond.com (nschwmtas06p.mx.bigpond.com [61.9.189.152]) by mx1.freebsd.org (Postfix) with ESMTP id 5C5508FC15 for ; Sat, 29 May 2010 07:47:11 +0000 (UTC) Received: from nschwotgx03p.mx.bigpond.com ([124.188.161.100]) by nschwmtas06p.mx.bigpond.com with ESMTP id <20100529074710.WHGU26010.nschwmtas06p.mx.bigpond.com@nschwotgx03p.mx.bigpond.com> for ; Sat, 29 May 2010 07:47:10 +0000 Received: from duncan.reilly.home ([124.188.161.100]) by nschwotgx03p.mx.bigpond.com with ESMTP id <20100529074709.IFSP2192.nschwotgx03p.mx.bigpond.com@duncan.reilly.home> for ; Sat, 29 May 2010 07:47:09 +0000 Date: Sat, 29 May 2010 17:47:09 +1000 From: Andrew Reilly To: current@freebsd.org Message-ID: <20100529074709.GA40241@duncan.reilly.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Authentication-Info: Submitted using SMTP AUTH LOGIN at nschwotgx03p.mx.bigpond.com from [124.188.161.100] using ID areilly@bigpond.net.au at Sat, 29 May 2010 07:47:09 +0000 X-RPD-ScanID: Class unknown; VirusThreatLevel unknown, RefID str=0001.0A090204.4C00C67E.00C2,ss=1,fgs=0 X-SIH-MSG-ID: rx02ENT8TAD0zmQs0WyzOwJxyArnqyN48Z4QX81loRIGTUDCp8DeQ9rAIudRvN+vxDxFJhqCNGUnaa3kTY3Rs9mK Cc: Subject: Yoics! Just upgraded and cc is (mostly) bus-error-ing on buildworld. 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, 29 May 2010 07:47:13 -0000 Just to prefix with my config: FreeBSD duncan.reilly.home 9.0-CURRENT FreeBSD 9.0-CURRENT #7: Sat May 29 11:20:54 EST 2010 root@duncan.reilly.home:/nb/obj/nb/src/sys/DUNCAN amd64 Current source tree was csupped about half an hour ago. I don't think that my hardware has gone dodgy: everything else seems to be working properly. cc itself seems to work OK when compiling my own code, too. But make buildworld --> /nb/src/cddl/usr.bin/sgsmsg/../../../sys/cddl/contrib/opensolaris/common/avl/avl.c:128: internal compiler error: Bus error: 10 Please submit a full bug report, with preprocessed source if appropriate. See for instructions. *** Error code 1 Stop in /nb/src/cddl/usr.bin/sgsmsg. Also, if I run buildworld with -j4 (my usual config), then a different compile crashes the same way : /nb/src/cddl/usr.bin/sgsmsg/../../../cddl/contrib/opensolaris/cmd/sgs/tools/common/string_table.c:467: internal compiler error: Bus error: 10 but in that case it was not the first compile which broke, and several (parallel, I assume) broke at the same time. So: is anyone else seeing this? Is it likely that heisenbugs have found their way into the compiler in the last week, or perhaps in the kernel's page table handling code? More importantly: any thoughts about how I can proceed from here? Re-install from a snapshot? Cheers, -- Andrew From owner-freebsd-current@FreeBSD.ORG Sat May 29 10:20:27 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B1B41065679 for ; Sat, 29 May 2010 10:20:27 +0000 (UTC) (envelope-from rpaulo@freebsd.org) Received: from karen.lavabit.com (karen.lavabit.com [72.249.41.33]) by mx1.freebsd.org (Postfix) with ESMTP id D95BF8FC20 for ; Sat, 29 May 2010 10:20:26 +0000 (UTC) Received: from e.earth.lavabit.com (e.earth.lavabit.com [192.168.111.14]) by karen.lavabit.com (Postfix) with ESMTP id AB02A157546; Sat, 29 May 2010 05:20:22 -0500 (CDT) Received: from 10.0.10.3 (54.81.54.77.rev.vodafone.pt [77.54.81.54]) by lavabit.com with ESMTP id VJK577EJTNG2; Sat, 29 May 2010 05:20:22 -0500 Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: text/plain; charset=us-ascii From: Rui Paulo In-Reply-To: Date: Sat, 29 May 2010 11:20:18 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> References: <4C00832A.4030102@FreeBSD.org> To: bf1783@gmail.com X-Mailer: Apple Mail (2.1078) Cc: Doug Barton , freebsd-current@freebsd.org Subject: Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)) 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, 29 May 2010 10:20:27 -0000 On 29 May 2010, at 05:39, b. f. wrote: > On 5/28/10, Doug Barton wrote: >> On 5/28/2010 4:50 PM, b. f. wrote: >>>=20 >>> I can't see any problems when using WPA2 with AES on r208606 i386 = with >>> uath(4). I'm updating this machine to r208630 tonight, and if I >>> encounter problems with the later revision, I'll let you know. >>=20 >> Ok, thanks. >>=20 >>> Are >>> you saying that you experienced problems when trying to use a = r207134 >>> base with a r208626 kernel? If that's the case, I would recommend >>> updating the base to the same revision as the kernel, and then >>> retesting. >>=20 >> Yes, that's what I'm doing I actually tried running the newly built >> wpa_supplicant but that didn't work. I'm kind of hesitant to do the = full >> upgrade since I'm having kernel problems with the nvidia driver, but = if >> I'm sure wpa_supplicant will work then I suppose I can bite the = bullet. >>=20 >=20 > It appears that something is wrong. My wireless stick no longer > associates with the network with r208630. I'll do some tinkering. That's odd. The only way for that to happen would be caused bug in the = taskqueue stuff that zml committed, I think, but that's a long shot. Regards, -- Rui Paulo From owner-freebsd-current@FreeBSD.ORG Sat May 29 10:54:02 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60AA0106564A; Sat, 29 May 2010 10:54:02 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ww0-f54.google.com (mail-ww0-f54.google.com [74.125.82.54]) by mx1.freebsd.org (Postfix) with ESMTP id 736C58FC17; Sat, 29 May 2010 10:54:01 +0000 (UTC) Received: by wwb34 with SMTP id 34so798064wwb.13 for ; Sat, 29 May 2010 03:54:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to :in-reply-to:references:date:message-id:subject:from:to:cc :content-type; bh=w/mYc3i3nshkpcZ8QQ1inn2dVwmgTflXI7vT8pygDr4=; b=LEtS/R95QTPfZSyl+w8Ye8UnGgPxbxJBBeX9g45UQ7gJBMMstW6eiQnrsZfuiLVGGx lPAOIs025S/ZrlzkTxgBny3W0TDcQrMuF5HZTGc3fYc/KvGxAzxDe+FXRUnXtUUmLNqw bg8qJpGncCfjqcrZBCJRn37WRnEB4Mecn0Brg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; b=Jj7QjfyE8ev5G9nIpFuNM5Eq6hcLa0ZH5vAivsSe9NXcmqq2qMQM1dF8lUqwcOxOtz 6Aw5AlkwVJmCwIy05R7Bbl9mldSFpT3CPd75ndc2+igIxhFDmgcB8vaBJXWC6lB3ZH2J Sk6J0yzcCSRf+jPR5JCuvrf41kVSUsOMlKreM= MIME-Version: 1.0 Received: by 10.227.128.193 with SMTP id l1mr1424417wbs.197.1275130440347; Sat, 29 May 2010 03:54:00 -0700 (PDT) Received: by 10.216.158.146 with HTTP; Sat, 29 May 2010 03:54:00 -0700 (PDT) In-Reply-To: <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> References: <4C00832A.4030102@FreeBSD.org> <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> Date: Sat, 29 May 2010 06:54:00 -0400 Message-ID: From: "b. f." To: Rui Paulo Content-Type: text/plain; charset=ISO-8859-1 Cc: Doug Barton , zml@FreeBSD.org, freebsd-current@freebsd.org Subject: Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@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: Sat, 29 May 2010 10:54:02 -0000 On 5/29/10, Rui Paulo wrote: > > On 29 May 2010, at 05:39, b. f. wrote: > >> On 5/28/10, Doug Barton wrote: >>> On 5/28/2010 4:50 PM, b. f. wrote: >>>> >>>> I can't see any problems when using WPA2 with AES on r208606 i386 with >>>> uath(4). I'm updating this machine to r208630 tonight, and if I >>>> encounter problems with the later revision, I'll let you know. >>> >>> Ok, thanks. >>> >>>> Are >>>> you saying that you experienced problems when trying to use a r207134 >>>> base with a r208626 kernel? If that's the case, I would recommend >>>> updating the base to the same revision as the kernel, and then >>>> retesting. >>> >>> Yes, that's what I'm doing I actually tried running the newly built >>> wpa_supplicant but that didn't work. I'm kind of hesitant to do the full >>> upgrade since I'm having kernel problems with the nvidia driver, but if >>> I'm sure wpa_supplicant will work then I suppose I can bite the bullet. >>> >> >> It appears that something is wrong. My wireless stick no longer >> associates with the network with r208630. I'll do some tinkering. > > That's odd. The only way for that to happen would be caused bug in the > taskqueue stuff that zml committed, I think, but that's a long shot. > > Regards, > -- > Rui Paulo Yes, that was also my suspicion, and after seeing, via top(1), that ifconfig is stuck in the "*taskq" state while attempting to set up the wlan, I believe either r208623, or r208624, or both, is responsible for the regression. b. From owner-freebsd-current@FreeBSD.ORG Sat May 29 13:06:08 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2937C1065677 for ; Sat, 29 May 2010 13:06:08 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (lev.vlakno.cz [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id C1A728FC0C for ; Sat, 29 May 2010 13:06:07 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id A53709CB0D8 for ; Sat, 29 May 2010 15:02:42 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tgYWWCMStlWf for ; Sat, 29 May 2010 15:02:40 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 7DEB89CB1A1 for ; Sat, 29 May 2010 15:02:40 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id o4TD2e1G005544 for current@freebsd.org; Sat, 29 May 2010 15:02:40 +0200 (CEST) (envelope-from rdivacky) Date: Sat, 29 May 2010 15:02:40 +0200 From: Roman Divacky To: current@freebsd.org Message-ID: <20100529130240.GA99732@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: [TESTING]: ClangBSD branch needs testing before the import to HEAD 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, 29 May 2010 13:06:08 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable hi, ClangBSD was updated to LLVM/clang revision 104832 which is what we aim to = import into HEAD in roughly a week. We would like the initial import to be as pain= less as possible and therefore we ask you to test ClangBSD to assure that the re= vision we are importing does not have some really embarassing bugs. How to do it (on i386 and amd64): 0) install fresh devel/llvm-devel port 1) svn co http://svn.freebsd.org/base/projects/clangbsd src 2) echo NO_WERROR=3D >> /etc/src.conf ; echo WERROR=3D >> /etc/src.conf 3) cd src && make buildworld 4) make installworld DESTDIR=3D/usr/clangbsd 5) (optional) try to build kernel with clang and boot it 5.1) cd /sys/{arch}/conf 5.2) config YOUR_KERNEL 5.3) setenv CC clang in tcsh or export CC=3Dclang in bash 5.4) cd ../compile/YOUR_KERNEL 5.5) make && make install please make sure that it builds (on amd64/i386) and that the resulting world is runnable. ie. try to chroot into it and "do stuff". ie. chroot /clangbsd /bin/tcsh ... stuff ... there's a wiki page on this effort: http://wiki.freebsd.org/BuildingFreeBSD= WithClang please report back any problems/success to me and/or this mailing list.=20 thank you for your testing! Roman Divacky on behalf of the ClangBSD team --17pEHd4RhPHOinZp Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAkwBEHAACgkQLVEj6D3CBEzU9wCdGaSKqxEmb54TnBst6vdr/1QJ ODsAn10Y0vAP5iecMHaWeJlmZTzX+p4z =jxoj -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-current@FreeBSD.ORG Sat May 29 14:31:59 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with SMTP id 6D11D1065670; Sat, 29 May 2010 14:31:58 +0000 (UTC) (envelope-from nork@FreeBSD.org) Date: Sat, 29 May 2010 23:31:52 +0900 From: Norikatsu Shigemura To: Roman Divacky Message-Id: <20100529233152.a59cd08e.nork@FreeBSD.org> In-Reply-To: <20100529021741.674bf85f.nork@FreeBSD.org> References: <20100529021741.674bf85f.nork@FreeBSD.org> X-Mailer: Sylpheed 3.0.2 (GTK+ 2.20.1; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org, Norikatsu Shigemura Subject: Re: clangBSD build error on r208621 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, 29 May 2010 14:31:59 -0000 Hi rdivacky. On Sat, 29 May 2010 02:17:41 +0900 Norikatsu Shigemura wrote: > error: unknown argument: '-ferror-limit' > mkdep: compile failed > Do you have any idea? Of cause I set following environment: > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > $ cat /etc/src.conf > NO_WERROR= > WERROR= > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - OK, I got so that clang is too old. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ /usr/bin/clang --version clang version 1.5 (trunk) Target: x86_64-undermydesk-freebsd9.0 Thread model: posix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - So I did use latest clang by installing devel/llvm-devel. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - $ /usr/local/bin/clang --version clang version 2.0 (trunk) Target: x86_64-portbld-freebsd9.0 Thread model: posix - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - I can compile to well-known error point. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ===> sys/boot/i386/boot2 (all) dd if=/dev/zero of=boot2.ldr bs=512 count=1 1+0 records in 1+0 records out 512 bytes transferred in 0.000027 secs (18837576 bytes/sec) /usr/local/bin/clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/ -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -m32 -march=i386 -std=gnu99 -c /usr/src/sys/boot/i386/boot2/sio.S clang: warning: the clang compiler does not support '-fno-unit-at-a-time' clang: warning: argument unused during compilation: '-L/usr/obj/usr/src/tmp/usr/lib/' clang: warning: argument unused during compilation: '-fno-guess-branch-probability' clang: warning: argument unused during compilation: '-mno-align-long-strings' clang: warning: argument unused during compilation: '-mrtd' clang: warning: argument unused during compilation: '--param max-inline-insns-single=100' clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' objcopy -S -O binary boot1.out boot1 /usr/local/bin/clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/ -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -m32 -march=i386 -std=gnu99 -S -o boot2.s.tmp /usr/src/sys/boot/i386/boot2/boot2.c clang: warning: the clang compiler does not support '-fno-unit-at-a-time' clang: warning: argument unused during compilation: '-L/usr/obj/usr/src/tmp/usr/lib/' clang: warning: argument unused during compilation: '-fno-guess-branch-probability' clang: warning: argument unused during compilation: '-mno-align-long-strings' clang: warning: argument unused during compilation: '-mrtd' clang: warning: argument unused during compilation: '--param max-inline-insns-single=100' clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' /usr/src/sys/boot/i386/boot2/boot2.c:234:1: warning: no previous prototype for function 'main' [-Wmissing-prototypes] main(void) ^ 1 warning generated. sed -e '/align/d' -e '/nop/d' < boot2.s.tmp > boot2.s rm -f boot2.s.tmp as --32 -o boot2.o boot2.s ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o objcopy -S -O binary boot2.out boot2.bin btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 client: fmt=bin size=1705 text=0 data=0 bss=0 entry=0 output: fmt=bin size=1f95 text=200 data=1d95 org=0 entry=0 -405 bytes available *** Error code 1 1 error - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- Norikatsu Shigemura From owner-freebsd-current@FreeBSD.ORG Sat May 29 17:37:22 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C37621065674; Sat, 29 May 2010 17:37:22 +0000 (UTC) (envelope-from buganini@gmail.com) Received: from mail-gy0-f182.google.com (mail-gy0-f182.google.com [209.85.160.182]) by mx1.freebsd.org (Postfix) with ESMTP id 674058FC18; Sat, 29 May 2010 17:37:22 +0000 (UTC) Received: by gyh20 with SMTP id 20so2334972gyh.13 for ; Sat, 29 May 2010 10:37:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=IyL3KEZzpbnQKzc/D/kGowLiqhVTNEKWqUkq2imXqYU=; b=XPWXfTxnxKln/EaisbCsFkndAloHMgjd2TKi8ZFQz6TTqMFiPIolZHQJAN/KyLGasb pZqGeOR6rj6HultZo1Cpyo8AJOUC6Fkdnwx63ipVXONIwlfbjblkzZ4WTe7JMFE49Sv+ +gDxFfBS86wYbGx/V9KPwPmf5O4lmvIptEKbs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=S/qqExVFrbajPE5Wo8ZnqXgacTW8q5Os0xJulJG5MdQf9Qe7zaaPVHYH5d6zXfESFD kH1geuaPipQV9pPNtAEhvducN6JjcWgOVDpZOso61PilPRPGGpVdCx4c0tytA0CF4/pk B8Aonv3GcI98NLXJLlHMnzYEbgeJIEsP8SdCY= MIME-Version: 1.0 Received: by 10.231.178.132 with SMTP id bm4mr2612026ibb.62.1275154638196; Sat, 29 May 2010 10:37:18 -0700 (PDT) Received: by 10.231.200.147 with HTTP; Sat, 29 May 2010 10:37:18 -0700 (PDT) In-Reply-To: <20100524210945.GE1295@weongyo> References: <20100303082833.GB22865@weongyo> <20100303111014.6564ea1e.ray@dlink.ua> <20100312231333.GZ1295@weongyo> <4BD2201E.3090409@entel.upc.edu> <20100424231755.GI65380@weongyo> <4BD4A928.8020901@entel.upc.edu> <20100506190653.GA31100@weongyo> <58220.88.15.97.205.1273248485.squirrel@webmail.entel.upc.edu> <20100510195622.GA1295@weongyo> <4BF54F93.9000409@entel.upc.edu> <20100524210945.GE1295@weongyo> Date: Sun, 30 May 2010 01:37:18 +0800 Message-ID: From: Buganini To: Weongyo Jeong , current@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: Subject: Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver 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, 29 May 2010 17:37:22 -0000 Hi, with yesterday's CURRENT my bwn works partially. this is my hardware siba_bwn0@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network it works with WPA ap without destroy/re-create wlan0 , but it's unstable, at the first time it works, it goes forth and back between "associated" and "no carrier", the other times it stay associated but network is down. and this usually followed by system freeze if I `/etc/rc.d/netif restart` later. and it never get associated with a open ap. --Buganini From owner-freebsd-current@FreeBSD.ORG Sat May 29 17:53:05 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37C491065676 for ; Sat, 29 May 2010 17:53:05 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id D1EC18FC0A for ; Sat, 29 May 2010 17:53:04 +0000 (UTC) Received: (qmail 21372 invoked by uid 399); 29 May 2010 17:53:03 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 29 May 2010 17:53:03 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C01547E.2020303@FreeBSD.org> Date: Sat, 29 May 2010 10:53:02 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: bf1783@gmail.com References: <4C00832A.4030102@FreeBSD.org> <958F0C5A-3CE8-41E2-9C6B-AC1C3C1863C7@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Rui Paulo , "b. f." , zml@FreeBSD.org Subject: Re: wpa_supplicant (Was: Re: wpi not working on today's current (r208626)) 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, 29 May 2010 17:53:05 -0000 On 05/29/10 03:54, b. f. wrote: > On 5/29/10, Rui Paulo wrote: >> >> On 29 May 2010, at 05:39, b. f. wrote: >> >>> On 5/28/10, Doug Barton wrote: >>>> On 5/28/2010 4:50 PM, b. f. wrote: >>>>> >>>>> I can't see any problems when using WPA2 with AES on r208606 i386 with >>>>> uath(4). I'm updating this machine to r208630 tonight, and if I >>>>> encounter problems with the later revision, I'll let you know. >>>> >>>> Ok, thanks. >>>> >>>>> Are >>>>> you saying that you experienced problems when trying to use a r207134 >>>>> base with a r208626 kernel? If that's the case, I would recommend >>>>> updating the base to the same revision as the kernel, and then >>>>> retesting. >>>> >>>> Yes, that's what I'm doing I actually tried running the newly built >>>> wpa_supplicant but that didn't work. I'm kind of hesitant to do the full >>>> upgrade since I'm having kernel problems with the nvidia driver, but if >>>> I'm sure wpa_supplicant will work then I suppose I can bite the bullet. >>>> >>> >>> It appears that something is wrong. My wireless stick no longer >>> associates with the network with r208630. I'll do some tinkering. >> >> That's odd. The only way for that to happen would be caused bug in the >> taskqueue stuff that zml committed, I think, but that's a long shot. >> >> Regards, >> -- >> Rui Paulo > > Yes, that was also my suspicion, and after seeing, via top(1), that > ifconfig is stuck in the "*taskq" state while attempting to set up > the wlan, I believe either r208623, or r208624, or both, is > responsible for the regression. Reverting those two changes allows wpa_supplicant to work again. Thanks for the hint bf. Zach? Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Sat May 29 18:11:31 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2B735106566C for ; Sat, 29 May 2010 18:11:31 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id AC9E08FC17 for ; Sat, 29 May 2010 18:11:30 +0000 (UTC) Received: (qmail 20049 invoked by uid 399); 29 May 2010 18:11:29 -0000 Received: from localhost (HELO foreign.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 29 May 2010 18:11:29 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C0158D0.1000902@FreeBSD.org> Date: Sat, 29 May 2010 11:11:28 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.9) Gecko/20100330 Thunderbird/3.0.4 MIME-Version: 1.0 To: Kostik Belousov References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> In-Reply-To: <20100526165141.GF83316@deviant.kiev.zoral.com.ua> X-Enigmail-Version: 1.0.1 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, Garrett Cooper , FreeBSD Current , Alan Cox Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 29 May 2010 18:11:31 -0000 On 05/26/10 09:51, Kostik Belousov wrote: > > I did a quick glance over the driver, try this: > http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch > I did not even compiled the patched driver. Ok, I just tried this with an r208622 kernel and sources, and the system locks up as soon as I type 'startx'. No panic, no core dump, it just wedges, requiring it to be powered off. Doug -- ... and that's just a little bit of history repeating. -- Propellerheads Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ From owner-freebsd-current@FreeBSD.ORG Sat May 29 19:10:53 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 18D64106566B; Sat, 29 May 2010 19:10:53 +0000 (UTC) (envelope-from datastream.freecity@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8EAC88FC08; Sat, 29 May 2010 19:10:52 +0000 (UTC) Received: by vws12 with SMTP id 12so3137737vws.13 for ; Sat, 29 May 2010 12:10:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=tCCmuO6S9xN86VMRptXNs9ur1bBU6nKpaoleJhDbYSM=; b=ZfCNdXpFXsZZToS3SExXmcVSKFcosU5xSaTisD/3NnmoSujBuyrv9k+v0c76wdLtfZ gXvNQHAQYqWvXsiwifNhKdQ5ZljD3DzR+Tv9KTvG+1TAaJqcVtOm9xTCkAerSUIlra92 veJhVqUE1OfddeEDVDGqlnrjc6rPuMNtTbIGI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=J3u37BuX097pScKdeomohv5f0kwge+qQzSfGZbcXij0V3obzBjfiOIpGyzK58RvPvm 5NmTodGFCoIedL6vB7eL+aEr02saIBheAR32EBOWreQ1yKq8Ij2ksrMAFLQ2MirA5IqD pN+b41W8NJ6Co6w0kFy8EwODpjCI3lnjVNBsQ= MIME-Version: 1.0 Received: by 10.220.123.68 with SMTP id o4mr1627777vcr.8.1275158893981; Sat, 29 May 2010 11:48:13 -0700 (PDT) Received: by 10.220.194.138 with HTTP; Sat, 29 May 2010 11:48:13 -0700 (PDT) In-Reply-To: <4C0158D0.1000902@FreeBSD.org> References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> <4C0158D0.1000902@FreeBSD.org> Date: Sun, 30 May 2010 02:48:13 +0800 Message-ID: From: "datastream datastream.freecity" To: Doug Barton Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Kostik Belousov , alc@freebsd.org, FreeBSD Current , Alan Cox , Garrett Cooper Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 29 May 2010 19:10:53 -0000 On Sun, May 30, 2010 at 2:11 AM, Doug Barton wrote: > On 05/26/10 09:51, Kostik Belousov wrote: > >> >> I did a quick glance over the driver, try this: >> http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch >> I did not even compiled the patched driver. >> > > Ok, I just tried this with an r208622 kernel and sources, and the system > locks up as soon as I type 'startx'. No panic, no core dump, it just wedges, > requiring it to be powered off. > > > > http://www.nvnews.net/vbulletin/showthread.php?t=150719 NVIDIA-FreeBSD-x86_64-195.36.24 with r208117 in my T61 laptop works well. Thanks, Kevin From owner-freebsd-current@FreeBSD.ORG Sat May 29 19:31:23 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED34A1065670; Sat, 29 May 2010 19:31:23 +0000 (UTC) (envelope-from yanefbsd@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6D8918FC1F; Sat, 29 May 2010 19:31:23 +0000 (UTC) Received: by vws12 with SMTP id 12so3155431vws.13 for ; Sat, 29 May 2010 12:31:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=ZiJnR7OfAkuimh3r2JQoU383x/f0MamZLx/qM6QUgao=; b=to6Wsd3KdEaQiiwCx5vXdWCBaJbZAe4x2cmkPEP6tqLY4ZnuEYYPwgEC3fpjsLCddD nYl4iVz/cOGv6z3iI8YB6iJ9Zi8KIFknDo8WVXBLsIAR9Y1ZiOM96Gw+v590S5QIaTcG TDX8sxyeB6Ia/2TcMyHpBrvf+OsRAbxqGU0C0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=LvK7VgoWlKi4aRkEwB1JxIcYe3MkEXGTj8+l+deAx2yUTfHqxWVnNeF2LGUKHndi18 WlijDxMzMTwJiIjQgBJZyudJ0ae8znTgF9CH0+jTvdiiVJms7v1qRfb7ClwzPwq2F2du 3dlWgMzgxksJOPMiTsnrY+bKyz8dncxUjaMmY= MIME-Version: 1.0 Received: by 10.224.52.154 with SMTP id i26mr899344qag.154.1275161480892; Sat, 29 May 2010 12:31:20 -0700 (PDT) Received: by 10.229.190.83 with HTTP; Sat, 29 May 2010 12:31:20 -0700 (PDT) In-Reply-To: References: <4BFD4AE6.5040105@cs.rice.edu> <20100526165141.GF83316@deviant.kiev.zoral.com.ua> <4C0158D0.1000902@FreeBSD.org> Date: Sat, 29 May 2010 12:31:20 -0700 Message-ID: From: Garrett Cooper To: "datastream datastream.freecity" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Kostik Belousov , alc@freebsd.org, Doug Barton , Alan Cox , FreeBSD Current Subject: Re: nvidia-driver 195.22 use horribly broken on amd64 between r206173 and 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, 29 May 2010 19:31:24 -0000 On Sat, May 29, 2010 at 11:48 AM, datastream datastream.freecity wrote: > > On Sun, May 30, 2010 at 2:11 AM, Doug Barton wrote: >> >> On 05/26/10 09:51, Kostik Belousov wrote: >>> >>> I did a quick glance over the driver, try this: >>> http://people.freebsd.org/~kib/misc/nvidia-vm_page_lock.1.patch >>> I did not even compiled the patched driver. >> >> Ok, I just tried this with an r208622 kernel and sources, and the system >> locks up as soon as I type 'startx'. No panic, no core dump, it just wed= ges, >> requiring it to be powered off. >> >> > =A0http://www.nvnews.net/vbulletin/showthread.php?t=3D150719 > NVIDIA-FreeBSD-x86_64-195.36.24 with r208117 in my T61 laptop works well. I'll try out this driver then. I'll have to see what the delta was with the kernel glue... Thanks for the feedback, -Garrett From owner-freebsd-current@FreeBSD.ORG Sat May 29 19:45:59 2010 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A1AC1065674 for ; Sat, 29 May 2010 19:45:59 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (lev.vlakno.cz [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id E4F1D8FC08 for ; Sat, 29 May 2010 19:45:58 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 1B86E9CB0DF; Sat, 29 May 2010 21:42:32 +0200 (CEST) X-Virus-Scanned: amavisd-new at vlakno.cz Received: from vlakno.cz ([127.0.0.1]) by localhost (lev.vlakno.cz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NGJJtKWsOAa2; Sat, 29 May 2010 21:42:29 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 388629CB149; Sat, 29 May 2010 21:42:29 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id o4TJgTSG052155; Sat, 29 May 2010 21:42:29 +0200 (CEST) (envelope-from rdivacky) Date: Sat, 29 May 2010 21:42:29 +0200 From: Roman Divacky To: Norikatsu Shigemura Message-ID: <20100529194229.GA51865@freebsd.org> References: <20100529021741.674bf85f.nork@FreeBSD.org> <20100529233152.a59cd08e.nork@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100529233152.a59cd08e.nork@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@FreeBSD.org Subject: Re: clangBSD build error on r208621 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, 29 May 2010 19:45:59 -0000 On Sat, May 29, 2010 at 11:31:52PM +0900, Norikatsu Shigemura wrote: > Hi rdivacky. > > On Sat, 29 May 2010 02:17:41 +0900 > Norikatsu Shigemura wrote: > > error: unknown argument: '-ferror-limit' > > mkdep: compile failed > > Do you have any idea? Of cause I set following environment: > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > $ cat /etc/src.conf > > NO_WERROR= > > WERROR= > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > OK, I got so that clang is too old. > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > $ /usr/bin/clang --version > clang version 1.5 (trunk) > Target: x86_64-undermydesk-freebsd9.0 > Thread model: posix > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > So I did use latest clang by installing devel/llvm-devel. > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > $ /usr/local/bin/clang --version > clang version 2.0 (trunk) > Target: x86_64-portbld-freebsd9.0 > Thread model: posix > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > I can compile to well-known error point. > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > ===> sys/boot/i386/boot2 (all) > dd if=/dev/zero of=boot2.ldr bs=512 count=1 > 1+0 records in > 1+0 records out > 512 bytes transferred in 0.000027 secs (18837576 bytes/sec) > /usr/local/bin/clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/ -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -m32 -march=i386 -std=gnu99 -c /usr/src/sys/boot/i386/boot2/sio.S > clang: warning: the clang compiler does not support '-fno-unit-at-a-time' > clang: warning: argument unused during compilation: '-L/usr/obj/usr/src/tmp/usr/lib/' > clang: warning: argument unused during compilation: '-fno-guess-branch-probability' > clang: warning: argument unused during compilation: '-mno-align-long-strings' > clang: warning: argument unused during compilation: '-mrtd' > clang: warning: argument unused during compilation: '--param max-inline-insns-single=100' > clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' > objcopy -S -O binary boot1.out boot1 > /usr/local/bin/clang -isysroot /usr/obj/usr/src/tmp -B/usr/obj/usr/src/tmp/usr/lib/ -L/usr/obj/usr/src/tmp/usr/lib/ -Os -fno-guess-branch-probability -fomit-frame-pointer -fno-unit-at-a-time -mno-align-long-strings -mrtd -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -DUFS1_AND_UFS2 -DFLAGS=0x80 -DSIOPRT=0x3f8 -DSIOFMT=0x3 -DSIOSPD=9600 -I/usr/src/sys/boot/i386/boot2/../../common -I/usr/src/sys/boot/i386/boot2/../btx/lib -I. -Wall -Waggregate-return -Wbad-function-cast -Wcast-align -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wshadow -Wstrict-prototypes -Wwrite-strings -Winline --param max-inline-insns-single=100 -ffreestanding -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -m32 -march=i386 -std=gnu99 -S -o boot2.s.tmp /usr/src/sys/boot/i386/boot2/boot2.c > clang: warning: the clang compiler does not support '-fno-unit-at-a-time' > clang: warning: argument unused during compilation: '-L/usr/obj/usr/src/tmp/usr/lib/' > clang: warning: argument unused during compilation: '-fno-guess-branch-probability' > clang: warning: argument unused during compilation: '-mno-align-long-strings' > clang: warning: argument unused during compilation: '-mrtd' > clang: warning: argument unused during compilation: '--param max-inline-insns-single=100' > clang: warning: argument unused during compilation: '-mpreferred-stack-boundary=2' > /usr/src/sys/boot/i386/boot2/boot2.c:234:1: warning: no previous prototype for function 'main' [-Wmissing-prototypes] > main(void) > ^ > 1 warning generated. > sed -e '/align/d' -e '/nop/d' < boot2.s.tmp > boot2.s > rm -f boot2.s.tmp > as --32 -o boot2.o boot2.s > ld -static -N --gc-sections -nostdlib -m elf_i386_fbsd -Ttext 0x2000 -o boot2.out /usr/obj/usr/src/sys/boot/i386/boot2/../btx/lib/crt0.o boot2.o sio.o > objcopy -S -O binary boot2.out boot2.bin > btxld -v -E 0x2000 -f bin -b /usr/obj/usr/src/sys/boot/i386/boot2/../btx/btx/btx -l boot2.ldr -o boot2.ld -P 1 boot2.bin > kernel: ver=1.02 size=690 load=9000 entry=9010 map=16M pgctl=1:1 > client: fmt=bin size=1705 text=0 data=0 bss=0 entry=0 > output: fmt=bin size=1f95 text=200 data=1d95 org=0 entry=0 > -405 bytes available > *** Error code 1 > 1 error clang as is cant compile boot2. there's a makefile goo that forces it to use gcc but for some reason (unknown to me) you force it to use clang. this issue is known and there's even a known fix, documented at http://llvm.org/bugs/show_bug.cgi?id=6623 http://llvm.org/bugs/show_bug.cgi?id=6627 I hope that those problems will be fixed in a few days...