From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 05:27:42 2009 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 4019C106566B for ; Sun, 11 Oct 2009 05:27:42 +0000 (UTC) (envelope-from faber@zod.isi.edu) Received: from zod.isi.edu (zod.isi.edu [128.9.168.221]) by mx1.freebsd.org (Postfix) with ESMTP id 219008FC22 for ; Sun, 11 Oct 2009 05:27:41 +0000 (UTC) Received: from zod.isi.edu (localhost [127.0.0.1]) by zod.isi.edu (8.14.3/8.14.3) with ESMTP id n9B5RfM5046935 for ; Sat, 10 Oct 2009 22:27:41 -0700 (PDT) (envelope-from faber@zod.isi.edu) Received: (from faber@localhost) by zod.isi.edu (8.14.3/8.14.3/Submit) id n9B5RfMW046934 for freebsd-current@freebsd.org; Sat, 10 Oct 2009 22:27:41 -0700 (PDT) (envelope-from faber) Date: Sat, 10 Oct 2009 22:27:41 -0700 From: Ted Faber To: freebsd-current@freebsd.org Message-ID: <20091011052741.GA46868@zod.isi.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="iFRdW5/EC4oqxDHL" Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-url: http://www.isi.edu/~faber Subject: 80RC1 can't find onboard Intel PRO (pciconf & dmesg attached) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2009 05:27:42 -0000 --iFRdW5/EC4oqxDHL Content-Type: multipart/mixed; boundary="KFztAG8eRSV9hGtP" Content-Disposition: inline --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I have an Intel DP55WB motherboard that claims to have an Intel PRO 10/100/1000 device on it, but FreeBSD isn't detecting it properly. I've attached a pciconf -l and verbose dmesg. I think the offender had a PCI ID of 10F08086, which http://www.clavister.com/support/utilities/vendors.txt thinks is an Interl Ethernet as well. I tried just adding that ID to the table in /sys/dev/e1000/if_em.c, but that was insufficient. I'm happy to try patches. Thanks! --=20 Ted Faber http://www.isi.edu/~faber PGP: http://www.isi.edu/~faber/pubkeys.= asc Unexpected attachment on this mail? See http://www.isi.edu/~faber/FAQ.html#= SIG --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=dmesg Content-Transfer-Encoding: quoted-printable ugen1.4: at usbus1 umass0: on= usbus1 umass0: SCSI over Bulk-Only; quirks =3D 0x0000 umass0:1:0:-1: Attached to scbus1 da0 at umass-sim0 bus 0 target 0 lun 0 da0: Removable Direct Access SCSI-0 device=20 da0: 40.000MB/s transfers da0: 955MB (1957887 512 byte sectors: 64H 32S/T 955C) (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0=20 (probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:1): SCSI Status: Check Condition (probe0:umass-sim0:0:0:1): UNIT ATTENTION asc:29,0 (probe0:umass-sim0:0:0:1): Power on, reset, or bus device reset occurred (probe0:umass-sim0:0:0:1): Retrying Command (per Sense Data) (probe0:umass-sim0:0:0:1): TEST UNIT READY. CDB: 0 20 0 0 0 0=20 (probe0:umass-sim0:0:0:1): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:1): SCSI Status: Check Condition (probe0:umass-sim0:0:0:1): NOT READY asc:3a,0 (probe0:umass-sim0:0:0:1): Medium not present (probe0:umass-sim0:0:0:1): Unretryable error cd0 at umass-sim0 bus 0 target 0 lun 1 cd0: Removable CD-ROM SCSI-0 device=20 cd0: 40.000MB/s transfers cd0: cd present [32767 x 2048 byte records] GEOM: da0: partition 1 does not start on a track boundary. GEOM: da0: partition 1 does not end on a track boundary. ugen1.4: at usbus1 (disconnected) umass0: at uhub3, port 2, addr 4 (disconnected) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry (cd0:umass-sim0:0:0:1): lost device (cd0:umass-sim0:0:0:1): removing device entry (cd0:umass-sim0:0:0:1): removing changer entry Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...2 2 2 2 0 0 done All buffers synced. Copyright (c) 1992-2009 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-RC1 #14: Sat Oct 10 22:14:36 PDT 2009 root@ylum.lunabase.org:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0fef000. Preloaded elf module "/boot/kernel/geom_mirror.ko" at 0xc0fef234. Preloaded elf module "/boot/kernel/snd_via8233.ko" at 0xc0fef2e4. Preloaded elf module "/boot/kernel/sound.ko" at 0xc0fef394. Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2666776980 Hz CPU: Intel(R) Core(TM) i5 CPU 750 @ 2.67GHz (2666.78-MHz 686-class= CPU) Origin =3D "GenuineIntel" Id =3D 0x106e5 Stepping =3D 5 Features=3D0xbfebfbff Features2=3D0x98e3fd AMD Features=3D0x28100000 AMD Features2=3D0x1 TSC: P-state invariant Data TLB: 4 KB pages, 4-way set associative, 64 entries Instruction TLB: 4 KB Pages, 4-way set associative, 128 entries 1st-level data cache: 32 KB, 8-way set associative, 64 byte line size L2 cache: 256 kbytes, 8-way associative, 64 bytes/line real memory =3D 4294967296 (4096 MB) Physical memory chunk(s): 0x0000000000001000 - 0x000000000008dfff, 577536 bytes (141 pages) 0x0000000000100000 - 0x00000000003fffff, 3145728 bytes (768 pages) 0x0000000001026000 - 0x00000000db73ffff, 3664879616 bytes (894746 pages) 0x00000000df6bf000 - 0x00000000df6e4fff, 155648 bytes (38 pages) 0x00000000df7bf000 - 0x00000000df7d7fff, 102400 bytes (25 pages) avail memory =3D 3663699968 (3493 MB) Table 'FACP' at 0xdf7fc000 Table 'APIC' at 0xdf7f7000 MADT: Found table at 0xdf7f7000 APIC: Using the MADT enumerator. MADT: Found CPU APIC ID 0 ACPI ID 0: enabled SMP: Added CPU 0 (AP) MADT: Found CPU APIC ID 1 ACPI ID 1: disabled MADT: Found CPU APIC ID 2 ACPI ID 2: enabled SMP: Added CPU 2 (AP) MADT: Found CPU APIC ID 3 ACPI ID 3: disabled MADT: Found CPU APIC ID 4 ACPI ID 4: enabled SMP: Added CPU 4 (AP) MADT: Found CPU APIC ID 5 ACPI ID 5: disabled MADT: Found CPU APIC ID 6 ACPI ID 6: enabled SMP: Added CPU 6 (AP) MADT: Found CPU APIC ID 7 ACPI ID 7: disabled ACPI APIC Table: INTR: Adding local APIC 2 as a target INTR: Adding local APIC 4 as a target INTR: Adding local APIC 6 as a target FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 pnpbios: Found PnP BIOS data at 0xc00fe0e0 pnpbios: Entry =3D f0000:ba00 Rev =3D 1.0 pnpbios: OEM ID 8224744e Other BIOS signatures found: APIC: CPU 0 has ACPI ID 0 APIC: CPU 1 has ACPI ID 2 APIC: CPU 2 has ACPI ID 4 APIC: CPU 3 has ACPI ID 6 ULE: setup cpu 0 ULE: setup cpu 1 ULE: setup cpu 2 ULE: setup cpu 3 ACPI: RSDP 0xfe020 00024 (v2 INTEL ) ACPI: XSDT 0xdf7fd120 0006C (v1 INTEL WBIBX10J 0000007A 01000013) ACPI: FACP 0xdf7fc000 000F4 (v3 INTEL WBIBX10J 0000007A MSFT 0100000D) ACPI: DSDT 0xdf7f8000 03432 (v2 INTEL WBIBX10J 0000007A MSFT 0100000D) ACPI: FACS 0xdf76c000 00040 ACPI: APIC 0xdf7f7000 000BC (v2 INTEL WBIBX10J 0000007A MSFT 0100000D) ACPI: WDDT 0xdf7f6000 00040 (v1 INTEL WBIBX10J 0000007A MSFT 0100000D) ACPI: MCFG 0xdf7f5000 0003C (v1 INTEL WBIBX10J 0000007A MSFT 0100000D) ACPI: ASF! 0xdf7f4000 000A5 (v32 INTEL WBIBX10J 0000007A MSFT 0100000D) ACPI: HPET 0xdf7f3000 00038 (v1 INTEL WBIBX10J 0000007A MSFT 0100000D) ACPI: ASPT 0xdf7f1000 00034 (v5 INTEL WBIBX10J 0000007A MSFT 0100000D) ACPI: WDTT 0xdf7f0000 00224 (v2 INTEL WBIBX10J 0000007A MSFT 0100000D) ACPI: SSDT 0xdf7e9000 06F74 (v1 INTEL SSDT PM 0000007A MSFT 0100000D) MADT: Found IO APIC ID 8, Interrupt 0 at 0xfec00000 ioapic0: Changing APIC ID to 8 ioapic0: Routing external 8259A's -> intpin 0 MADT: Interrupt override: source 0, irq 2 ioapic0: Routing IRQ 0 -> intpin 2 MADT: Interrupt override: source 9, irq 9 ioapic0: intpin 9 trigger: level lapic0: Routing NMI -> LINT1 lapic0: LINT1 trigger: level lapic0: LINT1 polarity: high MADT: Ignoring local NMI routed to ACPI CPU 1 lapic2: Routing NMI -> LINT1 lapic2: LINT1 trigger: level lapic2: LINT1 polarity: high MADT: Ignoring local NMI routed to ACPI CPU 3 lapic4: Routing NMI -> LINT1 lapic4: LINT1 trigger: level lapic4: LINT1 polarity: high MADT: Ignoring local NMI routed to ACPI CPU 5 lapic6: Routing NMI -> LINT1 lapic6: LINT1 trigger: level lapic6: LINT1 polarity: high MADT: Ignoring local NMI routed to ACPI CPU 7 ioapic0 irqs 0-23 on motherboard lapic0: Forcing LINT1 to edge trigger cpu0 BSP: ID: 0x00000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00008400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010400 snd_unit_init() u=3D0x00ff8000 [512] d=3D0x00007c00 [32] c=3D0x000003ff [10= 24] feeder_register: snd_unit=3D-1 snd_maxautovchans=3D16 latency=3D5 feeder_ra= te_min=3D1 feeder_rate_max=3D2016000 feeder_rate_round=3D25 wlan: <802.11 Link Layer> null: random: nfslock: pseudo-device io: kbd: new array size 4 kbd1 at kbdmux0 mem: Pentium Pro MTRR support enabled hptrr: RocketRAID 17xx/2xxx SATA controller driver v1.2 npx0: INT 16 interface acpi0: on motherboard PCIe: Memory Mapped configuration base @ 0xf8000000 pcibios: No call entry point ioapic0: routing intpin 9 (ISA IRQ 9) to lapic 0 vector 48 acpi0: [MPSAFE] acpi0: [ITHREAD] acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \\_SB_.PCI0.GFX0.IGDP -> bus 0 dev 2 func 0 acpi0: Power Button (fixed) acpi0: wakeup code va 0xc6c59000 pa 0x1000 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \\_SB_.PCI0.LPC_.PRR0 -> bus 0 dev 31 func 0 acpi_bus_number: root bus has no _BBN, assuming 0 AcpiOsDerivePciId: \\_SB_.PCI0.LPC_.PRR1 -> bus 0 dev 31 func 0 ACPI timer: 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 1/1 -> 10 Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pci_link0: Index IRQ Rtd Ref IRQs Initial Probe 0 9 N 0 3 4 5 7 9 10 11 12 Validation 0 9 N 0 3 4 5 7 9 10 11 12 After Disable 0 255 N 0 3 4 5 7 9 10 11 12 pci_link1: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 3 4 5 7 9 10 11 12 Validation 0 255 N 0 3 4 5 7 9 10 11 12 After Disable 0 255 N 0 3 4 5 7 9 10 11 12 pci_link2: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 3 4 5 7 9 10 11 12 Validation 0 10 N 0 3 4 5 7 9 10 11 12 After Disable 0 255 N 0 3 4 5 7 9 10 11 12 pci_link3: Index IRQ Rtd Ref IRQs Initial Probe 0 10 N 0 3 4 5 7 9 10 11 12 Validation 0 10 N 0 3 4 5 7 9 10 11 12 After Disable 0 255 N 0 3 4 5 7 9 10 11 12 pci_link4: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 7 9 10 11 12 Validation 0 11 N 0 3 4 5 7 9 10 11 12 After Disable 0 255 N 0 3 4 5 7 9 10 11 12 pci_link5: Index IRQ Rtd Ref IRQs Initial Probe 0 255 N 0 3 4 5 7 9 10 11 12 Validation 0 255 N 0 3 4 5 7 9 10 11 12 After Disable 0 255 N 0 3 4 5 7 9 10 11 12 pci_link6: Index IRQ Rtd Ref IRQs Initial Probe 0 11 N 0 3 4 5 7 9 10 11 12 Validation 0 11 N 0 3 4 5 7 9 10 11 12 After Disable 0 255 N 0 3 4 5 7 9 10 11 12 pci_link7: Index IRQ Rtd Ref IRQs Initial Probe 0 9 N 0 3 4 5 7 9 10 11 12 Validation 0 9 N 0 3 4 5 7 9 10 11 12 After Disable 0 255 N 0 3 4 5 7 9 10 11 12 acpi_hpet0: iomem 0xfed00000-0xfed003ff on acp= i0 acpi_hpet0: vend: 0x8086 rev: 0x1 num: 7 hz: 14318180 opts: legacy_route 64= -bit Timecounter "HPET" frequency 14318180 Hz quality 900 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pci0: domain=3D0, physical bus=3D0 found-> vendor=3D0x8086, dev=3D0xd131, revid=3D0x11 domain=3D0, bus=3D0, slot=3D0, func=3D0 class=3D06-00-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) found-> vendor=3D0x8086, dev=3D0xd138, revid=3D0x11 domain=3D0, bus=3D0, slot=3D3, func=3D0 class=3D06-04-00, hdrtype=3D0x01, mfdev=3D0 cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x04 (1000 ns), maxlat=3D0x00 (0 ns) intpin=3Da, irq=3D255 powerspec 3 supports D0 D3 current D0 MSI supports 2 messages, vector masks found-> vendor=3D0x8086, dev=3D0xd155, revid=3D0x11 domain=3D0, bus=3D0, slot=3D8, func=3D0 class=3D08-80-00, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) found-> vendor=3D0x8086, dev=3D0xd156, revid=3D0x11 domain=3D0, bus=3D0, slot=3D8, func=3D1 class=3D08-80-00, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) found-> vendor=3D0x8086, dev=3D0xd157, revid=3D0x11 domain=3D0, bus=3D0, slot=3D8, func=3D2 class=3D08-80-00, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) found-> vendor=3D0x8086, dev=3D0xd158, revid=3D0x11 domain=3D0, bus=3D0, slot=3D8, func=3D3 class=3D08-80-00, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x0000, statreg=3D0x0000, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) found-> vendor=3D0x8086, dev=3D0xd150, revid=3D0x11 domain=3D0, bus=3D0, slot=3D16, func=3D0 class=3D08-80-00, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x0000, statreg=3D0x0000, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) found-> vendor=3D0x8086, dev=3D0xd151, revid=3D0x11 domain=3D0, bus=3D0, slot=3D16, func=3D1 class=3D08-80-00, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x0000, statreg=3D0x0000, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) found-> vendor=3D0x8086, dev=3D0x10f0, revid=3D0x05 domain=3D0, bus=3D0, slot=3D25, func=3D0 class=3D02-00-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0007, statreg=3D0x0010, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Da, irq=3D11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 32, base 0xe2100000, size 17, enabled map[14]: type Memory, range 32, base 0xe2124000, size 12, enabled map[18]: type I/O Port, range 32, base 0x1020, size 5, enabled pcib0: matched entry for 0.25.INTA pcib0: slot 25 INTA hardwired to IRQ 20 found-> vendor=3D0x8086, dev=3D0x3b3c, revid=3D0x05 domain=3D0, bus=3D0, slot=3D26, func=3D0 class=3D0c-03-20, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0006, statreg=3D0x0290, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Da, irq=3D9 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xe2125400, size 10, enabled pcib0: matched entry for 0.26.INTA pcib0: slot 26 INTA hardwired to IRQ 16 found-> vendor=3D0x8086, dev=3D0x3b56, revid=3D0x05 domain=3D0, bus=3D0, slot=3D27, func=3D0 class=3D04-03-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0006, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Da, irq=3D11 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit map[10]: type Memory, range 64, base 0xe2120000, size 14, enabled pcib0: matched entry for 0.27.INTA pcib0: slot 27 INTA hardwired to IRQ 22 found-> vendor=3D0x8086, dev=3D0x3b42, revid=3D0x05 domain=3D0, bus=3D0, slot=3D28, func=3D0 class=3D06-04-00, hdrtype=3D0x01, mfdev=3D1 cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x04 (1000 ns), maxlat=3D0x00 (0 ns) intpin=3Da, irq=3D255 powerspec 2 supports D0 D3 current D0 MSI supports 1 message found-> vendor=3D0x8086, dev=3D0x3b4a, revid=3D0x05 domain=3D0, bus=3D0, slot=3D28, func=3D4 class=3D06-04-00, hdrtype=3D0x01, mfdev=3D1 cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x04 (1000 ns), maxlat=3D0x00 (0 ns) intpin=3Da, irq=3D255 powerspec 2 supports D0 D3 current D0 MSI supports 1 message found-> vendor=3D0x8086, dev=3D0x3b4e, revid=3D0x05 domain=3D0, bus=3D0, slot=3D28, func=3D6 class=3D06-04-00, hdrtype=3D0x01, mfdev=3D1 cmdreg=3D0x0000, statreg=3D0x0010, cachelnsz=3D16 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x04 (1000 ns), maxlat=3D0x00 (0 ns) intpin=3Dc, irq=3D255 powerspec 2 supports D0 D3 current D0 MSI supports 1 message found-> vendor=3D0x8086, dev=3D0x3b34, revid=3D0x05 domain=3D0, bus=3D0, slot=3D29, func=3D0 class=3D0c-03-20, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0006, statreg=3D0x0290, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Da, irq=3D9 powerspec 2 supports D0 D3 current D0 map[10]: type Memory, range 32, base 0xe2125000, size 10, enabled pcib0: matched entry for 0.29.INTA pcib0: slot 29 INTA hardwired to IRQ 23 found-> vendor=3D0x8086, dev=3D0x244e, revid=3D0xa5 domain=3D0, bus=3D0, slot=3D30, func=3D0 class=3D06-04-01, hdrtype=3D0x01, mfdev=3D0 cmdreg=3D0x0107, statreg=3D0x0010, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x18 (6000 ns), maxlat=3D0x00 (0 ns) found-> vendor=3D0x8086, dev=3D0x3b02, revid=3D0x05 domain=3D0, bus=3D0, slot=3D31, func=3D0 class=3D06-01-00, hdrtype=3D0x00, mfdev=3D1 cmdreg=3D0x0107, statreg=3D0x0210, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) found-> vendor=3D0x8086, dev=3D0x3b20, revid=3D0x05 domain=3D0, bus=3D0, slot=3D31, func=3D2 class=3D01-01-8f, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0007, statreg=3D0x02b0, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Db, irq=3D10 powerspec 3 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0x1098, size 3, enabled map[14]: type I/O Port, range 32, base 0x10ac, size 2, enabled map[18]: type I/O Port, range 32, base 0x1090, size 3, enabled map[1c]: type I/O Port, range 32, base 0x10a8, size 2, enabled map[20]: type I/O Port, range 32, base 0x1070, size 4, enabled map[24]: type I/O Port, range 32, base 0x1060, size 4, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 19 found-> vendor=3D0x8086, dev=3D0x3b30, revid=3D0x05 domain=3D0, bus=3D0, slot=3D31, func=3D3 class=3D0c-05-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0003, statreg=3D0x0280, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Dc, irq=3D10 map[10]: type Memory, range 64, base 0xe2125800, size 8, enabled map[20]: type I/O Port, range 32, base 0x1000, size 5, enabled pcib0: matched entry for 0.31.INTC pcib0: slot 31 INTC hardwired to IRQ 18 found-> vendor=3D0x8086, dev=3D0x3b26, revid=3D0x05 domain=3D0, bus=3D0, slot=3D31, func=3D5 class=3D01-01-85, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0005, statreg=3D0x02b0, cachelnsz=3D0 (dwords) lattimer=3D0x00 (0 ns), mingnt=3D0x00 (0 ns), maxlat=3D0x00 (0 ns) intpin=3Db, irq=3D10 powerspec 3 supports D0 D3 current D0 map[10]: type I/O Port, range 32, base 0x1088, size 3, enabled map[14]: type I/O Port, range 32, base 0x10a4, size 2, enabled map[18]: type I/O Port, range 32, base 0x1080, size 3, enabled map[1c]: type I/O Port, range 32, base 0x10a0, size 2, enabled map[20]: type I/O Port, range 32, base 0x1050, size 4, enabled map[24]: type I/O Port, range 32, base 0x1040, size 4, enabled pcib0: matched entry for 0.31.INTB pcib0: slot 31 INTB hardwired to IRQ 19 pcib1: at device 3.0 on pci0 pcib1: domain 0 pcib1: secondary bus 1 pcib1: subordinate bus 1 pcib1: I/O decode 0x0-0x0 pcib1: no prefetched decode pci1: on pcib1 pci1: domain=3D0, physical bus=3D1 pci0: at device 8.0 (no driver attached) pci0: at device 8.1 (no driver attached) pci0: at device 8.2 (no driver attached) pci0: at device 8.3 (no driver attached) pci0: at device 16.0 (no driver attached) pci0: at device 16.1 (no driver attached) pci0: at device 25.0 (no driver attached) ehci0: mem 0xe2125400-0xe21257ff irq 16= at device 26.0 on pci0 ehci0: Reserved 0x400 bytes for rid 0x10 type 3 at 0xe2125400 ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 0 vector 49 ehci0: [MPSAFE] ehci0: [ITHREAD] usbus0: waiting for BIOS to give up control usbus0: EHCI version 1.0 usbus0: on ehci0 pci0: at device 27.0 (no driver attached) pcib2: at device 28.0 on pci0 pcib2: domain 0 pcib2: secondary bus 2 pcib2: subordinate bus 2 pcib2: I/O decode 0x0-0x0 pcib2: no prefetched decode pci2: on pcib2 pci2: domain=3D0, physical bus=3D2 pcib3: at device 28.4 on pci0 pcib3: domain 0 pcib3: secondary bus 3 pcib3: subordinate bus 3 pcib3: I/O decode 0x0-0x0 pcib3: no prefetched decode pci3: on pcib3 pci3: domain=3D0, physical bus=3D3 pcib4: at device 28.6 on pci0 pcib4: domain 0 pcib4: secondary bus 4 pcib4: subordinate bus 4 pcib4: I/O decode 0x0-0x0 pcib4: no prefetched decode pci4: on pcib4 pci4: domain=3D0, physical bus=3D4 ehci1: mem 0xe2125000-0xe21253ff irq 23= at device 29.0 on pci0 ehci1: Reserved 0x400 bytes for rid 0x10 type 3 at 0xe2125000 ioapic0: routing intpin 23 (PCI IRQ 23) to lapic 0 vector 50 ehci1: [MPSAFE] ehci1: [ITHREAD] usbus1: waiting for BIOS to give up control usbus1: EHCI version 1.0 usbus1: on ehci1 pcib5: at device 30.0 on pci0 pcib5: domain 0 pcib5: secondary bus 5 pcib5: subordinate bus 5 pcib5: I/O decode 0xf000-0xfff pcib5: memory decode 0xe1000000-0xe20fffff pcib5: prefetched decode 0xe0000000-0xe0ffffff pcib5: Subtractively decoded bridge. pci5: on pcib5 pci5: domain=3D0, physical bus=3D5 found-> vendor=3D0x12d2, dev=3D0x0018, revid=3D0x10 domain=3D0, bus=3D5, slot=3D1, func=3D0 class=3D03-00-00, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0007, statreg=3D0x02a0, cachelnsz=3D0 (dwords) lattimer=3D0x20 (960 ns), mingnt=3D0x03 (750 ns), maxlat=3D0x01 (250 ns) intpin=3Da, irq=3D11 map[10]: type Memory, range 32, base 0xe1000000, size 24, enabled pcib5: requested memory range 0xe1000000-0xe1ffffff: good map[14]: type Prefetchable Memory, range 32, base 0xe0000000, size 24, ena= bled pcib5: requested memory range 0xe0000000-0xe0ffffff: good pcib5: matched entry for 5.1.INTA pcib5: slot 1 INTA hardwired to IRQ 22 found-> vendor=3D0x104c, dev=3D0x8023, revid=3D0x00 domain=3D0, bus=3D5, slot=3D3, func=3D0 class=3D0c-00-10, hdrtype=3D0x00, mfdev=3D0 cmdreg=3D0x0016, statreg=3D0x0210, cachelnsz=3D16 (dwords) lattimer=3D0x20 (960 ns), mingnt=3D0x02 (500 ns), maxlat=3D0x04 (1000 ns) intpin=3Da, irq=3D255 powerspec 2 supports D0 D1 D2 D3 current D0 map[10]: type Memory, range 32, base 0xe2004000, size 11, enabled pcib5: requested memory range 0xe2004000-0xe20047ff: good map[14]: type Memory, range 32, base 0xe2000000, size 14, enabled pcib5: requested memory range 0xe2000000-0xe2003fff: good vgapci0: mem 0xe1000000-0xe1ffffff,0xe0000000-0xe0= ffffff irq 22 at device 1.0 on pci5 fwohci0: mem 0xe2004000-0xe20047ff,0xe20000= 00-0xe2003fff at device 3.0 on pci5 fwohci0: Reserved 0x800 bytes for rid 0x10 type 3 at 0xe2004000 pcib5: matched entry for 5.3.INTA pcib5: slot 3 INTA hardwired to IRQ 19 ioapic0: routing intpin 19 (PCI IRQ 19) to lapic 0 vector 51 fwohci0: [MPSAFE] fwohci0: [ITHREAD] fwohci0: OHCI version 1.10 (ROM=3D0) fwohci0: No. of Isochronous channels is 4. fwohci0: EUI64 00:90:27:00:02:53:d6:7f fwohci0: Phy 1394a available S400, 2 ports. fwohci0: Link S400, max_rec 2048 bytes. firewire0: on fwohci0 dcons_crom0: on firewire0 dcons_crom0: bus_addr 0x128c000 fwe0: on firewire0 if_fwe0: Fake Ethernet address: 02:90:27:53:d6:7f fwe0: bpf attached fwe0: Ethernet address: 02:90:27:53:d6:7f fwip0: on firewire0 fwip0: bpf attached fwip0: Firewire address: 00:90:27:00:02:53:d6:7f @ 0xfffe00000000, S400, ma= xrec 2048 sbp0: on firewire0 fwohci0: Initiate bus reset fwohci0: fwohci_intr_core: BUS reset fwohci0: fwohci_intr_core: node_id=3D0x00000000, SelfID Count=3D1, CYCLEMAS= TER mode isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0x1098-0x109f,0x10ac-0x10af,0x1090-0x1= 097,0x10a8-0x10ab,0x1070-0x107f,0x1060-0x106f irq 19 at device 31.2 on pci0 atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0x1070 atapci0: [MPSAFE] atapci0: [ITHREAD] ata2: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1098 atapci0: Reserved 0x4 bytes for rid 0x14 type 4 at 0x10ac ata2: reset tp1 mask=3D03 ostat0=3D50 ostat1=3D00 ata2: stat0=3D0x50 err=3D0x01 lsb=3D0x00 msb=3D0x00 ata2: stat1=3D0x00 err=3D0x01 lsb=3D0x00 msb=3D0x00 ata2: reset tp2 stat0=3D50 stat1=3D00 devices=3D0x1 ata2: [MPSAFE] ata2: [ITHREAD] ata3: on atapci0 atapci0: Reserved 0x8 bytes for rid 0x18 type 4 at 0x1090 atapci0: Reserved 0x4 bytes for rid 0x1c type 4 at 0x10a8 ata3: reset tp1 mask=3D03 ostat0=3D7f ostat1=3D7f ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: stat1=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata3: reset tp2 stat0=3Dff stat1=3Dff devices=3D0x0 ata3: [MPSAFE] ata3: [ITHREAD] pci0: at device 31.3 (no driver attached) atapci1: port 0x1088-0x108f,0x10a4-0x10a7,0x1080-0x1= 087,0x10a0-0x10a3,0x1050-0x105f,0x1040-0x104f irq 19 at device 31.5 on pci0 atapci1: Reserved 0x10 bytes for rid 0x20 type 4 at 0x1050 atapci1: [MPSAFE] atapci1: [ITHREAD] ata4: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x10 type 4 at 0x1088 atapci1: Reserved 0x4 bytes for rid 0x14 type 4 at 0x10a4 ata4: reset tp1 mask=3D03 ostat0=3D7f ostat1=3D7f ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: stat1=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata4: reset tp2 stat0=3Dff stat1=3Dff devices=3D0x0 ata4: [MPSAFE] ata4: [ITHREAD] ata5: on atapci1 atapci1: Reserved 0x8 bytes for rid 0x18 type 4 at 0x1080 atapci1: Reserved 0x4 bytes for rid 0x1c type 4 at 0x10a0 ata5: reset tp1 mask=3D03 ostat0=3D7f ostat1=3D7f ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat0=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: stat1=3D0x7f err=3D0xff lsb=3D0xff msb=3D0xff ata5: reset tp2 stat0=3Dff stat1=3Dff devices=3D0x0 ata5: [MPSAFE] ata5: [ITHREAD] atrtc0: port 0x70-0x71,0x74-0x77 irq 8 on acpi0 atrtc0: registered as a time-of-day clock (resolution 1000000us) cpu0: on acpi0 est0: on cpu0 est0: Invalid id16 (set, cur) =3D (19, 20) est0: Invalid freq 2527, ignored. est0: Invalid id16 (set, cur) =3D (18, 20) est0: Invalid freq 2394, ignored. est0: Invalid id16 (set, cur) =3D (17, 20) est0: Invalid freq 2261, ignored. est0: Invalid id16 (set, cur) =3D (16, 20) est0: Invalid freq 2128, ignored. est0: Invalid id16 (set, cur) =3D (15, 20) est0: Invalid freq 1995, ignored. est0: Invalid id16 (set, cur) =3D (14, 20) est0: Invalid freq 1862, ignored. est0: Invalid id16 (set, cur) =3D (13, 20) est0: Invalid freq 1729, ignored. est0: Invalid id16 (set, cur) =3D (12, 20) est0: Invalid freq 1596, ignored. est0: Invalid id16 (set, cur) =3D (11, 20) est0: Invalid freq 1463, ignored. est0: Invalid id16 (set, cur) =3D (10, 20) est0: Invalid freq 1330, ignored. est0: Invalid id16 (set, cur) =3D (9, 20) est0: Invalid freq 1197, ignored. p4tcc0: on cpu0 cpu1: on acpi0 device_attach: acpi_perf1 attach returned 6 device_attach: acpi_perf1 attach returned 6 est1: on cpu1 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 14 device_attach: est1 attach returned 6 p4tcc1: on cpu1 cpu2: on acpi0 est2: on cpu2 est2: Invalid id16 (set, cur) =3D (19, 20) est2: Invalid freq 2527, ignored. est2: Invalid id16 (set, cur) =3D (18, 20) est2: Invalid freq 2394, ignored. est2: Invalid id16 (set, cur) =3D (17, 20) est2: Invalid freq 2261, ignored. est2: Invalid id16 (set, cur) =3D (16, 20) est2: Invalid freq 2128, ignored. est2: Invalid id16 (set, cur) =3D (15, 20) est2: Invalid freq 1995, ignored. est2: Invalid id16 (set, cur) =3D (14, 20) est2: Invalid freq 1862, ignored. est2: Invalid id16 (set, cur) =3D (13, 20) est2: Invalid freq 1729, ignored. est2: Invalid id16 (set, cur) =3D (12, 20) est2: Invalid freq 1596, ignored. est2: Invalid id16 (set, cur) =3D (11, 20) est2: Invalid freq 1463, ignored. est2: Invalid id16 (set, cur) =3D (10, 20) est2: Invalid freq 1330, ignored. est2: Invalid id16 (set, cur) =3D (9, 20) est2: Invalid freq 1197, ignored. p4tcc2: on cpu2 cpu3: on acpi0 device_attach: acpi_perf3 attach returned 6 device_attach: acpi_perf3 attach returned 6 est3: on cpu3 est: CPU supports Enhanced Speedstep, but is not recognized. est: cpu_vendor GenuineIntel, msr 14 device_attach: est3 attach returned 6 p4tcc3: on cpu3 unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff unknown: status reg test failed ff 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 ex_isa_identify() isa_probe_children: disabling PnP devices pmtimer0 on isa0 atrtc: atrtc0 already exists; skipping it sc: sc0 already exists; skipping it isa_probe_children: probing non-PnP devices orm0: at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xc9000-0x= c9fff pnpid ORM0000 on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=3D0x300> sc0: fb0, kbd1, terminal emulator: scteken (teken terminal) vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata0: reset tp1 mask=3D00 ostat0=3Dff ostat1=3Dff ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 0 vector 52 ata0: [MPSAFE] ata0: [ITHREAD] ata1 at port 0x170-0x177,0x376 irq 15 on isa0 ata1: reset tp1 mask=3D00 ostat0=3Dff ostat1=3Dff ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 0 vector 53 ata1: [MPSAFE] ata1: [ITHREAD] atkbdc0: failed to probe at port 0x60,0x64 on= isa0 fdc0 failed to probe at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 ppc0: parallel port not found. 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 Device configuration finished. Reducing kern.maxvnodes 230093 -> 100000 procfs registered lapic: Divisor 2, Frequency 66669425 hz Timecounter "TSC" frequency 2666776980 Hz quality -100 Timecounters tick every 1.000 msec lo0: bpf attached hptrr: no controller detected. ata0: Identifying devices: 00000000 ata0: New devices: 00000000 ata1: Identifying devices: 00000000firewire0: 1 nodes, maxhop <=3D 0 cable = IRM irm(0) (me)=20 firewire0: bus manager 0=20 ata1: New devices: 00000000 ata2: Identifying devices: 00000001 ata2: New devices: 00000001 usbus0: 480Mbps High Speed USB v2.0 usbus1: 480Mbps High Speed USB v2.0 ata2-master: pio=3DPIO4 wdma=3DWDMA2 udma=3DUDMA133 cable=3D40 wire ad4: 476940MB at ata2-master UDMA33 ad4: 976773168 sectors [969021C/16H/63S] 16 sectors/interrupt 1 depth queue GEOM: new disk ad4 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: at usbus1 uhub1: on usbus1 ad4: Intel check1 failedGEOM_MIRROR: Device mirror/gm0 launched (1/1). ad4: Adaptec check1 failed ad4: LSI (v3) check1 failed ad4: LSI (v2) check1 failed ad4: FreeBSD check1 failed ata3: Identifying devices: 00000000 ata3: New devices: 00000000 ata4: Identifying devices: 00000000 ata4: New devices: 00000000 ata5: Identifying devices: 00000000 ata5: New devices: 00000000 GEOM: ad4s1: geometry does not match label (255h,63s !=3D 16h,63s). uhub0: 2 ports with 2 removable, self powered uhub1: 2 ports with 2 removable, self powered ugen0.2: at usbus0 uhub2: on = usbus0 ugen1.2: at usbus1 uhub3: on = usbus1 uhub2: 6 ports with 6 removable, self powered uhub3: 8 ports with 8 removable, self powered ugen0.3: at usbus0 ukbd0: on usbus0 kbd0 at ukbd0 kbd0: ukbd0, generic (0), config:0x0, flags:0x3d0000 ugen1.3: at usbus1 ulpt0: on usbus1 ulpt0: using bi-directional mode (probe2:sbp0:0:2:0): error 22 (probe2:sbp0:0:2:0): Unretryable Error (probe3:sbp0:0:3:0): error 22 (probe3:sbp0:0:3:0): Unretryable Error (probe4:sbp0:0:4:0): error 22 (probe4:sbp0:0:4:0): Unretryable Error (probe5:sbp0:0:5:0): error 22 (probe5:sbp0:0:5:0): Unretryable Error (probe6:sbp0:0:6:0): error 22 (probe6:sbp0:0:6:0): Unretryable Error (probe0:sbp0:0:0:0): error 22 (probe0:sbp0:0:0:0): Unretryable Error (probe1:sbp0:0:1:0): error 22 (probe1:sbp0:0:1:0): Unretryable Error ATA PseudoRAID loaded lapic6: Forcing LINT1 to edge trigger SMP: AP CPU #3 Launched! cpu3 AP: ID: 0x06000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00008400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010400 lapic4: Forcing LINT1 to edge trigger SMP: AP CPU #2 Launched! cpu2 AP: ID: 0x04000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00008400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010400 lapic2: Forcing LINT1 to edge trigger SMP: AP CPU #1 Launched! cpu1 AP: ID: 0x02000000 VER: 0x00060015 LDR: 0x00000000 DFR: 0xffffffff lint0: 0x00010700 lint1: 0x00008400 TPR: 0x00000000 SVR: 0x000001ff timer: 0x000200ef therm: 0x00010000 err: 0x00010000 pcm: 0x00010400 ioapic0: routing intpin 14 (ISA IRQ 14) to lapic 2 vector 48 ioapic0: routing intpin 15 (ISA IRQ 15) to lapic 4 vector 48 ioapic0: routing intpin 16 (PCI IRQ 16) to lapic 6 vector 48 ioapic0: routing intpin 23 (PCI IRQ 23) to lapic 2 vector 49 Root mount waiting for: usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 Root mount waiting for: usbus0 ugen0.4: at usbus0 ums0: on us= bus0 ums0: 3 buttons and [XYZ] coordinates ID=3D0 Trying to mount root from ufs:/dev/mirror/gm0s1a ct_to_ts([2009-10-11 05:16:55]) =3D 1255238215.000000000 start_init: trying /sbin/init Linux ELF exec handler installed linprocfs registered ipfw2 (+ipv6) initialized, divert loadable, nat loadable, rule-based forwar= ding disabled, default to deny, logging disabled splash: image decoder found: green_saver link_elf: symbol callout_reset undefined --KFztAG8eRSV9hGtP Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=pciconf hostb0@pci0:0:0:0: class=0x060000 card=0x00008086 chip=0xd1318086 rev=0x11 hdr=0x00 pcib1@pci0:0:3:0: class=0x060400 card=0x00008086 chip=0xd1388086 rev=0x11 hdr=0x01 none0@pci0:0:8:0: class=0x088000 card=0x00000000 chip=0xd1558086 rev=0x11 hdr=0x00 none1@pci0:0:8:1: class=0x088000 card=0x00000000 chip=0xd1568086 rev=0x11 hdr=0x00 none2@pci0:0:8:2: class=0x088000 card=0x00000000 chip=0xd1578086 rev=0x11 hdr=0x00 none3@pci0:0:8:3: class=0x088000 card=0x00000000 chip=0xd1588086 rev=0x11 hdr=0x00 none4@pci0:0:16:0: class=0x088000 card=0x00000000 chip=0xd1508086 rev=0x11 hdr=0x00 none5@pci0:0:16:1: class=0x088000 card=0x00000000 chip=0xd1518086 rev=0x11 hdr=0x00 none6@pci0:0:25:0: class=0x020000 card=0x00008086 chip=0x10f08086 rev=0x05 hdr=0x00 ehci0@pci0:0:26:0: class=0x0c0320 card=0x42578086 chip=0x3b3c8086 rev=0x05 hdr=0x00 none7@pci0:0:27:0: class=0x040300 card=0x00348086 chip=0x3b568086 rev=0x05 hdr=0x00 pcib2@pci0:0:28:0: class=0x060400 card=0x42578086 chip=0x3b428086 rev=0x05 hdr=0x01 pcib3@pci0:0:28:4: class=0x060400 card=0x42578086 chip=0x3b4a8086 rev=0x05 hdr=0x01 pcib4@pci0:0:28:6: class=0x060400 card=0x42578086 chip=0x3b4e8086 rev=0x05 hdr=0x01 ehci1@pci0:0:29:0: class=0x0c0320 card=0x42578086 chip=0x3b348086 rev=0x05 hdr=0x00 pcib5@pci0:0:30:0: class=0x060401 card=0x42578086 chip=0x244e8086 rev=0xa5 hdr=0x01 isab0@pci0:0:31:0: class=0x060100 card=0x42578086 chip=0x3b028086 rev=0x05 hdr=0x00 atapci0@pci0:0:31:2: class=0x01018f card=0x42578086 chip=0x3b208086 rev=0x05 hdr=0x00 none8@pci0:0:31:3: class=0x0c0500 card=0x42578086 chip=0x3b308086 rev=0x05 hdr=0x00 atapci1@pci0:0:31:5: class=0x010185 card=0x42578086 chip=0x3b268086 rev=0x05 hdr=0x00 vgapci0@pci0:5:1:0: class=0x030000 card=0x10921092 chip=0x001812d2 rev=0x10 hdr=0x00 fwohci0@pci0:5:3:0: class=0x0c0010 card=0x42578086 chip=0x8023104c rev=0x00 hdr=0x00 --KFztAG8eRSV9hGtP-- --iFRdW5/EC4oqxDHL Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkrRbM0ACgkQaUz3f+Zf+XufBwCgqL3MTzyXtrDNrIWZxI3o/x1A 3pkAoP4hrfRXobbW8mYDLkZWe1NvSL2C =ycDc -----END PGP SIGNATURE----- --iFRdW5/EC4oqxDHL-- From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 06:33:08 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from alona.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E9C02106566B; Sun, 11 Oct 2009 06:33:05 +0000 (UTC) (envelope-from davidxu@freebsd.org) Message-ID: <4AD17C1F.8020709@freebsd.org> Date: Sun, 11 Oct 2009 14:33:03 +0800 From: David Xu User-Agent: Thunderbird 2.0.0.21 (X11/20090522) MIME-Version: 1.0 To: Kostik Belousov References: <20091001120730.GR3130@deviant.kiev.zoral.com.ua> <20091002201213.GA16633@stack.nl> <20091005192144.GA2259@deviant.kiev.zoral.com.ua> <4AD01ABC.50901@freebsd.org> <20091010143643.GA2259@deviant.kiev.zoral.com.ua> In-Reply-To: <20091010143643.GA2259@deviant.kiev.zoral.com.ua> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, Jilles Tjoelker , Justin Teller Subject: Re: Signals and an exiting thread 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, 11 Oct 2009 06:33:08 -0000 Kostik Belousov wrote: > On Sat, Oct 10, 2009 at 01:25:16PM +0800, David Xu wrote: > >> Kostik Belousov wrote: >> >> >>> I agree that postponing assignment of the thread for signal delivery >>> till the actual delivery occurs is the proper fix. I tried to cheat >>> in my previous patch. Below is an experimental change that did very >>> minimal testing. >>> >>> >> Even if the signal is put into process's signal queue, it is still >> possible that signal notification is lost because selected thread >> exits before seeing it, if other threads are sleeping, they are >> not notified, this leaves signal in process queue long time before >> it can be delivered to userland. >> >> > > Agreed. Actually, there is one more race. Namely, when thread enters > kernel for executing sigprocmask syscall, but still did not acquired > process mutex, some signal may be scheduled for the thread which will > block it later while still in kernel, so wakeup is lost again. I did > fixed that in later version of the patch, by waking up possible target > threads that have newly blocked signals unblocked. > > Resulting code seems to be relevant for exiting thread as well, where > we also shall set sigmask to indicate that thread is not willing (cannot) > handle any further signals. > > Updated patch below. > The patch looks fine to me. From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 06:50:06 2009 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 574501065697 for ; Sun, 11 Oct 2009 06:50:06 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from dd12710.kasserver.com (dd12710.kasserver.com [85.13.134.233]) by mx1.freebsd.org (Postfix) with ESMTP id 1684C8FC24 for ; Sun, 11 Oct 2009 06:50:06 +0000 (UTC) Received: from current.Sisis.de (ppp-93-104-113-73.dynamic.mnet-online.de [93.104.113.73]) by dd12710.kasserver.com (Postfix) with ESMTP id 3168E18662684; Sun, 11 Oct 2009 08:24:18 +0200 (CEST) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id n9B6OKNB002205; Sun, 11 Oct 2009 08:24:20 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Sun, 11 Oct 2009 08:24:19 +0200 From: Matthias Apitz To: freebsd-current@freebsd.org, kde-freebsd@kde.org Message-ID: <20091011062419.GA2168@current.Sisis.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) Cc: Subject: 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2009 06:50:06 -0000 Hello, I've compiled 9-CURRENT from SVN (r197801) and CVS'uped /usr/ports at the same day (October, 6) to compile KDE and a lot of other stuff. The artsd of KDE reproduceable crashes on 'test sound' with: $ gdb /usr/local/bin/artsd 2650 ... (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x28144166 in Arts::PlayObject_base::_create () from /usr/local/lib/libkmedia2_idl.so.1 (gdb) bt #0 0x28144166 in Arts::PlayObject_base::_create () from /usr/local/lib/libkmedia2_idl.so.1 #1 0x08063bd1 in Arts::SimpleSoundServer_impl::createPlayObject () #2 0x08061288 in Arts::SimpleSoundServer_impl::play () #3 0x280f7103 in _dispatch_Arts_SimpleSoundServer_00 () from /usr/local/lib/libsoundserver_idl.so.1 #4 0x28579df6 in Arts::Object_skel::_dispatch () from /usr/local/lib/libmcop.so.1 #5 0x2856fae8 in Arts::Dispatcher::handle () from /usr/local/lib/libmcop.so.1 #6 0x2853e371 in Arts::Connection::receive () from /usr/local/lib/libmcop.so.1 #7 0x2857d4fe in Arts::SocketConnection::notifyIO () from /usr/local/lib/libmcop.so.1 #8 0x2857281f in Arts::StdIOManager::processOneEvent () from /usr/local/lib/libmcop.so.1 #9 0x28571e70 in Arts::StdIOManager::run () from /usr/local/lib/libmcop.so.1 #10 0x28568447 in Arts::Dispatcher::run () from /usr/local/lib/libmcop.so.1 #11 0x0806a307 in main () Other applications, for example mplayer, play sound fine. The sound driver is snd_ich.ko. Any ideas what to do? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 09:57:25 2009 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 7C9741065670; Sun, 11 Oct 2009 09:57:25 +0000 (UTC) (envelope-from hselasky@freebsd.org) Received: from swip.net (mailfe11.swip.net [212.247.155.65]) by mx1.freebsd.org (Postfix) with ESMTP id D27488FC40; Sun, 11 Oct 2009 09:57:24 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=JgJz4lpzYnkA:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=6I5d2MoRAAAA:8 a=crGzQoN6Asx_Qzrb9UIA:9 a=J6yXXhKjCth5NJ_l8soA:7 a=O1xM5XO3q_M5QAzimG4otUWd6wEA:4 a=knub8hjH8h4A:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe11.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 1148126911; Sun, 11 Oct 2009 11:57:22 +0200 Received-SPF: softfail receiver=mailfe11.swip.net; client-ip=188.126.201.140; envelope-from=hselasky@freebsd.org From: Hans Petter Selasky To: freebsd-ports@freebsd.org, freebsd-usb@freebsd.org, freebsd-current@freebsd.org Date: Sun, 11 Oct 2009 11:58:11 +0200 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910111158.14692.hselasky@freebsd.org> Cc: Subject: [patch] USB video support in KDE4 + sane + more under FreeBSD 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, 11 Oct 2009 09:57:25 -0000 Hi, I was compiling the latest version of KDE4 on my box and I noticed it picked up my installed libv4l2. The only problem is that you need some patches before everything is compiling :-) About libv4lX on FreeBSD, please see: http://lists.freebsd.org/pipermail/freebsd-emulation/2009-June/006231.html Only USB webcams supported yet. After installation manually add -lv4lxdrivers to all the libv4l*.pc files! I will try to get this included into my ulinux distribution soon. Before: Libs: -L${libdir} -lv4lconvert After: Libs: -L${libdir} -lv4lconvert -lv4lxdrivers /usr/local/lib/pkgconfig/libv4lconvert.pc /usr/local/lib/pkgconfig/libv4l2.pc /usr/local/lib/pkgconfig/libv4l1.pc Then patch KDE4 like this: --- /usr/ports/net/kdenetwork4/work/kdenetwork-4.3.1/kopete/libkopete/avdevice/videodevice.h.orig 2009-10-11 11:41:54.000000000 +0200 +++ /usr/ports/net/kdenetwork4/work/kdenetwork-4.3.1/kopete/libkopete/avdevice/videodevice.h 2009-10-11 11:44:34.000000000 +0200 @@ -62,6 +62,13 @@ #endif // __linux__ +#if defined(__FreeBSD__) && defined(ENABLE_AV) +#include +#ifdef HAVE_LIBV4L2 +#include +#endif // HAVE_V4L2 +#endif + #include #include #include 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 66CFA106566B for ; Sun, 11 Oct 2009 12:34:49 +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 449148FC0A for ; Sun, 11 Oct 2009 12:34:49 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id E914846B09 for ; Sun, 11 Oct 2009 08:34:48 -0400 (EDT) Date: Sun, 11 Oct 2009 13:34:48 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Subject: FYI: "8.0TODO" wiki page updated 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, 11 Oct 2009 12:34:49 -0000 FYI for those tracking the 8.0 release: after a haitus of about a month around the FreeBSD Developer Summit and EuroBSDCon 2009 here in Cambridge, and with the help of Colin Percival, the 8.0TODO wiki page is now up-to-date: http://wiki.FreeBSD.org/8.0TODO We'll endeavour to keep it more up-to-date going forward; there's nothing like hosting a conference to get you behind on e-mail :-). Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 12:51:00 2009 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 529F91065693 for ; Sun, 11 Oct 2009 12:51:00 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw1.york.ac.uk (mail-gw1.york.ac.uk [144.32.128.246]) by mx1.freebsd.org (Postfix) with ESMTP id E09ED8FC15 for ; Sun, 11 Oct 2009 12:50:59 +0000 (UTC) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw1.york.ac.uk (8.13.6/8.13.6) with ESMTP id n9BCov8P029712; Sun, 11 Oct 2009 13:50:57 +0100 (BST) Received: from ury.york.ac.uk ([144.32.108.81]) by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1Mwxt3-0001XW-Ci; Sun, 11 Oct 2009 13:50:57 +0100 Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.14.3/8.14.3) with ESMTP id n9BCovwX028693; Sun, 11 Oct 2009 13:50:57 +0100 (BST) (envelope-from gavin@FreeBSD.org) Received: from localhost (gavin@localhost) by ury.york.ac.uk (8.14.3/8.14.3/Submit) with ESMTP id n9BCovgD028690; Sun, 11 Oct 2009 13:50:57 +0100 (BST) (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Sun, 11 Oct 2009 13:50:57 +0100 (BST) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: David Ehrmann In-Reply-To: <4AD0E286.9030508@gmail.com> Message-ID: <20091011133411.A80896@ury.york.ac.uk> References: <4AD0E286.9030508@gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: daichi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: Strange md/unionfs issue 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, 11 Oct 2009 12:51:00 -0000 On Sat, 10 Oct 2009, David Ehrmann wrote: > I have a system running on a flash disk. To prevent it from wearing out > quickly, I don't run with a swap and mount /tmp and /var from memory. > Because /var needs some directories and contains files I probably should save > from time to time, I mount it from flash, mount /var to /var_real so I can > access the underlying files, and then I mount an md device on top of /var as > a unionfs. Initially, it seems to work, but seconds later, the unionfs seems > to fail. When the mount "fails", is it still shown in the output of mount(1)? It appears that this problem is the same as is reported in PR kern/131441, which has so far not had any activity. It appears that this bug has existed since at least 7.1-RELEASE. I've included Goto-san in the CC-list, as he may be able to see if this is a bug in unionfs or in nullfs. Thanks, Gavin From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 14:23:00 2009 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 73DE5106566B; Sun, 11 Oct 2009 14:23:00 +0000 (UTC) (envelope-from uqs@spoerlein.net) Received: from acme.spoerlein.net (cl-43.dus-01.de.sixxs.net [IPv6:2a01:198:200:2a::2]) by mx1.freebsd.org (Postfix) with ESMTP id 072E78FC1D; Sun, 11 Oct 2009 14:22:59 +0000 (UTC) Received: from roadrunner.spoerlein.net (e180138115.adsl.alicedsl.de [85.180.138.115]) by acme.spoerlein.net (8.14.3/8.14.3) with ESMTP id n9BEMvhY046166 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sun, 11 Oct 2009 16:22:58 +0200 (CEST) (envelope-from uqs@spoerlein.net) Received: from roadrunner.spoerlein.net (localhost [127.0.0.1]) by roadrunner.spoerlein.net (8.14.3/8.14.3) with ESMTP id n9BEMuX0003809 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 11 Oct 2009 16:22:56 +0200 (CEST) (envelope-from uqs@spoerlein.net) Received: (from uqs@localhost) by roadrunner.spoerlein.net (8.14.3/8.14.3/Submit) id n9BEMuXn003808; Sun, 11 Oct 2009 16:22:56 +0200 (CEST) (envelope-from uqs@spoerlein.net) Date: Sun, 11 Oct 2009 16:22:56 +0200 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: current@freebsd.org Message-ID: <20091011142256.GA3770@roadrunner.spoerlein.net> Mail-Followup-To: current@freebsd.org, acpi@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.20 (2009-06-14) Cc: acpi@freebsd.org Subject: ACPI Warning: Converted Buffer to expected String 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, 11 Oct 2009 14:23:00 -0000 Just FYI, Dell Inspiron 8600c laptop, semi-recent CURRENT, latest BIOS (A14), machine is 5 years old and producing these warnings when inserting a battery (or booting with one inserted) ACPI Warning for \\_SB_.BAT0._BIF: Converted Buffer to expected String at index 9 (20090903/nsrepair-215) ACPI Warning for \\_SB_.BAT0._BIF: Converted Buffer to expected String at index 10 (20090903/nsrepair-215) ACPI Warning for \\_SB_.BAT0._BIF: Converted Buffer to expected String at index 11 (20090903/nsrepair-215) ACPI Warning for \\_SB_.BAT0._BIF: Converted Buffer to expected String at index 12 (20090903/nsrepair-215) Everything works just before the ACPI import, there's also another bunch of (harmless) errors during boot. acpi0: on motherboard acpi0: [ITHREAD] acpi0: reservation of 0, 9fc00 (3) failed acpi0: reservation of 100000, 3fef0000 (3) failed This is just for reference, perhaps someone wants to know. Cheers, Uli From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 14:51:18 2009 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 6A611106568D for ; Sun, 11 Oct 2009 14:51:18 +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 829918FC0A for ; Sun, 11 Oct 2009 14:51:17 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 1879746B09 for ; Sun, 11 Oct 2009 10:51:17 -0400 (EDT) Date: Sun, 11 Oct 2009 15:51:16 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Subject: Re: FYI: "8.0TODO" wiki page updated 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, 11 Oct 2009 14:51:18 -0000 On Sun, 11 Oct 2009, Robert Watson wrote: > FYI for those tracking the 8.0 release: after a haitus of about a month > around the FreeBSD Developer Summit and EuroBSDCon 2009 here in Cambridge, > and with the help of Colin Percival, the 8.0TODO wiki page is now > up-to-date: > > http://wiki.FreeBSD.org/8.0TODO > > We'll endeavour to keep it more up-to-date going forward; there's nothing > like hosting a conference to get you behind on e-mail :-). And, BTW, during the month's worth of updates, I counted approx 135 approved changes, many quite important fixes, at an average of about 4-5 per day. The rush has definitely slowed down, but the 2-3 critical things left are pretty important. Robert From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 15:57:17 2009 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 BC8DB1065672 for ; Sun, 11 Oct 2009 15:57:17 +0000 (UTC) (envelope-from stefan.hegnauer@gmx.ch) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 11E9D8FC19 for ; Sun, 11 Oct 2009 15:57:16 +0000 (UTC) Received: (qmail invoked by alias); 11 Oct 2009 15:30:35 -0000 Received: from unknown (EHLO inspiron) [84.226.237.147] by mail.gmx.net (mp059) with SMTP; 11 Oct 2009 17:30:35 +0200 X-Authenticated: #1868052 X-Provags-ID: V01U2FsdGVkX19UFN4X9tBUYB6SxIBF0Z5klwZmOaFUS3HtiaOJKe SvwHYdxXLnqTQ+ From: "Stefan Hegnauer" To: , , Date: Sun, 11 Oct 2009 17:30:35 +0200 Message-ID: <503AFE6B3CD0492BA2DFE6ED41691A1A@inspiron> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 Thread-Index: AcpKh8a9sjA+GDuuQHyRQJ+yxOpCww== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Y-GMX-Trusted: 0 X-FuHaFi: 0.55 Cc: Subject: [patch] typo in portaudit - fails with latest /bin/sh 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, 11 Oct 2009 15:57:17 -0000 Hi, portaudit (/usr/ports/ports-mgmt/portaudit) did not work anymore on a recent build of FreeBSD 9.0-CURRENT #0 as of Fri Oct 9 09:27:54 CEST 2009. As it turns out there seems to be a typo in the portaudit script which manifests itself since the changes applied to /bin/sh in http://svn.freebsd.org/viewvc/base?view=revision&sortby=date&revision=197691 The following patch cures this typo: --- /usr/local/sbin/portaudit.orig 2009-10-09 12:36:10.000000000 +0200 +++ /usr/local/sbin/portaudit 2009-10-09 12:39:11.000000000 +0200 @@ -264,7 +264,7 @@ return 2 fi - PKGNAME=`make -VPKGNAME 2>/dev/null || true"` + PKGNAME=`make -VPKGNAME 2>/dev/null || true` if [ -z "$PKGNAME" ]; then echo "portaudit: Can't determine the package name" >&2 If somebody (eik@FreeBSD.org ?) could merge this in, please ... --SH From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 17:54:29 2009 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 427CE10656DE; Sun, 11 Oct 2009 17:54:29 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 2E0BA8FC0C; Sun, 11 Oct 2009 17:54:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9BHsTe4004836; Sun, 11 Oct 2009 17:54:29 GMT (envelope-from danger@freefall.freebsd.org) Received: (from danger@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9BHsTI8004835; Sun, 11 Oct 2009 17:54:29 GMT (envelope-from danger) Date: Sun, 11 Oct 2009 17:54:29 +0000 From: Daniel Gerzo To: hackers@FreeBSD.org Message-ID: <20091011175428.GA3626@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.4.2.3i Cc: stable@FreeBSD.org, questions@FreeBSD.org, current@FreeBSD.org Subject: FreeBSD Status Reports April - September, 2009 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: monthly@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2009 17:54:29 -0000 FreeBSD Quarterly Status Report Introduction This report covers FreeBSD related projects between April and September 2009. During that time a lot of work has been done on wide variety of projects, including the Google Summer of Code projects. The BSDCan conference was held in Ottawa, CA, in May. The EuroBSDCon conference was held in Cambridge, UK, in September. Both events were very successful. A new major version of FreeBSD, 8.0 is to be released soon. If you are wondering what's new in this long-awaited release, read Ivan Voras' excellent summary. Thanks to all the reporters for the excellent work! We hope you enjoy the reading. Please note that the next deadline for submissions covering reports between October and December 2009 is January 15th, 2010. __________________________________________________________________ Google Summer of Code * About Google Summer of Code 2009 * BSD-licensed iconv (Summer of Code 2009) * BSD-licensed text-processing tools (Summer of Code 2008) * Ext2fs Status report (Summer of Code 2009) * libnetstat(3) - networking statistics (Summer of Code 2009) * pefs - stacked cryptographic filesystem (Summer of Code 2009) Projects * BSD# Project * Clang replacing GCC in the base system * FreeBSD TDM Framework * Grand Central Dispatch - FreeBSD port * libprocstat(3) - process statistics * New BSD licensed debugger * NFSv4 ACLs * The Newcons project * VirtualBox on FreeBSD FreeBSD Team Reports * FreeBSD Bugbusting Team * FreeBSD KDE Team * FreeBSD Ports Management Team * Release Engineering Status Report * The FreeBSD Foundation Status Report Network Infrastructure * Enhancing the FreeBSD TCP Implementation * Modular Congestion Control * Network Stack Virtualization * Stream Control Transmission Protocol (SCTP) Kernel * FreeBSD/ZFS * hwpmc for MIPS Documentation * The FreeBSD Dutch Documentation Project * The FreeBSD German Documentation Project * The FreeBSD Hungarian Documentation Project * The FreeBSD Spanish Documentation Project Architectures * FreeBSD/sparc64 Ports * FreeBSD Gecko Project * Portmaster - utility to assist users with managing ports * Valgrind suite on FreeBSD Miscellaneous * EuroBSDcon 2009 * FreeBSD Developer Summit, Cambridge UK * New approach to the locale database * The FreeBSD Forums __________________________________________________________________ About Google Summer of Code 2009 URL: http://socghop.appspot.com/org/home/google/gsoc2009/freebsd URL: http://wiki.freebsd.org/SummerOfCode2009Projects Contact: Brooks Davis Contact: Tim Kientzle Contact: Robert Watson 2009 was The FreeBSD Project's fifth year of participation in the Google Summer of Code. We had a total of 17 successful projects. Some GSoC code will be shipping with FreeBSD 8.0-RELEASE and others will be integrated into future releases. The FreeBSD GSoC admin team would like to thank Google and our students and mentors of another great year! __________________________________________________________________ BSD# Project URL: http://code.google.com/p/bsd-sharp/ URL: http://www.mono-project.org/ Contact: Romain TartiÄre The BSD# Project is devoted to porting the Mono .NET framework and applications to the FreeBSD operating system. During the past year, the BSD# Team continued to track the Mono development and the lang/mono port have almost always been up-to-date (we however had to skip mono-2.2 because of some regression issues in this release). Most of our patches have been merged in the mono trunk upstream, and should be included in the upcoming mono-2.6 release. In the meantime, a few more .NET related ports have been updated or added to the FreeBSD ports tree. These ports include: * www/xsp and www/mod_mono that make it possible to use FreeBSD for hosting ASP.NET application; * lang/boo, a CLI-targeted programming language similar to Python; * lang/mono-basic, the Visual Basic .NET Framework for Mono; * devel/monodevelop, an Integrated Development Environment for .NET; * and much more... Open tasks: 1. Test mono ports and send feedback (we are especially interested in tests where NOPORTDOCS / WITH_DEBUG is enabled). 2. Port the mono-debugger to FreeBSD. 3. Build a debug live-image of FreeBSD so that Mono hackers without a FreeBSD box can help us fixing bugs more efficiently. __________________________________________________________________ BSD-licensed iconv (Summer of Code 2009) URL: http://wiki.freebsd.org/G%C3%A1borSoC2009 Contact: Gábor Kövesdán The code has been extracted from NetBSD and has been transformed into an independent shared library. The basic encodings are well supported. Almost all forward conversions (foo -> UTF-32) are compatible with GNU but the reverse ones are not so accurate because of GNU's advanced transliteration. Some extra encodings have also been added. There are two modules, which segfault; they need some debugging. I can keep working on this project as part of my BSc thesis, so I hope to be able to solve the remaining issues. Improved GNU compatibility is also very desired (extra command line options for iconv(1), iconvctl(), private interfaces, etc.). Open tasks: 1. Fix segfaults in Big5 and HZ modules 2. Improve transliteration in reverse encodings 3. Improve GNU compatibility by implementing extra features 4. Verify POSIX compatibility 5. Verify GNU compatibility 6. Check performance __________________________________________________________________ BSD-licensed text-processing tools (Summer of Code 2008) URL: http://wiki.freebsd.org/G%C3%A1borSoC2008 Contact: Gábor Kövesdán This project was started as part of Google Summer of Code 2008 but there is still a bit of work to complete some missing parts. The BSD-licensed grep implementation is feature-complete and has a good level of GNU compatibility. Our only current concern about the BSD-licensed version is to improve its performance. The GNU variant is much more complex, has about 8 KSLOC, while BSD grep is tiny, has only 1.5 KSLOC. GNU uses some shortcuts and optimizations to speed-up calls to the regex library; that is why it is significantly faster. My point of view is that such optimizations must be implemented in the regex library, keeping the dependent utilities clean and easy to read. BSD grep is so tiny that there is hardly any optimization opportunity by simplifying the code, so the regex library is the next important TODO. There is another issue with the current regex library. It does not support some invalid regular expressions, which work in GNU. We need to maintain compatibility, so we cannot just drop this feature. Actually, BSD grep is linked to the GNU regex library to maintain this feature but due to the lack of the mentioned shortcuts, it is still slower than GNU. Anyway, if we can live with this little performance hit until we get a modern regex library, I think grep is ready to enter HEAD. As for the regex library, NetBSD's result of the last SoC is worth taking a look. The sort utility has been rewritten from scratch. The existing BSD-licensed implementation could not deal with wide characters by design. The new implementation is still lacking some features but is quite complete. There is a performance issue, though. Sorting is a typical algorithmic subject but I am not an algorithmic expert, so my implementation is not completely optimal. Some help would be welcome with this part. The bc/dc utilities have been ported from OpenBSD. They pass OpenBSD's and GNU's regression tests but they arrived too late to catch 8.X, so they will go to HEAD after the release. Open tasks: 1. Improve sort's sorting and file merging algorithms 2. Complete missing features for sort 3. Get a modern regex library for FreeBSD __________________________________________________________________ Clang replacing GCC in the base system URL: http://wiki.freebsd.org/BuildingFreeBSDWithClang Contact: Ed Schouten Contact: Roman Divacky Contact: Brooks Davis Contact: Pawel Worach The clang@FreeBSD team presents the status of clang/LLVM being able to compile FreeBSD system. The current status is: * i386 - kernel boots, world needs little hacks but works * amd64 - kernel boots, world needs little hacks but works * ppc - broken because of unknown RTLD bug * other - unknown All other platforms are untested. A lot has happened over the spring/summer: amd64 got proper mcmodel=kernel support, compiler-rt has been introduced (paving the way for libgcc replacement), we have run two experimental port builds to see how clang does there. The C++ support is able to parse devd.cc without warnings. We have got the kernel working with -O2. FreeBSD has been promoted to be an officially supported plaform in LLVM. As a result of all this work, many parts of FreeBSD that did not compile before now build without problems. Open tasks: 1. The "ClangBSD" branch of FreeBSD got a little stale and has not been updated for a while. 2. We also need to get some important fixes into LLVM to get libc compiling and some other smaller issues. 3. We can still appreciate more testers on minor platforms (mostly on ARM, PPC and MIPS, but testing on other platforms is also welcome). __________________________________________________________________ Enhancing the FreeBSD TCP Implementation URL: http://caia.swin.edu.au/freebsd/etcp09/ URL: http://caia.swin.edu.au/urp/newtcp/ URL: http://www.freebsdfoundation.org/projects.shtml URL: http://people.freebsd.org/~lstewart/patches/tcp_ffcaia2008/ Contact: Lawrence Stewart TCP appropriate byte counting (RFC 3465) support has been merged into the FreeBSD 8 branch and will ship in FreeBSD 8.0-RELEASE. The reassembly queue auto-tuning and SIFTR work was not ready in time to safely integrate for 8.0-RELEASE. Padding has been added to necessary TCP structs to facilitate MFCing features back to the 8-STABLE branch after 8.0 is released. Candidate patches against FreeBSD-CURRENT will be ready for wider testing in the coming weeks. The freebsd-net mailing list will be solicited for testing/feedback when everything is ready. Open tasks: 1. Solicit review/testing and integrate the ALQ kld and variable length message support patch into FreeBSD-CURRENT. 2. Solicit review/testing and integrate the SIFTR tool into FreeBSD-CURRENT. 3. Complete dynamic reassembly queue auto-tuning patch for FreeBSD-CURRENT. 4. Fix an identified bug in the SACK implementation's fast retransmit/fast recovery behavior. 5. Profit! __________________________________________________________________ EuroBSDcon 2009 URL: http://2009.eurobsdcon.org/ URL: http://2010.eurobsdcon.org/ Contact: Sam Smith Contact: Robert Watson EuroBSDcon 2009 happened in Cambridge, with over 160 users, developers, friends and others. Slides, papers and audio are now up on the website for those who could not make it to Cambridge. Next year's event in 2010 will take place in Karlsruhe from 8 to 10 October 2010. If you are interested in what you missed in 2009, or to join the mailing list so you do not miss out next year, visit http://2009.eurosbsdcon.org. __________________________________________________________________ Ext2fs Status report (Summer of Code 2009) URL: http://wiki.freebsd.org/SOC2009AdityaSarawgi Contact: Aditya Sarawgi FreeBSD's ext2fs had some parts under GPL. The aim of my project was to rewrite those parts and free ext2fs from GPL. I have been successful in rewriting the parts and NetBSD's ext2fs was a great help in this. Certain critical parts under GPL were also removed due to which the write performance suffered. I also implemented Orlov Block Allocator for ext2fs. Currently I am planning to make ext2fs Multiprocessor Safe (MPSAFE). My work resides in truncs_ext2fs branch of Perforce. Open tasks: 1. Ext4 support for FreeBSD 2. Directory indexing for ext2fs 3. Journaling in ext2fs using gjournal __________________________________________________________________ FreeBSD Bugbusting Team URL: http://www.FreeBSD.org/support.html#gnats URL: http://wiki.FreeBSD.org/BugBusting URL: http://people.FreeBSD.org/~linimon/studies/prs/ URL: http://people.FreeBSD.org/~linimon/studies/prs/recommended_prs.html Contact: Gavin Atkinson Contact: Mark Linimon Contact: Remko Lodder Contact: Volker Werth We continue to classify PRs as they arrive, adding 'tags' to the subject lines corresponding to the kernel subsystem involved, or man page references for userland PRs. These tags, in turn, produce lists of PRs sorted both by tag and by manpage. The list of PRs recommended for committer evaluation by the Bugbusting Team continues to receive new additions. This list contains PRs, mostly with patches, that the Bugbusting Team feel are probably ready to be committed as-is, or are probably trivially resolved in the hands of a committer with knowledge of the particular subsystem. All committers are invited to take a look at this list whenever they have a spare 5 minutes and wish to close a PR. A full list of all the automatically generated reports is also available at one of the cited URLs. Any recommendations for reports which not currently exist but which would be beneficial are welcomed. Gavin Atkinson gave a presentation on "The PR Collection Status" at the EuroBSDCon 2009 DevSummit, and discussed with other participants several other ideas to make the PR database more useful and usable. Several good ideas came from this, and will hopefully lead to more useful tools in the near future. Discussions also took place on how it may be possible to automatically classify non-ports PRs with a view towards notifying interested parties, although investigations into this have not yet begun. Mark Linimon also continues attempting to define the general problem and investigating possible new workflow models, and presented work on this at BSDCan 2009. Since the last status report, the number of open bugs has increased to around the 5900 mark, partially because of an increased focus on getting more information into the existing PRs, in an attempt to make sure all the information required is now available. As a result, although the number of open PRs has increased, they are hopefully of better quality. As always, more help is appreciated, and committers and non-committers alike are always invited to join us on #freebsd-bugbusters on EFnet and help close stale PRs or commit patches from valid PRs. Open tasks: 1. Work on suggestions from developers who were at the EuroBSDCon DevSummit. 2. Try to find ways to get more committers helping us with closing the PRs that the team has already analyzed. __________________________________________________________________ FreeBSD Developer Summit, Cambridge UK URL: http://wiki.FreeBSD.org/200909DevSummit Contact: Robert Watson Around 70 FreeBSD developers and guests attended the FreeBSD developer summit prior to EuroBSDCon 2009 in Cambridge, UK. Hosted at the University of Cambridge Computer Laboratory, the workshop-style event consisted of prepared presentations, as well as group hacking and discussion sessions. Talks covered topics including 802.11 mesh networking, virtual network stacks and kernels, a new BSD-licensed debugger, benchmarking, bugbusting, NetFPGA, a port of Apple's GCD (Grand Central Dispatch) to FreeBSD, security policy work, cryptographic signatures, FreeBSD.org system administration, time geeks, a new console driver, and the FreeBSD subversion migration. Slides for many talks are now available on the wiki page. A good time was had by all, including a punting outing on the River Cam! __________________________________________________________________ FreeBSD Gecko Project URL: https://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO Contact: Beat Gaetzi Contact: Martin Wilke Contact: Andreas Tobler Andreas Tobler made the classic mistake of sending us a lot of powerpc and sparc64 related patches. The usual punishment, of giving him a commit bit to the Gecko repository, has been applied. We currently have some old ports in the ports tree: * www/mozilla is 5 year old now, no longer supported upstream, and has a lot of security vulnerabilities. We can use www/seamonkey instead. * www/xulrunner is superseeded by www/libxul. A patch that includes the following changes has been tested on pointyhat and is ready for commit: * Remove references to www/mozilla/Makefile.common and www/mozilla/bsd.gecko.mk * Switch USE_GECKO= xulrunner firefox mozilla to USE_GECKO= libxul and remove www/xulrunner We are also working on Firefox 3.6 (Alpha 2), Thunderbird 3.0 (Beta 4), new libxul 1.9.1.3 and Seamonkey 2.0 (Beta 2) ports. All of them are already committed to our Gecko repository. A current status and todo list can be found at http://trillian.chruetertee.ch/freebsd-gecko/wiki/TODO. Open tasks: 1. Remove mozilla, xulrunner and firefox2 from the ports tree. 2. The www/firefox35 port should be moved to www/firefox. 3. The old (and somewhat stale) Gecko providers mozilla, nvu, xulrunner, flock and firefox also need to be removed. __________________________________________________________________ FreeBSD KDE Team URL: http://freebsd.kde.org URL: http://miwi.bsdcrew.de/category/kde/ URL: http://blogs.freebsdish.org/tabthorpe/category/kde Contact: Thomas Abthorpe Contact: Max Brazhnikov Contact: Martin Wilke Since the spring, the FreeBSD KDE team has been busy upgrading KDE from 4.2.0 up through to 4.3.1. As part of the ongoing maintenance of KDE, the team also updated Qt4 from 4.4.3 through to 4.5.2 We added two new committers/maintainers to the team, Kris Moore (kmoore@) and Dima Panov (fluffy@). We also granted enhanced area51 access to contributors Alberto Villa and Raphael Kubo da Costa. Alberto has been our key contributor updating and testing Qt 4.6.0-tp1. Raphael is a KDE developer, who has become our Gitorious liaison, he has been responsible for getting FreeBSD Qt patches merged in upstream. Markus Brüffer (markus@) spent a lot of time patching widgets and system plugins so they would work under FreeBSD. We would like to thank him for all his effort! Open tasks: 1. Update to Qt 4.6.0 2. Update to KDE 4.4.0 3. Work with our userbase on fixing an EOL for KDE3 in the ports tree __________________________________________________________________ FreeBSD Ports Management Team URL: http://www.freebsd.org/ports/ URL: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/ URL: http://portsmon.FreeBSD.org/index.html URL: http://www.freebsd.org/portmgr/index.html URL: http://tinderbox.marcuscom.com Contact: Mark Linimon The ports count has soared to over 20,700. The PR count had been driven below 800 by some extraordinary effort, but once again is back to its usual count of around 900. We are currently building packages for amd64-6, amd64-7, amd64-8, i386-6, i386-7, i386-8, sparc64-7, and sparc64-8. There have been preliminary runs of i386-9; however, to be able to continue builds on -9, we will either need to find places to host a number of new machines, or drop package building for -6. The mailing list discussion of the latter proved quite controversial. We have added some new i386 machines to help speed up the builds, but this only makes up for the disk failures on some of our older, slower, i386 nodes. We also appreciate the loan of more package build machines from several committers, including pgollucci@, gahr@, erwin@, Boris Kochergin, and Craig Butler. The portmgr@ team has also welcomed new members Ion-Mihai Tetcu (itetcu@) and Martin Wilke (miwi@). We also thank departing member Kirill Ponomarew (krion@) for his long service. Ion-Mihai has spent much time working on a system that does automatic Quality Assurance on new commits, called QAT. A second tinderbox called QATty has helped us to fix many problems, especially those involving custom PREFIX and LOCALBASE settings, and documentation inclusion options. Ports conformance to documented features / non-default configuration will follow. Between pav and miwi, over 2 dozen experimental ports runs have been completed and committed. We have added 5 new committers since the last report, and 2 older ones have rejoined. Open tasks: 1. We are currently trying to set up ports tinderboxes that can be made available to committers for pre-testing; those who can loan machines for this should contact Ion-Mihai (itetcu@) with details regarding the hardware and bandwidth. 2. Most of the remaining ports PRs are "existing port/PR assigned to committer". Although the maintainer-timeout policy is helping to keep the backlog down, we are going to need to do more to get the ports in the shape they really need to be in. 3. Although we have added many maintainers, we still have almost 4,700 unmaintained ports (see, for instance, the list on portsmon). (The percentage is down to 22%.) We are always looking for dedicated volunteers to adopt at least a few unmaintained ports. As well, the packages on amd64 and sparc64 lag behind i386, and we need more testers for those. __________________________________________________________________ FreeBSD TDM Framework Contact: Rafal Czubak Contact: Michal Hajduk This work's purpose is a generic and flexible framework for systems equipped with Time Division Multiplexing (TDM) units, often found on embedded telecom chips. The framework is designed to support various controllers and many types of TDM channels e.g. voiceband, sound and miscellaneous data channels. Currently, voiceband infrastructure is being developed on Marvell RD-88F6281 reference board. It will serve as an example of how to use the TDM framework for other channel types. The direct objective of using TDM with voiceband channels is bringing a FreeBSD based VoIP system, capable of bridging analog telephone world with digital IP telephony. Together with third party VoIP software (e.g. Asterisk), the design can serve as VoIP Private Branch Exchange (PBX). Current state highlights: * TDM controller interface * TDM channel interface * TDM channel API for kernel modules * codec interface * voiceband channel character device driver * TDM controller driver for Marvell Kirkwood and Discovery SoCs * Si3215 SLIC driver * Si3050 DAA driver Open tasks: 1. Develop demo application showing example usage of voiceband channel. 2. Integrate voiceband infrastructure with Zaptel/DAHDI telephony hardware drivers. __________________________________________________________________ FreeBSD/sparc64 Contact: Marius Strobl Noteworthy developments regarding FreeBSD/sparc64 since the last Status Reports are: * Cas(4), a driver for Sun Cassini/Cassini+, as well as National Semiconductor DP83065 Saturn Gigabit NICs has been committed and thus will be part of FreeBSD beginning with 8.0-RELEASE and 7.3-RELEASE, respectively. This means that the on-board NICs found in Fire V440, as well as the add-on cards based on these chips, are now supported, including on non-sparc64 machines. Unfortunately, the cas(4) driver triggers what seem to be secondary problems with the on-board NICs found in B100 blades and Fire V480, which due to lack of access to such systems could not be fixed so far. * Initial support for sun4u machines based on the "Fire" Host-PCI-Express bridge like Fire V215, V245, etc. has been completed (including support for the on-board ATA controller, which caused several problems at first, and MSI/MSI-X). Some code like the quirk handling for the ALi/ULi chips found in these machines needs to be revisited though and no stability tests have been conducted so far. If all goes well, the code will hit HEAD some time after FreeBSD 8.0-RELEASE has been released. In theory, machines based on the "Oberon" Host-PCI-Express bridge, at least for the most part, should also be supported with these changes, but due to lack of access to a Mx000 series machine the code could not be tested with these so far. * Some bugs in the snd_t4dwave(4) driver have been fixed, as well as some special handling for sparc64 has been added so it does 32-bit DMA and now generally works with the on-board ALi M5451 found for example in Blade 100 and Blade 1500. Unfortunately, it was only tested to work correctly in two out of three Blade 100. Why it still does not work correctly in the remaining one is currently unknown but at least no longer causes IOMMU-panics so testing snd_t4dwave(4) on sparc64 is no longer harmful. These changes will be part of FreeBSD 8.0-RELEASE and 7.3-RELEASE. * Ata-marvell(4) has been fixed to work on sparc64 (actually also on anything that is not x86 with less than 4GB of RAM). These fixes will be part of FreeBSD 8.0-RELEASE and 7.3-RELEASE. * A proper and machine-independent fix for the old problem that the loader leaves the NIC opened by the firmware, which could lead to panics during boot when netbooting, has been developed but not committed yet. Open tasks: __________________________________________________________________ FreeBSD/ZFS Contact: Pawel Dawidek We believe that the ZFS file system is now production-ready in FreeBSD 8.0. Most (if not all) reported bugs were fixed and ZFS is no longer tagged as experimental. There is also ongoing work in Perforce to bring the latest ZFS version (v19) to FreeBSD. Open tasks: 1. Download 8.0 release candidates and test, test, test and report any problems to the freebsd-fs@FreeBSD.org mailing list. __________________________________________________________________ Grand Central Dispatch - FreeBSD port URL: http://libdispatch.macosforge.org/ Contact: Robert Watson Contact: Stacey Son Contact: libdispatch mailing list We have ported libdispatch, Apple's Grand Central Dispatch event and concurrency framework to FreeBSD: * Added new kqueue primitives required to support GCD, such as EVFILT_USER and EV_TRIGGER * Created autoconf and automake build framework for libdispatch * Modified libdispatch to use POSIX semaphores instead of Mach semaphores * Adapted libdispatch to use portable POSIX time routines Jordan Hubbard has also prepared a blocks-aware clang compiler package for FreeBSD. When compiled with clang, libdispatch provides blocks-based, as well as function-based callbacks. The port was presented at the FreeBSD Developer Summit in Cambridge, UK in September, and slides are online on the devsummit wiki page. A FreeBSD port is now available in the Ports Collection. After FreeBSD 8.0-RELEASE has shipped, the new kqueue primitives will be MFC'd so that libdispatch works out of the box on FreeBSD 8.1-RELEASE. Open tasks: 1. Complete porting of libdispatch test suite to FreeBSD. 2. Investigate pthread work queue implementation for FreeBSD. 3. Evaluate performance impact of some machine-dependent and OS-dependent optimizations present in the Mac OS X version of libdispatch to decide if they should be done for other platforms and OS's. 4. Explore whether FreeBSD base operating system tools would benefit from being modified to use libdispatch. __________________________________________________________________ hwpmc for MIPS URL: http://wiki.freebsd.org/FreeBSD/mips URL: http://wiki.freebsd.org/FreeBSD/mips/UBNT-RouterStationPro Contact: George Neville-Neil Currently working on board bringup. I have looked over the docs for how MIPS provides performance counters and will begin adding code soon. __________________________________________________________________ libnetstat(3) - networking statistics (Summer of Code 2009) URL: http://wiki.FreeBSD.org/PGJSoc2009 URL: http://p4web.freebsd.org/@md=d&cd=//&c=McZ@//depot/projects/soc2009/pgj _libstat/?ac=83 Contact: Gábor Páli The libnetstat(3) project provides a user-space library API to monitor networking functions with the following benefits: * ABI-robust interface making use of accessor functions in order to divorce monitoring applications from kernel or user ABI changes. * Supports running 32-bit monitoring tools on top of a 64-bit kernel. * Improved consistency for both kvm(3) and sysctl(3) when retrieving information. The supported abstractions are as follows: * Active sockets and socket buffers * Network interfaces and multicast interfaces * mbuf(9) statistics * bpf(4) statistics * Routing statistics, routing tables, multicast routing * Protocol-dependent statistics There is a sample application, called nettop(8), which provides a simple ncurses-based top(1)-like interface for monitoring active connections and network buffer allocations via the library. A modified version of netstat(1) has also been created to use libnetstat(3) as much as possible. __________________________________________________________________ libprocstat(3) - process statistics URL: http://svn.freebsd.org/viewvc/base/projects/libprocstat/ Contact: Stanislav Sedov Contact: Ulf Lilleengen The libprocstat project is an ongoing effort to develop a library that can be used to retrieve information about running processes and open files in the uniform and platform-independent way both from a running system or from core files. This will facilitate the implementation of file- or process-monitoring applications like lsof(1), fstat(1), fuser, etc. The libprocstat repository contains a preliminary version of the library. It also includes rewrites of the fstat and the fuser utilities ported to use this library instead of retrieving all the required information via the kvm(3) interface; one of the important advantages of the versions that use libprocstat is that these utilities are ABI independent. Open tasks: 1. Implement KVM-based namecache lookup to retrieve filesystem paths associated with file descriptors and VM objects. 2. Analyze possible ways of exporting file and process information from the kernel in an extensible and ABI-independent way. __________________________________________________________________ Modular Congestion Control URL: http://caia.swin.edu.au/urp/newtcp/ URL: http://svn.freebsd.org/viewvc/base/projects/tcp_cc_8.x/ Contact: Lawrence Stewart The patch has received some significant rototilling in the past few months to prepare it for merging to FreeBSD-CURRENT. Additionally, I completed an implementation of the CUBIC congestion control algorithm to complement the existing NewReno and H-TCP algorithm implementations already available. I have one further intrusive change to make, which will allow congestion control modules to be shared between the TCP and SCTP stacks. Once this is complete, I will be soliciting for review/testing in the hope of committing the patch to FreeBSD-CURRENT in time to be able to backport it for 8.1-RELEASE. Open tasks: 1. Abstract the congestion control specific variables out of the TCP and SCTP control blocks into a new struct that can be passed into the API instead of the control block itself. __________________________________________________________________ Network Stack Virtualization URL: http://wiki.freebsd.org/Image URL: http://wiki.freebsd.org/200909DevSummit Contact: Bjoern A. Zeeb Contact: Marko Zec Contact: Robert Watson The network stack virtualization project aims at extending the FreeBSD kernel to maintain multiple independent instances of networking state. This allows for networking independence between jail environment, each maintaining its private network interfaces, IPv4 and IPv6 network and port address space, routing tables, IPSec configuration, firewalls, and more. During the last months the remaining pieces of the VIMAGE work were merged by Marko, Julian and Bjoern. Robert Watson developed a vnet allocator to overcome ABI issues. Jamie Gritton merged his hierachical jail framework that now also is the management interface for virtual network stacks. During the FreeBSD Developer Summit that took place at EuroBSDCon 2009 in Cambridge, UK, people virtualized more code. As a result SCTP and another accept filter were virtualized and more people became familiar with the design of VImage and the underlying concepts. Finally getting more hands involved was a crucial first step for the long term success of kernel virtualization. The next steps will be to finish the network stack virtualization, generalize the allocator framework before thinking of virtualizing further subsystems and to update the related documentation. Along with that a proper jail management framework will be worked on. Long term goals, amongst others, will be to virtualize more subsystems like SYS-V IPC, better privilege handling, and resource limits. In the upcoming FreeBSD 8.0 Release, vnets are treated as an experimental feature. As a result, they are not yet recommended for use in production environments. There was lots of time spent to finalize the infrastructure for vnets though, so that further changes can be merged and we are aiming to have things production ready for 8.2. In case you want to help to achieve this goal, feel free to contact us and support or help virtualizing outstanding parts like two firewalls, appletalk, netipx, ... as well as generating regression tests. __________________________________________________________________ New approach to the locale database URL: http://wiki.freebsd.org/LocaleNewApproach URL: svn://svn.freebsd.org/base/user/edwin/locale Contact: Edwin Groothuis Contact: i18n mailinglist Problem: Over the years the FreeBSD locale database (share/colldef, share/monetdef, share/msgdef, share/numericdef, share/timedef) has accumulated a total of 165 definitions (language - country-code - character-set triplets). The contents of the files for Western European languages are often low-ASCII but for Eastern European and Asian languages partly or fully high-ASCII. Without knowing how to display or interpret the character-sets, it is difficult to make sure by the general audience that the local language (language - country-code) definitions are displayed properly in various character-sets. Suggested approach: With the combination of the data in the Unicode project (whose goal is to define all the possible written characters and symbols on this planet) and the Common Locale Data Repository (whose goal is to document all the different data and definitions needed for the locale database), we can easily keep track of the data, without the need of being able to display the data in the required character sets or understand them fully when updates are submitted by third parties. Current status: Conversion of share/monetdef, share/msgdef, share/numericdef, share/timedef to the new design is completed. The Makefile infrastructure is converted. Regression checks are done. Most of the tools are in place, waiting on the import of bsdiconv to the base system. Open tasks: 1. At this moment the system is not self-hosted yet, because of the lack of an iconv-kind of program in the base operating system. Gabor@ is working on bsdiconv as a GSoC project and once that has been imported we will be able to perform a clean install from the definitions in Unicode text format to the required formats and character sets. __________________________________________________________________ New BSD licensed debugger URL: http://wiki.freebsd.org/TheBsdDebugger URL: http://people.freebsd.org/~dfr/ngdb.git URL: http://wiki.freebsd.org/200909DevSummit?action=AttachFile&do=view&targe t=NGDB-200909.pdf Contact: Doug Rabson <> I have been working recently on writing a new debugger, primarily for the FreeBSD platform. For various reasons, I have been writing it in a relatively obscure C-like language called D. So far, I have a pretty useful (if a little raw at the edges) command line debugger which supports ELF, Dwarf debugging information and (currently) 32 bit FreeBSD and Linux. The engine includes parsing and evaluation of arbitrary C expressions along with the usual debugging tools such as breakpoints, source code listing, single-step etc. All the code is new and BSD licensed. Currently, the thing supports userland debugging of i386 targets via ptrace and post-mortem core file debugging of the same. I will be adding amd64 support real soon (TM) and maybe support for GDB's remote debugging protocol later. __________________________________________________________________ NFSv4 ACLs URL: http://wiki.freebsd.org/NFSv4_ACLs Contact: Edward Tomasz Napierala During Google Summer of Code 2008, I have implemented native support for NFSv4 ACLs for both ZFS and UFS. Most of the code has already been merged to CURRENT. NFSv4 ACLs are unconditionally enabled in ZFS and the usual tools, like getfacl(1) and setfacl(1) can be used to view and change them. I plan to merge the remaining bits (UFS support) this month. It should be possible to MFC it in order to ship in FreeBSD 8.1-RELEASE. Open tasks: 1. UFS changes review 2. Support for NFSv4 ACLs in tar(1) __________________________________________________________________ pefs - stacked cryptographic filesystem (Summer of Code 2009) URL: http://blogs.freebsdish.org/gleb/ URL: http://wiki.freebsd.org/SOC2009GlebKurtsov Contact: Gleb Kurtsou Contact: Stanislav Sedov Pefs is a kernel level filesystem for transparently encrypting files on top of other filesystems (like zfs or ufs). It adds no extra information into files (unlike others), doesn't require cipher block sized io operations, supports per directory/file keys and key chaining, uses unique per file tweak for encryption. Supported algorithms: AES, Camellia, Salsa20. The code is ready for testing. Open tasks: 1. Implement encrypted name lookup/readir cache 2. Optimize sparse files handling and file resizing __________________________________________________________________ Portmaster - utility to assist users with managing ports URL: http://dougbarton.us/portmaster.html Contact: Doug Barton I am currently seeking funding for further development work on portmaster. There are several features that are regularly requested by the community (such as support for installing packages) that I would very much like to implement but that will take more time than I can reasonably volunteer to implement correctly. There is information about the funding proposal available at the link above. Meanwhile I have recently completed another round of bug fixes and feature enhancements. The often-requested ability to specify the -x (exclude) option more than once on the command line was added in version 2.12. Also in that version I added the --list-origins option to make it easier to reinstall ports after a major version upgrade, or install the same set of ports on another system. Open tasks: 1. See the funding proposal. __________________________________________________________________ Release Engineering Status Report URL: http://www.FreeBSD.org/releng/ Contact: Release Engineering Team The Release Engineering Team continues to work on FreeBSD 8.0-RELEASE. Public testing has turned up quite a few problems, many related to the low-level network (routing/ARP table) changes and their interactions with IPv6. Progress continues to be made on fixing up the issues that have been identified during the public testing. At this point in time we are shooting for two more public test builds (RC2 and RC3) followed by the release late October or early November. __________________________________________________________________ Stream Control Transmission Protocol (SCTP) Contact: Randall Stewart SCTP continues to have minor fixes added to it as well as some new features. First and foremost, we now have VIMAGE and SCTP working and playing together. This goal was accomplished with the help of bz@, my new mentee tuexen@ and myself working together at the FreeBSD DevSummit in Cambridge, UK. Also the non-renegable SACK feature contributed by the university of Delaware was fixed so that now its safe to turn on (its sysctl). If you are using SCTP with CMT (Conncurrent Multipath Transfer) you will want to enable this option (CMT is also a sysctl). With CMT enabled you will be able to send data to all the destinations of an SCTP peer. We welcomed a new mentee (soon to be a commiter) to FreeBSD. Michael Tuexen is now a mentee of rrs@. Michael has been contributing to the SCTP work for quite some time and also moonlights as a Professor at the University of Muenster in Germany (when not doing SCTP coding). __________________________________________________________________ The FreeBSD Dutch Documentation Project URL: http://www.freebsd.org/docproj/translations.html#dutch Contact: René Ladan Contact: Remko Lodder The current translations (Handbook and some articles) are kept up to date with the English versions. Some parts of the website have been translated, more work is in progress. Open tasks: 1. Find more volunteers for translating the remaining parts of the website and the FAQ. __________________________________________________________________ The FreeBSD Forums URL: http://forums.freebsd.org/ Contact: FreeBSD Forums Admins Contact: FreeBSD Forums Moderators Since their public launch in November 2008, the FreeBSD Forums (the most recent addition to the user community and support channels for the FreeBSD Operating System) have witnessed a healthy and steady growth. The user population is now at over 8,000 registered users, who have participated in over 6,000 topics, containing over 40,000 posts in total. The sign-up rate hovers between 50-100 each week. The total number of visitors (including 'guests') is hard to gauge but is likely to be a substantial multiple of the registered userbase. New topics and posts are actively 'pushed out' to search engines. This in turn makes the Forums show up in search results more and more often, making it a valuable and very accessible source of information for the FreeBSD community. One of the contributing factors to the Forums' success is their 'BSD-style' approach when it comes to administration and moderation. The Forums have a strong and unified identity, they are neatly divided into sub-forums (like 'Networking', 'Installing & Upgrading', etc.), very actively moderated, spam-free, and with a core group of very active and helpful members, dispensing many combined decades' worth of knowledge to starting, intermediate and professional users of FreeBSD. We expect the Forums to be, and to remain, a central hub in FreeBSD's community and support efforts. __________________________________________________________________ The FreeBSD Foundation Status Report URL: http://www.freebsdfoundation.org Contact: Deb Goodkin Kicking off our fall fund-raising campaign! Find out more at http://www.freebsdfoundation.org/donate/. We were a sponsor for EuroBSDCon 2009, and provided travel grants to 8 FreeBSD developers and users. We sponsored Kyiv BSD 2009, in Kiev Ukraine. We were also a sponsor of BSDCan, and sponsored 7 developers. We funded three new projects, New Console Driver by Ed Schouten, AVR32 Support by Arnar Mar Sig, and Wireless Mesh Support by Rui Paulo, which has completed. We continued funding a project that is making improvements to the FreeBSD TCP Stack by Lawrence Stewart. The project that made removing disk devices with mounted filesystems on them safe, by Edward Napierala, is now complete. We recognized the following FreeBSD developers at EuroBSDCon 2009: Poul-Henning Kamp, Bjoern Zeeb, and Simon Nielsen. These developers received limited edition FreeBSD Foundation vests. Follow us on Twitter now! __________________________________________________________________ The FreeBSD German Documentation Project URL: https://doc.bsdgroup.de URL: http://code.google.com/p/bsdcg-trans/wiki/BSDPJTAdede Contact: Johann Kois Contact: Benedict Reuschling Contact: Martin Wilke In May 2009, Benedict Reuschling received his commit bit to the www/de and doc/de_DE.ISO8859-1 trees under the mentorship of Johann Kois. Since then, he has been working primarily on the Handbook, updating existing chapters and translating new ones. Most notably, the filesystems and DTrace chapters have been recently translated. Bugs found in the original documents along the way were reported back so that the other translation teams could incorporate them, as well. Christoph Sold has put his time in translating the wiki pages of the BSD Certification Group into the German language. This is very helpful for all German people who want to take the exam and like to read the information about it in their native language. Daniel Seuffert has sent valuable corrections and bugfixes. Thanks to both of them for their time and efforts! The website is translated and updated constantly. Missing parts will be translated as time permits. We appreciate any help from volunteers in proofreading documents, translating new ones and keeping them up to date. Even small error reports are of great help for us. You can find contact information at the above URL. Open tasks: 1. Update the existing documentation set (especially the Handbook). 2. Translate more articles to German. 3. Read the translations. Check for problems and mistakes. Send feedback. __________________________________________________________________ The FreeBSD Hungarian Documentation Project URL: http://www.FreeBSD.org/hu URL: http://www.FreeBSD.org/doc/hu URL: http://wiki.FreeBSD.org/HungarianDocumentationProject URL: http://p4web.freebsd.org/@md=d&cd=//depot/projects/docproj_hu/&c=aXw@// depot/projects/docproj_hu/?ac=83 Contact: Gábor Kövesdán Contact: Gábor Páli In the last months, we have not added new translations, although we have been working on the existing ones to have them updated. We need more translators and volunteers to keep the amount of the translated documentation growing, so feel free to contribute. Every line of submission or feedback is appreciated and highly welcome. If you want to join our work, please read the introduction to the project as well as the FDP Primer (both of them are available in Hungarian). Open tasks: 1. Translate news entries, press releases 2. Translate Release Notes for -CURRENT and 8.X 3. Translate articles 4. Translate web pages 5. Read the translations, send feedback __________________________________________________________________ The FreeBSD Spanish Documentation Project URL: http://www.FreeBSD.org/es URL: http://www.FreeBSD.org/doc/es URL: http://www.freebsd.org/doc/es/articles/fdp-es/ Contact: José Vicente Carrasco Vayá Contact: Gábor Kövesdán Recently, we have added one new article translation. The existing translations have not been updated, though. We need more human resources to keep up with the work and keep the translations up-to-date. Open tasks: 1. Update the Handbook translation 2. Update the web page translation __________________________________________________________________ The Newcons project URL: http://wiki.FreeBSD.org/Newcons URL: http://people.freebsd.org/~ed/newcons/patches/ Contact: Ed Schouten Some time ago I started writing a new driver for the FreeBSD kernel called vt(4), which is basically a replacement of syscons. There is still a lot of work that needs to be done but it is probably useful to mention what it does (and what does not). Right now there are just two graphics drivers for vt(4), namely a VGA driver for i386 and amd64 and a Microsoft Xbox graphics driver (because it was so easy to implement). I still have to figure out what I am going to do with VESA, because maybe it is better to just ignore VESA and figure out how hard it is to extend DRM to interact with vt(4). Some random features: it already supports both Unicode (UTF-8) input and output, it is MPSAFE and supports per-window graphical fonts of variable dimensions, containing an almost infinite amount of glyphs (both bold and regular). Open tasks: 1. Research needs to be done on DRM's codebase. 2. Syscons should already be migrated to TERM=xterm to make switching between drivers a bit easier. __________________________________________________________________ Valgrind suite on FreeBSD URL: http://wiki.freebsd.org/Valgrind Contact: Stanislav Sedov The Valgrind suite in the FreeBSD ports collection has been updated to version 3.5.0 (the latest available version). Most of the issues of the previous version should be resolved now: we expect memcheck, callgrind and cachegrind to be fully functional on both i386 and amd64 platforms as well as for i386 binaries running on amd64 system. DRD/hellgrind should work too, though they generate a lot of false-positives for now, so their output is a bit messy. Open tasks: 1. Port exp-ptrcheck valgrind tool and fix outstanding issues that show up in memcheck/helgrind/DRD in the Valgrind regression tests suite. 2. More testing (please, help). 3. Integrate our patches upstream. __________________________________________________________________ VirtualBox on FreeBSD URL: http://wiki.freebsd.org/VirtualBox Contact: Beat Gaetzi Contact: Bernhard Froehlich Contact: Dennis Herrmann Contact: Juergen Lock Contact: Martin Wilke VirtualBox has been committed to the Ports tree and synchronized with the latest trunk version from Sun. Several known problems are already fixed and some new features have been added: * VT-x support * Bridging support (Big Thanks to Fredrik Lindberg) * Host Serial Support * ACPI Support * Host DVD/CD access * SMP Support We would like to say thanks to all the people who helped us by reporting bugs and submitting fixes. We also thank the VirtualBox developers for their help with the ongoing effort to port VirtualBox on FreeBSD. From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 18:32:46 2009 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 80A5E10656A8 for ; Sun, 11 Oct 2009 18:32:46 +0000 (UTC) (envelope-from andy@neu.net) Received: from neu.net (neu.net [199.237.202.236]) by mx1.freebsd.org (Postfix) with ESMTP id 364E28FC19 for ; Sun, 11 Oct 2009 18:32:46 +0000 (UTC) Received: from neu.net (neu.net [199.237.202.236]) by neu.net (8.13.6.20060614/8.13.6) with ESMTP id n9BIWhHI084966 for ; Sun, 11 Oct 2009 18:32:45 GMT Date: Sun, 11 Oct 2009 18:32:43 +0000 (GMT) From: AN To: freebsd-current@freebsd.org Message-ID: User-Agent: Alpine 1.10 (BSF 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Virus-Scanned: clamav-milter 0.95.1 at neu.net X-Virus-Status: Clean Subject: ELF interpreter /libexec/ld-elf.so.1 not found 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, 11 Oct 2009 18:32:46 -0000 On a recently installed 8.0RC1 system I am getting this when trying to start the cups printing daemon: # cupsd ELF interpreter /libexec/ld-elf.so.1 not found Abort trap: 6 A listing of the directory shows the following: ls -l /libexec/ total 544 -r-xr-xr-x 1 root wheel 249544 Oct 10 07:14 ld-elf.so.1 It also happened when I tried to start firefox35 that was installed as a package. After deleting the package and installing from ports, firefox now works. I tried to install cups from ports, but I still have the problem. Any help is appreciated. TIA From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 19:14:23 2009 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 0D6A8106566B for ; Sun, 11 Oct 2009 19:14:23 +0000 (UTC) (envelope-from onemda@gmail.com) Received: from ey-out-2122.google.com (ey-out-2122.google.com [74.125.78.25]) by mx1.freebsd.org (Postfix) with ESMTP id 977EA8FC18 for ; Sun, 11 Oct 2009 19:14:22 +0000 (UTC) Received: by ey-out-2122.google.com with SMTP id 4so1943057eyf.9 for ; Sun, 11 Oct 2009 12:14:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=Dz5TNn4F19425P4GxkGvy0VpoWBdpqtcV8SH4dIlaXE=; b=tz1//9C7VXBdqzPYgOqrHFZIsSAgP2QFKNoeMY9Kf3anSmzIZmPFJWsI2mbitT2eRd XPma1lWWPFCHdjqE270rUvSDs9lWhhOg/BkZOSwM7d22rNYq3IqERrknU+jJB2CF2oML P3x7+xlOLCSZ/5Z/fqT+hC5KSl5Sgya52N5W8= 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=vCgDPxp85aAZNWTaYJCRNov6pbqPF8sh+X7Zxm3TWSY3Es8AmQkS/jiNnfZN4urlV1 4cU+75VsbUZ0rhXARt4ufuOl0k0WTpdC1kD9Ds/FV3hXq75CvH43ZPFyq35syxIZ9zGZ nP+CRndTdASa+5Jo688pMb6LHkxrNkvAQhdFM= MIME-Version: 1.0 Received: by 10.211.159.19 with SMTP id l19mr6040045ebo.83.1255288461563; Sun, 11 Oct 2009 12:14:21 -0700 (PDT) In-Reply-To: <20091011062419.GA2168@current.Sisis.de> References: <20091011062419.GA2168@current.Sisis.de> Date: Sun, 11 Oct 2009 19:14:21 +0000 Message-ID: <3a142e750910111214rb75f185k12b2cc7e1aba59d9@mail.gmail.com> From: Paul B Mahol To: Matthias Apitz Content-Type: text/plain; charset=ISO-8859-1 Cc: kde-freebsd@kde.org, freebsd-current@freebsd.org Subject: Re: 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV 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, 11 Oct 2009 19:14:23 -0000 On 10/11/09, Matthias Apitz wrote: > > Hello, > > I've compiled 9-CURRENT from SVN (r197801) and CVS'uped /usr/ports at > the same day (October, 6) to compile KDE and a lot of other stuff. > > The artsd of KDE reproduceable crashes on 'test sound' with: > > $ gdb /usr/local/bin/artsd 2650 > ... > (gdb) c > Continuing. > > Program received signal SIGSEGV, Segmentation fault. > 0x28144166 in Arts::PlayObject_base::_create () from > /usr/local/lib/libkmedia2_idl.so.1 > (gdb) bt > #0 0x28144166 in Arts::PlayObject_base::_create () from > /usr/local/lib/libkmedia2_idl.so.1 > #1 0x08063bd1 in Arts::SimpleSoundServer_impl::createPlayObject () > #2 0x08061288 in Arts::SimpleSoundServer_impl::play () > #3 0x280f7103 in _dispatch_Arts_SimpleSoundServer_00 () from > /usr/local/lib/libsoundserver_idl.so.1 > #4 0x28579df6 in Arts::Object_skel::_dispatch () from > /usr/local/lib/libmcop.so.1 > #5 0x2856fae8 in Arts::Dispatcher::handle () from > /usr/local/lib/libmcop.so.1 > #6 0x2853e371 in Arts::Connection::receive () from > /usr/local/lib/libmcop.so.1 > #7 0x2857d4fe in Arts::SocketConnection::notifyIO () from > /usr/local/lib/libmcop.so.1 > #8 0x2857281f in Arts::StdIOManager::processOneEvent () from > /usr/local/lib/libmcop.so.1 > #9 0x28571e70 in Arts::StdIOManager::run () from > /usr/local/lib/libmcop.so.1 > #10 0x28568447 in Arts::Dispatcher::run () from /usr/local/lib/libmcop.so.1 > #11 0x0806a307 in main () > > Other applications, for example mplayer, play sound fine. The sound > driver is snd_ich.ko. > > Any ideas what to do? Make sure that all libraries and binarys are rebuild, thare may be ABI changes and not support for older code .... From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 19:40:20 2009 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 7F4B0106566B; Sun, 11 Oct 2009 19:40:20 +0000 (UTC) (envelope-from inpcb.harsha@gmail.com) Received: from mail-pz0-f104.google.com (mail-pz0-f104.google.com [209.85.222.104]) by mx1.freebsd.org (Postfix) with ESMTP id 544F88FC15; Sun, 11 Oct 2009 19:40:20 +0000 (UTC) Received: by pzk2 with SMTP id 2so38269pzk.27 for ; Sun, 11 Oct 2009 12:40:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=/RxWVwFUS5owVd6Ri/CahM5jQC4e/TygkwtAoUYCTao=; b=p72suf6ilsuy079BhTbe053MNHk6wLwXav5det3prOxxt6cS5vYTpwRA12vHSfJbuB mRp4TxqFIjsXGgYG3eVXu6MyufnXm+tpH409449odE/sM7hhfj1vxXBKmPdMnG0AMVU9 kvW9aQPbuNDh7Kl/9+yIkQ1u+wXeB9Lmq4SDE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=uW9vyJ4nMyUbaWixyxCSF4R+Dr7JwMQGmzU3zhAU1rC/zVUn2PKrqop3E1hXTVwGAJ Bhxy99PQv1vwBGi45fdiq3vtsnSTfATjmphFbr8s4E5kW6aqFW7gbrVDNL7iULLl5LlY BXYaoEGPwWV4cDEY+hqpRNJfXfW9H7Dt8kiIU= MIME-Version: 1.0 Received: by 10.141.1.12 with SMTP id d12mr336935rvi.268.1255289192721; Sun, 11 Oct 2009 12:26:32 -0700 (PDT) Date: Sun, 11 Oct 2009 12:26:31 -0700 Message-ID: From: Harsha Srinath To: net@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c] 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, 11 Oct 2009 19:40:20 -0000 Hi all, I'm running an updated HEAD kernel and got a page fault in ifindex_alloc_locked() in if.c. I figured that the problem was caused by the (pluggable) network card of my laptop and found that during the initialization of the interface, cb_event_thread() takes the giant lock and up the call chain in if_alloc(), we call IFNET_WLOCK() and assert on the RW locks in ifindex_alloc_locked(). It is in the asset macro IFNET_WLOCK_ASSERT() I see the page fault. I looked up some recent related changes and noticed the following comment in one of the check-ins in- http://svn.freebsd.org/viewvc/base/head/sys/net/if.c "Break out allocation of new ifindex values from if_alloc() and if_vmove(), and centralize in a single function ifindex_alloc(). Assert the IFNET_WLOCK, and add missing IFNET_WLOCK in if_alloc(). This does not close all known races in this code." So I think I have hit one of those fault conditions. Apparently the giant lock code was removed and added back recently - http://svn.freebsd.org/viewvc/base/head/sys/dev/pccbb/pccbb.c I believe that the root cause is that ifnet_rw is a non sleepable exclusive RW lock and we have taken the exclusive sleep mutex Giant before that. Any pointers and suggestions are welcome. Many thanks, Harsha From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 20:30:58 2009 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 49B0E1065672; Sun, 11 Oct 2009 20:30:58 +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 246F68FC0A; Sun, 11 Oct 2009 20:30:58 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id C582546B09; Sun, 11 Oct 2009 16:30:57 -0400 (EDT) Date: Sun, 11 Oct 2009 21:30:57 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Harsha Srinath In-Reply-To: Message-ID: References: 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@freebsd.org, net@freebsd.org Subject: Re: Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c] 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, 11 Oct 2009 20:30:58 -0000 On Sun, 11 Oct 2009, Harsha Srinath wrote: > I'm running an updated HEAD kernel and got a page fault in > ifindex_alloc_locked() in if.c. I figured that the problem was caused by the > (pluggable) network card of my laptop and found that during the > initialization of the interface, cb_event_thread() takes the giant lock and > up the call chain in if_alloc(), we call IFNET_WLOCK() and assert on the RW > locks in ifindex_alloc_locked(). It is in the asset macro > IFNET_WLOCK_ASSERT() I see the page fault. > > I looked up some recent related changes and noticed the following comment in > one of the check-ins in- > http://svn.freebsd.org/viewvc/base/head/sys/net/if.c > > "Break out allocation of new ifindex values from if_alloc() and if_vmove(), > and centralize in a single function ifindex_alloc(). Assert the IFNET_WLOCK, > and add missing IFNET_WLOCK in if_alloc(). This does not close all known > races in this code." > > So I think I have hit one of those fault conditions. > > Apparently the giant lock code was removed and added back recently - > http://svn.freebsd.org/viewvc/base/head/sys/dev/pccbb/pccbb.c > > I believe that the root cause is that ifnet_rw is a non sleepable exclusive > RW lock and we have taken the exclusive sleep mutex Giant before that. > > Any pointers and suggestions are welcome. Hi Harsha-- Giant is a bit special in that the long-term sleep code in the kernel knows to drop it when sleeping, and re-acquire when waking up. So, unlike all other mutexes, it should be OK to hold it in this case, as Giant will simply get dropped if the kernel has to sleep waiting on a sleepable lock. This is because, historically in FreeBSD 3.x/4.x, the kernel was protected by a single spinlock, which would get released whenever the kernel stopped executing, such as during an I/O sleep. On the whole, Giant has disappeared from the modern kernel, but where it is used, it retains those curious historic properties. To break things down a bit further, IFNET_WLOCK is, itself, a bit special: notice that in FreeBSD 8, it's actually two locks, a sleep lock, and a mutex, which must both be acquired exclusively to ensure mutual exclusion. if_alloc() and associated calls are also sleepable because they perform potentially sleeping memory allocation (M_WAITOK), so it's an invariant of any code calling interface allocation that it must be able to tolerate a sleep. Do you have a copy of the stack trace and fault information handy? In my experience, a NULL pointer deref or other page fault in the locking code for a global lock is almost always corrupted thread state, perhaps due to tripping over another thread having locked a corrupted/freed/uninitialized lock. We might be able to track that down by tracing other threads that were in execution at the time of the panic. Robert From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 21:05:31 2009 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 672BD106568F for ; Sun, 11 Oct 2009 21:05:31 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw0.york.ac.uk (mail-gw0.york.ac.uk [144.32.128.245]) by mx1.freebsd.org (Postfix) with ESMTP id F38418FC13 for ; Sun, 11 Oct 2009 21:05:30 +0000 (UTC) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw0.york.ac.uk (8.13.6/8.13.6) with ESMTP id n9BL5RNv029146; Sun, 11 Oct 2009 22:05:27 +0100 (BST) Received: from ury.york.ac.uk ([144.32.108.81]) by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1Mx5bb-0004QS-HV; Sun, 11 Oct 2009 22:05:27 +0100 Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.14.3/8.14.3) with ESMTP id n9BL5RSG010586; Sun, 11 Oct 2009 22:05:27 +0100 (BST) (envelope-from gavin@FreeBSD.org) Received: from localhost (gavin@localhost) by ury.york.ac.uk (8.14.3/8.14.3/Submit) with ESMTP id n9BL5RaK010583; Sun, 11 Oct 2009 22:05:27 +0100 (BST) (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Sun, 11 Oct 2009 22:05:27 +0100 (BST) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: AN In-Reply-To: Message-ID: <20091011220341.U7003@ury.york.ac.uk> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: freebsd-current@FreeBSD.org Subject: Re: ELF interpreter /libexec/ld-elf.so.1 not found 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, 11 Oct 2009 21:05:31 -0000 On Sun, 11 Oct 2009, AN wrote: > On a recently installed 8.0RC1 system I am getting this when trying to start > the cups printing daemon: > > # cupsd > ELF interpreter /libexec/ld-elf.so.1 not found > Abort trap: 6 > > A listing of the directory shows the following: > ls -l /libexec/ > total 544 > -r-xr-xr-x 1 root wheel 249544 Oct 10 07:14 ld-elf.so.1 I'm assuming there are a lot more files than this in there? Can you show the following output: uname -a file `which cupsd` file /libexec/ld-elf.so.1 ldd `which cupsd` Is it possible you've somehow installed amd64 packages on an i386 system? Gavin From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 21:09:47 2009 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 E5D6B1065679 for ; Sun, 11 Oct 2009 21:09:46 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com [209.85.220.222]) by mx1.freebsd.org (Postfix) with ESMTP id 79DC18FC1D for ; Sun, 11 Oct 2009 21:09:46 +0000 (UTC) Received: by fxm22 with SMTP id 22so7748260fxm.36 for ; Sun, 11 Oct 2009 14:09:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=aBspTNElDTqkTAC3jisKaXq9QSJfxJtdk9/3/Z0vOgQ=; b=qUQq/lN9j2nVFh2GRWZ4K4HxCWnG+Fe1WScfawWvDCENu8XrFmD8eyEg533u8BRAA5 +ydr3RlFWnrAq9YYJvyZyB7MKECv4mShJTZUpr244nyKZp2HpGhWP3AG+RnMf1sEB4BH PBDBcMQyGJRF5nlFoewFtsL+GwVgdCKzMrLzo= 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=mefGvU9l8VNFMMlkX/EN0VhoHzCnG7FBkc1LeYJapatHbcGVhI8M66C9OjYJ1MS0AJ flzOT7oYf0PlPcityitat+yut37O6C/gIe3JnBAPvUdyJPDLxFfRjlIJcoEtcJosu2d9 GAbbmR34lCr5h+dxBE0u8vG5ncdF+pg4PWvU8= MIME-Version: 1.0 Received: by 10.239.168.200 with SMTP id l8mr307834hbe.83.1255295385362; Sun, 11 Oct 2009 14:09:45 -0700 (PDT) In-Reply-To: References: Date: Sun, 11 Oct 2009 18:09:45 -0300 Message-ID: <19e9a5dc0910111409l6e9b80a3rafaca3abe6d63e32@mail.gmail.com> From: Gonzalo Nemmi To: Robert Watson Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org Subject: Re: FYI: "8.0TODO" wiki page updated 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, 11 Oct 2009 21:09:47 -0000 On Sun, Oct 11, 2009 at 9:34 AM, Robert Watson wrote: > > FYI for those tracking the 8.0 release: after a haitus of about a month > around the FreeBSD Developer Summit and EuroBSDCon 2009 here in Cambridge, > and with the help of Colin Percival, the 8.0TODO wiki page is now > up-to-date: > > http://wiki.FreeBSD.org/8.0TODO > > We'll endeavour to keep it more up-to-date going forward; there's nothing > like hosting a conference to get you behind on e-mail :-). > > Robert N M Watson > Computer Laboratory > University of Cambridge > Hello Mr. Watson! I just took a look at the recently anounced updated TODO lists for 8.0 ( http://wiki.freebsd.org/8.0TODO) but couldn't find a anything about PR kern/136876: [bge] bge will not resume properly after suspend. Does that mean that 8.0 will be released without a fix for kern/136876? Thanks in advanced Gonzalo Nemmi From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 22:59:54 2009 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 226111065670 for ; Sun, 11 Oct 2009 22:59:54 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.freebsd.org (Postfix) with ESMTP id ED6628FC08 for ; Sun, 11 Oct 2009 22:59:53 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lerami; d=lerctr.org; h=Received:Received:Message-ID:Date:Subject:From:To:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance:X-Spam-Score:X-LERCTR-Spam-Score:X-Spam-Report:X-LERCTR-Spam-Report:DomainKey-Status; b=XFsmKTZwEi0DDl3hENGKNGKFlF1RN5QD0DUh7rX6qRMChz5EjzNRHhXLpMZzWG98HgxDd05SYI149qrDuWlDjeyAgk4nv8U6ozGvYgY/fTYAGnglVDSserZa/lz4fpMGzWq42DfVP1RCdQiOTxbJkRowbUHO1AlmSGEzjevVjJU=; Received: from localhost.lerctr.org ([127.0.0.1]:52065 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mx7OK-0007oU-0t for freebsd-current@freebsd.org; Sun, 11 Oct 2009 17:59:53 -0500 Received: from 76.205.169.61 (SquirrelMail authenticated user ler) by webmail.lerctr.org with HTTP; Sun, 11 Oct 2009 17:59:52 -0500 Message-ID: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> Date: Sun, 11 Oct 2009 17:59:52 -0500 From: "Larry Rosenman" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.20-RC2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 X-LERCTR-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 DomainKey-Status: no signature Subject: Scheduler weirdness 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, 11 Oct 2009 22:59:54 -0000 Ok, running RELENG_8 from Friday (10/9/2009). If I have 4 Folding-at-home processes running (they nice themselves) the system is slow as a dog. If I stop them, it's speedy. This is running SCHED_ULE is this expected? What can I do to help? These are Linux binaries. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 23:11:17 2009 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 414DA1065672 for ; Sun, 11 Oct 2009 23:11:17 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com [209.85.220.222]) by mx1.freebsd.org (Postfix) with ESMTP id C994E8FC1C for ; Sun, 11 Oct 2009 23:11:16 +0000 (UTC) Received: by fxm22 with SMTP id 22so7785849fxm.36 for ; Sun, 11 Oct 2009 16:11:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=PH2OXdkW2xM+UsQa5w2ry3ECewMPYm3lyJN1wYruvWg=; b=R+gAZKM+hLPAL3coGBXNd+MZdfP8Db0oTIRMUlzsVipS0X33VjslHKV2F4gQKI+g3h LcINLzSR8pOtjrm1wcBilm+kSSajjDs/1k7B7KU8NZ8Di/hal8QwYKooeL/Q1O+O70vM vEU4Zw5ErRz7oAe33KwQCFaXlO+SW/pNmituQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=E5ijRv7jCXfib95OsaDLRiNBst9+ags3j7Ismow1Phk9rMWz+b7zj2urNLW7ezdsox AxXFlafwiXX3qqgvt+6Y6BC3ImhKSRdWVPngNfPobp6bfVvHqdb2a7v2Cull+OYtPwgw u9C2s5ihiuKBbJsen9ucUFMd6GzcF+68Mwah8= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.223.97.155 with SMTP id l27mr1366166fan.91.1255302675788; Sun, 11 Oct 2009 16:11:15 -0700 (PDT) In-Reply-To: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> Date: Mon, 12 Oct 2009 01:11:15 +0200 X-Google-Sender-Auth: 6c19d39e34a4bcd5 Message-ID: <3bbf2fe10910111611p2f48d89cpa80350980f4f03e4@mail.gmail.com> From: Attilio Rao To: Larry Rosenman Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org Subject: Re: Scheduler weirdness 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, 11 Oct 2009 23:11:17 -0000 2009/10/12 Larry Rosenman : > > Ok, running RELENG_8 from Friday (10/9/2009). > > If I have 4 Folding-at-home processes running (they nice themselves) the > system is slow as a dog. > > If I stop them, it's speedy. > > This is running SCHED_ULE > > is this expected? > > What can I do to help? Can you please produce the schedgraph output for this workload? Do you know how to setup it? Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 23:13:53 2009 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 2D2E7106566B for ; Sun, 11 Oct 2009 23:13:53 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.freebsd.org (Postfix) with ESMTP id 004BF8FC1C for ; Sun, 11 Oct 2009 23:13:52 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lerami; d=lerctr.org; h=Received:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance:X-Spam-Score:X-LERCTR-Spam-Score:X-Spam-Report:X-LERCTR-Spam-Report:DomainKey-Status; b=DK5KarXRCoQFmTXAmZNFUzmhVz171QnEQElbRG5/sleDXt8lDeaTRpJDKg0YOHSEvPAjlbJmXGGGiUqddmtMFRzhwUtdYBS1YAaafTHtMDdeA8l8g53p8T/4ZKMggzBSbdAPUlvvlGivxmVwL0EXVpiZDG3hVgZqTRprmdlt4HA=; Received: from localhost.lerctr.org ([127.0.0.1]:64405 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mx7br-0007wk-4v; Sun, 11 Oct 2009 18:13:52 -0500 Received: from 76.205.169.61 (SquirrelMail authenticated user ler) by webmail.lerctr.org with HTTP; Sun, 11 Oct 2009 18:13:51 -0500 Message-ID: <100658409950385d656fb5d8030af744.squirrel@webmail.lerctr.org> In-Reply-To: <3bbf2fe10910111611p2f48d89cpa80350980f4f03e4@mail.gmail.com> References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> <3bbf2fe10910111611p2f48d89cpa80350980f4f03e4@mail.gmail.com> Date: Sun, 11 Oct 2009 18:13:51 -0500 From: "Larry Rosenman" To: "Attilio Rao" User-Agent: SquirrelMail/1.4.20-RC2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 X-LERCTR-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 DomainKey-Status: no signature Cc: freebsd-current@freebsd.org Subject: Re: Scheduler weirdness 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, 11 Oct 2009 23:13:53 -0000 On Sun, October 11, 2009 6:11 pm, Attilio Rao wrote: > 2009/10/12 Larry Rosenman : >> >> Ok, running RELENG_8 from Friday (10/9/2009). >> >> If I have 4 Folding-at-home processes running (they nice themselves) the >> system is slow as a dog. >> >> If I stop them, it's speedy. >> >> This is running SCHED_ULE >> >> is this expected? >> >> What can I do to help? > > Can you please produce the schedgraph output for this workload? > Do you know how to setup it? I'm not familiar with this. What do I need to do? > > Attilio > > > -- > Peace can only be achieved by understanding - A. Einstein > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 23:20:50 2009 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 A35FA106568F for ; Sun, 11 Oct 2009 23:20:50 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-bw0-f223.google.com (mail-bw0-f223.google.com [209.85.218.223]) by mx1.freebsd.org (Postfix) with ESMTP id 2D4FB8FC18 for ; Sun, 11 Oct 2009 23:20:49 +0000 (UTC) Received: by bwz23 with SMTP id 23so1636763bwz.43 for ; Sun, 11 Oct 2009 16:20:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=1rwIL9TDV6vDI4xzHwR0BZF105003jMqDjH2vA5GML0=; b=mQVVEKQgfcgOX3cIgxn2+tw/5tPv91VQQ9a4HeDAfhiZyO7EVuXkuSN4cXQR6jkx2u tkSriXOR7aTzPy+E/gE3OQfoimEAUy1dPPVvBjcJnoVqtWbFAc5lFL8W/yLuG203YPb3 RmLZ+unL7MFmTtQSaq0u5EdK9fjfeXkwGWkaU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=o5IoJ5zysev2WwCjSbpnGLOcPp9OBt28mM95UDnNsXe7/E+eFODTYKS6D67VjgjQ3x U8NY88Pco7dJNvjVIIS2iTjX62XUjZg7QC2iW9vky6ZkZSF259WGLdwaBHAQNN/2uFyc pSElkAO1GE5N7O8RMHKu19G7lonF0G+LYrTrI= MIME-Version: 1.0 Sender: asmrookie@gmail.com Received: by 10.223.97.155 with SMTP id l27mr1367281fan.91.1255303248884; Sun, 11 Oct 2009 16:20:48 -0700 (PDT) In-Reply-To: <100658409950385d656fb5d8030af744.squirrel@webmail.lerctr.org> References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> <3bbf2fe10910111611p2f48d89cpa80350980f4f03e4@mail.gmail.com> <100658409950385d656fb5d8030af744.squirrel@webmail.lerctr.org> Date: Mon, 12 Oct 2009 01:20:48 +0200 X-Google-Sender-Auth: e0d85796f3383cc5 Message-ID: <3bbf2fe10910111620p3aa5d4cbgb5db2659d8477142@mail.gmail.com> From: Attilio Rao To: Larry Rosenman Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org Subject: Re: Scheduler weirdness 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, 11 Oct 2009 23:20:50 -0000 2009/10/12 Larry Rosenman : > > On Sun, October 11, 2009 6:11 pm, Attilio Rao wrote: >> 2009/10/12 Larry Rosenman : >>> >>> Ok, running RELENG_8 from Friday (10/9/2009). >>> >>> If I have 4 Folding-at-home processes running (they nice themselves) the >>> system is slow as a dog. >>> >>> If I stop them, it's speedy. >>> >>> This is running SCHED_ULE >>> >>> is this expected? >>> >>> What can I do to help? >> >> Can you please produce the schedgraph output for this workload? >> Do you know how to setup it? > > I'm not familiar with this. What do I need to do? - Recompile your kernel with the following options: KTR KTR_COMPILE=(KTR_SCHED) KTR_MASK=(KTR_SCHED) KTR_ENTRIES=262144 - Run the buggy workload - When the slowness has been experienced a bit (a reasonable timeframe is within 10/20 secs) do: sysctl debug.ktr.mask=0 - do: ktrdump -ct > ktr.out - send here this file along with the number and frequency of your CPUs Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Sun Oct 11 23:38:27 2009 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 1AA0B106568B for ; Sun, 11 Oct 2009 23:38:27 +0000 (UTC) (envelope-from ehrmann@gmail.com) Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by mx1.freebsd.org (Postfix) with ESMTP id E3A588FC23 for ; Sun, 11 Oct 2009 23:38:26 +0000 (UTC) Received: from [10.0.0.171] (unknown [64.9.236.71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 05A8622DD6D; Sun, 11 Oct 2009 19:38:24 -0400 (EDT) Message-ID: <4AD26C69.4040202@gmail.com> Date: Sun, 11 Oct 2009 16:38:17 -0700 From: David Ehrmann User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Gavin Atkinson References: <4AD0E286.9030508@gmail.com> <20091011133411.A80896@ury.york.ac.uk> In-Reply-To: <20091011133411.A80896@ury.york.ac.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: daichi@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: Strange md/unionfs issue 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, 11 Oct 2009 23:38:27 -0000 Gavin Atkinson wrote: > > On Sat, 10 Oct 2009, David Ehrmann wrote: > >> I have a system running on a flash disk. To prevent it from wearing >> out quickly, I don't run with a swap and mount /tmp and /var from >> memory. Because /var needs some directories and contains files I >> probably should save from time to time, I mount it from flash, mount >> /var to /var_real so I can access the underlying files, and then I >> mount an md device on top of /var as a unionfs. Initially, it seems >> to work, but seconds later, the unionfs seems to fail. > > When the mount "fails", is it still shown in the output of mount(1)? The output of mount is the same; it reports that a md-backed unionfs is on top of /var. > > It appears that this problem is the same as is reported in PR > kern/131441, which has so far not had any activity. It appears that > this bug has existed since at least 7.1-RELEASE. It does seem to be the same bug (or similar). With mine, I mounted a unionfs on top of a mount point that a nullfs was based on, not the nullfs's mount point. I think the bug in kern/131441 was with a unionfs over a nullfs. This probably means md's off the hook as the culprit, and the same thing would happen with ufs on /dev/foo. From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 01:43:30 2009 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 9E8A4106566B for ; Mon, 12 Oct 2009 01:43:30 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.freebsd.org (Postfix) with ESMTP id 6EE598FC0C for ; Mon, 12 Oct 2009 01:43:30 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lerami; d=lerctr.org; h=Received:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance:X-Spam-Score:X-LERCTR-Spam-Score:X-Spam-Report:X-LERCTR-Spam-Report:DomainKey-Status; b=IFsxwHqBBwz6HgBvE4qDgzzMwBPEc5ak3hE8MrUnsRoC4tuDU6OgZM9vZKt1sDwPUvxQjFTZGuzkmAHnP1MVz20dtY95HEhqdOwL8k7UjW4RmGRFcUeMARe3SOkBSbq+pEMrFneEwxWncXAFlYgWSB3VXJQVR8qWVhL2xwuedvM=; Received: from localhost.lerctr.org ([127.0.0.1]:53091 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mx9we-0009Oh-D6 for freebsd-current@freebsd.org; Sun, 11 Oct 2009 20:43:30 -0500 Received: from 76.205.169.61 (SquirrelMail authenticated user ler) by webmail.lerctr.org with HTTP; Sun, 11 Oct 2009 20:43:28 -0500 Message-ID: <6495ee63c0e2b33aded5d63decbaff02.squirrel@webmail.lerctr.org> In-Reply-To: <3bbf2fe10910111620p3aa5d4cbgb5db2659d8477142@mail.gmail.com> References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> <3bbf2fe10910111611p2f48d89cpa80350980f4f03e4@mail.gmail.com> <100658409950385d656fb5d8030af744.squirrel@webmail.lerctr.org> <3bbf2fe10910111620p3aa5d4cbgb5db2659d8477142@mail.gmail.com> Date: Sun, 11 Oct 2009 20:43:28 -0500 From: "Larry Rosenman" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.20-RC2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 X-LERCTR-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 DomainKey-Status: no signature Subject: Re: Scheduler weirdness 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, 12 Oct 2009 01:43:30 -0000 On Sun, October 11, 2009 6:20 pm, Attilio Rao wrote: > 2009/10/12 Larry Rosenman : >> >> On Sun, October 11, 2009 6:11 pm, Attilio Rao wrote: >>> 2009/10/12 Larry Rosenman : >>>> >>>> Ok, running RELENG_8 from Friday (10/9/2009). >>>> >>>> If I have 4 Folding-at-home processes running (they nice themselves) >>>> the >>>> system is slow as a dog. >>>> >>>> If I stop them, it's speedy. >>>> >>>> This is running SCHED_ULE >>>> >>>> is this expected? >>>> >>>> What can I do to help? >>> >>> Can you please produce the schedgraph output for this workload? >>> Do you know how to setup it? >> >> I'm not familiar with this. What do I need to do? > > - Recompile your kernel with the following options: > KTR > KTR_COMPILE=(KTR_SCHED) > KTR_MASK=(KTR_SCHED) > KTR_ENTRIES=262144 > > - Run the buggy workload > - When the slowness has been experienced a bit (a reasonable timeframe > is within 10/20 secs) do: sysctl debug.ktr.mask=0 > - do: ktrdump -ct > ktr.out > - send here this file along with the number and frequency of your CPUs Sent under separate cover direct to Attilio. Thanks, Attilio! > > Thanks, > Attilio > > > -- > Peace can only be achieved by understanding - A. Einstein > _______________________________________________ > 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" > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 01:48:48 2009 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 ADC07106568B for ; Mon, 12 Oct 2009 01:48:48 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 94EFD8FC1E for ; Mon, 12 Oct 2009 01:48:48 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.3/8.14.3) with ESMTP id n9C1mkrO038533; Sun, 11 Oct 2009 18:48:46 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.3/8.14.3/Submit) id n9C1mkg7038532; Sun, 11 Oct 2009 18:48:46 -0700 (PDT) (envelope-from sgk) Date: Sun, 11 Oct 2009 18:48:46 -0700 From: Steve Kargl To: Larry Rosenman Message-ID: <20091012014846.GB38325@troutmask.apl.washington.edu> References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Scheduler weirdness 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, 12 Oct 2009 01:48:48 -0000 On Sun, Oct 11, 2009 at 05:59:52PM -0500, Larry Rosenman wrote: > > Ok, running RELENG_8 from Friday (10/9/2009). > > If I have 4 Folding-at-home processes running (they nice themselves) the > system is slow as a dog. > > If I stop them, it's speedy. > > This is running SCHED_ULE > > is this expected? > > What can I do to help? > How many cpus are available on your system? If you're in an over-commit situation with numerical intensive applications, you may find 4BSD to be a better option. -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 01:51:50 2009 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 32ED5106568D for ; Mon, 12 Oct 2009 01:51:50 +0000 (UTC) (envelope-from ler@lerctr.org) Received: from thebighonker.lerctr.org (thebighonker.lerctr.org [192.147.25.65]) by mx1.freebsd.org (Postfix) with ESMTP id 047BF8FC19 for ; Mon, 12 Oct 2009 01:51:49 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=lerami; d=lerctr.org; h=Received:Received:Message-ID:In-Reply-To:References:Date:Subject:From:To:Cc:User-Agent:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:Importance:X-Spam-Score:X-LERCTR-Spam-Score:X-Spam-Report:X-LERCTR-Spam-Report:DomainKey-Status; b=ZXWwPZC3haHYMYMkVKTzSmJCA4jgcZHTtNDHks+uip9tIHn/3r/0z6WF3hzXVnKpgoAKf0W88+rOzVlZrf4yblCNhMMSkJ48fX5o1jd2+3+BuWnNdbPEOxuerGnwJraazXZZjjqLgAqVcM9hz3C6xuEjukH8odKosd6G2LZ3Sj8=; Received: from localhost.lerctr.org ([127.0.0.1]:55187 helo=webmail.lerctr.org) by thebighonker.lerctr.org with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MxA4i-0009WZ-0q; Sun, 11 Oct 2009 20:51:49 -0500 Received: from 76.205.169.61 (SquirrelMail authenticated user ler) by webmail.lerctr.org with HTTP; Sun, 11 Oct 2009 20:51:48 -0500 Message-ID: In-Reply-To: <20091012014846.GB38325@troutmask.apl.washington.edu> References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> <20091012014846.GB38325@troutmask.apl.washington.edu> Date: Sun, 11 Oct 2009 20:51:48 -0500 From: "Larry Rosenman" To: "Steve Kargl" User-Agent: SquirrelMail/1.4.20-RC2 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Spam-Score: -4.4 (----) X-LERCTR-Spam-Score: -4.4 (----) X-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 X-LERCTR-Spam-Report: SpamScore (-4.4/5.0) ALL_TRUSTED=-1.8,BAYES_00=-2.599 DomainKey-Status: no signature Cc: freebsd-current@freebsd.org Subject: Re: Scheduler weirdness 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, 12 Oct 2009 01:51:50 -0000 On Sun, October 11, 2009 8:48 pm, Steve Kargl wrote: > On Sun, Oct 11, 2009 at 05:59:52PM -0500, Larry Rosenman wrote: >> >> Ok, running RELENG_8 from Friday (10/9/2009). >> >> If I have 4 Folding-at-home processes running (they nice themselves) the >> system is slow as a dog. >> >> If I stop them, it's speedy. >> >> This is running SCHED_ULE >> >> is this expected? >> >> What can I do to help? >> > > How many cpus are available on your system? If you're in an > over-commit situation with numerical intensive applications, > you may find 4BSD to be a better option. 4 cpu's. $ sysctl dev.cpu dev.cpu.0.%desc: ACPI CPU dev.cpu.0.%driver: cpu dev.cpu.0.%location: handle=\_PR_.CPU0 dev.cpu.0.%pnpinfo: _HID=none _UID=0 dev.cpu.0.%parent: acpi0 dev.cpu.0.temperature: 50.0C dev.cpu.0.freq: 1867 dev.cpu.0.freq_levels: 1867/35000 1633/30625 1400/26250 1166/21875 933/17500 700/13125 466/8750 233/4375 dev.cpu.0.cx_supported: C1/1 dev.cpu.0.cx_lowest: C1 dev.cpu.0.cx_usage: 100.00% last 500us dev.cpu.1.%desc: ACPI CPU dev.cpu.1.%driver: cpu dev.cpu.1.%location: handle=\_PR_.CPU1 dev.cpu.1.%pnpinfo: _HID=none _UID=0 dev.cpu.1.%parent: acpi0 dev.cpu.1.temperature: 53.0C dev.cpu.1.cx_supported: C1/1 dev.cpu.1.cx_lowest: C1 dev.cpu.1.cx_usage: 100.00% last 500us dev.cpu.2.%desc: ACPI CPU dev.cpu.2.%driver: cpu dev.cpu.2.%location: handle=\_PR_.CPU2 dev.cpu.2.%pnpinfo: _HID=none _UID=0 dev.cpu.2.%parent: acpi0 dev.cpu.2.temperature: 54.0C dev.cpu.2.cx_supported: C1/1 dev.cpu.2.cx_lowest: C1 dev.cpu.2.cx_usage: 100.00% last 500us dev.cpu.3.%desc: ACPI CPU dev.cpu.3.%driver: cpu dev.cpu.3.%location: handle=\_PR_.CPU3 dev.cpu.3.%pnpinfo: _HID=none _UID=0 dev.cpu.3.%parent: acpi0 dev.cpu.3.temperature: 55.0C dev.cpu.3.cx_supported: C1/1 dev.cpu.3.cx_lowest: C1 dev.cpu.3.cx_usage: 100.00% last 500us $ > > -- > Steve > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: ler@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 02:39:13 2009 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 0550B1065670 for ; Mon, 12 Oct 2009 02:39:13 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id D9CC88FC16 for ; Mon, 12 Oct 2009 02:39:12 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.3/8.14.3) with ESMTP id n9C2dCSL038836; Sun, 11 Oct 2009 19:39:12 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.3/8.14.3/Submit) id n9C2dCnx038835; Sun, 11 Oct 2009 19:39:12 -0700 (PDT) (envelope-from sgk) Date: Sun, 11 Oct 2009 19:39:12 -0700 From: Steve Kargl To: Larry Rosenman Message-ID: <20091012023912.GA38822@troutmask.apl.washington.edu> References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> <20091012014846.GB38325@troutmask.apl.washington.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Scheduler weirdness 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, 12 Oct 2009 02:39:13 -0000 On Sun, Oct 11, 2009 at 08:51:48PM -0500, Larry Rosenman wrote: > > On Sun, October 11, 2009 8:48 pm, Steve Kargl wrote: > > On Sun, Oct 11, 2009 at 05:59:52PM -0500, Larry Rosenman wrote: > >> > >> Ok, running RELENG_8 from Friday (10/9/2009). > >> > >> If I have 4 Folding-at-home processes running (they nice themselves) the > >> system is slow as a dog. > >> > >> If I stop them, it's speedy. > >> > >> This is running SCHED_ULE > >> > >> is this expected? > >> > >> What can I do to help? > >> > > > > How many cpus are available on your system? If you're in an > > over-commit situation with numerical intensive applications, > > you may find 4BSD to be a better option. > 4 cpu's. > So, you have 4 cpus and 4 folding-at-home processes and you're trying to use the system with other apps? Switch to 4BSD. -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 04:06:19 2009 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 8D96F1065672 for ; Mon, 12 Oct 2009 04:06:19 +0000 (UTC) (envelope-from alex@mailinglist.ahhyes.net) Received: from fallbackmx07.syd.optusnet.com.au (fallbackmx07.syd.optusnet.com.au [211.29.132.9]) by mx1.freebsd.org (Postfix) with ESMTP id 0E5B88FC0A for ; Mon, 12 Oct 2009 04:06:18 +0000 (UTC) Received: from mail07.syd.optusnet.com.au (mail07.syd.optusnet.com.au [211.29.132.188]) by fallbackmx07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n9C2nffg013261 for ; Mon, 12 Oct 2009 13:49:41 +1100 Received: from bsddesktop.xor.net (c122-106-77-13.rivrw1.nsw.optusnet.com.au [122.106.77.13]) by mail07.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n9C2nbxG026044 for ; Mon, 12 Oct 2009 13:49:38 +1100 Message-ID: <4AD29937.2040004@mailinglist.ahhyes.net> Date: Mon, 12 Oct 2009 13:49:27 +1100 From: Alex R User-Agent: Thunderbird 2.0.0.23 (X11/20091009) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> <20091012014846.GB38325@troutmask.apl.washington.edu> <20091012023912.GA38822@troutmask.apl.washington.edu> In-Reply-To: <20091012023912.GA38822@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Scheduler weirdness 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, 12 Oct 2009 04:06:19 -0000 Steve Kargl wrote: > So, you have 4 cpus and 4 folding-at-home processes and you're > trying to use the system with other apps? Switch to 4BSD. > > I thought SCHED_ULE was meant to be a much better choice under an SMP environment. Why are you suggesting he rebuild his kernel and use the legacy scheduler? From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 04:33:59 2009 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 4ED49106566B for ; Mon, 12 Oct 2009 04:33:59 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 3268E8FC0A for ; Mon, 12 Oct 2009 04:33:59 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.3/8.14.3) with ESMTP id n9C4XwMf039404; Sun, 11 Oct 2009 21:33:58 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.3/8.14.3/Submit) id n9C4XwE8039403; Sun, 11 Oct 2009 21:33:58 -0700 (PDT) (envelope-from sgk) Date: Sun, 11 Oct 2009 21:33:58 -0700 From: Steve Kargl To: Alex R Message-ID: <20091012043358.GA39364@troutmask.apl.washington.edu> References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> <20091012014846.GB38325@troutmask.apl.washington.edu> <20091012023912.GA38822@troutmask.apl.washington.edu> <4AD29937.2040004@mailinglist.ahhyes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AD29937.2040004@mailinglist.ahhyes.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Scheduler weirdness 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, 12 Oct 2009 04:33:59 -0000 On Mon, Oct 12, 2009 at 01:49:27PM +1100, Alex R wrote: > Steve Kargl wrote: > >So, you have 4 cpus and 4 folding-at-home processes and you're > >trying to use the system with other apps? Switch to 4BSD. > > > > > > I thought SCHED_ULE was meant to be a much better choice under an SMP > environment. Why are you suggesting he rebuild his kernel and use the > legacy scheduler? > If you have N cpus and N+1 numerical intensitive applications, ULE may have poor performance compared to 4BSD. In OP's case, he has 4 cpus and 4 numerical intensity (?) applications. He, however, also is trying to use the system in some interactive way. -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 04:35:29 2009 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 092A31065676 for ; Mon, 12 Oct 2009 04:35:29 +0000 (UTC) (envelope-from alex@mailinglist.ahhyes.net) Received: from mail09.syd.optusnet.com.au (mail09.syd.optusnet.com.au [211.29.132.190]) by mx1.freebsd.org (Postfix) with ESMTP id 7F6BC8FC14 for ; Mon, 12 Oct 2009 04:35:28 +0000 (UTC) Received: from bsddesktop.xor.net (c122-106-77-13.rivrw1.nsw.optusnet.com.au [122.106.77.13]) by mail09.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id n9C4ZPdH020120 for ; Mon, 12 Oct 2009 15:35:26 +1100 Message-ID: <4AD2B203.8030405@mailinglist.ahhyes.net> Date: Mon, 12 Oct 2009 15:35:15 +1100 From: Alex R User-Agent: Thunderbird 2.0.0.23 (X11/20091009) MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> <20091012014846.GB38325@troutmask.apl.washington.edu> <20091012023912.GA38822@troutmask.apl.washington.edu> <4AD29937.2040004@mailinglist.ahhyes.net> <20091012043358.GA39364@troutmask.apl.washington.edu> In-Reply-To: <20091012043358.GA39364@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: Scheduler weirdness 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, 12 Oct 2009 04:35:29 -0000 Steve Kargl wrote: > On Mon, Oct 12, 2009 at 01:49:27PM +1100, Alex R wrote: > >> Steve Kargl wrote: >> >>> So, you have 4 cpus and 4 folding-at-home processes and you're >>> trying to use the system with other apps? Switch to 4BSD. >>> >>> >>> >> I thought SCHED_ULE was meant to be a much better choice under an SMP >> environment. Why are you suggesting he rebuild his kernel and use the >> legacy scheduler? >> >> > > If you have N cpus and N+1 numerical intensitive applications, > ULE may have poor performance compared to 4BSD. In OP's case, > he has 4 cpus and 4 numerical intensity (?) applications. He, > however, also is trying to use the system in some interactive > way. > > Ah ok. Is this just an accepted thing by the freebsd dev's or are they trying to fix it? From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 04:38:34 2009 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 E89B21065670; Mon, 12 Oct 2009 04:38:33 +0000 (UTC) (envelope-from inpcb.harsha@gmail.com) Received: from mail-pz0-f104.google.com (mail-pz0-f104.google.com [209.85.222.104]) by mx1.freebsd.org (Postfix) with ESMTP id B00E58FC19; Mon, 12 Oct 2009 04:38:33 +0000 (UTC) Received: by pzk2 with SMTP id 2so56608pzk.27 for ; Sun, 11 Oct 2009 21:38:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=kg19ioURrVW8nlWRB8B7SDXkqF7azLwDeBAZWHD1rog=; b=AkhPO54KKrJMUDoxXDbWq7eQT8tGIY4wDD7ocCOTOgCLewTIH8W8bFCmcDQj6VcnDZ OmSKfg/c9T2nrWfLud/cBFpXKRFbR9RKmdbpw/6eImAvWC2RNMQqyYzJGmRYnQhLHOMm n1zpBRDLRf+hEuLbA0p99Tgy1DGMJoKZhuCYc= 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=CsesZlrKorw+PjmQVkxD7iXEMT9RU8W8SF0F0ASKAnnvN8flIBvhC8iFqhbFO5EBXl nkv+MhtJVb07zi28Vurv3p8CF4PVai75YzodaUNYl9G1/i3KMd0Z3tPKypAgQpYU8S5a EQ/b3D+Sm/E0lzafSeSyKRnwIa7Vb5+AFmXK0= MIME-Version: 1.0 Received: by 10.141.34.20 with SMTP id m20mr360036rvj.120.1255322313072; Sun, 11 Oct 2009 21:38:33 -0700 (PDT) In-Reply-To: References: Date: Sun, 11 Oct 2009 21:38:33 -0700 Message-ID: From: Harsha To: Robert Watson Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, net@freebsd.org Subject: Re: Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c] 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, 12 Oct 2009 04:38:34 -0000 Hi Robert, On Sun, Oct 11, 2009 at 1:30 PM, Robert Watson wrote: > Giant is a bit special in that the long-term sleep code in the kernel kno= ws > to drop it when sleeping, and re-acquire when waking up. =A0So, unlike al= l > other mutexes, it should be OK to hold it in this case, as Giant will sim= ply > get dropped if the kernel has to sleep waiting on a sleepable lock. =A0Th= is is > because, historically in FreeBSD 3.x/4.x, the kernel was protected by a > single spinlock, which would get released whenever the kernel stopped > executing, such as during an I/O sleep. =A0On the whole, Giant has disapp= eared > from the modern kernel, but where it is used, it retains those curious > historic properties. > > To break things down a bit further, IFNET_WLOCK is, itself, a bit special= : > notice that in FreeBSD 8, it's actually two locks, a sleep lock, and a > mutex, which must both be acquired exclusively to ensure mutual exclusion= . > if_alloc() and associated calls are also sleepable because they perform > potentially sleeping memory allocation (M_WAITOK), so it's an invariant o= f > any code calling interface allocation that it must be able to tolerate a > sleep. Thanks a lot for the clarification. I had assumed that the lock was non-sleepable looking at this log - Kernel page fault with the following non-sleepable locks held: exclusive rw ifnet_rw (ifnet_rw) r =3D 0 (0xc0f63464) locked @ /usr/src/sys/net/if.c:409 > Do you have a copy of the stack trace and fault information handy? =A0In = my > experience, a NULL pointer deref or other page fault in the locking code = for > a global lock is almost always corrupted thread state, perhaps due to > tripping over another thread having locked a corrupted/freed/uninitialize= d > lock. =A0We might be able to track that down by tracing other threads tha= t > were in execution at the time of the panic. I just tried the textdump feature and I think its an awesome tool. Here is ddb.txt- http://docs.google.com/View?id=3Ddddwnxfj_0dh4x58hc And msgbuf.txt- http://docs.google.com/View?id=3Ddddwnxfj_1cnmrb8fw For some reason the output of show alllocks is not written into ddb.txt, though I have increased the buffer size to 2MB. Thanks, Harsha From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 04:42:05 2009 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 053F71065670 for ; Mon, 12 Oct 2009 04:42:05 +0000 (UTC) (envelope-from taku@tackymt.homeip.net) Received: from basalt.tackymt.homeip.net (unknown [IPv6:2001:3e0:577:0:20d:61ff:fecc:2253]) by mx1.freebsd.org (Postfix) with ESMTP id A25F78FC13 for ; Mon, 12 Oct 2009 04:42:04 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by basalt.tackymt.homeip.net (Postfix) with ESMTP id 60C961074E; Mon, 12 Oct 2009 13:42:03 +0900 (JST) X-Virus-Scanned: amavisd-new at tackymt.homeip.net Received: from localhost ([127.0.0.1]) by localhost (basalt.tackymt.homeip.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wtmVkiBfKecn; Mon, 12 Oct 2009 13:42:00 +0900 (JST) Received: from basalt.tackymt.homeip.net (basalt.tackymt.homeip.net [IPv6:2001:3e0:577:0:20d:61ff:fecc:2253]) by basalt.tackymt.homeip.net (Postfix) with ESMTP; Mon, 12 Oct 2009 13:42:00 +0900 (JST) Date: Mon, 12 Oct 2009 13:41:59 +0900 From: Taku YAMAMOTO To: "Larry Rosenman" Message-Id: <20091012134159.8f6e4d66.taku@tackymt.homeip.net> In-Reply-To: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.16.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: Re: Scheduler weirdness 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, 12 Oct 2009 04:42:05 -0000 On Sun, 11 Oct 2009 17:59:52 -0500 "Larry Rosenman" wrote: > > Ok, running RELENG_8 from Friday (10/9/2009). > > If I have 4 Folding-at-home processes running (they nice themselves) the > system is slow as a dog. Ah, I reminded a local patch regarding SCHED_ULE against niced threads. Something like this: --- sys/kern/sched_ule.c.orig 2009-04-29 12:26:30.000000000 +0900 +++ sys/kern/sched_ule.c 2009-04-30 08:13:30.951440396 +0900 @@ -1406,7 +1406,7 @@ sched_priority(struct thread *td) * score. Negative nice values make it easier for a thread to be * considered interactive. */ - score = imax(0, sched_interact_score(td) - td->td_proc->p_nice); + score = imax(0, sched_interact_score(td) + td->td_proc->p_nice); if (score < sched_interact) { pri = PRI_MIN_REALTIME; pri += ((PRI_MAX_REALTIME - PRI_MIN_REALTIME) / sched_interact) > > If I stop them, it's speedy. > > This is running SCHED_ULE > > is this expected? > > What can I do to help? > > These are Linux binaries. -- -|-__ YAMAMOTO, Taku | __ < - A chicken is an egg's way of producing more eggs. - From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 04:49:12 2009 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 3AD741065679 for ; Mon, 12 Oct 2009 04:49:12 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 0D7DB8FC64 for ; Mon, 12 Oct 2009 04:49:12 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.3/8.14.3) with ESMTP id n9C4nBj0039530; Sun, 11 Oct 2009 21:49:11 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.3/8.14.3/Submit) id n9C4nBgs039529; Sun, 11 Oct 2009 21:49:11 -0700 (PDT) (envelope-from sgk) Date: Sun, 11 Oct 2009 21:49:11 -0700 From: Steve Kargl To: Alex R Message-ID: <20091012044911.GA39479@troutmask.apl.washington.edu> References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> <20091012014846.GB38325@troutmask.apl.washington.edu> <20091012023912.GA38822@troutmask.apl.washington.edu> <4AD29937.2040004@mailinglist.ahhyes.net> <20091012043358.GA39364@troutmask.apl.washington.edu> <4AD2B203.8030405@mailinglist.ahhyes.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AD2B203.8030405@mailinglist.ahhyes.net> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: Scheduler weirdness 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, 12 Oct 2009 04:49:12 -0000 On Mon, Oct 12, 2009 at 03:35:15PM +1100, Alex R wrote: > Steve Kargl wrote: > >On Mon, Oct 12, 2009 at 01:49:27PM +1100, Alex R wrote: > > > >>Steve Kargl wrote: > >> > >>>So, you have 4 cpus and 4 folding-at-home processes and you're > >>>trying to use the system with other apps? Switch to 4BSD. > >>> > >>> > >>> > >>I thought SCHED_ULE was meant to be a much better choice under an SMP > >>environment. Why are you suggesting he rebuild his kernel and use the > >>legacy scheduler? > >> > >> > > > >If you have N cpus and N+1 numerical intensitive applications, > >ULE may have poor performance compared to 4BSD. In OP's case, > >he has 4 cpus and 4 numerical intensity (?) applications. He, > >however, also is trying to use the system in some interactive > >way. > > > > > Ah ok. Is this just an accepted thing by the freebsd dev's or are they > trying to fix it? > Jeff appears to be extremely busy with other projects. He is aware of the problem, and I have set up my system to give him access when/if it is so desired. Here's the text of my last set of tests that I sent to him OK, I've manage to recreate the problem. User kargl launches a mpi job on node10 that creates two images on node20. This is command z in the top(1) info. 30 seconds later, user sgk lauches a mpi process on node10 that creates 8 images on node20. This is command rivmp in top(1) info. With 8 available cpus, this is a (slightly) oversubscribed node. For 4BSD, I see last pid: 1432; load averages: 8.68, 5.65, 2.82 up 0+01:52:14 17:07:22 40 processes: 11 running, 29 sleeping CPU: 100% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle Mem: 32M Active, 12M Inact, 203M Wired, 424K Cache, 29M Buf, 31G Free Swap: 4096M Total, 4096M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME CPU COMMAND 1428 sgk 1 124 0 81788K 5848K CPU3 6 1:13 78.81% rivmp 1431 sgk 1 124 0 81788K 5652K RUN 1 1:13 78.52% rivmp 1415 kargl 1 124 0 78780K 4668K CPU7 1 1:38 78.42% z 1414 kargl 1 124 0 78780K 4664K CPU0 0 1:37 77.25% z 1427 sgk 1 124 0 81788K 5852K CPU4 3 1:13 78.42% rivmp 1432 sgk 1 124 0 81788K 5652K CPU2 4 1:13 78.27% rivmp 1425 sgk 1 124 0 81788K 6004K CPU5 5 1:12 78.17% rivmp 1426 sgk 1 124 0 81788K 5832K RUN 6 1:13 78.03% rivmp 1429 sgk 1 124 0 81788K 5788K CPU6 7 1:12 77.98% rivmp 1430 sgk 1 124 0 81788K 5764K RUN 2 1:13 77.93% rivmp Notice, the accumulated times appear reasonable. At this point in the computations, rivmp is doing no communication between processes. z is the netpipe benchmark and is essentially sending messages between the two processes over the memory bus. For ULE, I see last pid: 1169; load averages: 7.56, 2.61, 1.02 up 0+00:03:15 17:13:01 40 processes: 11 running, 29 sleeping CPU: 100% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle Mem: 31M Active, 9392K Inact, 197M Wired, 248K Cache, 26M Buf, 31G Free Swap: 4096M Total, 4096M Free PID USERNAME THR PRI NICE SIZE RES STATE C TIME CPU COMMAND 1168 sgk 1 118 0 81788K 5472K CPU6 6 1:18 100.00% rivmp 1169 sgk 1 118 0 81788K 5416K CPU7 7 1:18 100.00% rivmp 1167 sgk 1 118 0 81788K 5496K CPU5 5 1:18 100.00% rivmp 1166 sgk 1 118 0 81788K 5564K RUN 4 1:18 100.00% rivmp 1151 kargl 1 118 0 78780K 4464K CPU3 3 1:48 99.27% z 1152 kargl 1 110 0 78780K 4464K CPU0 0 1:18 62.89% z 1164 sgk 1 113 0 81788K 5592K CPU1 1 0:55 80.76% rivmp 1165 sgk 1 110 0 81788K 5544K RUN 0 0:52 62.16% rivmp 1163 sgk 1 107 0 81788K 5624K RUN 2 0:40 50.68% rivmp 1162 sgk 1 107 0 81788K 5824K CPU2 2 0:39 50.49% rivmp In the above, processes 1162-1165 are clearly not receiving sufficient time slices to keep up with the other 4 rivmp images. From watching top at a 1 second interval, once the 4 rivmp hit 100% CPU, they stayed pinned to their cpu and stay at 100% CPU. It is also seen that processes 1152, 1165 and 1162, 1163 are stuck on cpus 0 and 2, respectively. -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 07:44:38 2009 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 301381065672; Mon, 12 Oct 2009 07:44:38 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id AABF18FC1C; Mon, 12 Oct 2009 07:44:37 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1MxFa8-0000Wg-DE>; Mon, 12 Oct 2009 09:44:36 +0200 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1MxFa8-0004DV-Bd>; Mon, 12 Oct 2009 09:44:36 +0200 Message-ID: <4AD2DE71.5060601@zedat.fu-berlin.de> Date: Mon, 12 Oct 2009 07:44:49 +0000 From: "O. Hartmann" Organization: Freie =?ISO-8859-15?Q?Universit=E4t_Berlin?= User-Agent: Thunderbird 2.0.0.23 (X11/20090824) MIME-Version: 1.0 To: Steve Kargl References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> <20091012014846.GB38325@troutmask.apl.washington.edu> <20091012023912.GA38822@troutmask.apl.washington.edu> <4AD29937.2040004@mailinglist.ahhyes.net> <20091012043358.GA39364@troutmask.apl.washington.edu> <4AD2B203.8030405@mailinglist.ahhyes.net> <20091012044911.GA39479@troutmask.apl.washington.edu> In-Reply-To: <20091012044911.GA39479@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Cc: "freebsd-performance@freebsd.org" , freebsd-current@freebsd.org Subject: Re: Scheduler weirdness 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, 12 Oct 2009 07:44:38 -0000 Steve Kargl wrote: > On Mon, Oct 12, 2009 at 03:35:15PM +1100, Alex R wrote: >> Steve Kargl wrote: >>> On Mon, Oct 12, 2009 at 01:49:27PM +1100, Alex R wrote: >>> >>>> Steve Kargl wrote: >>>> >>>>> So, you have 4 cpus and 4 folding-at-home processes and you're >>>>> trying to use the system with other apps? Switch to 4BSD. >>>>> >>>>> >>>>> >>>> I thought SCHED_ULE was meant to be a much better choice under an SMP >>>> environment. Why are you suggesting he rebuild his kernel and use the >>>> legacy scheduler? >>>> >>>> >>> If you have N cpus and N+1 numerical intensitive applications, >>> ULE may have poor performance compared to 4BSD. In OP's case, >>> he has 4 cpus and 4 numerical intensity (?) applications. He, >>> however, also is trying to use the system in some interactive >>> way. >>> >>> >> Ah ok. Is this just an accepted thing by the freebsd dev's or are they >> trying to fix it? >> > > Jeff appears to be extremely busy with other projects. He is aware of > the problem, and I have set up my system to give him access when/if it > is so desired. > > Here's the text of my last set of tests that I sent to him > > OK, I've manage to recreate the problem. User kargl launches a mpi > job on node10 that creates two images on node20. This is command z > in the top(1) info. 30 seconds later, user sgk lauches a mpi process > on node10 that creates 8 images on node20. This is command rivmp in > top(1) info. With 8 available cpus, this is a (slightly) oversubscribed > node. > > For 4BSD, I see > > last pid: 1432; load averages: 8.68, 5.65, 2.82 up 0+01:52:14 17:07:22 > 40 processes: 11 running, 29 sleeping > CPU: 100% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle > Mem: 32M Active, 12M Inact, 203M Wired, 424K Cache, 29M Buf, 31G Free > Swap: 4096M Total, 4096M Free > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME CPU COMMAND > 1428 sgk 1 124 0 81788K 5848K CPU3 6 1:13 78.81% rivmp > 1431 sgk 1 124 0 81788K 5652K RUN 1 1:13 78.52% rivmp > 1415 kargl 1 124 0 78780K 4668K CPU7 1 1:38 78.42% z > 1414 kargl 1 124 0 78780K 4664K CPU0 0 1:37 77.25% z > 1427 sgk 1 124 0 81788K 5852K CPU4 3 1:13 78.42% rivmp > 1432 sgk 1 124 0 81788K 5652K CPU2 4 1:13 78.27% rivmp > 1425 sgk 1 124 0 81788K 6004K CPU5 5 1:12 78.17% rivmp > 1426 sgk 1 124 0 81788K 5832K RUN 6 1:13 78.03% rivmp > 1429 sgk 1 124 0 81788K 5788K CPU6 7 1:12 77.98% rivmp > 1430 sgk 1 124 0 81788K 5764K RUN 2 1:13 77.93% rivmp > > > Notice, the accumulated times appear reasonable. At this point in the > computations, rivmp is doing no communication between processes. z is > the netpipe benchmark and is essentially sending messages between the > two processes over the memory bus. > > > For ULE, I see > > last pid: 1169; load averages: 7.56, 2.61, 1.02 up 0+00:03:15 17:13:01 > 40 processes: 11 running, 29 sleeping > CPU: 100% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle > Mem: 31M Active, 9392K Inact, 197M Wired, 248K Cache, 26M Buf, 31G Free > Swap: 4096M Total, 4096M Free > > PID USERNAME THR PRI NICE SIZE RES STATE C TIME CPU COMMAND > 1168 sgk 1 118 0 81788K 5472K CPU6 6 1:18 100.00% rivmp > 1169 sgk 1 118 0 81788K 5416K CPU7 7 1:18 100.00% rivmp > 1167 sgk 1 118 0 81788K 5496K CPU5 5 1:18 100.00% rivmp > 1166 sgk 1 118 0 81788K 5564K RUN 4 1:18 100.00% rivmp > 1151 kargl 1 118 0 78780K 4464K CPU3 3 1:48 99.27% z > 1152 kargl 1 110 0 78780K 4464K CPU0 0 1:18 62.89% z > 1164 sgk 1 113 0 81788K 5592K CPU1 1 0:55 80.76% rivmp > 1165 sgk 1 110 0 81788K 5544K RUN 0 0:52 62.16% rivmp > 1163 sgk 1 107 0 81788K 5624K RUN 2 0:40 50.68% rivmp > 1162 sgk 1 107 0 81788K 5824K CPU2 2 0:39 50.49% rivmp > > > In the above, processes 1162-1165 are clearly not receiving sufficient time > slices to keep up with the other 4 rivmp images. From watching top at a > 1 second interval, once the 4 rivmp hit 100% CPU, they stayed pinned to > their cpu and stay at 100% CPU. It is also seen that processes 1152, 1165 > and 1162, 1163 are stuck on cpus 0 and 2, respectively. > This isn't only bound to floating-point intense applications, even the operating system itselfs seems to suffer from SCHED_ULE. I saw, see and reported several performance issue under heavy load and for seconds (if not minutes!) 4+ CPU boxes get as stuck as a UP box does. Those sticky sitiuations are painful in cases where the box needs to be accessed via X11. The remaining four FreeBSD 8.0-boxes used for numerical applications in our lab (others switched to Linux a long time ago) all uses SCHED_ULE, as this scheduler was introduced to be the superior scheduler over the legacy 4BSD. Well, I'll give 4BSD a chance again. At the moment, even our 8-core DELL Poweredge box is in production use, but if there is something I can do, menas: benchmarking, I'll give it a try. Regards, Oliver From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 07:52:55 2009 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 4E21B106566B for ; Mon, 12 Oct 2009 07:52:55 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net [41.161.16.135]) by mx1.freebsd.org (Postfix) with ESMTP id 845B78FC0C for ; Mon, 12 Oct 2009 07:52:54 +0000 (UTC) Received: from [41.154.0.10] (helo=clue.co.za) by inbound01.jnb1.gp-online.net with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1MxFi8-0002qo-0D; Mon, 12 Oct 2009 09:52:52 +0200 Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MxFi6-0007jF-OU; Mon, 12 Oct 2009 09:52:50 +0200 To: pyunyh@gmail.com From: Ian FREISLICH In-Reply-To: <20091009194037.GI3843@michelle.cdnetworks.com> References: <20091009194037.GI3843@michelle.cdnetworks.com> <20091008170458.GC3843@michelle.cdnetworks.com> <20091007180257.GA3843@michelle.cdnetworks.com> X-Attribution: BOFH Date: Mon, 12 Oct 2009 09:52:50 +0200 Message-Id: Cc: current@freebsd.org Subject: Re: alc(4) link autoselect problem 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, 12 Oct 2009 07:52:55 -0000 Pyun YongHyeon wrote: > On Fri, Oct 09, 2009 at 07:29:08AM +0200, Ian FREISLICH wrote: > > Pyun YongHyeon wrote: > > > On Thu, Oct 08, 2009 at 12:38:45PM +0200, Ian FREISLICH wrote: > > > > wgsw-24010# sh interfaces status ethernet g14 > > > > Flow Link Back Mdix > > > > Port Type Duplex Speed Neg ctrl State Pressure Mode > > > > -------- ------------ ------ ----- -------- ---- ----------- -------- ---- > > --- > > > > g14 1G-Copper Full 100 Enabled Off Up Disabled Off > > > > > > > > > > Hmm, does your switch have an option to enable/disable downshifting > > > feature? If so, how about toggling the option? > > > > I'm not sure exactly what you mean. There's no configuration options > > that obviously match. > > > > Modern PHYs have ability to correct several cabling problems, for > example, > - pair swaps > - pair skews > - pair polarity > - automatic MDI/MDIX > - downshift to enable 10/100Mps link establishment with two > pairs by downgrading the link speed to 10/100Mbps during > auto-negotiation process when it can't establish 1000Mbps link. > Existing cables used to connect 10/100Mbps link partners may > have only two pairs. With two pairs PHYs can announce 1000Mbps > capability to link partner but it can't establish the link as > 1000Mbps link requires 4 pairs. > > Since F1 PHY seems to have above capability I just wanted to see > whether disabling downshifting on link partner makes any > difference. Yes, if I tell the switch to negotiate but not to advertise 1000f, link negotiation works with this PHY: wgsw-24010# sh interfaces advertise ethernet g14 Port: g14 Type: 1G-Copper Link state: Up Auto negotiation: Enabled 1000f 1000h 100f 100h 10f 10h ----- ----- ---- ---- --- --- Admin Local link Advertisement no no yes yes yes yes Oper Local link Advertisement no no yes yes yes yes Oper Remote link Advertisement no no yes yes yes yes Priority Resolution - - yes - - - alc0: flags=8843 metric 0 mtu 1500 options=3198 ether 00:25:b3:6f:ab:9a media: Ethernet autoselect (100baseTX ) status: active Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 05:21:37 2009 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 E2D541065694 for ; Mon, 12 Oct 2009 05:21:37 +0000 (UTC) (envelope-from jh@sandstorm.net) Received: from sirocco.sandstorm.net (sirocco.sandstorm.net [69.33.111.75]) by mx1.freebsd.org (Postfix) with ESMTP id 95BD68FC29 for ; Mon, 12 Oct 2009 05:21:37 +0000 (UTC) Received: from h17.glup.org (207-172-212-135.c3-0.smr-ubr1.sbo-smr.ma.static.cable.rcn.com [207.172.212.135]) (authenticated bits=0) by sirocco.sandstorm.net (8.13.8/8.13.3) with ESMTP id n9C5LYDp000780 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 12 Oct 2009 01:21:34 -0400 (EDT) (envelope-from jh@sandstorm.net) Message-ID: <4AD2BCD9.2090904@sandstorm.net> Date: Mon, 12 Oct 2009 01:21:29 -0400 From: john hood User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: Christian Schmidt References: <309b65830910060054g16a099abxb8e203a46aa9e89c@mail.gmail.com> In-Reply-To: <309b65830910060054g16a099abxb8e203a46aa9e89c@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00 autolearn=ham version=3.1.7 X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on sirocco.sandstorm.net X-Mailman-Approved-At: Mon, 12 Oct 2009 11:10:13 +0000 Cc: freebsd-current@freebsd.org Subject: Re: Boot issues with a Dell Inspiron 530 and 8.0 RC1 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, 12 Oct 2009 05:21:38 -0000 Christian Schmidt wrote: > Hello list, > > I am seeing a strange issue with my Dell Inspiron 530 with 8.0 RC1-p1 > at around 50-75% percent of all boots. It all boils down to GENERIC > throwing the following: > > AP #1 (PHY #1) failed! > panic y/n? [y] panic: bye-bye > cpuid = 0 > > However, this only happens when booting from the hard disk. A boot > from the install CD works perfectly every time. Testing the machine > with 7.2 last night revealed the same issue, so this is not specific > to 8.0 > As an interesting side-note: the odds of a successful boot increase > dramtically when cold-booting. Rebooting from e.g. Linux or Windows > seems to push the failure-rate to around a 100% every time. > We have 3 of these machines. In my experience, keyboard activity triggers the problem. If I boot the machine without any keyboard presses/releases between the time the loader starts the kernel and some time later, definitely by the time the USB keyboard driver attaches, then I don't get this problem. This includes any key-up (and maybe key repeat) events you may generate after typing a key at the boot menu, or after typing enter at the OK prompt, or pressing a key to bypass the autoboot timeout that counts down by seconds. If you let the machine start from cold without touching the keyboard, what happens? If you get to the loader "ok " prompt, then enter "autoboot" and wait for it to time out and boot, what happens? If you press a key or type "boot" to boot the machine while in the loader, what happens? There's been some discussion of SMI-related problems and the long time SMI interrupts take on some machines; my guess is that this is related to that. --jh From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 11:19:06 2009 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 7210F1065692 for ; Mon, 12 Oct 2009 11:19:06 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [91.121.44.19]) by mx1.freebsd.org (Postfix) with ESMTP id 36CC88FC17 for ; Mon, 12 Oct 2009 11:19:06 +0000 (UTC) Received: from baby-jane.lamaiziere.net (20.6.192-77.rev.gaoland.net [77.192.6.20]) by smtp.lamaiziere.net (Postfix) with ESMTPA id C5F52633321; Mon, 12 Oct 2009 13:19:04 +0200 (CEST) Received: from baby-jane.lamaiziere.net (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id 7D276C984; Mon, 12 Oct 2009 13:19:02 +0200 (CEST) Date: Mon, 12 Oct 2009 13:19:01 +0200 From: Patrick Lamaiziere To: freebsd-current@freebsd.org Message-ID: <20091012131901.6421666b@baby-jane.lamaiziere.net> In-Reply-To: <20091008123001.GA82997@nagual.pp.ru> References: <20091004090156.GA85409@crete.org.ua> <20091008123001.GA82997@nagual.pp.ru> X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.6; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Andrey Chernov Subject: Re: 'ee' editor prints cyrillic characters on white background 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, 12 Oct 2009 11:19:06 -0000 Le Thu, 8 Oct 2009 16:30:01 +0400, Andrey Chernov a =E9crit : > > I've upgraded my 7.2-RELEASE to 8.0-RC1. ee editor began to > > highlight cyrillic characters (locale uk_UA.KOI8-U) with white > > background and underscoring. Does anyone know how to disable this? > > Thanks. >=20 > Fixed in -current. It would be nice to have this fixed in 8.0 too :-) Is it planned? Thanks, regards. From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 12:03:55 2009 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 19D301065698 for ; Mon, 12 Oct 2009 12:03:55 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from dd12710.kasserver.com (dd12710.kasserver.com [85.13.134.233]) by mx1.freebsd.org (Postfix) with ESMTP id CE1C78FC14 for ; Mon, 12 Oct 2009 12:03:54 +0000 (UTC) Received: from current.Sisis.de (cazador.sisis.de [193.31.11.193]) by dd12710.kasserver.com (Postfix) with ESMTP id A278F1866D82B for ; Mon, 12 Oct 2009 14:03:55 +0200 (CEST) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id n9CC3rh9003757 for freebsd-current@freebsd.org; Mon, 12 Oct 2009 14:03:53 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Mon, 12 Oct 2009 14:03:52 +0200 From: Matthias Apitz To: freebsd-current@freebsd.org Message-ID: <20091012120352.GA3722@current.Sisis.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) Subject: kernel && SVN rev. number in 'uname -a' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Oct 2009 12:03:55 -0000 Hello, I've build a kernel based on SVN checkout of head and compiled/installed the kernel with: # cd /usr # rm -rf src # svn co svn://.... # cd /usr/src # make buildkernel KERNCONF=GENERIC # make installkernel KERNCONF=GENERIC # shutdown -r now the booting kernel says: $ uname -a FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r197801: Mon Oct 12 13:33:32 CEST 2009 guru@vm-azul.Sisis.de:/usr/obj/usr/src/sys/GENERIC i386 i.e. does contain the SVN rev. number r197801, so far so good: when I now move the /usr/src to some other machine with: # cd /usr # tar cf src.tar src ... # cd /usr # rm -rf src # tar --unlink -xpf src.tar and build the kernel there exact the same way as on the originating machine, the output of 'uname -a' does not contain the SVN revision number. Any idea why is that? Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 12:18:00 2009 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 7CE54106568B for ; Mon, 12 Oct 2009 12:18:00 +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 ABAF78FC13 for ; Mon, 12 Oct 2009 12:17:59 +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 PAA15832; Mon, 12 Oct 2009 15:17:50 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4AD31E6E.5020504@icyb.net.ua> Date: Mon, 12 Oct 2009 15:17:50 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: Matthias Apitz References: <20091012120352.GA3722@current.Sisis.de> In-Reply-To: <20091012120352.GA3722@current.Sisis.de> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: kernel && SVN rev. number in 'uname -a' 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, 12 Oct 2009 12:18:00 -0000 on 12/10/2009 15:03 Matthias Apitz said the following: [snip] > and build the kernel there exact the same way as on the originating > machine, the output of 'uname -a' does not contain the SVN revision > number. Any idea why is that? Thanks Perhaps svn client is not installed there? -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 12:33:18 2009 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 64301106568F; Mon, 12 Oct 2009 12:33:18 +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 7826F8FC0A; Mon, 12 Oct 2009 12:33:17 +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 PAA16105; Mon, 12 Oct 2009 15:33:15 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4AD3220B.5030502@icyb.net.ua> Date: Mon, 12 Oct 2009 15:33:15 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Subject: zfs boot vs loader 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, 12 Oct 2009 12:33:18 -0000 I am using ZFS for boot-and-root filesystem. gptzfsboot is used for bootstrapping, if that matters. Maybe the following is some kind of a pilot error, but I think that I see a problem with selecting a different kernel using loader prompt. That is, I escape to a loader prompt from boot menu. There I do 'unload'. Then I 'load' a different kernel, opensolaris.ko and zfs.ko. Then I 'boot'. Then root mounting inevitably fails because ZFS root filesystem can not be found. This is an unexpected result for me. I wonder if something important for ZFS get unloaded when I unload preloaded kernel and modules. Perhaps I have to manually re-load zpool.cache? This happens with recent CURRENT, amd64. What's strange is that I think that I can switch kernels from loader prompt without any problems when using RELENG_7 and UFS-boot-plus-ZFS-root approach. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 12:35:52 2009 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 6D1AE106568D for ; Mon, 12 Oct 2009 12:35:52 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from dd12710.kasserver.com (dd12710.kasserver.com [85.13.134.233]) by mx1.freebsd.org (Postfix) with ESMTP id 2A7348FC13 for ; Mon, 12 Oct 2009 12:35:52 +0000 (UTC) Received: from current.Sisis.de (cazador.sisis.de [193.31.11.193]) by dd12710.kasserver.com (Postfix) with ESMTP id 9F1631866DDE8; Mon, 12 Oct 2009 14:35:53 +0200 (CEST) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id n9CCZoqb004017; Mon, 12 Oct 2009 14:35:51 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Mon, 12 Oct 2009 14:35:50 +0200 From: Matthias Apitz To: Andriy Gapon Message-ID: <20091012123550.GB3882@current.Sisis.de> References: <20091012120352.GA3722@current.Sisis.de> <4AD31E6E.5020504@icyb.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <4AD31E6E.5020504@icyb.net.ua> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) Cc: freebsd-current@freebsd.org Subject: Re: kernel && SVN rev. number in 'uname -a' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Oct 2009 12:35:52 -0000 El día Monday, October 12, 2009 a las 03:17:50PM +0300, Andriy Gapon escribió: > on 12/10/2009 15:03 Matthias Apitz said the following: > [snip] > > and build the kernel there exact the same way as on the originating > > machine, the output of 'uname -a' does not contain the SVN revision > > number. Any idea why is that? Thanks > > Perhaps svn client is not installed there? Thanks for your hint. Ofc, the svn client is not installed on the 2nd machine (which has no access to Internet). Do you know how this, picking up the SVN rev. number during 'make buildkernel', is done exactly? I did a 2nd kernel build on the primary host, but the SVN cmd /usr/local/bin/svn is not touched as a 'ls -lu' shows ... As well I don't see any svn usage in the Makefiles to pick up a revision number; Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 12:43:33 2009 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 1CF1F1065679 for ; Mon, 12 Oct 2009 12:43:33 +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 61B8E8FC13 for ; Mon, 12 Oct 2009 12:43:32 +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 PAA16242; Mon, 12 Oct 2009 15:43:20 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4AD32467.7020404@icyb.net.ua> Date: Mon, 12 Oct 2009 15:43:19 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: Matthias Apitz References: <20091012120352.GA3722@current.Sisis.de> <4AD31E6E.5020504@icyb.net.ua> <20091012123550.GB3882@current.Sisis.de> In-Reply-To: <20091012123550.GB3882@current.Sisis.de> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: freebsd-current@freebsd.org Subject: Re: kernel && SVN rev. number in 'uname -a' 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, 12 Oct 2009 12:43:33 -0000 on 12/10/2009 15:35 Matthias Apitz said the following: > El día Monday, October 12, 2009 a las 03:17:50PM +0300, Andriy Gapon escribió: > >> on 12/10/2009 15:03 Matthias Apitz said the following: >> [snip] >>> and build the kernel there exact the same way as on the originating >>> machine, the output of 'uname -a' does not contain the SVN revision >>> number. Any idea why is that? Thanks >> Perhaps svn client is not installed there? > > Thanks for your hint. Ofc, the svn client is not installed on the 2nd > machine (which has no access to Internet). Do you know how this, picking > up the SVN rev. number during 'make buildkernel', is done exactly? I did > a 2nd kernel build on the primary host, but the SVN cmd > /usr/local/bin/svn is not touched as a 'ls -lu' shows ... > As well I don't see any svn usage in the Makefiles to pick up a revision > number; See sys/conf/newvers.sh. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 12:44:51 2009 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 27E831065693 for ; Mon, 12 Oct 2009 12:44:51 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id DDEFD8FC0A for ; Mon, 12 Oct 2009 12:44:50 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id E64CB6D41C; Mon, 12 Oct 2009 12:44:49 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id B6FFD84531; Mon, 12 Oct 2009 14:44:49 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Matthias Apitz References: <20091012120352.GA3722@current.Sisis.de> <4AD31E6E.5020504@icyb.net.ua> <20091012123550.GB3882@current.Sisis.de> Date: Mon, 12 Oct 2009 14:44:49 +0200 In-Reply-To: <20091012123550.GB3882@current.Sisis.de> (Matthias Apitz's message of "Mon, 12 Oct 2009 14:35:50 +0200") Message-ID: <86k4z0rdby.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Andriy Gapon Subject: Re: kernel && SVN rev. number in 'uname -a' 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, 12 Oct 2009 12:44:51 -0000 Matthias Apitz writes: > Thanks for your hint. Ofc, the svn client is not installed on the 2nd > machine (which has no access to Internet). Do you know how this, picking > up the SVN rev. number during 'make buildkernel', is done exactly? /usr/local/bin/svnversion > As well I don't see any svn usage in the Makefiles to pick up a revision > number; grep svn /sys/conf/newvers.sh I wish there were a way to disable this; it's slow and meaningless. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 13:00:02 2009 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 034391065670; Mon, 12 Oct 2009 13:00:01 +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 A13328FC13; Mon, 12 Oct 2009 13:00:01 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CD00Ig051458; Mon, 12 Oct 2009 09:00:00 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CD002u051427; Mon, 12 Oct 2009 13:00:00 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 13:00:00 GMT Message-Id: <200910121300.n9CD002u051427@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: Mon, 12 Oct 2009 13:00:02 -0000 TB --- 2009-10-12 12:02:58 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 12:02:58 - starting HEAD tinderbox run for ia64/ia64 TB --- 2009-10-12 12:02:58 - cleaning the object tree TB --- 2009-10-12 12:03:21 - cvsupping the source tree TB --- 2009-10-12 12:03:21 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2009-10-12 12:03:43 - building world TB --- 2009-10-12 12:03:43 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 12:03:43 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 12:03:43 - TARGET=ia64 TB --- 2009-10-12 12:03:43 - TARGET_ARCH=ia64 TB --- 2009-10-12 12:03:43 - TZ=UTC TB --- 2009-10-12 12:03:43 - __MAKE_CONF=/dev/null TB --- 2009-10-12 12:03:43 - cd /src TB --- 2009-10-12 12:03:43 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 12:03:44 UTC 2009 >>> 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 [...] /src/sbin/ifconfig/ifieee80211.c:2634: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2636: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2638: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2639: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2641: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2642: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2644: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2645: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast *** Error code 1 Stop in /src/sbin/ifconfig. *** Error code 1 Stop in /obj/ia64/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 13:00:00 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 13:00:00 - ERROR: failed to build world TB --- 2009-10-12 13:00:00 - 2693.48 user 431.46 system 3421.80 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 13:09:17 2009 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 00BFC1065679 for ; Mon, 12 Oct 2009 13:09:17 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from dd12710.kasserver.com (dd12710.kasserver.com [85.13.134.233]) by mx1.freebsd.org (Postfix) with ESMTP id 84B068FC17 for ; Mon, 12 Oct 2009 13:09:16 +0000 (UTC) Received: from current.Sisis.de (cazador.sisis.de [193.31.11.193]) by dd12710.kasserver.com (Postfix) with ESMTP id E61431866C85C; Mon, 12 Oct 2009 15:09:17 +0200 (CEST) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id n9CD9FDS004230; Mon, 12 Oct 2009 15:09:15 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Mon, 12 Oct 2009 15:09:15 +0200 From: Matthias Apitz To: Paul B Mahol Message-ID: <20091012130914.GA4180@current.Sisis.de> References: <20091011062419.GA2168@current.Sisis.de> <3a142e750910111214rb75f185k12b2cc7e1aba59d9@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3a142e750910111214rb75f185k12b2cc7e1aba59d9@mail.gmail.com> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) Cc: kde-freebsd@kde.org, freebsd-current@freebsd.org Subject: Re: 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Oct 2009 13:09:17 -0000 El día Sunday, October 11, 2009 a las 07:14:21PM +0000, Paul B Mahol escribió: > Make sure that all libraries and binarys are rebuild, thare may be ABI > changes and not > support for older code .... Hi Paul, I've compiled all (kernel, user land and the ports) in a virtual machine I'm using for preparing binary installation, i.e. after compiling the ports I create packages to install them on machines where you either can't compile for being to small/slow (like my EeePC 900) or to give a binary set away for installation where machines have limited access to Internet. I've build and installed kernel and user land based on SVN checkout: # svn info Path: . URL: svn://svn.freebsd.org/base/head Repository Root: svn://svn.freebsd.org/base Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f Revision: 197801 Node Kind: directory Schedule: normal Last Changed Author: maxim Last Changed Rev: 197799 Last Changed Date: 2009-10-06 06:57:18 +0200 (Tue, 06 Oct 2009) # uname -a FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r197801: Tue Oct 6 13:57:38 CEST 2009 guru@vm-azul.Sisis.de:/usr/obj/usr/src/sys/REBELION-HEAD i386 When kernel and user land have been on 9-CURRENT, I removed /usr/ports, checked them out with CVS and build all my ports, especially KDE3. I don't see how an old library or binary can cause this. Only some ABI change which is not supported in the KDE sources... Don't know if someone from FreeBSD's KDE team can (or will) comment on it. It seems to me that they all went away (to KDE4 :-)). Thx matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 13:29:00 2009 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 A36B91065672; Mon, 12 Oct 2009 13:29:00 +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 533188FC14; Mon, 12 Oct 2009 13:29:00 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CDSxJw092756; Mon, 12 Oct 2009 09:28:59 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CDSxCG092752; Mon, 12 Oct 2009 13:28:59 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 13:28:59 GMT Message-Id: <200910121328.n9CDSxCG092752@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 mips/mips 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: Mon, 12 Oct 2009 13:29:00 -0000 TB --- 2009-10-12 12:49:04 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 12:49:04 - starting HEAD tinderbox run for mips/mips TB --- 2009-10-12 12:49:04 - cleaning the object tree TB --- 2009-10-12 12:49:14 - cvsupping the source tree TB --- 2009-10-12 12:49:14 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2009-10-12 12:49:39 - building world TB --- 2009-10-12 12:49:39 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 12:49:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 12:49:39 - TARGET=mips TB --- 2009-10-12 12:49:39 - TARGET_ARCH=mips TB --- 2009-10-12 12:49:39 - TZ=UTC TB --- 2009-10-12 12:49:39 - __MAKE_CONF=/dev/null TB --- 2009-10-12 12:49:39 - cd /src TB --- 2009-10-12 12:49:39 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 12:49:39 UTC 2009 >>> 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 [...] /src/sbin/ifconfig/ifieee80211.c:2634: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2636: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2638: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2639: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2641: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2642: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2644: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2645: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast *** Error code 1 Stop in /src/sbin/ifconfig. *** Error code 1 Stop in /src/sbin. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 13:28:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 13:28:59 - ERROR: failed to build world TB --- 2009-10-12 13:28:59 - 1713.18 user 395.52 system 2395.04 real http://tinderbox.des.no/tinderbox-head-HEAD-mips-mips.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 13:44:06 2009 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 6BC211065694; Mon, 12 Oct 2009 13:44:06 +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 138808FC1C; Mon, 12 Oct 2009 13:44:06 +0000 (UTC) Received: from lemongrass.sec.cl.cam.ac.uk (lemongrass.sec.cl.cam.ac.uk [128.232.18.47]) by cyrus.watson.org (Postfix) with ESMTPSA id 3B72646B1A; Mon, 12 Oct 2009 09:44:05 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1076) From: "Robert N. M. Watson" In-Reply-To: <19e9a5dc0910111409l6e9b80a3rafaca3abe6d63e32@mail.gmail.com> Date: Mon, 12 Oct 2009 14:44:03 +0100 Message-Id: <0037C4F1-7AA4-4010-AE7B-75360EA17D2D@freebsd.org> References: <19e9a5dc0910111409l6e9b80a3rafaca3abe6d63e32@mail.gmail.com> To: Gonzalo Nemmi X-Mailer: Apple Mail (2.1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Stanislav Sedov , current@freebsd.org Subject: Re: FYI: "8.0TODO" wiki page updated 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, 12 Oct 2009 13:44:06 -0000 On 11 Oct 2009, at 22:09, Gonzalo Nemmi wrote: > On Sun, Oct 11, 2009 at 9:34 AM, Robert Watson > wrote: > > FYI for those tracking the 8.0 release: after a haitus of about a > month around the FreeBSD Developer Summit and EuroBSDCon 2009 here > in Cambridge, and with the help of Colin Percival, the 8.0TODO wiki > page is now up-to-date: > > http://wiki.FreeBSD.org/8.0TODO > > We'll endeavour to keep it more up-to-date going forward; there's > nothing like hosting a conference to get you behind on e-mail :-). > I just took a look at the recently anounced updated TODO lists for > 8.0 (http://wiki.freebsd.org/8.0TODO) but couldn't find a anything > about PR kern/136876: [bge] bge will not resume properly after > suspend. > Does that mean that 8.0 will be released without a fix for kern/ > 136876? Hi Gonzalo-- I'm not aware of the status of this bug, but have CC'd Stanislav Sedov, who has recently been working on other known if_bge issues for 8.0. At this point things are pretty late in the cycle, and device driver modifications (especially for sensitive drivers such as bge) represent a significant risk, so things may not change; however, perhaps he has some thoughts along these lines? Thanks, Robert From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 13:46:06 2009 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 3C47B1065672; Mon, 12 Oct 2009 13:46:06 +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 133F28FC23; Mon, 12 Oct 2009 13:46:06 +0000 (UTC) Received: from lemongrass.sec.cl.cam.ac.uk (lemongrass.sec.cl.cam.ac.uk [128.232.18.47]) by cyrus.watson.org (Postfix) with ESMTPSA id DFFB146B1A; Mon, 12 Oct 2009 09:46:04 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: "Robert N. M. Watson" In-Reply-To: Date: Mon, 12 Oct 2009 14:46:03 +0100 Content-Transfer-Encoding: 7bit Message-Id: References: To: Harsha X-Mailer: Apple Mail (2.1076) Cc: freebsd-current@freebsd.org, net@freebsd.org Subject: Re: Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c] 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, 12 Oct 2009 13:46:06 -0000 On 12 Oct 2009, at 05:38, Harsha wrote: > Thanks a lot for the clarification. > > I had assumed that the lock was non-sleepable looking at this log - > Kernel page fault with the following non-sleepable locks held: > exclusive rw ifnet_rw (ifnet_rw) r = 0 (0xc0f63464) locked @ > /usr/src/sys/net/if.c:409 Looks like a NULL pointer dereference, so perhaps a more traditional bug -- could you convert ifindex_alloc_locked+0x71 to a line of code? You can do this using kgdb on the kernel symbols file, perhaps "l *ifindex_alloc_locked+0x71". Robert From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 13:47:07 2009 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 38BD41065696; Mon, 12 Oct 2009 13:47: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 DC24B8FC19; Mon, 12 Oct 2009 13:47:06 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CDl6Zu007444; Mon, 12 Oct 2009 09:47:06 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CDl6Ur007443; Mon, 12 Oct 2009 13:47:06 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 13:47:06 GMT Message-Id: <200910121347.n9CDl6Ur007443@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: Mon, 12 Oct 2009 13:47:07 -0000 TB --- 2009-10-12 13:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 13:00:00 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-10-12 13:00:00 - cleaning the object tree TB --- 2009-10-12 13:00:18 - cvsupping the source tree TB --- 2009-10-12 13:00:18 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-10-12 13:00:44 - building world TB --- 2009-10-12 13:00:44 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 13:00:44 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 13:00:44 - TARGET=powerpc TB --- 2009-10-12 13:00:44 - TARGET_ARCH=powerpc TB --- 2009-10-12 13:00:44 - TZ=UTC TB --- 2009-10-12 13:00:44 - __MAKE_CONF=/dev/null TB --- 2009-10-12 13:00:44 - cd /src TB --- 2009-10-12 13:00:44 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 13:00:44 UTC 2009 >>> 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 [...] /src/sbin/ifconfig/ifieee80211.c:2634: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2636: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2638: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2639: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2641: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2642: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2644: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2645: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast *** Error code 1 Stop in /src/sbin/ifconfig. *** Error code 1 Stop in /obj/powerpc/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 13:47:06 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 13:47:06 - ERROR: failed to build world TB --- 2009-10-12 13:47:06 - 2190.93 user 424.20 system 2825.24 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 13:53:12 2009 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 E617F1065697; Mon, 12 Oct 2009 13:53:12 +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 949398FC15; Mon, 12 Oct 2009 13:53:12 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CDrBGj036539; Mon, 12 Oct 2009 09:53:11 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CDrBvV036530; Mon, 12 Oct 2009 13:53:11 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 13:53:11 GMT Message-Id: <200910121353.n9CDrBvV036530@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: Mon, 12 Oct 2009 13:53:13 -0000 TB --- 2009-10-12 13:09:14 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 13:09:14 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2009-10-12 13:09:14 - cleaning the object tree TB --- 2009-10-12 13:09:29 - cvsupping the source tree TB --- 2009-10-12 13:09:29 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2009-10-12 13:09:54 - building world TB --- 2009-10-12 13:09:54 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 13:09:54 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 13:09:54 - TARGET=sparc64 TB --- 2009-10-12 13:09:54 - TARGET_ARCH=sparc64 TB --- 2009-10-12 13:09:54 - TZ=UTC TB --- 2009-10-12 13:09:54 - __MAKE_CONF=/dev/null TB --- 2009-10-12 13:09:54 - cd /src TB --- 2009-10-12 13:09:54 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 13:09:55 UTC 2009 >>> 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 [...] /src/sbin/ifconfig/ifieee80211.c:2634: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2636: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2638: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2639: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2641: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2642: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2644: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2645: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast *** Error code 1 Stop in /src/sbin/ifconfig. *** Error code 1 Stop in /obj/sparc64/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 13:53:11 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 13:53:11 - ERROR: failed to build world TB --- 2009-10-12 13:53:11 - 2032.88 user 417.82 system 2637.34 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 13:55:01 2009 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 288241065693; Mon, 12 Oct 2009 13:55:01 +0000 (UTC) (envelope-from stas@deglitch.com) Received: from mx0.deglitch.com (backbone.deglitch.com [IPv6:2001:16d8:fffb:4::abba]) by mx1.freebsd.org (Postfix) with ESMTP id C1FBD8FC20; Mon, 12 Oct 2009 13:55:00 +0000 (UTC) Received: from stasss.yandex.ru (dhcp170-227-red.yandex.net [95.108.170.227]) by mx0.deglitch.com (Postfix) with ESMTPSA id 354FF8FC4E; Mon, 12 Oct 2009 17:54:58 +0400 (MSD) Date: Mon, 12 Oct 2009 17:54:57 +0400 From: Stanislav Sedov To: "Robert N. M. Watson" Message-Id: <20091012175457.4ea1bf2e.stas@deglitch.com> In-Reply-To: <0037C4F1-7AA4-4010-AE7B-75360EA17D2D@freebsd.org> References: <19e9a5dc0910111409l6e9b80a3rafaca3abe6d63e32@mail.gmail.com> <0037C4F1-7AA4-4010-AE7B-75360EA17D2D@freebsd.org> Organization: Deglitch Networks X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Mon__12_Oct_2009_17_54_57_+0400_RrnEZWDV=wTBHMI9" X-Mailman-Approved-At: Mon, 12 Oct 2009 14:01:14 +0000 Cc: Stanislav Sedov , Gonzalo Nemmi , current@freebsd.org Subject: Re: FYI: "8.0TODO" wiki page updated 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, 12 Oct 2009 13:55:01 -0000 --Signature=_Mon__12_Oct_2009_17_54_57_+0400_RrnEZWDV=wTBHMI9 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, 12 Oct 2009 14:44:03 +0100 "Robert N. M. Watson" mentioned: > Hi Gonzalo-- >=20 > I'm not aware of the status of this bug, but have CC'd Stanislav =20 > Sedov, who has recently been working on other known if_bge issues for =20 > 8.0. At this point things are pretty late in the cycle, and device =20 > driver modifications (especially for sensitive drivers such as bge) =20 > represent a significant risk, so things may not change; however, =20 > perhaps he has some thoughts along these lines? >=20 Hi, Gonzalo! I've not looked into this issue yet, but I'll do it in the near future. Unfortunatly, I believe it is too late to expect the fix to be present in 8.x, but I'll look what I can do wrt. this issue. --=20 Stanislav Sedov ST4096-RIPE --Signature=_Mon__12_Oct_2009_17_54_57_+0400_RrnEZWDV=wTBHMI9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJK0zUxAAoJEKN82nOYvCd0EUMP/3jqlew+8sVNwiI5hNNNVIcB /8edzv+21UuQkpaLxS8WuGUVBzQdrMIQfnubwI4pEKwHx98eiC1B99akM9ASaf75 w/ANmTqaMjYmPtr77fBAVow87Pd/Nq7CpIYVDBtJ+527tCryxQngnV25YHD8aaJk bhmHM9qgI0fJVTWTNRcDq+NraKoBZb1ci3bwOdy+TSiFMbmXxfGxyhhDEIBPKyNv AcGswMhX9mybVsLEk1L9EiCLrvYsD2wDz6BcEjag1ms5X8KdKft8gFwAvvs50ZrW tFstrWzyxzOY2r4wVN5p0TeuW7DfvGw7YlTVeV9aJ4+RuzK41Kl/nNfyd8+GiP7P bEpWB6+rV+kZH7/y8x3WM5lcSt81pg1dNeM42fGAeJu3tHtNWuYRBhSn9+BjCgsx lXNAvF6iowx6d0ZwJZ1l4b5Yur3de4UL2voNttZdFrzetFIxNYGsGytNZsolXbeX u60yFzlRlRmb6YU0akvHXR+QL4bahRsmRakNbMQ+mvUTyBRFqMl/pgrWe0Mn8TDu GAowOjle/WcXA+sHS9d6QAFYLqgyKrrMNynUrWnhgqwu1I5VtkIlpACqBJ+DsMVN 2nOQGEHqscpsgxfbloSPI3L5ifKBVBWW7S4d8Ad8V87LDyxIfrVWTVFsR7LKTJX4 nTHYSC+zMG6VnixlPC52 =Z9i9 -----END PGP SIGNATURE----- --Signature=_Mon__12_Oct_2009_17_54_57_+0400_RrnEZWDV=wTBHMI9-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 14:08:19 2009 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 33BDF1065670; Mon, 12 Oct 2009 14:08:19 +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 D6FF88FC0C; Mon, 12 Oct 2009 14:08:18 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CE8ILm062664; Mon, 12 Oct 2009 10:08:18 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CE8Itx062663; Mon, 12 Oct 2009 14:08:18 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 14:08:18 GMT Message-Id: <200910121408.n9CE8Itx062663@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: Mon, 12 Oct 2009 14:08:19 -0000 TB --- 2009-10-12 13:26:06 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 13:26:06 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2009-10-12 13:26:06 - cleaning the object tree TB --- 2009-10-12 13:26:19 - cvsupping the source tree TB --- 2009-10-12 13:26:19 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2009-10-12 13:26:44 - building world TB --- 2009-10-12 13:26:44 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 13:26:44 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 13:26:44 - TARGET=sun4v TB --- 2009-10-12 13:26:44 - TARGET_ARCH=sparc64 TB --- 2009-10-12 13:26:44 - TZ=UTC TB --- 2009-10-12 13:26:44 - __MAKE_CONF=/dev/null TB --- 2009-10-12 13:26:44 - cd /src TB --- 2009-10-12 13:26:44 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 13:26:44 UTC 2009 >>> 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 [...] /src/sbin/ifconfig/ifieee80211.c:2634: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2636: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2638: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2639: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2641: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2642: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2644: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast /src/sbin/ifconfig/ifieee80211.c:2645: warning: passing argument 1 of 'memcmp' makes pointer from integer without a cast *** Error code 1 Stop in /src/sbin/ifconfig. *** Error code 1 Stop in /obj/sun4v/src/rescue/rescue. *** Error code 1 Stop in /src/rescue/rescue. *** Error code 1 Stop in /src/rescue. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 14:08:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 14:08:18 - ERROR: failed to build world TB --- 2009-10-12 14:08:18 - 2047.42 user 399.23 system 2531.70 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 14:55:02 2009 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 91291106566B for ; Mon, 12 Oct 2009 14:55:02 +0000 (UTC) (envelope-from kraduk@googlemail.com) Received: from mail-bw0-f223.google.com (mail-bw0-f223.google.com [209.85.218.223]) by mx1.freebsd.org (Postfix) with ESMTP id D50AC8FC08 for ; Mon, 12 Oct 2009 14:55:01 +0000 (UTC) Received: by bwz23 with SMTP id 23so1980978bwz.43 for ; Mon, 12 Oct 2009 07:55:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=4ih3QCVWx9Doe1BaEE8PK4OYt4APD28RwTYrBjjFqKA=; b=X1dLA1Hg0W+q5XnApi7or6amBVl8eZ7mxh5EICcsXAIjkcsmztn9d7XGX+QoLRybjq eEZO5Q/1p+FlqrprD2Ar5PKJfoibgJhn1auLpjN8WeIzOAPRi8zfAXtorgB3e+dvlOUj MC0R5SI8a1Hu6glGyKbS8yHY9VRhcUqoYE+uw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=jiEy2ESHfw337qALL91qh6CI4FxOAjbCn5LXLJ5U+rkB7HO4aqrTPlXhEYUxfR5C8X x1CnQt2m4dLTiVBXg08+DiMcz/FWThEXOjRSZ7R6W+aUtgHOXrTKP9vvOkbfI0KJLaCe gBXNQjMw7oKZ+YP6W+kPzQNwIw6PJ7u00PrDU= MIME-Version: 1.0 Received: by 10.239.145.142 with SMTP id s14mr368689hba.144.1255359300585; Mon, 12 Oct 2009 07:55:00 -0700 (PDT) In-Reply-To: <4AD3220B.5030502@icyb.net.ua> References: <4AD3220B.5030502@icyb.net.ua> Date: Mon, 12 Oct 2009 15:55:00 +0100 Message-ID: From: krad To: Andriy Gapon Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: zfs boot vs loader 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, 12 Oct 2009 14:55:02 -0000 2009/10/12 Andriy Gapon > > I am using ZFS for boot-and-root filesystem. gptzfsboot is used for > bootstrapping, > if that matters. > Maybe the following is some kind of a pilot error, but I think that I see a > problem with selecting a different kernel using loader prompt. > That is, I escape to a loader prompt from boot menu. There I do 'unload'. > Then I > 'load' a different kernel, opensolaris.ko and zfs.ko. Then I 'boot'. Then > root > mounting inevitably fails because ZFS root filesystem can not be found. > > This is an unexpected result for me. > I wonder if something important for ZFS get unloaded when I unload > preloaded > kernel and modules. Perhaps I have to manually re-load zpool.cache? > > This happens with recent CURRENT, amd64. > What's strange is that I think that I can switch kernels from loader prompt > without any problems when using RELENG_7 and UFS-boot-plus-ZFS-root > approach. > > -- > Andriy Gapon > _______________________________________________ > 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" > before you boot the kernels check the values of the following are still set eg vfs.root.mountfrom="zfs:system/root" vfs.root.mountfrom.options=rw From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 15:00:48 2009 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 82B4E1065672 for ; Mon, 12 Oct 2009 15:00:48 +0000 (UTC) (envelope-from ckane@colemankane.org) Received: from mail-out2.fuse.net (mail-out2.fuse.net [216.68.8.171]) by mx1.freebsd.org (Postfix) with ESMTP id 46D1F8FC24 for ; Mon, 12 Oct 2009 15:00:47 +0000 (UTC) X-CNFS-Analysis: v=1.1 cv=b7ONQlh8LqIPzQSMoESTRogmdKKmQKxrYVP/ED+TJrg= c=1 sm=0 a=6I5d2MoRAAAA:8 a=h8OEPAnC3I52AqhOy7EA:9 a=JUrnMzXn_1uMJ3GCEEIPmJ2ZZkYA:4 a=SV7veod9ZcQA:10 a=LkYvsgB9u1MH7Ao0BLhsLg==:117 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Authentication-Results: ecout2 smtp.mail=ckane@colemankane.org; spf=neutral Received-SPF: neutral (ecout2: 74.215.227.9 is neither permitted nor denied by domain of colemankane.org) Received: from [74.215.227.9] ([74.215.227.9:50612] helo=mail.colemankane.org) by ecout2 (envelope-from ) (ecelerity 2.2.2.43 r()) with ESMTP id 16/26-23671-91143DA4; Mon, 12 Oct 2009 10:45:46 -0400 Received: from [172.20.0.76] (rrcs-96-11-231-210.central.biz.rr.com [96.11.231.210]) by mail.colemankane.org (Postfix) with ESMTPSA id 35D181143E; Mon, 12 Oct 2009 11:48:58 -0400 (EDT) From: Coleman Kane To: Stanislav Sedov In-Reply-To: <20091012175457.4ea1bf2e.stas@deglitch.com> References: <19e9a5dc0910111409l6e9b80a3rafaca3abe6d63e32@mail.gmail.com> <0037C4F1-7AA4-4010-AE7B-75360EA17D2D@freebsd.org> <20091012175457.4ea1bf2e.stas@deglitch.com> Content-Type: text/plain Date: Mon, 12 Oct 2009 10:44:41 -0400 Message-Id: <1255358681.10169.2.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Mon, 12 Oct 2009 16:19:53 +0000 Cc: Stanislav Sedov , Gonzalo Nemmi , "Robert N. M. Watson" , current@freebsd.org Subject: Re: FYI: "8.0TODO" wiki page updated 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, 12 Oct 2009 15:00:48 -0000 On Mon, 2009-10-12 at 17:54 +0400, Stanislav Sedov wrote: > On Mon, 12 Oct 2009 14:44:03 +0100 > "Robert N. M. Watson" mentioned: > > > Hi Gonzalo-- > > > > I'm not aware of the status of this bug, but have CC'd Stanislav > > Sedov, who has recently been working on other known if_bge issues for > > 8.0. At this point things are pretty late in the cycle, and device > > driver modifications (especially for sensitive drivers such as bge) > > represent a significant risk, so things may not change; however, > > perhaps he has some thoughts along these lines? > > > > Hi, Gonzalo! > > I've not looked into this issue yet, but I'll do it in the near future. > Unfortunatly, I believe it is too late to expect the fix to be present > in 8.x, but I'll look what I can do wrt. this issue. > Hi guys, Please send any fix or potential fix for evaluation my way. I attempted to fix this bug awhile back myself, but was unable to pin down what was going on. FreeBSD 9-CURRENT/amd64. This one is particularly a nuisance for me, as is the last thing that prevents me from using Suspend on my HP notebook for anything. (Well, I still need to fix whatever causes NDIS to break as well, but that's less important, and I suspect partly a Win32 API issue). -- Coleman Kane From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 17:27:44 2009 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 B91191065676; Mon, 12 Oct 2009 17:27:44 +0000 (UTC) (envelope-from gnemmi@gmail.com) Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com [209.85.220.222]) by mx1.freebsd.org (Postfix) with ESMTP id DCDEF8FC16; Mon, 12 Oct 2009 17:27:43 +0000 (UTC) Received: by fxm22 with SMTP id 22so8320487fxm.36 for ; Mon, 12 Oct 2009 10:27:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=j3lCxMB6UwYuT9wxiYwGeriwZUr0gjjVOt59qd6K9sM=; b=QCScdVXFeGVOOhaXgdkYPSFggxVFXoCMEmYtwBGN+p+Vhvnk8VhHYxRPYhifGQNPHN wvEt6j2WmTj6iT5JWRa8L1Ht+GLiw/qxajEUlerDcgKL3RU+XJMnwGbyPKNY0Sgw9/kT nxbXqqHyRnz2zd5Kaj9oq8kAJZO+LcmhS5Fy8= 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=tBA1iE+NvAtcjj72krajtUAAcU0krk/1bw9ECTZAZXYWI4yvE0lGwgZlYcrrHEMW6o /G4bL4bnulfkvMHdxc2h4P4H2BSXrJy5DSAfwbHjJDxwD8zPJO3l07h4Q8TSBK4dXPDe hBauzl9Y3yzNSaAGIVPUQP2hznbAyfQ9Fjoy0= MIME-Version: 1.0 Received: by 10.239.170.20 with SMTP id q20mr416572hbe.152.1255368462895; Mon, 12 Oct 2009 10:27:42 -0700 (PDT) In-Reply-To: <1255358681.10169.2.camel@localhost> References: <19e9a5dc0910111409l6e9b80a3rafaca3abe6d63e32@mail.gmail.com> <0037C4F1-7AA4-4010-AE7B-75360EA17D2D@freebsd.org> <20091012175457.4ea1bf2e.stas@deglitch.com> <1255358681.10169.2.camel@localhost> Date: Mon, 12 Oct 2009 14:27:42 -0300 Message-ID: <19e9a5dc0910121027l597697a9j48a17fde6da28aa4@mail.gmail.com> From: Gonzalo Nemmi To: Coleman Kane Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Stanislav Sedov , "Robert N. M. Watson" , Stanislav Sedov , current@freebsd.org Subject: Re: FYI: "8.0TODO" wiki page updated 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, 12 Oct 2009 17:27:44 -0000 On Mon, Oct 12, 2009 at 11:44 AM, Coleman Kane wrote: > On Mon, 2009-10-12 at 17:54 +0400, Stanislav Sedov wrote: > > On Mon, 12 Oct 2009 14:44:03 +0100 > > "Robert N. M. Watson" mentioned: > > > > > Hi Gonzalo-- > > > > > > I'm not aware of the status of this bug, but have CC'd Stanislav > > > Sedov, who has recently been working on other known if_bge issues for > > > 8.0. At this point things are pretty late in the cycle, and device > > > driver modifications (especially for sensitive drivers such as bge) > > > represent a significant risk, so things may not change; however, > > > perhaps he has some thoughts along these lines? > > > > > > > Hi, Gonzalo! > > > > I've not looked into this issue yet, but I'll do it in the near future. > > Unfortunatly, I believe it is too late to expect the fix to be present > > in 8.x, but I'll look what I can do wrt. this issue. > > > > Hi guys, > > Please send any fix or potential fix for evaluation my way. I attempted > to fix this bug awhile back myself, but was unable to pin down what was > going on. FreeBSD 9-CURRENT/amd64. > > This one is particularly a nuisance for me, as is the last thing that > prevents me from using Suspend on my HP notebook for anything. (Well, I > still need to fix whatever causes NDIS to break as well, but that's less > important, and I suspect partly a Win32 API issue). > > -- > Coleman Kane > > Same in here, please send any fix or potential fix for evaluation my way ... if_bge not waking up is the only thing preventing me from resuming (regardless of kern/136946 which doesn't affect me that much as I don't own or use firewire dongles .. I even comment the driver out ouf my kernel) on my i386 8.0-RC1, so .. if_bge waking up makes a lot of difference for me Thanks Robert and Stanislav for you kind and prompt answers. Thanks Coleman for pitching in. Best Regards Gonzalo Nemmi From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 17:41:07 2009 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 45E751065672 for ; Mon, 12 Oct 2009 17:41:07 +0000 (UTC) (envelope-from bland@bbnest.net) Received: from mail1.asahi-net.or.jp (mail1.asahi-net.or.jp [202.224.39.197]) by mx1.freebsd.org (Postfix) with ESMTP id 10DE38FC0C for ; Mon, 12 Oct 2009 17:41:06 +0000 (UTC) Received: from hub.bbnest.net (w133033.ppp.asahi-net.or.jp [121.1.133.33]) by mail1.asahi-net.or.jp (Postfix) with ESMTP id 1C8E27C1B8; Tue, 13 Oct 2009 02:41:03 +0900 (JST) Received: from nest.bbnest.net (nest.bbnest.net [10.0.0.249]) by hub.bbnest.net (8.14.3/8.14.3) with ESMTP id n9CHemVd004578 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 13 Oct 2009 02:40:49 +0900 (JST) (envelope-from bland@bbnest.net) Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Alexander Nedotsukov In-Reply-To: Date: Tue, 13 Oct 2009 02:40:48 +0900 Content-Transfer-Encoding: 7bit Message-Id: References: <54ee35ff63fa25ea4c082134892835fb@mail> <0EA2E119-29DF-4DDE-84C3-432E35D61C76@rabson.org> To: Alexander Nedotsukov X-Mailer: Apple Mail (2.1076) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Tue Oct 13 02:41:02 2009 X-DSPAM-Confidence: 0.9995 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4ad36a2e45791963699761 X-Mailman-Approved-At: Mon, 12 Oct 2009 17:56:30 +0000 Cc: FreeBSD Current Subject: Re: 8.0 Dynamic Linker Broken? (Was: [PATCH] SASL problems with spnego on 8.0-BETA4) 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, 12 Oct 2009 17:41:07 -0000 On 05.10.2009, at 20:07, Alexander Nedotsukov wrote: > Doug, > > I share your concerns about wrong libgssapi_foo usage. > Do you see any possible drawbacks of: > 3) Move libgssapi_foo into gssapi/libfoo_mech and link libgoo_mech > against libgssapi Well after reading about GSSAPI private extensions. I'd say this was not a good idea. If it even can be considered an idea at all. > > Thanks, > Alexander > > On 05.10.2009, at 16:29, Doug Rabson wrote: > >> This is the core of the problem, I think. There are two possible >> solutions: >> >> 1. Link libgssapi_foo.so against libgssapi.so. I'm not a fan of >> this because it will encourage people to link with >> libgssapi_krb5.so when they really ought to be linking with >> libgssapi.so to give them mechanism independance. >> >> 2. Split the various mechanism libs in to two parts, mech_foo.so >> which will contain the actual mechanism implementation (this can >> link with libgssapi.so to handle the RTLD_LOCAL issue) and >> optionally libgssapi_foo.so to contain any mechanism-specific >> extensions. >> >> Clearly (2) is unsuitable for 8.0 but could happen in current. I >> guess we could use (1) as a band-aid fix for 8.0. >> >> On 5 Oct 2009, at 05:50, Alexander Nedotsukov wrote: >> >>> >>> Actually this may mean quite otherwise. >>> What I saying is if some code (eg. libsasl) dlopen() libgssapi as >>> RTLD_LOCAL then later attempt to load libgssapi_xxx inside >>> libgssapi may >>> fail because of this: >>> >>> $ldd /usr/lib/libgssapi_spnego.so >>> /usr/lib/libgssapi_spnego.so: >>> libasn1.so.10 => /usr/lib/libasn1.so.10 (0x28300000) >>> libc.so.7 => /lib/libc.so.7 (0x2808f000) >>> >>> I would expect to see libgssapi.so.10 dependency here. >>> >>> On Mon, 5 Oct 2009 10:07:20 +1100, John Marshall >>> wrote: >>>> On Fri, 02 Oct 2009, 08:24 -0400, John Baldwin wrote: >>>>> On Friday 02 October 2009 4:13:19 am John Marshall wrote: >>>>>> On Tue, 22 Sep 2009, 08:22 +1000, John Marshall wrote: >>>>>>> On Mon, 21 Sep 2009, 11:26 -0400, Rick Macklem wrote: >>>>>>> >>>> [snip] >>>>>>>> >>>>>>>> Now, hopefully someone who understands enough about dynamic >>>>>>>> linking will >>>>>>>> know if this is the correct fix for 8.0? (I'm going on a couple >>> of >>>>>>>> weeks >>>>>>>> vacation at the end of this week, so I won't be around to >>>>>>>> commit >>>>>>>> anything >>>>>>>> and don't understand it well enough to know if this is the >>> correct >>>>>>>> way >>>>>>>> to fix it.) >>>>>>>> >>>>>>>> So, hopefully someone else can pick this one up? >>>>>>>> >>>> [snip] >>>>>>> >>>>>>> I have submitted a patch to the FreeBSD Makefile which patches >>>>>>> the >>>>>>> vendor-supplied template for krb5-config. I should be >>>>>>> grateful if >>>>>>> dfr@ >>>>>>> or another src committer would please review this with a view to >>>>>>> obtaining re@ approval to commit it before 8.0-RC2. >>>>>>> >>>>>>> >>>>>> >>>>>> Any src committers able to help with this? >>>>> >>>>> Hmmm, I thought that libgssapi was supposed to use dlopen to >>>>> load the >>>>> proper >>>>> back-end libraries using /etc/gss/mech rather than having >>>>> applications >>>>> directly link against them. >>>> >>>> OK, so if my proposed solution is, in fact, only masking a >>>> symptom of a >>>> broken dynamic linker, would somebody who understands this stuff >>>> please >>>> weigh in on this with some debugging suggestions or with a patch to >>>> address this problem? >>>> >>>> I'm able to help with testing but I'm not a programmer and know >>>> nothing >>>> about the FreeBSD dynamic linker. >>>> >>>> Thanks. >> >> _______________________________________________ >> 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 >> " > > _______________________________________________ > 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 > " From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 18:51:27 2009 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 508D51065696; Mon, 12 Oct 2009 18:51:27 +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 12FD88FC0C; Mon, 12 Oct 2009 18:51:26 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CIpQW7073663; Mon, 12 Oct 2009 14:51:26 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CIpQLI073656; Mon, 12 Oct 2009 18:51:26 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 18:51:26 GMT Message-Id: <200910121851.n9CIpQLI073656@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: Mon, 12 Oct 2009 18:51:27 -0000 TB --- 2009-10-12 18:33:09 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 18:33:09 - starting HEAD tinderbox run for ia64/ia64 TB --- 2009-10-12 18:33:09 - cleaning the object tree TB --- 2009-10-12 18:33:16 - cvsupping the source tree TB --- 2009-10-12 18:33:16 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2009-10-12 18:33:44 - building world TB --- 2009-10-12 18:33:44 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 18:33:44 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 18:33:44 - TARGET=ia64 TB --- 2009-10-12 18:33:44 - TARGET_ARCH=ia64 TB --- 2009-10-12 18:33:44 - TZ=UTC TB --- 2009-10-12 18:33:44 - __MAKE_CONF=/dev/null TB --- 2009-10-12 18:33:44 - cd /src TB --- 2009-10-12 18:33:44 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 18:33:44 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/ia64/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 18:51:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 18:51:26 - ERROR: failed to build world TB --- 2009-10-12 18:51:26 - 811.99 user 156.52 system 1096.90 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 19:07:00 2009 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 0A3EB106566B; Mon, 12 Oct 2009 19:07:00 +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 BF34D8FC14; Mon, 12 Oct 2009 19:06:59 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CJ6xRq097311; Mon, 12 Oct 2009 15:06:59 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CJ6xjP097300; Mon, 12 Oct 2009 19:06:59 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 19:06:59 GMT Message-Id: <200910121906.n9CJ6xjP097300@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 mips/mips 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: Mon, 12 Oct 2009 19:07:00 -0000 TB --- 2009-10-12 18:51:26 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 18:51:26 - starting HEAD tinderbox run for mips/mips TB --- 2009-10-12 18:51:26 - cleaning the object tree TB --- 2009-10-12 18:51:32 - cvsupping the source tree TB --- 2009-10-12 18:51:32 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2009-10-12 18:51:57 - building world TB --- 2009-10-12 18:51:57 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 18:51:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 18:51:57 - TARGET=mips TB --- 2009-10-12 18:51:57 - TARGET_ARCH=mips TB --- 2009-10-12 18:51:57 - TZ=UTC TB --- 2009-10-12 18:51:57 - __MAKE_CONF=/dev/null TB --- 2009-10-12 18:51:57 - cd /src TB --- 2009-10-12 18:51:57 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 18:51:58 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O -pipe -EL -msoft-float -G0 -mno-dsp -mabicalls -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O -pipe -EL -msoft-float -G0 -mno-dsp -mabicalls -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/mips/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 19:06:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 19:06:59 - ERROR: failed to build world TB --- 2009-10-12 19:06:59 - 664.40 user 150.72 system 932.48 real http://tinderbox.des.no/tinderbox-head-HEAD-mips-mips.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 19:24:15 2009 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 5C771106566B; Mon, 12 Oct 2009 19:24:15 +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 1D8B18FC19; Mon, 12 Oct 2009 19:24:14 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CJOEPR037985; Mon, 12 Oct 2009 15:24:14 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CJOE4X037979; Mon, 12 Oct 2009 19:24:14 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 19:24:14 GMT Message-Id: <200910121924.n9CJOE4X037979@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: Mon, 12 Oct 2009 19:24:15 -0000 TB --- 2009-10-12 19:06:59 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 19:06:59 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-10-12 19:06:59 - cleaning the object tree TB --- 2009-10-12 19:07:06 - cvsupping the source tree TB --- 2009-10-12 19:07:06 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-10-12 19:07:31 - building world TB --- 2009-10-12 19:07:31 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 19:07:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 19:07:31 - TARGET=powerpc TB --- 2009-10-12 19:07:31 - TARGET_ARCH=powerpc TB --- 2009-10-12 19:07:31 - TZ=UTC TB --- 2009-10-12 19:07:31 - __MAKE_CONF=/dev/null TB --- 2009-10-12 19:07:31 - cd /src TB --- 2009-10-12 19:07:31 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 19:07:32 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/powerpc/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 19:24:14 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 19:24:14 - ERROR: failed to build world TB --- 2009-10-12 19:24:14 - 748.28 user 155.19 system 1035.12 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 19:25:16 2009 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 3487F1065672; Mon, 12 Oct 2009 19:25:16 +0000 (UTC) (envelope-from marius@alchemy.franken.de) Received: from alchemy.franken.de (alchemy.franken.de [194.94.249.214]) by mx1.freebsd.org (Postfix) with ESMTP id A4A4A8FC13; Mon, 12 Oct 2009 19:25:15 +0000 (UTC) Received: from alchemy.franken.de (localhost [127.0.0.1]) by alchemy.franken.de (8.14.3/8.14.3/ALCHEMY.FRANKEN.DE) with ESMTP id n9CJD5jl009555; Mon, 12 Oct 2009 21:13:05 +0200 (CEST) (envelope-from marius@alchemy.franken.de) Received: (from marius@localhost) by alchemy.franken.de (8.14.3/8.14.3/Submit) id n9CJD5Mv009554; Mon, 12 Oct 2009 21:13:05 +0200 (CEST) (envelope-from marius) Date: Mon, 12 Oct 2009 21:13:05 +0200 From: Marius Strobl To: Roman Divacky Message-ID: <20091012191305.GA9480@alchemy.franken.de> References: <20090924192103.GA84535@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090924192103.GA84535@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: [STATUS]: clang/llvm support on FreeBSD 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, 12 Oct 2009 19:25:16 -0000 On Thu, Sep 24, 2009 at 09:21:03PM +0200, Roman Divacky wrote: > Hi, > > The clang@freebsd team presents the status of clang/llvm being > able to compile FreeBSD system. The situation as of today > (Sep 24th) is: > > > i386 - kernel boots, world needs little hacks but works > > amd64 - kernel compiles but does not boot, world needs > little hacks > > ppc - broken because of unknown RTLD bug > > other - unknown > > > all other platforms are untested. Ie. this is a regression from the > situation in early spring when we could boot amd64 as well... > > A lot has happened over the spring/summer - amd64 got proper mcmodel=kernel > support, compiler-rt was introduced (paving the way for libgcc replacement), > we ran two experimental ports build to see how clang does there, C++ support > is able to parse devd.cc without warnings, we got kernel working with -O2, > we promoted FreeBSD to be officially supported plaform in LLVM etc. etc. > > We have problems though: we don't have manpower for testing (thats why amd64 > kernel stopped booting) and developers for integrating stuff into FreeBSD > (maintaining ports etc.). So if you are interested in helping please contact > me or join us on IRC in #freebsd-clang on irc.oftc.net. We especially need > amd64 testers (because of the amd64 kernel bug) and people with minor platforms > like arm/mips/sparc to see how clang/llvm performs there and improve that > situation. > Is there any progress on support for 64-bit SPARC-V9 in LLVM as required for sparc64? Marius From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 19:26:25 2009 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 A1EFF106568F for ; Mon, 12 Oct 2009 19:26:25 +0000 (UTC) (envelope-from marcus@freebsd.org) Received: from av-tac-rtp.cisco.com (hen.cisco.com [64.102.19.198]) by mx1.freebsd.org (Postfix) with ESMTP id 6B02D8FC20 for ; Mon, 12 Oct 2009 19:26:25 +0000 (UTC) X-TACSUNS: Virus Scanned Received: from rooster.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-rtp.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n9CJQNnW024258 for ; Mon, 12 Oct 2009 15:26:23 -0400 (EDT) Received: from dhcp-64-102-221-161.cisco.com (dhcp-64-102-221-161.cisco.com [64.102.221.161]) by rooster.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n9CJQNZR016692 for ; Mon, 12 Oct 2009 15:26:23 -0400 (EDT) Message-ID: <4AD382DF.3040105@freebsd.org> Date: Mon, 12 Oct 2009 15:26:23 -0400 From: Joe Marcus Clarke Organization: FreeBSD, Inc. User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812) MIME-Version: 1.0 To: current Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: sbsndptr panic on recent 9-CURRENT 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, 12 Oct 2009 19:26:25 -0000 I just upgraded to: FreeBSD jclarke-pc.cisco.com 9.0-CURRENT FreeBSD 9.0-CURRENT #6: Mon Oct 12 14:23:45 EDT 2009 marcus@jclarke-pc.cisco.com:/usr/obj/usr/src/sys/JCLARKE-PC i386 A few minutes after a reboot, I see: panic: sbsndptr: sockbuf 0xc5ba7c2c and mbuf 0xc5471300 clashing #3 0xc0667c1a in sbsndptr (sb=0xc5ba7c2c, off=Variable "off" is not available. ) at /usr/src/sys/kern/uipc_sockbuf.c:954 #4 0xc0755724 in tcp_output (tp=0xc5ab2000) at /usr/src/sys/netinet/tcp_output.c:814 #5 0xc0762b4a in tcp_usr_send (so=0xc5ba7b44, flags=0, m=0xc5471300, nam=0x0, control=0x0, td=0xc55ef8c0) at tcp_offload.h:282 #6 0xc066ded5 in sosend_generic (so=0xc5ba7b44, addr=0x0, uio=0xe7a62c58, top=0xc5471300, control=0x0, flags=0, td=0xc55ef8c0) at /usr/src/sys/kern/uipc_socket.c:1265 #7 0xc06697df in sosend (so=0xc5ba7b44, addr=0x0, uio=0xe7a62c58, top=0x0, control=0x0, flags=0, td=0xc55ef8c0) at /usr/src/sys/kern/uipc_socket.c:1309 #8 0xc064f343 in soo_write (fp=0xc5ad84d0, uio=0xe7a62c58, active_cred=0xc5bb4600, flags=0, td=0xc55ef8c0) at /usr/src/sys/kern/sys_socket.c:102 #9 0xc0648dd7 in dofilewrite (td=0xc55ef8c0, fd=3, fp=0xc5ad84d0, auio=0xe7a62c58, offset=-1, flags=0) at file.h:239 #10 0xc06490c8 in kern_writev (td=0xc55ef8c0, fd=3, auio=0xe7a62c58) at /usr/src/sys/kern/sys_generic.c:446 #11 0xc064914f in write (td=0xc55ef8c0, uap=0xe7a62cf8) at /usr/src/sys/kern/sys_generic.c:362 #12 0xc089f765 in syscall (frame=0xe7a62d38) at /usr/src/sys/i386/i386/trap.c:1078 #13 0xc0882440 in Xint0x80_syscall () at /usr/src/sys/i386/i386/exception.s:261 #14 0x00000033 in ?? () This machine uses em, gif, and PPP (tun) interfaces (with IPv4 and v6 addresses). I have since rebooted, so it may not be possible to provide many more details from this crash. However, if I see the crash again, is there anything more I should provide? Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 19:35:01 2009 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 79C31106568D; Mon, 12 Oct 2009 19:35:01 +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 3B6BB8FC14; Mon, 12 Oct 2009 19:35:00 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CJZ0CN015451; Mon, 12 Oct 2009 15:35:00 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CJZ0CH015449; Mon, 12 Oct 2009 19:35:00 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 19:35:00 GMT Message-Id: <200910121935.n9CJZ0CH015449@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: Mon, 12 Oct 2009 19:35:01 -0000 TB --- 2009-10-12 19:18:58 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 19:18:58 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2009-10-12 19:18:58 - cleaning the object tree TB --- 2009-10-12 19:19:05 - cvsupping the source tree TB --- 2009-10-12 19:19:05 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2009-10-12 19:19:29 - building world TB --- 2009-10-12 19:19:29 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 19:19:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 19:19:29 - TARGET=sparc64 TB --- 2009-10-12 19:19:29 - TARGET_ARCH=sparc64 TB --- 2009-10-12 19:19:29 - TZ=UTC TB --- 2009-10-12 19:19:29 - __MAKE_CONF=/dev/null TB --- 2009-10-12 19:19:29 - cd /src TB --- 2009-10-12 19:19:29 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 19:19:30 UTC 2009 >>> 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 [...] cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/sparc64/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 19:35:00 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 19:35:00 - ERROR: failed to build world TB --- 2009-10-12 19:35:00 - 680.11 user 150.86 system 961.63 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 19:40:01 2009 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 42532106566B; Mon, 12 Oct 2009 19:40:01 +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 F3DBA8FC15; Mon, 12 Oct 2009 19:40:00 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CJe0bk050058; Mon, 12 Oct 2009 15:40:00 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CJe0mH050057; Mon, 12 Oct 2009 19:40:00 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 19:40:00 GMT Message-Id: <200910121940.n9CJe0mH050057@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: Mon, 12 Oct 2009 19:40:01 -0000 TB --- 2009-10-12 19:24:14 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 19:24:14 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2009-10-12 19:24:14 - cleaning the object tree TB --- 2009-10-12 19:24:21 - cvsupping the source tree TB --- 2009-10-12 19:24:21 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2009-10-12 19:24:57 - building world TB --- 2009-10-12 19:24:57 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 19:24:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 19:24:57 - TARGET=sun4v TB --- 2009-10-12 19:24:57 - TARGET_ARCH=sparc64 TB --- 2009-10-12 19:24:57 - TZ=UTC TB --- 2009-10-12 19:24:57 - __MAKE_CONF=/dev/null TB --- 2009-10-12 19:24:57 - cd /src TB --- 2009-10-12 19:24:57 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 19:24:58 UTC 2009 >>> 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 [...] cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/sun4v/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 19:40:00 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 19:40:00 - ERROR: failed to build world TB --- 2009-10-12 19:40:00 - 677.78 user 150.29 system 945.77 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 20:53:21 2009 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 F2AD91065672 for ; Mon, 12 Oct 2009 20:53:21 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id AEC418FC15 for ; Mon, 12 Oct 2009 20:53:21 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 97E1E9CB0EA; Mon, 12 Oct 2009 22:52:56 +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 AFhsf3gg8nUf; Mon, 12 Oct 2009 22:52:54 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 400F39CB1FD; Mon, 12 Oct 2009 22:52:54 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id n9CKqsUT086806; Mon, 12 Oct 2009 22:52:54 +0200 (CEST) (envelope-from rdivacky) Date: Mon, 12 Oct 2009 22:52:54 +0200 From: Roman Divacky To: Marius Strobl Message-ID: <20091012205254.GA86649@freebsd.org> References: <20090924192103.GA84535@freebsd.org> <20091012191305.GA9480@alchemy.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091012191305.GA9480@alchemy.franken.de> User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: [STATUS]: clang/llvm support on FreeBSD 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, 12 Oct 2009 20:53:22 -0000 On Mon, Oct 12, 2009 at 09:13:05PM +0200, Marius Strobl wrote: > On Thu, Sep 24, 2009 at 09:21:03PM +0200, Roman Divacky wrote: > > Hi, > > > > The clang@freebsd team presents the status of clang/llvm being > > able to compile FreeBSD system. The situation as of today > > (Sep 24th) is: > > > > > > i386 - kernel boots, world needs little hacks but works > > > > amd64 - kernel compiles but does not boot, world needs > > little hacks > > > > ppc - broken because of unknown RTLD bug > > > > other - unknown > > > > > > all other platforms are untested. Ie. this is a regression from the > > situation in early spring when we could boot amd64 as well... > > > > A lot has happened over the spring/summer - amd64 got proper mcmodel=kernel > > support, compiler-rt was introduced (paving the way for libgcc replacement), > > we ran two experimental ports build to see how clang does there, C++ support > > is able to parse devd.cc without warnings, we got kernel working with -O2, > > we promoted FreeBSD to be officially supported plaform in LLVM etc. etc. > > > > We have problems though: we don't have manpower for testing (thats why amd64 > > kernel stopped booting) and developers for integrating stuff into FreeBSD > > (maintaining ports etc.). So if you are interested in helping please contact > > me or join us on IRC in #freebsd-clang on irc.oftc.net. We especially need > > amd64 testers (because of the amd64 kernel bug) and people with minor platforms > > like arm/mips/sparc to see how clang/llvm performs there and improve that > > situation. > > > > Is there any progress on support for 64-bit SPARC-V9 in LLVM as > required for sparc64? unfortunately no. at least I am not aware of any such effort From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 23:13:54 2009 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 9ACC91065670; Mon, 12 Oct 2009 23:13:54 +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 770C98FC14; Mon, 12 Oct 2009 23:13:54 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id EF42F46B03; Mon, 12 Oct 2009 19:13:53 -0400 (EDT) Date: Tue, 13 Oct 2009 00:13:53 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Joe Marcus Clarke In-Reply-To: <4AD382DF.3040105@freebsd.org> Message-ID: References: <4AD382DF.3040105@freebsd.org> 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 Subject: Re: sbsndptr panic on recent 9-CURRENT 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, 12 Oct 2009 23:13:54 -0000 On Mon, 12 Oct 2009, Joe Marcus Clarke wrote: > This machine uses em, gif, and PPP (tun) interfaces (with IPv4 and v6 > addresses). I have since rebooted, so it may not be possible to provide > many more details from this crash. However, if I see the crash again, is > there anything more I should provide? Looks like you have a crashdump, though. Could you paste into an e-mail dumps of various relevant variables, especially *so, *inp, *tp at various stack frames? Robert From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 23:42:24 2009 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 741B91065676; Mon, 12 Oct 2009 23:42:24 +0000 (UTC) (envelope-from marcus@FreeBSD.org) Received: from creme-brulee.marcuscom.com (marcuscom-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::1279]) by mx1.freebsd.org (Postfix) with ESMTP id EAFD58FC1C; Mon, 12 Oct 2009 23:42:23 +0000 (UTC) Received: from [IPv6:2001:470:1f00:2464::4] (shumai.marcuscom.com [IPv6:2001:470:1f00:2464::4]) by creme-brulee.marcuscom.com (8.14.3/8.14.3) with ESMTP id n9CNh5kB081461; Mon, 12 Oct 2009 19:43:05 -0400 (EDT) (envelope-from marcus@FreeBSD.org) From: Joe Marcus Clarke To: Robert Watson In-Reply-To: References: <4AD382DF.3040105@freebsd.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-Jh8aMCeeZ2raWFotW9Pl" Organization: FreeBSD, Inc. Date: Mon, 12 Oct 2009 19:42:35 -0400 Message-Id: <1255390955.22880.15.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on creme-brulee.marcuscom.com Cc: current Subject: Re: sbsndptr panic on recent 9-CURRENT 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, 12 Oct 2009 23:42:24 -0000 --=-Jh8aMCeeZ2raWFotW9Pl Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, 2009-10-13 at 00:13 +0100, Robert Watson wrote: > On Mon, 12 Oct 2009, Joe Marcus Clarke wrote: >=20 > > This machine uses em, gif, and PPP (tun) interfaces (with IPv4 and v6=20 > > addresses). I have since rebooted, so it may not be possible to provid= e=20 > > many more details from this crash. However, if I see the crash again, = is=20 > > there anything more I should provide? >=20 > Looks like you have a crashdump, though. Could you paste into an e-mail = dumps=20 > of various relevant variables, especially *so, *inp, *tp at various stack= =20 > frames? Yep: frame 3: print *sb: $1 =3D {sb_sel =3D {si_tdlist =3D {tqh_first =3D 0x0, tqh_last =3D 0x0}, si= _note =3D { kl_list =3D {slh_first =3D 0x0}, kl_lock =3D 0xc05d7f30 ,=20 kl_unlock =3D 0xc05d7ee0 ,=20 kl_assert_locked =3D 0xc05d50b0 ,=20 kl_assert_unlocked =3D 0xc05d50c0 ,=20 kl_lockarg =3D 0xc5ba7c50}, si_mtx =3D 0x0}, sb_mtx =3D {lock_object = =3D { lo_name =3D 0xc0902cd1 "so_snd", lo_flags =3D 16973824, lo_data =3D 0= ,=20 lo_witness =3D 0x0}, mtx_lock =3D 3311335616}, sb_sx =3D {lock_object= =3D { lo_name =3D 0xc09031f9 "so_snd_sx", lo_flags =3D 36896768, lo_data = =3D 0,=20 lo_witness =3D 0x0}, sx_lock =3D 3311335616}, sb_state =3D 0,=20 sb_mb =3D 0xc5471300, sb_mbtail =3D 0xc5471300, sb_lastrecord =3D 0xc5471= 300,=20 sb_sndptr =3D 0xc5471300, sb_sndptroff =3D 160, sb_cc =3D 224, sb_hiwat = =3D 33304,=20 sb_mbcnt =3D 256, sb_mcnt =3D 1, sb_ccnt =3D 0, sb_mbmax =3D 262144, sb_c= tl =3D 0,=20 sb_lowat =3D 2048, sb_timeo =3D 0, sb_flags =3D 2048, sb_upcall =3D 0,=20 sb_upcallarg =3D 0x0} frame 4: print *so: $3 =3D {so_count =3D 1, so_type =3D 1, so_options =3D 12, so_linger =3D 0, = so_state =3D 258, so_qstate =3D 0, so_pcb =3D 0xc5ab1000, so_vnet =3D 0x0, = so_proto =3D 0xc0956a48, so_head =3D 0x0, so_incomp =3D {tqh_first =3D 0x0,= tqh_last =3D 0x0}, so_comp =3D {tqh_first =3D 0x0, tqh_last =3D 0x0}, so_l= ist =3D {tqe_next =3D 0x0, tqe_prev =3D 0xc5779d08}, so_qlen =3D 0, so_incq= len =3D 0, so_qlimit =3D 0, so_timeo =3D 0, so_error =3D 0, so_sigio =3D 0x= 0, so_oobmark =3D 0, so_aiojobq =3D {tqh_first =3D 0x0, tqh_last =3D 0xc5ba= 7b90}, so_rcv =3D {sb_sel =3D {si_tdlist =3D {tqh_first =3D 0x0, tqh_last = =3D 0xc5ba7b98}, si_note =3D {kl_list =3D {slh_first =3D 0x0}, kl_lock =3D = 0xc05d7f30 , kl_unlock =3D 0xc05d7ee0 ,= kl_assert_locked =3D 0xc05d50b0 , kl_assert_unlo= cked =3D 0xc05d50c0 , kl_lockarg =3D 0xc5ba7bbc= }, si_mtx =3D 0xc55103f8}, sb_mtx =3D {lock_object =3D {lo_name =3D 0xc0902= cca "so_rcv", lo_flags =3D 16973824, lo_data =3D 0, lo_witness =3D 0x0}, mt= x_lock =3D 4}, sb_sx =3D {lock_object =3D {lo_name =3D 0xc0903203 "so_rcv_s= x", lo_flags =3D 36896768, lo_data =3D 0, lo_witness =3D 0x0}, sx_lock =3D = 1}, sb_state =3D 0, sb_mb =3D 0x0, sb_mbtail =3D 0x0, sb_lastrecord =3D 0x0= , sb_sndptr =3D 0x0, sb_sndptroff =3D 0, sb_cc =3D 0, sb_hiwat =3D 66608, s= b_mbcnt =3D 0, sb_mcnt =3D 0, sb_ccnt =3D 0, sb_mbmax =3D 262144, sb_ctl = =3D 0, sb_lowat =3D 1, sb_timeo =3D 0, sb_flags =3D 2056, sb_upcall =3D 0, = sb_upcallarg =3D 0x0}, so_snd =3D {sb_sel =3D {si_tdlist =3D {tqh_first =3D= 0x0, tqh_last =3D 0x0}, si_note =3D {kl_list =3D {slh_first =3D 0x0}, kl_l= ock =3D 0xc05d7f30 , kl_unlock =3D 0xc05d7ee0 , kl_assert_locked =3D 0xc05d50b0 , kl_ass= ert_unlocked =3D 0xc05d50c0 , kl_lockarg =3D 0x= c5ba7c50}, si_mtx =3D 0x0}, sb_mtx =3D {lock_object =3D {lo_name =3D 0xc090= 2cd1 "so_snd", lo_flags =3D 16973824, lo_data =3D 0, lo_witness =3D 0x0}, m= tx_lock =3D 3311335616}, sb_sx =3D {lock_object =3D {lo_name =3D 0xc09031f9= "so_snd_sx", lo_flags =3D 36896768, lo_data =3D 0, lo_witness =3D 0x0}, sx= _lock =3D 3311335616}, sb_state =3D 0, sb_mb =3D 0xc5471300, sb_mbtail =3D = 0xc5471300, sb_lastrecord =3D 0xc5471300, sb_sndptr =3D 0xc5471300, sb_sndp= troff =3D 160, sb_cc =3D 224, sb_hiwat =3D 33304, sb_mbcnt =3D 256, sb_mcnt= =3D 1, sb_ccnt =3D 0, sb_mbmax =3D 262144, sb_ctl =3D 0, sb_lowat =3D 2048= , sb_timeo =3D 0, sb_flags =3D 2048, sb_upcall =3D 0, sb_upcallarg =3D 0x0}= , so_cred =3D 0xc574a300, so_label =3D 0x0, so_peerlabel =3D 0x0, so_gencnt= =3D 672, so_emuldata =3D 0x0, so_accf =3D 0x0, so_fibnum =3D 0} print *tp $4 =3D {t_segq =3D {lh_first =3D 0x0}, t_pspare =3D {0x0, 0x0}, t_segqlen = =3D 0, t_dupacks =3D 0, t_timers =3D 0xc5ab21d8, t_inpcb =3D 0xc5ab1000, t_= state =3D 4, t_flags =3D 996, t_vnet =3D 0x0, snd_una =3D 345532936, snd_ma= x =3D 345533000, snd_nxt =3D 345533000, snd_up =3D 345532936, snd_wl1 =3D 8= 33432065, snd_wl2 =3D 345532936, iss =3D 345516135, irs =3D 833424923, rcv_= nxt =3D 833432113, rcv_adv =3D 833498721, rcv_wnd =3D 66608, rcv_up =3D 833= 432113, snd_wnd =3D 524280, snd_cwnd =3D 6472, snd_bwnd =3D 1073725440, snd= _ssthresh =3D 1073725440, snd_bandwidth =3D 0, snd_recover =3D 345532936, t= _maxopd =3D 1460, t_rcvtime =3D 161476, t_starttime =3D 45672, t_rtttime = =3D 161476, t_rtseq =3D 345532936, t_bw_rtttime =3D 45672, t_bw_rtseq =3D 0= , t_rxtcur =3D 230, t_maxseg =3D 1448, t_srtt =3D 48, t_rttvar =3D 9, t_rxt= shift =3D 0, t_rttmin =3D 30, t_rttbest =3D 53, t_rttupdated =3D 169, max_s= ndwnd =3D 524280, t_softerror =3D 0, t_oobflags =3D 0 '\0', t_iobc =3D 0 '\= 0', snd_scale =3D 3 '\003', rcv_scale =3D 3 '\003', request_r_scale =3D 3 '= \003', ts_recent =3D 467713397, ts_recent_age =3D 161476, ts_offset =3D 212= 9190315, last_ack_sent =3D 833432113, snd_cwnd_prev =3D 0, snd_ssthresh_pre= v =3D 0, snd_recover_prev =3D 0, t_badrxtwin =3D 0, snd_limited =3D 0 '\0',= snd_numholes =3D 0, snd_holes =3D {tqh_first =3D 0x0, tqh_last =3D 0xc5ab2= 0e4}, snd_fack =3D 0, rcv_numsacks =3D 0, sackblks =3D {{start =3D 0, end = =3D 0}, {start =3D 0, end =3D 0}, {start =3D 0, end =3D 0}, {start =3D 0, e= nd =3D 0}, {start =3D 0, end =3D 0}, {start =3D 0, end =3D 0}}, sack_newdat= a =3D 0, sackhint =3D {nexthole =3D 0x0, sack_bytes_rexmit =3D 0, ispare = =3D 0, _pad =3D {0, 0}}, t_rttlow =3D 1, rfbuf_ts =3D 161476, rfbuf_cnt =3D= 48, t_tu =3D 0x0, t_toe =3D 0x0, t_bytes_acked =3D 0, t_ispare =3D 0, t_ps= pare2 =3D {0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, _pad =3D {0 }} frame 5: print *so: $5 =3D {so_count =3D 1, so_type =3D 1, so_options =3D 12, so_linger =3D 0, = so_state =3D 258, so_qstate =3D 0, so_pcb =3D 0xc5ab1000, so_vnet =3D 0x0, = so_proto =3D 0xc0956a48, so_head =3D 0x0, so_incomp =3D {tqh_first =3D 0x0,= tqh_last =3D 0x0}, so_comp =3D {tqh_first =3D 0x0, tqh_last =3D 0x0}, so_l= ist =3D {tqe_next =3D 0x0, tqe_prev =3D 0xc5779d08}, so_qlen =3D 0, so_incq= len =3D 0, so_qlimit =3D 0, so_timeo =3D 0, so_error =3D 0, so_sigio =3D 0x= 0, so_oobmark =3D 0, so_aiojobq =3D {tqh_first =3D 0x0, tqh_last =3D 0xc5ba= 7b90}, so_rcv =3D {sb_sel =3D {si_tdlist =3D {tqh_first =3D 0x0, tqh_last = =3D 0xc5ba7b98}, si_note =3D {kl_list =3D {slh_first =3D 0x0}, kl_lock =3D = 0xc05d7f30 , kl_unlock =3D 0xc05d7ee0 ,= kl_assert_locked =3D 0xc05d50b0 , kl_assert_unlo= cked =3D 0xc05d50c0 , kl_lockarg =3D 0xc5ba7bbc= }, si_mtx =3D 0xc55103f8}, sb_mtx =3D {lock_object =3D {lo_name =3D 0xc0902= cca "so_rcv", lo_flags =3D 16973824, lo_data =3D 0, lo_witness =3D 0x0}, mt= x_lock =3D 4}, sb_sx =3D {lock_object =3D {lo_name =3D 0xc0903203 "so_rcv_s= x", lo_flags =3D 36896768, lo_data =3D 0, lo_witness =3D 0x0}, sx_lock =3D = 1}, sb_state =3D 0, sb_mb =3D 0x0, sb_mbtail =3D 0x0, sb_lastrecord =3D 0x0= , sb_sndptr =3D 0x0, sb_sndptroff =3D 0, sb_cc =3D 0, sb_hiwat =3D 66608, s= b_mbcnt =3D 0, sb_mcnt =3D 0, sb_ccnt =3D 0, sb_mbmax =3D 262144, sb_ctl = =3D 0, sb_lowat =3D 1, sb_timeo =3D 0, sb_flags =3D 2056, sb_upcall =3D 0, = sb_upcallarg =3D 0x0}, so_snd =3D {sb_sel =3D {si_tdlist =3D {tqh_first =3D= 0x0, tqh_last =3D 0x0}, si_note =3D {kl_list =3D {slh_first =3D 0x0}, kl_l= ock =3D 0xc05d7f30 , kl_unlock =3D 0xc05d7ee0 , kl_assert_locked =3D 0xc05d50b0 , kl_ass= ert_unlocked =3D 0xc05d50c0 , kl_lockarg =3D 0x= c5ba7c50}, si_mtx =3D 0x0}, sb_mtx =3D {lock_object =3D {lo_name =3D 0xc090= 2cd1 "so_snd", lo_flags =3D 16973824, lo_data =3D 0, lo_witness =3D 0x0}, m= tx_lock =3D 3311335616}, sb_sx =3D {lock_object =3D {lo_name =3D 0xc09031f9= "so_snd_sx", lo_flags =3D 36896768, lo_data =3D 0, lo_witness =3D 0x0}, sx= _lock =3D 3311335616}, sb_state =3D 0, sb_mb =3D 0xc5471300, sb_mbtail =3D = 0xc5471300, sb_lastrecord =3D 0xc5471300, sb_sndptr =3D 0xc5471300, sb_sndp= troff =3D 160, sb_cc =3D 224, sb_hiwat =3D 33304, sb_mbcnt =3D 256, sb_mcnt= =3D 1, sb_ccnt =3D 0, sb_mbmax =3D 262144, sb_ctl =3D 0, sb_lowat =3D 2048= , sb_timeo =3D 0, sb_flags =3D 2048, sb_upcall =3D 0, sb_upcallarg =3D 0x0}= , so_cred =3D 0xc574a300, so_label =3D 0x0, so_peerlabel =3D 0x0, so_gencnt= =3D 672, so_emuldata =3D 0x0, so_accf =3D 0x0, so_fibnum =3D 0} print *inp: $6 =3D {inp_hash =3D {le_next =3D 0x0, le_prev =3D 0xc5304294}, inp_list = =3D {le_next =3D 0xc5a487bc, le_prev =3D 0xc09a9a04}, inp_ppcb =3D 0xc5ab20= 00, inp_pcbinfo =3D 0xc09a9a20, inp_socket =3D 0xc5ba7b44, inp_cred =3D 0xc= 574a300, inp_flow =3D 0, inp_flags =3D 8396800, inp_flags2 =3D 0, inp_vflag= =3D 1 '\001', inp_ip_ttl =3D 64 '@', inp_ip_p =3D 0 '\0', inp_ip_minttl = =3D 0 '\0', inp_flowid =3D 0, inp_refcount =3D 1, inp_pspare =3D {0x0, 0x0,= 0x0, 0x0}, inp_ispare =3D {0, 0, 0, 0}, inp_inc =3D {inc_flags =3D 0 '\0',= inc_len =3D 0 '\0', inc_fibnum =3D 0, inc_ie =3D {ie_fport =3D 11973, ie_l= port =3D 5632, ie_dependfaddr =3D {ie46_foreign =3D {ia46_pad32 =3D {0, 0, = 0}, ia46_addr4 =3D {s_addr =3D 2715641408}}, ie6_foreign =3D {__u6_addr =3D= {__u6_addr8 =3D '\0' , "@f=DD=A1", __u6_addr16 =3D {0, 0= , 0, 0, 0, 0, 26176, 41437}, __u6_addr32 =3D {0, 0, 0, 2715641408}}}}, ie_d= ependladdr =3D {ie46_local =3D {ia46_pad32 =3D {0, 0, 0}, ia46_addr4 =3D {s= _addr =3D 3976073900}}, ie6_local =3D {__u6_addr =3D {__u6_addr8 =3D '\0' <= repeats 12 times>, "=EF=BF=BD\022=EF=BF=BD=EF=BF=BD", __u6_addr16 =3D {0, 0= , 0, 0, 0, 0, 4780, 60670}, __u6_addr32 =3D {0, 0, 0, 3976073900}}}}}}, inp= _label =3D 0x0, inp_sp =3D 0x0, inp_depend4 =3D {inp4_ip_tos =3D 16 '\020',= inp4_options =3D 0x0, inp4_moptions =3D 0x0}, inp_depend6 =3D {inp6_option= s =3D 0x0, inp6_outputopts =3D 0x0, inp6_moptions =3D 0x0, inp6_icmp6filt = =3D 0x0, inp6_cksum =3D 0, inp6_hops =3D 0}, inp_portlist =3D {le_next =3D = 0xc5a487bc, le_prev =3D 0xc54f8428}, inp_phd =3D 0xc54f8420, inp_gencnt =3D= 21, inp_lle =3D 0x0, inp_rt =3D 0x0, inp_lock =3D {lock_object =3D {lo_nam= e =3D 0xc090c024 "tcpinp", lo_flags =3D 74121216, lo_data =3D 0, lo_witness= =3D 0x0}, rw_lock =3D 3311335616}} print *tp: $7 =3D {t_segq =3D {lh_first =3D 0x0}, t_pspare =3D {0x0, 0x0}, t_segqlen = =3D 0, t_dupacks =3D 0, t_timers =3D 0xc5ab21d8, t_inpcb =3D 0xc5ab1000, t_= state =3D 4, t_flags =3D 996, t_vnet =3D 0x0, snd_una =3D 345532936, snd_ma= x =3D 345533000, snd_nxt =3D 345533000, snd_up =3D 345532936, snd_wl1 =3D 8= 33432065, snd_wl2 =3D 345532936, iss =3D 345516135, irs =3D 833424923, rcv_= nxt =3D 833432113, rcv_adv =3D 833498721, rcv_wnd =3D 66608, rcv_up =3D 833= 432113, snd_wnd =3D 524280, snd_cwnd =3D 6472, snd_bwnd =3D 1073725440, snd= _ssthresh =3D 1073725440, snd_bandwidth =3D 0, snd_recover =3D 345532936, t= _maxopd =3D 1460, t_rcvtime =3D 161476, t_starttime =3D 45672, t_rtttime = =3D 161476, t_rtseq =3D 345532936, t_bw_rtttime =3D 45672, t_bw_rtseq =3D 0= , t_rxtcur =3D 230, t_maxseg =3D 1448, t_srtt =3D 48, t_rttvar =3D 9, t_rxt= shift =3D 0, t_rttmin =3D 30, t_rttbest =3D 53, t_rttupdated =3D 169, max_s= ndwnd =3D 524280, t_softerror =3D 0, t_oobflags =3D 0 '\0', t_iobc =3D 0 '\= 0', snd_scale =3D 3 '\003', rcv_scale =3D 3 '\003', request_r_scale =3D 3 '= \003', ts_recent =3D 467713397, ts_recent_age =3D 161476, ts_offset =3D 212= 9190315, last_ack_sent =3D 833432113, snd_cwnd_prev =3D 0, snd_ssthresh_pre= v =3D 0, snd_recover_prev =3D 0, t_badrxtwin =3D 0, snd_limited =3D 0 '\0',= snd_numholes =3D 0, snd_holes =3D {tqh_first =3D 0x0, tqh_last =3D 0xc5ab2= 0e4}, snd_fack =3D 0, rcv_numsacks =3D 0, sackblks =3D {{start =3D 0, end = =3D 0}, {start =3D 0, end =3D 0}, {start =3D 0, end =3D 0}, {start =3D 0, e= nd =3D 0}, {start =3D 0, end =3D 0}, {start =3D 0, end =3D 0}}, sack_newdat= a =3D 0, sackhint =3D {nexthole =3D 0x0, sack_bytes_rexmit =3D 0, ispare = =3D 0, _pad =3D {0, 0}}, t_rttlow =3D 1, rfbuf_ts =3D 161476, rfbuf_cnt =3D= 48, t_tu =3D 0x0, t_toe =3D 0x0, t_bytes_acked =3D 0, t_ispare =3D 0, t_ps= pare2 =3D {0x0, 0x0, 0x0, 0x0, 0x0, 0x0}, _pad =3D {0 }} frame 6: print *so: $8 =3D {so_count =3D 1, so_type =3D 1, so_options =3D 12, so_linger =3D 0, = so_state =3D 258, so_qstate =3D 0, so_pcb =3D 0xc5ab1000, so_vnet =3D 0x0, = so_proto =3D 0xc0956a48, so_head =3D 0x0, so_incomp =3D {tqh_first =3D 0x0,= tqh_last =3D 0x0}, so_comp =3D {tqh_first =3D 0x0, tqh_last =3D 0x0}, so_l= ist =3D {tqe_next =3D 0x0, tqe_prev =3D 0xc5779d08}, so_qlen =3D 0, so_incq= len =3D 0, so_qlimit =3D 0, so_timeo =3D 0, so_error =3D 0, so_sigio =3D 0x= 0, so_oobmark =3D 0, so_aiojobq =3D {tqh_first =3D 0x0, tqh_last =3D 0xc5ba= 7b90}, so_rcv =3D {sb_sel =3D {si_tdlist =3D {tqh_first =3D 0x0, tqh_last = =3D 0xc5ba7b98}, si_note =3D {kl_list =3D {slh_first =3D 0x0}, kl_lock =3D = 0xc05d7f30 , kl_unlock =3D 0xc05d7ee0 ,= kl_assert_locked =3D 0xc05d50b0 , kl_assert_unlo= cked =3D 0xc05d50c0 , kl_lockarg =3D 0xc5ba7bbc= }, si_mtx =3D 0xc55103f8}, sb_mtx =3D {lock_object =3D {lo_name =3D 0xc0902= cca "so_rcv", lo_flags =3D 16973824, lo_data =3D 0, lo_witness =3D 0x0}, mt= x_lock =3D 4}, sb_sx =3D {lock_object =3D {lo_name =3D 0xc0903203 "so_rcv_s= x", lo_flags =3D 36896768, lo_data =3D 0, lo_witness =3D 0x0}, sx_lock =3D = 1}, sb_state =3D 0, sb_mb =3D 0x0, sb_mbtail =3D 0x0, sb_lastrecord =3D 0x0= , sb_sndptr =3D 0x0, sb_sndptroff =3D 0, sb_cc =3D 0, sb_hiwat =3D 66608, s= b_mbcnt =3D 0, sb_mcnt =3D 0, sb_ccnt =3D 0, sb_mbmax =3D 262144, sb_ctl = =3D 0, sb_lowat =3D 1, sb_timeo =3D 0, sb_flags =3D 2056, sb_upcall =3D 0, = sb_upcallarg =3D 0x0}, so_snd =3D {sb_sel =3D {si_tdlist =3D {tqh_first =3D= 0x0, tqh_last =3D 0x0}, si_note =3D {kl_list =3D {slh_first =3D 0x0}, kl_l= ock =3D 0xc05d7f30 , kl_unlock =3D 0xc05d7ee0 , kl_assert_locked =3D 0xc05d50b0 , kl_ass= ert_unlocked =3D 0xc05d50c0 , kl_lockarg =3D 0x= c5ba7c50}, si_mtx =3D 0x0}, sb_mtx =3D {lock_object =3D {lo_name =3D 0xc090= 2cd1 "so_snd", lo_flags =3D 16973824, lo_data =3D 0, lo_witness =3D 0x0}, m= tx_lock =3D 3311335616}, sb_sx =3D {lock_object =3D {lo_name =3D 0xc09031f9= "so_snd_sx", lo_flags =3D 36896768, lo_data =3D 0, lo_witness =3D 0x0}, sx= _lock =3D 3311335616}, sb_state =3D 0, sb_mb =3D 0xc5471300, sb_mbtail =3D = 0xc5471300, sb_lastrecord =3D 0xc5471300, sb_sndptr =3D 0xc5471300, sb_sndp= troff =3D 160, sb_cc =3D 224, sb_hiwat =3D 33304, sb_mbcnt =3D 256, sb_mcnt= =3D 1, sb_ccnt =3D 0, sb_mbmax =3D 262144, sb_ctl =3D 0, sb_lowat =3D 2048= , sb_timeo =3D 0, sb_flags =3D 2048, sb_upcall =3D 0, sb_upcallarg =3D 0x0}= , so_cred =3D 0xc574a300, so_label =3D 0x0, so_peerlabel =3D 0x0, so_gencnt= =3D 672, so_emuldata =3D 0x0, so_accf =3D 0x0, so_fibnum =3D 0} frame 7: print *so: $9 =3D {so_count =3D 1, so_type =3D 1, so_options =3D 12, so_linger =3D 0, = so_state =3D 258, so_qstate =3D 0, so_pcb =3D 0xc5ab1000, so_vnet =3D 0x0, = so_proto =3D 0xc0956a48, so_head =3D 0x0, so_incomp =3D {tqh_first =3D 0x0,= tqh_last =3D 0x0}, so_comp =3D {tqh_first =3D 0x0, tqh_last =3D 0x0}, so_l= ist =3D {tqe_next =3D 0x0, tqe_prev =3D 0xc5779d08}, so_qlen =3D 0, so_incq= len =3D 0, so_qlimit =3D 0, so_timeo =3D 0, so_error =3D 0, so_sigio =3D 0x= 0, so_oobmark =3D 0, so_aiojobq =3D {tqh_first =3D 0x0, tqh_last =3D 0xc5ba= 7b90}, so_rcv =3D {sb_sel =3D {si_tdlist =3D {tqh_first =3D 0x0, tqh_last = =3D 0xc5ba7b98}, si_note =3D {kl_list =3D {slh_first =3D 0x0}, kl_lock =3D = 0xc05d7f30 , kl_unlock =3D 0xc05d7ee0 ,= kl_assert_locked =3D 0xc05d50b0 , kl_assert_unlo= cked =3D 0xc05d50c0 , kl_lockarg =3D 0xc5ba7bbc= }, si_mtx =3D 0xc55103f8}, sb_mtx =3D {lock_object =3D {lo_name =3D 0xc0902= cca "so_rcv", lo_flags =3D 16973824, lo_data =3D 0, lo_witness =3D 0x0}, mt= x_lock =3D 4}, sb_sx =3D {lock_object =3D {lo_name =3D 0xc0903203 "so_rcv_s= x", lo_flags =3D 36896768, lo_data =3D 0, lo_witness =3D 0x0}, sx_lock =3D = 1}, sb_state =3D 0, sb_mb =3D 0x0, sb_mbtail =3D 0x0, sb_lastrecord =3D 0x0= , sb_sndptr =3D 0x0, sb_sndptroff =3D 0, sb_cc =3D 0, sb_hiwat =3D 66608, s= b_mbcnt =3D 0, sb_mcnt =3D 0, sb_ccnt =3D 0, sb_mbmax =3D 262144, sb_ctl = =3D 0, sb_lowat =3D 1, sb_timeo =3D 0, sb_flags =3D 2056, sb_upcall =3D 0, = sb_upcallarg =3D 0x0}, so_snd =3D {sb_sel =3D {si_tdlist =3D {tqh_first =3D= 0x0, tqh_last =3D 0x0}, si_note =3D {kl_list =3D {slh_first =3D 0x0}, kl_l= ock =3D 0xc05d7f30 , kl_unlock =3D 0xc05d7ee0 , kl_assert_locked =3D 0xc05d50b0 , kl_ass= ert_unlocked =3D 0xc05d50c0 , kl_lockarg =3D 0x= c5ba7c50}, si_mtx =3D 0x0}, sb_mtx =3D {lock_object =3D {lo_name =3D 0xc090= 2cd1 "so_snd", lo_flags =3D 16973824, lo_data =3D 0, lo_witness =3D 0x0}, m= tx_lock =3D 3311335616}, sb_sx =3D {lock_object =3D {lo_name =3D 0xc09031f9= "so_snd_sx", lo_flags =3D 36896768, lo_data =3D 0, lo_witness =3D 0x0}, sx= _lock =3D 3311335616}, sb_state =3D 0, sb_mb =3D 0xc5471300, sb_mbtail =3D = 0xc5471300, sb_lastrecord =3D 0xc5471300, sb_sndptr =3D 0xc5471300, sb_sndp= troff =3D 160, sb_cc =3D 224, sb_hiwat =3D 33304, sb_mbcnt =3D 256, sb_mcnt= =3D 1, sb_ccnt =3D 0, sb_mbmax =3D 262144, sb_ctl =3D 0, sb_lowat =3D 2048= , sb_timeo =3D 0, sb_flags =3D 2048, sb_upcall =3D 0, sb_upcallarg =3D 0x0}= , so_cred =3D 0xc574a300, so_label =3D 0x0, so_peerlabel =3D 0x0, so_gencnt= =3D 672, so_emuldata =3D 0x0, so_accf =3D 0x0, so_fibnum =3D 0} Joe >=20 > Robert >=20 --=20 Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome --=-Jh8aMCeeZ2raWFotW9Pl Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEABECAAYFAkrTvukACgkQb2iPiv4Uz4fT3wCfQHJJ7/PiEQruGwrYszWEfT9S 8Z0An0VmNi/55RM3PACHB0o8iGHN2OI2 =HhnI -----END PGP SIGNATURE----- --=-Jh8aMCeeZ2raWFotW9Pl-- From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 23:44:47 2009 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 04DE11065672; Mon, 12 Oct 2009 23:44:47 +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 BA5C58FC22; Mon, 12 Oct 2009 23:44:46 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CNijju037646; Mon, 12 Oct 2009 19:44:45 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CNijv9037645; Mon, 12 Oct 2009 23:44:45 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 23:44:45 GMT Message-Id: <200910122344.n9CNijv9037645@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 arm/arm 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: Mon, 12 Oct 2009 23:44:47 -0000 TB --- 2009-10-12 23:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 23:30:00 - starting HEAD tinderbox run for arm/arm TB --- 2009-10-12 23:30:00 - cleaning the object tree TB --- 2009-10-12 23:30:11 - cvsupping the source tree TB --- 2009-10-12 23:30:11 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2009-10-12 23:30:42 - building world TB --- 2009-10-12 23:30:42 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 23:30:42 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 23:30:42 - TARGET=arm TB --- 2009-10-12 23:30:42 - TARGET_ARCH=arm TB --- 2009-10-12 23:30:42 - TZ=UTC TB --- 2009-10-12 23:30:42 - __MAKE_CONF=/dev/null TB --- 2009-10-12 23:30:42 - cd /src TB --- 2009-10-12 23:30:42 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 23:30:42 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/arm/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 23:44:45 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 23:44:45 - ERROR: failed to build world TB --- 2009-10-12 23:44:45 - 645.96 user 159.28 system 885.73 real http://tinderbox.des.no/tinderbox-head-HEAD-arm-arm.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 23:46:57 2009 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 8AB5F1065676; Mon, 12 Oct 2009 23:46:57 +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 4B5CE8FC22; Mon, 12 Oct 2009 23:46:57 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CNku9X072635; Mon, 12 Oct 2009 19:46:56 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CNkui1072625; Mon, 12 Oct 2009 23:46:56 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 23:46:56 GMT Message-Id: <200910122346.n9CNkui1072625@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: Mon, 12 Oct 2009 23:46:57 -0000 TB --- 2009-10-12 23:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 23:30:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2009-10-12 23:30:00 - cleaning the object tree TB --- 2009-10-12 23:30:19 - cvsupping the source tree TB --- 2009-10-12 23:30:19 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2009-10-12 23:30:47 - building world TB --- 2009-10-12 23:30:47 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 23:30:47 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 23:30:47 - TARGET=pc98 TB --- 2009-10-12 23:30:47 - TARGET_ARCH=i386 TB --- 2009-10-12 23:30:47 - TZ=UTC TB --- 2009-10-12 23:30:47 - __MAKE_CONF=/dev/null TB --- 2009-10-12 23:30:47 - cd /src TB --- 2009-10-12 23:30:47 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 23:30:48 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/pc98/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 23:46:56 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 23:46:56 - ERROR: failed to build world TB --- 2009-10-12 23:46:56 - 740.84 user 166.48 system 1016.52 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 23:52:34 2009 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 97BAD106566B; Mon, 12 Oct 2009 23:52: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 590588FC12; Mon, 12 Oct 2009 23:52:33 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CNqXuu014827; Mon, 12 Oct 2009 19:52:33 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CNqXDO014823; Mon, 12 Oct 2009 23:52:33 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 23:52:33 GMT Message-Id: <200910122352.n9CNqXDO014823@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: Mon, 12 Oct 2009 23:52:34 -0000 TB --- 2009-10-12 23:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 23:30:00 - starting HEAD tinderbox run for i386/i386 TB --- 2009-10-12 23:30:00 - cleaning the object tree TB --- 2009-10-12 23:30:22 - cvsupping the source tree TB --- 2009-10-12 23:30:22 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2009-10-12 23:36:00 - building world TB --- 2009-10-12 23:36:00 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 23:36:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 23:36:00 - TARGET=i386 TB --- 2009-10-12 23:36:00 - TARGET_ARCH=i386 TB --- 2009-10-12 23:36:00 - TZ=UTC TB --- 2009-10-12 23:36:00 - __MAKE_CONF=/dev/null TB --- 2009-10-12 23:36:00 - cd /src TB --- 2009-10-12 23:36:00 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 23:36:01 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/i386/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 23:52:33 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 23:52:33 - ERROR: failed to build world TB --- 2009-10-12 23:52:33 - 746.54 user 167.70 system 1353.45 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Mon Oct 12 23:53:26 2009 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 18A4F106566B; Mon, 12 Oct 2009 23:53:26 +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 CDF6A8FC19; Mon, 12 Oct 2009 23:53:25 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9CNrP1n021798; Mon, 12 Oct 2009 19:53:25 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9CNrPiS021777; Mon, 12 Oct 2009 23:53:25 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 12 Oct 2009 23:53:25 GMT Message-Id: <200910122353.n9CNrPiS021777@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: Mon, 12 Oct 2009 23:53:26 -0000 TB --- 2009-10-12 23:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 23:30:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2009-10-12 23:30:00 - cleaning the object tree TB --- 2009-10-12 23:30:24 - cvsupping the source tree TB --- 2009-10-12 23:30:24 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile TB --- 2009-10-12 23:36:00 - building world TB --- 2009-10-12 23:36:00 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 23:36:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 23:36:00 - TARGET=amd64 TB --- 2009-10-12 23:36:00 - TARGET_ARCH=amd64 TB --- 2009-10-12 23:36:00 - TZ=UTC TB --- 2009-10-12 23:36:00 - __MAKE_CONF=/dev/null TB --- 2009-10-12 23:36:00 - cd /src TB --- 2009-10-12 23:36:00 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 23:36:01 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-12 23:53:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-12 23:53:25 - ERROR: failed to build world TB --- 2009-10-12 23:53:25 - 782.88 user 178.35 system 1405.22 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 00:02:38 2009 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 BADFD106566B; Tue, 13 Oct 2009 00:02:38 +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 7994C8FC08; Tue, 13 Oct 2009 00:02:38 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D02buW015534; Mon, 12 Oct 2009 20:02:37 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D02beC015527; Tue, 13 Oct 2009 00:02:37 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 00:02:37 GMT Message-Id: <200910130002.n9D02beC015527@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 mips/mips 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, 13 Oct 2009 00:02:38 -0000 TB --- 2009-10-12 23:46:57 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 23:46:57 - starting HEAD tinderbox run for mips/mips TB --- 2009-10-12 23:46:57 - cleaning the object tree TB --- 2009-10-12 23:47:00 - cvsupping the source tree TB --- 2009-10-12 23:47:00 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2009-10-12 23:47:23 - building world TB --- 2009-10-12 23:47:23 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 23:47:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 23:47:23 - TARGET=mips TB --- 2009-10-12 23:47:23 - TARGET_ARCH=mips TB --- 2009-10-12 23:47:23 - TZ=UTC TB --- 2009-10-12 23:47:23 - __MAKE_CONF=/dev/null TB --- 2009-10-12 23:47:23 - cd /src TB --- 2009-10-12 23:47:23 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 23:47:23 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O -pipe -EL -msoft-float -G0 -mno-dsp -mabicalls -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O -pipe -EL -msoft-float -G0 -mno-dsp -mabicalls -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/mips/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 00:02:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 00:02:37 - ERROR: failed to build world TB --- 2009-10-13 00:02:37 - 663.36 user 153.65 system 940.77 real http://tinderbox.des.no/tinderbox-head-HEAD-mips-mips.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 00:02:42 2009 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 7A41D1065676; Tue, 13 Oct 2009 00:02:42 +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 3AB888FC0A; Tue, 13 Oct 2009 00:02:42 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D02frI015864; Mon, 12 Oct 2009 20:02:41 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D02fVh015854; Tue, 13 Oct 2009 00:02:41 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 00:02:41 GMT Message-Id: <200910130002.n9D02fVh015854@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: Tue, 13 Oct 2009 00:02:42 -0000 TB --- 2009-10-12 23:44:46 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 23:44:46 - starting HEAD tinderbox run for ia64/ia64 TB --- 2009-10-12 23:44:46 - cleaning the object tree TB --- 2009-10-12 23:44:49 - cvsupping the source tree TB --- 2009-10-12 23:44:49 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2009-10-12 23:45:14 - building world TB --- 2009-10-12 23:45:14 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 23:45:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 23:45:14 - TARGET=ia64 TB --- 2009-10-12 23:45:14 - TARGET_ARCH=ia64 TB --- 2009-10-12 23:45:14 - TZ=UTC TB --- 2009-10-12 23:45:14 - __MAKE_CONF=/dev/null TB --- 2009-10-12 23:45:14 - cd /src TB --- 2009-10-12 23:45:14 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 23:45:14 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/ia64/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 00:02:41 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 00:02:41 - ERROR: failed to build world TB --- 2009-10-13 00:02:41 - 814.25 user 157.41 system 1075.65 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 00:08:43 2009 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 2567A1065670; Tue, 13 Oct 2009 00:08:43 +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 DA3258FC15; Tue, 13 Oct 2009 00:08:42 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D08gKd061100; Mon, 12 Oct 2009 20:08:42 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D08gsb061099; Tue, 13 Oct 2009 00:08:42 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 00:08:42 GMT Message-Id: <200910130008.n9D08gsb061099@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: Tue, 13 Oct 2009 00:08:43 -0000 TB --- 2009-10-12 23:53:25 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 23:53:25 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2009-10-12 23:53:25 - cleaning the object tree TB --- 2009-10-12 23:53:29 - cvsupping the source tree TB --- 2009-10-12 23:53:29 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2009-10-12 23:53:52 - building world TB --- 2009-10-12 23:53:52 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 23:53:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 23:53:52 - TARGET=sparc64 TB --- 2009-10-12 23:53:52 - TARGET_ARCH=sparc64 TB --- 2009-10-12 23:53:52 - TZ=UTC TB --- 2009-10-12 23:53:52 - __MAKE_CONF=/dev/null TB --- 2009-10-12 23:53:52 - cd /src TB --- 2009-10-12 23:53:52 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 23:53:53 UTC 2009 >>> 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 [...] cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/sparc64/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 00:08:42 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 00:08:42 - ERROR: failed to build world TB --- 2009-10-13 00:08:42 - 679.28 user 154.27 system 916.70 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 00:08:53 2009 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 2FC5D1065676; Tue, 13 Oct 2009 00:08:52 +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 E42738FC19; Tue, 13 Oct 2009 00:08:51 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D08p8E061368; Mon, 12 Oct 2009 20:08:51 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D08pC8061367; Tue, 13 Oct 2009 00:08:51 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 00:08:51 GMT Message-Id: <200910130008.n9D08pC8061367@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: Tue, 13 Oct 2009 00:08:53 -0000 TB --- 2009-10-12 23:52:33 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-12 23:52:33 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-10-12 23:52:33 - cleaning the object tree TB --- 2009-10-12 23:52:37 - cvsupping the source tree TB --- 2009-10-12 23:52:37 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-10-12 23:52:59 - building world TB --- 2009-10-12 23:52:59 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-12 23:52:59 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-12 23:52:59 - TARGET=powerpc TB --- 2009-10-12 23:52:59 - TARGET_ARCH=powerpc TB --- 2009-10-12 23:52:59 - TZ=UTC TB --- 2009-10-12 23:52:59 - __MAKE_CONF=/dev/null TB --- 2009-10-12 23:52:59 - cd /src TB --- 2009-10-12 23:52:59 - /usr/bin/make -B buildworld >>> World build started on Mon Oct 12 23:53:00 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/powerpc/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 00:08:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 00:08:51 - ERROR: failed to build world TB --- 2009-10-13 00:08:51 - 744.22 user 158.32 system 977.60 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 00:16:56 2009 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 58BC11065672; Tue, 13 Oct 2009 00:16:56 +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 198168FC16; Tue, 13 Oct 2009 00:16:55 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D0GtH4085237; Mon, 12 Oct 2009 20:16:55 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D0Gtk6085236; Tue, 13 Oct 2009 00:16:55 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 00:16:55 GMT Message-Id: <200910130016.n9D0Gtk6085236@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: Tue, 13 Oct 2009 00:16:56 -0000 TB --- 2009-10-13 00:02:38 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-13 00:02:38 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2009-10-13 00:02:38 - cleaning the object tree TB --- 2009-10-13 00:02:41 - cvsupping the source tree TB --- 2009-10-13 00:02:41 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2009-10-13 00:03:05 - building world TB --- 2009-10-13 00:03:05 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-13 00:03:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-13 00:03:05 - TARGET=sun4v TB --- 2009-10-13 00:03:05 - TARGET_ARCH=sparc64 TB --- 2009-10-13 00:03:05 - TZ=UTC TB --- 2009-10-13 00:03:05 - __MAKE_CONF=/dev/null TB --- 2009-10-13 00:03:05 - cd /src TB --- 2009-10-13 00:03:05 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 13 00:03:06 UTC 2009 >>> 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 [...] cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/sun4v/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 00:16:55 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 00:16:55 - ERROR: failed to build world TB --- 2009-10-13 00:16:55 - 682.57 user 145.23 system 857.38 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 00:43:04 2009 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 C636C106568F; Tue, 13 Oct 2009 00:43:04 +0000 (UTC) (envelope-from franson@gmail.com) Received: from mail-iw0-f189.google.com (mail-iw0-f189.google.com [209.85.223.189]) by mx1.freebsd.org (Postfix) with ESMTP id 6FF728FC1A; Tue, 13 Oct 2009 00:43:04 +0000 (UTC) Received: by iwn27 with SMTP id 27so4750722iwn.7 for ; Mon, 12 Oct 2009 17:43:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=GbigGXlKR8qqZz0vxufZFx/DJeFhIjRb4gW+LNjZTLA=; b=ZnW3Px+MLbjgHJLUsBblsuB4ajYxRaP2ZVX5LHsuKtvf0tzyiBYRkOxD7hJwn15FEA aNs3J+bLDvA2hVy3h5pMeDoPEYlzd9jZWQTW8QgEWTZVIFRy6kZHuGs5czxKJyQLMHW/ VwyzsxcS4P82TAYrbWuo9lT4O1PxHlYohWhu8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=hOqSDP7PvkhuPTgy/r98ivgwIqZoXZ+zZb7Gmv+k1bSgfZIx6IGHQNyWI5qCDLOPyN IkY1duFFZ5cHqydFvqNWtr8JFHOl4Cxz/Mm8pt1xfJjGTTIY2QOq+BFx4pWVZKREctNu 624KaEh6R/hilVzRN5XgPpvaCmOAijELAi8yU= MIME-Version: 1.0 Sender: franson@gmail.com Received: by 10.231.121.93 with SMTP id g29mr9842738ibr.13.1255393147008; Mon, 12 Oct 2009 17:19:07 -0700 (PDT) In-Reply-To: <200910122344.n9CNijv9037645@freebsd-current.sentex.ca> References: <200910122344.n9CNijv9037645@freebsd-current.sentex.ca> Date: Tue, 13 Oct 2009 08:19:06 +0800 X-Google-Sender-Auth: b1d7dfc81ac29ac4 Message-ID: From: quickembed To: FreeBSD Tinderbox Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 13 Oct 2009 01:15:03 +0000 Cc: arm@freebsd.org, current@freebsd.org Subject: Re: [head tinderbox] failure on arm/arm 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, 13 Oct 2009 00:43:04 -0000 this error shows you have not indicate how to compile libgssapi.a file. CC is for .c file, you need to tell what's for .a (assembly) file. On Tue, Oct 13, 2009 at 7:44 AM, FreeBSD Tinderbox wrote: > TB --- 2009-10-12 23:30:00 - tinderbox 2.6 running on freebsd-current.sen= tex.ca > TB --- 2009-10-12 23:30:00 - starting HEAD tinderbox run for arm/arm > TB --- 2009-10-12 23:30:00 - cleaning the object tree > TB --- 2009-10-12 23:30:11 - cvsupping the source tree > TB --- 2009-10-12 23:30:11 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sente= x.ca /tinderbox/HEAD/arm/arm/supfile > TB --- 2009-10-12 23:30:42 - building world > TB --- 2009-10-12 23:30:42 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2009-10-12 23:30:42 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2009-10-12 23:30:42 - TARGET=3Darm > TB --- 2009-10-12 23:30:42 - TARGET_ARCH=3Darm > TB --- 2009-10-12 23:30:42 - TZ=3DUTC > TB --- 2009-10-12 23:30:42 - __MAKE_CONF=3D/dev/null > TB --- 2009-10-12 23:30:42 - cd /src > TB --- 2009-10-12 23:30:42 - /usr/bin/make -B buildworld >>>> World build started on Mon Oct 12 23:30:42 UTC 2009 >>>> 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 > [...] > cc -fpic -DPIC -O -pipe =A0-I/src/kerberos5/lib/libgssapi_krb5/../../../c= rypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypt= o/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../cryp= to/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/hei= mdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/l= ib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../incl= ude -std=3Dgnu99 =A0-c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/he= imdal/lib/gssapi/krb5/wrap.c -o wrap.So > cc -fpic -DPIC -O -pipe =A0-I/src/kerberos5/lib/libgssapi_krb5/../../../c= rypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypt= o/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../cryp= to/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/hei= mdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/l= ib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../incl= ude -std=3Dgnu99 =A0-c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_= krb5.So > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extrac= t_authz_data_from_sec_context': > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit decla= ration of function 'der_get_oid' > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit decla= ration of function 'der_free_oid' > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit decla= ration of function 'der_length_oid' > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit decla= ration of function 'der_put_oid' > make: don't know how to make /obj/arm/src/tmp/usr/lib/libgssapi.a. Stop > *** Error code 2 > > Stop in /src. > *** Error code 1 > > Stop in /src. > *** Error code 1 > > Stop in /src. > *** Error code 1 > > Stop in /src. > TB --- 2009-10-12 23:44:45 - WARNING: /usr/bin/make returned exit code = =A01 > TB --- 2009-10-12 23:44:45 - ERROR: failed to build world > TB --- 2009-10-12 23:44:45 - 645.96 user 159.28 system 885.73 real > > > http://tinderbox.des.no/tinderbox-head-HEAD-arm-arm.full > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 00:45:26 2009 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 EB75F1065676; Tue, 13 Oct 2009 00:45:26 +0000 (UTC) (envelope-from bland@bbnest.net) Received: from mail2.asahi-net.or.jp (mail2.asahi-net.or.jp [202.224.39.198]) by mx1.freebsd.org (Postfix) with ESMTP id B878B8FC1C; Tue, 13 Oct 2009 00:45:26 +0000 (UTC) Received: from hub.bbnest.net (w133033.ppp.asahi-net.or.jp [121.1.133.33]) by mail2.asahi-net.or.jp (Postfix) with ESMTP id 037DB822FE; Tue, 13 Oct 2009 09:25:41 +0900 (JST) Received: from nest.bbnest.net (nest.bbnest.net [10.0.0.249]) by hub.bbnest.net (8.14.3/8.14.3) with ESMTP id n9D0PdGO008758 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 13 Oct 2009 09:25:39 +0900 (JST) (envelope-from bland@bbnest.net) Mime-Version: 1.0 (Apple Message framework v1076) Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes From: Alexander Nedotsukov In-Reply-To: <200910122352.n9CNqXDO014823@freebsd-current.sentex.ca> Date: Tue, 13 Oct 2009 09:25:39 +0900 Content-Transfer-Encoding: 7bit Message-Id: <8208113B-5BD3-4606-B6D3-6C19931B0E23@bbnest.net> References: <200910122352.n9CNqXDO014823@freebsd-current.sentex.ca> To: FreeBSD Tinderbox X-Mailer: Apple Mail (2.1076) X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Tue Oct 13 09:25:41 2009 X-DSPAM-Confidence: 0.9994 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4ad3c90587591610688996 X-Mailman-Approved-At: Tue, 13 Oct 2009 01:15:17 +0000 Cc: Kostik Belousov , current@freebsd.org, i386@freebsd.org Subject: Re: [head tinderbox] failure on i386/i386 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, 13 Oct 2009 00:45:27 -0000 This will fix it: Index: libgssapi_krb5/gss_krb5.c =================================================================== --- libgssapi_krb5/gss_krb5.c (revision 198008) +++ libgssapi_krb5/gss_krb5.c (working copy) @@ -31,6 +31,7 @@ /* RCSID("$Id: gss_krb5.c 21889 2007-08-09 07:43:24Z lha $"); */ +#include #include #include However I can't see yet how my commit triggered the problem. Sorry for the breakage. On 13.10.2009, at 8:52, FreeBSD Tinderbox wrote: > TB --- 2009-10-12 23:30:00 - tinderbox 2.6 running on freebsd-current.sentex.ca > TB --- 2009-10-12 23:30:00 - starting HEAD tinderbox run for i386/i386 > TB --- 2009-10-12 23:30:00 - cleaning the object tree > TB --- 2009-10-12 23:30:22 - cvsupping the source tree > TB --- 2009-10-12 23:30:22 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca > /tinderbox/HEAD/i386/i386/supfile > TB --- 2009-10-12 23:36:00 - building world > TB --- 2009-10-12 23:36:00 - MAKEOBJDIRPREFIX=/obj > TB --- 2009-10-12 23:36:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2009-10-12 23:36:00 - TARGET=i386 > TB --- 2009-10-12 23:36:00 - TARGET_ARCH=i386 > TB --- 2009-10-12 23:36:00 - TZ=UTC > TB --- 2009-10-12 23:36:00 - __MAKE_CONF=/dev/null > TB --- 2009-10-12 23:36:00 - cd /src > TB --- 2009-10-12 23:36:00 - /usr/bin/make -B buildworld >>>> World build started on Mon Oct 12 23:36:01 UTC 2009 >>>> 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 > [...] > cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/ > libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/ > lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/ > kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/ > kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/ > kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. - > DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include - > std=gnu99 -fstack-protector -c /src/kerberos5/lib/ > libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o > wrap.So > cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/ > libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/ > lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/ > kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/ > kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/ > kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. - > DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include - > std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/ > gss_krb5.c -o gss_krb5.So > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function > 'gsskrb5_extract_authz_data_from_sec_context': > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit > declaration of function 'der_get_oid' > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit > declaration of function 'der_free_oid' > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit > declaration of function 'der_length_oid' > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit > declaration of function 'der_put_oid' > make: don't know how to make /obj/i386/src/tmp/usr/lib/libgssapi.a. > Stop > *** Error code 2 > > Stop in /src. > *** Error code 1 > > Stop in /src. > *** Error code 1 > > Stop in /src. > *** Error code 1 > > Stop in /src. > TB --- 2009-10-12 23:52:33 - WARNING: /usr/bin/make returned exit > code 1 > TB --- 2009-10-12 23:52:33 - ERROR: failed to build world > TB --- 2009-10-12 23:52:33 - 746.54 user 167.70 system 1353.45 real > > > http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full > _______________________________________________ > 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 > " From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 04:09:39 2009 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 44661106568B; Tue, 13 Oct 2009 04:09:39 +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 046A98FC1E; Tue, 13 Oct 2009 04:09:38 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D49cjY060990; Tue, 13 Oct 2009 00:09:38 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D49c48060977; Tue, 13 Oct 2009 04:09:38 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 04:09:38 GMT Message-Id: <200910130409.n9D49c48060977@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 arm/arm 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, 13 Oct 2009 04:09:39 -0000 TB --- 2009-10-13 03:55:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-13 03:55:00 - starting HEAD tinderbox run for arm/arm TB --- 2009-10-13 03:55:00 - cleaning the object tree TB --- 2009-10-13 03:55:05 - cvsupping the source tree TB --- 2009-10-13 03:55:05 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2009-10-13 03:55:29 - building world TB --- 2009-10-13 03:55:29 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-13 03:55:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-13 03:55:29 - TARGET=arm TB --- 2009-10-13 03:55:29 - TARGET_ARCH=arm TB --- 2009-10-13 03:55:29 - TZ=UTC TB --- 2009-10-13 03:55:29 - __MAKE_CONF=/dev/null TB --- 2009-10-13 03:55:29 - cd /src TB --- 2009-10-13 03:55:29 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 13 03:55:29 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/arm/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 04:09:38 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 04:09:38 - ERROR: failed to build world TB --- 2009-10-13 04:09:38 - 644.73 user 158.41 system 878.05 real http://tinderbox.des.no/tinderbox-head-HEAD-arm-arm.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 04:11:35 2009 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 7585F1065670; Tue, 13 Oct 2009 04:11:35 +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 357638FC17; Tue, 13 Oct 2009 04:11:34 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D4BY6C093847; Tue, 13 Oct 2009 00:11:34 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D4BYFV093839; Tue, 13 Oct 2009 04:11:34 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 04:11:34 GMT Message-Id: <200910130411.n9D4BYFV093839@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, 13 Oct 2009 04:11:35 -0000 TB --- 2009-10-13 03:55:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-13 03:55:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2009-10-13 03:55:00 - cleaning the object tree TB --- 2009-10-13 03:55:05 - cvsupping the source tree TB --- 2009-10-13 03:55:05 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2009-10-13 03:55:29 - building world TB --- 2009-10-13 03:55:29 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-13 03:55:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-13 03:55:29 - TARGET=pc98 TB --- 2009-10-13 03:55:29 - TARGET_ARCH=i386 TB --- 2009-10-13 03:55:29 - TZ=UTC TB --- 2009-10-13 03:55:29 - __MAKE_CONF=/dev/null TB --- 2009-10-13 03:55:29 - cd /src TB --- 2009-10-13 03:55:29 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 13 03:55:29 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/pc98/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 04:11:34 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 04:11:34 - ERROR: failed to build world TB --- 2009-10-13 04:11:34 - 741.07 user 159.47 system 994.31 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 04:16:59 2009 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 ADA8E106566B; Tue, 13 Oct 2009 04:16:59 +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 6DA3D8FC0A; Tue, 13 Oct 2009 04:16:59 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D4GwFj036052; Tue, 13 Oct 2009 00:16:58 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D4GwVd036048; Tue, 13 Oct 2009 04:16:58 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 04:16:58 GMT Message-Id: <200910130416.n9D4GwVd036048@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: Tue, 13 Oct 2009 04:16:59 -0000 TB --- 2009-10-13 03:55:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-13 03:55:00 - starting HEAD tinderbox run for i386/i386 TB --- 2009-10-13 03:55:00 - cleaning the object tree TB --- 2009-10-13 03:55:05 - cvsupping the source tree TB --- 2009-10-13 03:55:05 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2009-10-13 04:00:33 - building world TB --- 2009-10-13 04:00:33 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-13 04:00:33 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-13 04:00:33 - TARGET=i386 TB --- 2009-10-13 04:00:33 - TARGET_ARCH=i386 TB --- 2009-10-13 04:00:33 - TZ=UTC TB --- 2009-10-13 04:00:33 - __MAKE_CONF=/dev/null TB --- 2009-10-13 04:00:33 - cd /src TB --- 2009-10-13 04:00:33 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 13 04:00:34 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/i386/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 04:16:58 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 04:16:58 - ERROR: failed to build world TB --- 2009-10-13 04:16:58 - 746.29 user 158.54 system 1318.54 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 04:18:00 2009 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 305F6106568F; Tue, 13 Oct 2009 04:18:00 +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 E43558FC1A; Tue, 13 Oct 2009 04:17:59 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D4HxpO040204; Tue, 13 Oct 2009 00:17:59 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D4Hx6r040179; Tue, 13 Oct 2009 04:17:59 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 04:17:59 GMT Message-Id: <200910130417.n9D4Hx6r040179@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: Tue, 13 Oct 2009 04:18:00 -0000 TB --- 2009-10-13 03:55:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-13 03:55:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2009-10-13 03:55:00 - cleaning the object tree TB --- 2009-10-13 03:55:05 - cvsupping the source tree TB --- 2009-10-13 03:55:05 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile TB --- 2009-10-13 04:00:33 - building world TB --- 2009-10-13 04:00:33 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-13 04:00:33 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-13 04:00:33 - TARGET=amd64 TB --- 2009-10-13 04:00:33 - TARGET_ARCH=amd64 TB --- 2009-10-13 04:00:33 - TZ=UTC TB --- 2009-10-13 04:00:33 - __MAKE_CONF=/dev/null TB --- 2009-10-13 04:00:33 - cd /src TB --- 2009-10-13 04:00:33 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 13 04:00:33 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 04:17:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 04:17:59 - ERROR: failed to build world TB --- 2009-10-13 04:17:59 - 783.20 user 167.37 system 1379.09 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 04:27:21 2009 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 E58B61065676; Tue, 13 Oct 2009 04:27:20 +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 A59108FC1A; Tue, 13 Oct 2009 04:27:20 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D4RKg8037272; Tue, 13 Oct 2009 00:27:20 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D4RKUj037271; Tue, 13 Oct 2009 04:27:20 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 04:27:20 GMT Message-Id: <200910130427.n9D4RKUj037271@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 mips/mips 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, 13 Oct 2009 04:27:21 -0000 TB --- 2009-10-13 04:11:34 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-13 04:11:34 - starting HEAD tinderbox run for mips/mips TB --- 2009-10-13 04:11:34 - cleaning the object tree TB --- 2009-10-13 04:11:37 - cvsupping the source tree TB --- 2009-10-13 04:11:37 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/mips/mips/supfile TB --- 2009-10-13 04:12:04 - building world TB --- 2009-10-13 04:12:04 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-13 04:12:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-13 04:12:04 - TARGET=mips TB --- 2009-10-13 04:12:04 - TARGET_ARCH=mips TB --- 2009-10-13 04:12:04 - TZ=UTC TB --- 2009-10-13 04:12:04 - __MAKE_CONF=/dev/null TB --- 2009-10-13 04:12:04 - cd /src TB --- 2009-10-13 04:12:04 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 13 04:12:05 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O -pipe -EL -msoft-float -G0 -mno-dsp -mabicalls -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O -pipe -EL -msoft-float -G0 -mno-dsp -mabicalls -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/mips/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 04:27:19 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 04:27:19 - ERROR: failed to build world TB --- 2009-10-13 04:27:19 - 664.61 user 152.35 system 945.26 real http://tinderbox.des.no/tinderbox-head-HEAD-mips-mips.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 04:27:37 2009 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 D57D710656C1; Tue, 13 Oct 2009 04:27:37 +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 9591A8FC13; Tue, 13 Oct 2009 04:27:37 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D4RbIN038778; Tue, 13 Oct 2009 00:27:37 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D4RbRG038774; Tue, 13 Oct 2009 04:27:37 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 04:27:37 GMT Message-Id: <200910130427.n9D4RbRG038774@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: Tue, 13 Oct 2009 04:27:38 -0000 TB --- 2009-10-13 04:09:38 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-13 04:09:38 - starting HEAD tinderbox run for ia64/ia64 TB --- 2009-10-13 04:09:38 - cleaning the object tree TB --- 2009-10-13 04:09:41 - cvsupping the source tree TB --- 2009-10-13 04:09:41 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2009-10-13 04:10:09 - building world TB --- 2009-10-13 04:10:09 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-13 04:10:09 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-13 04:10:09 - TARGET=ia64 TB --- 2009-10-13 04:10:09 - TARGET_ARCH=ia64 TB --- 2009-10-13 04:10:09 - TZ=UTC TB --- 2009-10-13 04:10:09 - __MAKE_CONF=/dev/null TB --- 2009-10-13 04:10:09 - cd /src TB --- 2009-10-13 04:10:09 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 13 04:10:10 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/ia64/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 04:27:37 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 04:27:37 - ERROR: failed to build world TB --- 2009-10-13 04:27:37 - 811.72 user 160.23 system 1078.49 real http://tinderbox.des.no/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 04:33:17 2009 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 EFF0E106566B; Tue, 13 Oct 2009 04:33:16 +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 AFFBC8FC08; Tue, 13 Oct 2009 04:33:16 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D4XGDC082635; Tue, 13 Oct 2009 00:33:16 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D4XGiI082632; Tue, 13 Oct 2009 04:33:16 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 04:33:16 GMT Message-Id: <200910130433.n9D4XGiI082632@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: Tue, 13 Oct 2009 04:33:17 -0000 TB --- 2009-10-13 04:17:59 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-13 04:17:59 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2009-10-13 04:17:59 - cleaning the object tree TB --- 2009-10-13 04:18:02 - cvsupping the source tree TB --- 2009-10-13 04:18:02 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2009-10-13 04:18:27 - building world TB --- 2009-10-13 04:18:27 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-13 04:18:27 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-13 04:18:27 - TARGET=sparc64 TB --- 2009-10-13 04:18:27 - TARGET_ARCH=sparc64 TB --- 2009-10-13 04:18:27 - TZ=UTC TB --- 2009-10-13 04:18:27 - __MAKE_CONF=/dev/null TB --- 2009-10-13 04:18:27 - cd /src TB --- 2009-10-13 04:18:27 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 13 04:18:28 UTC 2009 >>> 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 [...] cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/sparc64/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 04:33:16 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 04:33:16 - ERROR: failed to build world TB --- 2009-10-13 04:33:16 - 678.41 user 155.45 system 916.56 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 04:33:26 2009 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 C71D01065679; Tue, 13 Oct 2009 04:33:26 +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 86D908FC17; Tue, 13 Oct 2009 04:33:26 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D4XQC6082892; Tue, 13 Oct 2009 00:33:26 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D4XQ9V082891; Tue, 13 Oct 2009 04:33:26 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 04:33:26 GMT Message-Id: <200910130433.n9D4XQ9V082891@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: Tue, 13 Oct 2009 04:33:27 -0000 TB --- 2009-10-13 04:16:58 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-13 04:16:58 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2009-10-13 04:16:58 - cleaning the object tree TB --- 2009-10-13 04:17:03 - cvsupping the source tree TB --- 2009-10-13 04:17:03 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2009-10-13 04:17:31 - building world TB --- 2009-10-13 04:17:31 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-13 04:17:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-13 04:17:31 - TARGET=powerpc TB --- 2009-10-13 04:17:31 - TARGET_ARCH=powerpc TB --- 2009-10-13 04:17:31 - TZ=UTC TB --- 2009-10-13 04:17:31 - __MAKE_CONF=/dev/null TB --- 2009-10-13 04:17:31 - cd /src TB --- 2009-10-13 04:17:31 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 13 04:17:32 UTC 2009 >>> 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 [...] cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fpic -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/powerpc/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 04:33:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 04:33:26 - ERROR: failed to build world TB --- 2009-10-13 04:33:26 - 747.34 user 154.41 system 987.07 real http://tinderbox.des.no/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 04:41:38 2009 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 DBBD01065672; Tue, 13 Oct 2009 04:41:37 +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 9BCB48FC19; Tue, 13 Oct 2009 04:41:37 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9D4farQ006909; Tue, 13 Oct 2009 00:41:36 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9D4fa8c006908; Tue, 13 Oct 2009 04:41:36 GMT (envelope-from tinderbox@freebsd.org) Date: Tue, 13 Oct 2009 04:41:36 GMT Message-Id: <200910130441.n9D4fa8c006908@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: Tue, 13 Oct 2009 04:41:38 -0000 TB --- 2009-10-13 04:27:20 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-13 04:27:20 - starting HEAD tinderbox run for sparc64/sun4v TB --- 2009-10-13 04:27:20 - cleaning the object tree TB --- 2009-10-13 04:27:23 - cvsupping the source tree TB --- 2009-10-13 04:27:23 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sun4v/supfile TB --- 2009-10-13 04:27:50 - building world TB --- 2009-10-13 04:27:50 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-13 04:27:50 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-13 04:27:50 - TARGET=sun4v TB --- 2009-10-13 04:27:50 - TARGET_ARCH=sparc64 TB --- 2009-10-13 04:27:50 - TZ=UTC TB --- 2009-10-13 04:27:50 - __MAKE_CONF=/dev/null TB --- 2009-10-13 04:27:50 - cd /src TB --- 2009-10-13 04:27:50 - /usr/bin/make -B buildworld >>> World build started on Tue Oct 13 04:27:50 UTC 2009 >>> 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 [...] cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5/wrap.c -o wrap.So cc -fPIC -DPIC -O2 -pipe -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/gssapi/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/krb5 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/asn1 -I/src/kerberos5/lib/libgssapi_krb5/../../../crypto/heimdal/lib/roken -I. -DHAVE_CONFIG_H -I/src/kerberos5/lib/libgssapi_krb5/../../include -std=gnu99 -fstack-protector -c /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c -o gss_krb5.So /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declaration of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declaration of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declaration of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declaration of function 'der_put_oid' make: don't know how to make /obj/sun4v/src/tmp/usr/lib/libgssapi.a. Stop *** Error code 2 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-13 04:41:36 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-13 04:41:36 - ERROR: failed to build world TB --- 2009-10-13 04:41:36 - 682.20 user 145.82 system 856.61 real http://tinderbox.des.no/tinderbox-head-HEAD-sparc64-sun4v.full From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 10:46:40 2009 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 CC8EE106568F; Tue, 13 Oct 2009 10:46:40 +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 C61008FC12; Tue, 13 Oct 2009 10:46:39 +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 NAA07724; Tue, 13 Oct 2009 13:46:38 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4AD45A8D.4070605@icyb.net.ua> Date: Tue, 13 Oct 2009 13:46:37 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: freebsd-fs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG References: <4AD3220B.5030502@icyb.net.ua> <86ws30ikfw.fsf@gmail.com> In-Reply-To: <86ws30ikfw.fsf@gmail.com> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Anonymous Subject: Re: zfs boot vs loader 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, 13 Oct 2009 10:46:40 -0000 Thanks to all who replied! I think that I figured it out with your help. 'unload' does indeed unload zpool.cache and the latter is needed for proper zfs root mounting. 'boot /other/kernel' executes some loader scripts and zpool.cache gets loaded in this case (because of the settings in defaults/loader.conf). When doing manual 'load xxx' and then just 'boot' no loader scripts are executed and zpool.cache does not get loaded. In this case one has to load it manually using the suggested 'load -t xxx' approach. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 11:38:46 2009 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 07EAE106566B for ; Tue, 13 Oct 2009 11:38:46 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id B98B18FC23 for ; Tue, 13 Oct 2009 11:38:44 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 9177C9CB204 for ; Tue, 13 Oct 2009 13:38:19 +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 Kqdz7PgG03Yp for ; Tue, 13 Oct 2009 13:38:17 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id CED829CB2A1 for ; Tue, 13 Oct 2009 13:38:13 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id n9DBcDpK002563 for current@freebsd.org; Tue, 13 Oct 2009 13:38:13 +0200 (CEST) (envelope-from rdivacky) Date: Tue, 13 Oct 2009 13:38:13 +0200 From: Roman Divacky To: current@freebsd.org Message-ID: <20091013113813.GA2478@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: unifdef crashes 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, 13 Oct 2009 11:38:46 -0000 just to not lost it: unifdef -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -DCRT_BEGIN -DOBJECT_FORMAT_ELF /usr/src/contrib/gcc/crtstuff.c this crashes our unifdef if someone wants to look at it, you're welcome roman From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 13:50:43 2009 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 4A10F1065670 for ; Tue, 13 Oct 2009 13:50:43 +0000 (UTC) (envelope-from rdivacky@vlk.vlakno.cz) Received: from vlakno.cz (77-93-215-190.static.masterinter.net [77.93.215.190]) by mx1.freebsd.org (Postfix) with ESMTP id 063A48FC21 for ; Tue, 13 Oct 2009 13:50:41 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id DEF2F9CB10F for ; Tue, 13 Oct 2009 15:50:15 +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 02rxRfb+kA2T for ; Tue, 13 Oct 2009 15:50:13 +0200 (CEST) Received: from vlk.vlakno.cz (localhost [127.0.0.1]) by vlakno.cz (Postfix) with ESMTP id 899AB9CB204 for ; Tue, 13 Oct 2009 15:50:13 +0200 (CEST) Received: (from rdivacky@localhost) by vlk.vlakno.cz (8.14.3/8.14.3/Submit) id n9DDoDD7090837 for current@freebsd.org; Tue, 13 Oct 2009 15:50:13 +0200 (CEST) (envelope-from rdivacky) Date: Tue, 13 Oct 2009 15:50:13 +0200 From: Roman Divacky To: current@freebsd.org Message-ID: <20091013135013.GA90731@freebsd.org> References: <20091013113813.GA2478@freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091013113813.GA2478@freebsd.org> User-Agent: Mutt/1.4.2.3i Cc: Subject: Re: unifdef crashes 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, 13 Oct 2009 13:50:43 -0000 On Tue, Oct 13, 2009 at 01:38:13PM +0200, Roman Divacky wrote: > just to not lost it: > > unifdef -DIN_GCC -DHAVE_LD_EH_FRAME_HDR -DDT_CONFIG -D__GLIBC__=3 -DCRT_BEGIN -DOBJECT_FORMAT_ELF > /usr/src/contrib/gcc/crtstuff.c > > this crashes our unifdef > > if someone wants to look at it, you're welcome this is already fixed in -current and 8.x by fanf@ sorry for the noise From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 14:11:47 2009 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 6BFD9106568F for ; Tue, 13 Oct 2009 14:11:47 +0000 (UTC) (envelope-from minotaur@crete.org.ua) Received: from relay.padonki.org.ua (relay.padonki.org.ua [193.0.227.26]) by mx1.freebsd.org (Postfix) with ESMTP id 244E28FC1B for ; Tue, 13 Oct 2009 14:11:47 +0000 (UTC) Received: from minotaur by relay.padonki.org.ua with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Mxi6K-000EIH-Fw; Tue, 13 Oct 2009 17:11:44 +0300 Date: Tue, 13 Oct 2009 17:11:44 +0300 From: Alexander Shikoff To: Patrick Lamaiziere Message-ID: <20091013141144.GA54420@crete.org.ua> References: <20091004090156.GA85409@crete.org.ua> <20091008123001.GA82997@nagual.pp.ru> <20091012131901.6421666b@baby-jane.lamaiziere.net> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-u Content-Disposition: inline In-Reply-To: <20091012131901.6421666b@baby-jane.lamaiziere.net> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: Alexander Shikoff Cc: Andrey Chernov , freebsd-current@freebsd.org Subject: Re: 'ee' editor prints cyrillic characters on white background X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Alexander Shikoff List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2009 14:11:47 -0000 On Mon, Oct 12, 2009 at 01:19:01PM +0200, Patrick Lamaiziere wrote: > Le Thu, 8 Oct 2009 16:30:01 +0400, > Andrey Chernov a ?crit : > > > > I've upgraded my 7.2-RELEASE to 8.0-RC1. ee editor began to > > > highlight cyrillic characters (locale uk_UA.KOI8-U) with white > > > background and underscoring. Does anyone know how to disable this? > > > Thanks. > > > > Fixed in -current. > > It would be nice to have this fixed in 8.0 too :-) > Is it planned? It will be great if these changes be committed in 8-STABLE. But while they are only in -current you can easily edit sources by hands, look at http://svn.freebsd.org/viewvc/base/head/contrib/ee/ee.c?r1=196750&r2=196749&pathrev=196750 Just edit proper lines (with waddch) in your sources. I fixed it in my sources. Andrey, thanks a lot! -- MINO-RIPE From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 15:33:33 2009 Return-Path: Delivered-To: current@freebsd.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id AF919106566B; Tue, 13 Oct 2009 15:33:33 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-acpi@FreeBSD.org Date: Tue, 13 Oct 2009 11:33:14 -0400 User-Agent: KMail/1.6.2 References: <20091011142256.GA3770@roadrunner.spoerlein.net> In-Reply-To: <20091011142256.GA3770@roadrunner.spoerlein.net> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <200910131133.16487.jkim@FreeBSD.org> Cc: current@freebsd.org Subject: Re: ACPI Warning: Converted Buffer to expected String 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, 13 Oct 2009 15:33:33 -0000 On Sunday 11 October 2009 10:22 am, Ulrich Spörlein wrote: > Just FYI, > > Dell Inspiron 8600c laptop, semi-recent CURRENT, latest BIOS (A14), > machine is 5 years old and producing these warnings when inserting > a battery (or booting with one inserted) > > ACPI Warning for \\_SB_.BAT0._BIF: Converted Buffer to expected > String at index 9 (20090903/nsrepair-215) ACPI Warning for > \\_SB_.BAT0._BIF: Converted Buffer to expected String at index 10 > (20090903/nsrepair-215) ACPI Warning for \\_SB_.BAT0._BIF: > Converted Buffer to expected String at index 11 > (20090903/nsrepair-215) ACPI Warning for \\_SB_.BAT0._BIF: > Converted Buffer to expected String at index 12 > (20090903/nsrepair-215) These are just informational. FYI, new ACPICA checks predefined method/object types per spec. and tries to correct common DSDT errors. Previously these "quirks" were handled by OS layer case by case. The warning message is telling you that _BIF method (get battery information) returned Buffer object instead of String object and ACPICA corrected the errors. In fact, this is a very common mistake by laptop BIOS writers. Thus, it is automatically corrected by new ACPICA. However, if you see "ACPI Error", that's something to worry about, e.g., cannot convert predefined types. > Everything works just before the ACPI import, there's also another > bunch of (harmless) errors during boot. > > acpi0: on motherboard > acpi0: [ITHREAD] > acpi0: reservation of 0, 9fc00 (3) failed > acpi0: reservation of 100000, 3fef0000 (3) failed > > This is just for reference, perhaps someone wants to know. It is harmless. Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 15:38:19 2009 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 889E51065697 for ; Tue, 13 Oct 2009 15:38:19 +0000 (UTC) (envelope-from miwi@bsdcrew.de) Received: from bsdcrew.de (duro.unixfreunde.de [85.214.90.4]) by mx1.freebsd.org (Postfix) with ESMTP id 47B658FC24 for ; Tue, 13 Oct 2009 15:38:19 +0000 (UTC) Received: by bsdcrew.de (Postfix, from userid 1001) id CECF34AF56; Tue, 13 Oct 2009 17:38:15 +0200 (CEST) Date: Tue, 13 Oct 2009 17:38:15 +0200 From: Martin Wilke To: Matthias Apitz Message-ID: <20091013153815.GA88394@bsdcrew.de> References: <20091011062419.GA2168@current.Sisis.de> <3a142e750910111214rb75f185k12b2cc7e1aba59d9@mail.gmail.com> <20091012130914.GA4180@current.Sisis.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; x-action=pgp-signed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20091012130914.GA4180@current.Sisis.de> User-Agent: Mutt/1.5.19 (2009-01-05) Cc: kde-freebsd@kde.org, freebsd-current@freebsd.org Subject: Re: [kde-freebsd] 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV 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, 13 Oct 2009 15:38:19 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, Oct 12, 2009 at 03:09:15PM +0200, Matthias Apitz wrote: > El día Sunday, October 11, 2009 a las 07:14:21PM +0000, Paul B Mahol escribió: > > > Make sure that all libraries and binarys are rebuild, thare may be ABI > > changes and not > > support for older code .... > > Hi Paul, > > I've compiled all (kernel, user land and the ports) in a virtual machine > I'm using for preparing binary installation, i.e. after compiling the > ports I create packages to install them on machines where you either > can't compile for being to small/slow (like my EeePC 900) or to give a > binary set away for installation where machines have limited access to > Internet. > > I've build and installed kernel and user land based on SVN checkout: > > # svn info > Path: . > URL: svn://svn.freebsd.org/base/head > Repository Root: svn://svn.freebsd.org/base > Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f > Revision: 197801 > Node Kind: directory > Schedule: normal > Last Changed Author: maxim > Last Changed Rev: 197799 > Last Changed Date: 2009-10-06 06:57:18 +0200 (Tue, 06 Oct 2009) > > # uname -a > FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r197801: Tue > Oct 6 13:57:38 CEST 2009 > guru@vm-azul.Sisis.de:/usr/obj/usr/src/sys/REBELION-HEAD i386 > > When kernel and user land have been on 9-CURRENT, I removed /usr/ports, > checked them out with CVS and build all my ports, especially KDE3. > > I don't see how an old library or binary can cause this. Only some ABI > change which is not supported in the KDE sources... > > Don't know if someone from FreeBSD's KDE team can (or will) comment on it. It > seems to me that they all went away (to KDE4 :-)). > > Thx unfortunately you're right, we're a small team, we spend all our energy to KDE4. Sorry but so is the life. - - Martin > > matthias > -- > Matthias Apitz > t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 > e - w http://www.unixarea.de/ > Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu > _______________________________________________ > kde-freebsd mailing list > kde-freebsd@kde.org > https://mail.kde.org/mailman/listinfo/kde-freebsd > See also http://freebsd.kde.org/ for latest information > - -- +-----------------------+-------------------------------+ | PGP : 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de | | Skype : splash_111 | Mail : miwi(at)FreeBSD.org | +-----------------------+-------------------------------+ | Mess with the Best, Die like the Rest! | +-----------------------+-------------------------------+ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (FreeBSD) iEYEARECAAYFAkrUnucACgkQdLJIhLHm/Onz5ACg4bMNlKipfAGDsjm2saXg4W2i pfEAn2f+DbYaMq0WjxAZcc6L55Evi5Iq =L81j -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 17:41:31 2009 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 28F781065694 for ; Tue, 13 Oct 2009 17:41:31 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id A6D6C8FC13 for ; Tue, 13 Oct 2009 17:41:30 +0000 (UTC) Received: by ewy18 with SMTP id 18so4005832ewy.43 for ; Tue, 13 Oct 2009 10:41:29 -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=SLjL3drOu6Z7d65/Nn5OVrxTDjW22AsCjJbYEr2GDpM=; b=L5vRxlANsNurZ8OSie3cs00B8T5q95sNUQ2J/L05bUQEaiyCPRIGdb8YhovkrQQ5HO zyA6IbhscQwE7u3LFtHydhxr+CtgpeGhcJx3BmkQBoxIlQwqX2FOzaMd3yxD5PLGe5ki EcfiEfbr82WVZhbNg3liG5VagzG0eSQtBx//g= 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=cFvD2hhQu158gI67By2jXtXtMOvfMT02FPmE7qqkjNq7PBma1jRZmYceNGh20ClF1o bVucwGkMJgbO3+ctVtBttixMOZxwx3SNMOkXnZxiugoD9n2Ib/CmAlCYidT0oc0l66Cd m/0PldKvxv1L2tI7ZeaSffq8dBLGiESW9xcBk= Received: by 10.102.193.20 with SMTP id q20mr3116243muf.28.1255455689475; Tue, 13 Oct 2009 10:41:29 -0700 (PDT) Received: from weongyo ([174.35.1.224]) by mx.google.com with ESMTPS id u9sm506709muf.31.2009.10.13.10.41.26 (version=SSLv3 cipher=RC4-MD5); Tue, 13 Oct 2009 10:41:27 -0700 (PDT) Received: by weongyo (sSMTP sendmail emulation); Tue, 13 Oct 2009 10:42:01 -0700 From: Weongyo Jeong Date: Tue, 13 Oct 2009 10:42:01 -0700 To: Poul-Henning Kamp Message-ID: <20091013174201.GC67082@weongyo> Mail-Followup-To: Poul-Henning Kamp , current@freebsd.org References: <86051.1254232666@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: <86051.1254232666@critter.freebsd.dk> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: current@freebsd.org Subject: Re: if_rum dies on transmit... 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: Tue, 13 Oct 2009 17:41:31 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Sep 29, 2009 at 01:57:46PM +0000, Poul-Henning Kamp wrote: > > Has anybody else seen if_rum die when you try to transmit a file over > a TCP connection ? > > If I try to print across the network, upload a file with ftp or anything > else of that general tenor, if_rum seems to hang the output queue and > stops transmitting packets. > > Restarting wpa_supplicant mostly resolves the issue, but it does not > on its own discover the problem. > > According to tcpdump(8), packets are still received. > > Any ideas ? Could you please test with attached patch? regards, Weongyo Jeong --UugvWAfsgieZRqgk Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="patch_rum_20091013.diff" Index: if_rum.c =================================================================== --- if_rum.c (revision 198036) +++ if_rum.c (working copy) @@ -826,6 +826,9 @@ usbd_transfer_submit(xfer); } + RUM_UNLOCK(sc); + rum_start(ifp); + RUM_LOCK(sc); break; default: /* Error */ @@ -930,8 +933,8 @@ * the private mutex of a device! That is why we do the * "ieee80211_input" here, and not some lines up! */ + RUM_UNLOCK(sc); if (m) { - RUM_UNLOCK(sc); ni = ieee80211_find_rxnode(ic, mtod(m, struct ieee80211_frame_min *)); if (ni != NULL) { @@ -941,8 +944,11 @@ } else (void) ieee80211_input_all(ic, m, rssi, RT2573_NOISE_FLOOR); - RUM_LOCK(sc); } + if ((ifp->if_drv_flags & IFF_DRV_OACTIVE) == 0 && + !IFQ_IS_EMPTY(&ifp->if_snd)) + rum_start(ifp); + RUM_LOCK(sc); return; default: /* Error */ --UugvWAfsgieZRqgk-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 18:32:38 2009 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 9D93710656A9; Tue, 13 Oct 2009 18:32:38 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 574BE8FC19; Tue, 13 Oct 2009 18:32:38 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 228616D41B; Tue, 13 Oct 2009 18:32:37 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id CF1C784503; Tue, 13 Oct 2009 20:32:36 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: quickembed References: <200910122344.n9CNijv9037645@freebsd-current.sentex.ca> Date: Tue, 13 Oct 2009 20:32:36 +0200 In-Reply-To: (quickembed@gmail.com's message of "Tue, 13 Oct 2009 08:19:06 +0800") Message-ID: <86vdijdu0r.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: arm@freebsd.org, FreeBSD Tinderbox , current@freebsd.org Subject: Re: [head tinderbox] failure on arm/arm 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, 13 Oct 2009 18:32:38 -0000 quickembed writes: > this error shows you have not indicate how to compile libgssapi.a file. > CC is for .c file, you need to tell what's for .a (assembly) file. No, the command line is correct. Assembler sources end in .s or .S; .a is a static library. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 21:27:30 2009 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 4EB24106568D for ; Tue, 13 Oct 2009 21:27:30 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay2.uni-muenster.de (ZIVM-EXRELAY2.UNI-MUENSTER.DE [128.176.192.15]) by mx1.freebsd.org (Postfix) with ESMTP id C7AF38FC0A for ; Tue, 13 Oct 2009 21:27:29 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,553,1249250400"; d="scan'208";a="226204798" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER04.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay2.uni-muenster.de with ESMTP; 13 Oct 2009 23:27:28 +0200 Received: by ZIVMAILUSER04.UNI-MUENSTER.DE (Postfix, from userid 149459) id 41ABC1B07BE; Tue, 13 Oct 2009 23:27:28 +0200 (CEST) Date: Tue, 13 Oct 2009 23:27:27 +0200 (CEST) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Harald Schmalzbauer Message-ID: In-Reply-To: <4AD0ED9F.3080706@omnilan.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: Where to report LORs? (ffs and unionfs LORs included 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, 13 Oct 2009 21:27:30 -0000 Harald Schmalzbauer schrieb am 2009-10-10: > Alexander Best schrieb am 07.07.2009 21:33 (localtime): > >try http://sources.zabbadoz.net/freebsd/lor.html > I still see a unionfs LOR with RELENG_8 which is not listed, so I'd > like to report it again. > lock order reversal: > 1st 0xc372c488 unionfs (unionfs) @ > /FlashBSD/src/sys/fs/unionfs/union_subr.c:356 > 2nd 0xc372c594 ufs (ufs) @ /FlashBSD/src/sys/kern/vfs_subr.c:2188 > KDB: stack backtrace: > db_trace_self_wrapper(c0616390,c08cd5d5,c3416770,c3416500,d5c42864,.. > .) at db_trace_self_wrapper+0x26 > _witness_debugger(c08cd5d5,c372c594,c08c0703,c3416500,c08d4ec2,...) > at _witness_debugger+0x49 > witness_checkorder(c372c594,9,c08d4ec2,88c,0,...) at > witness_checkorder+0x6ec > __lockmgr_args(c372c594,80100,c372c5b0,0,0,...) at > __lockmgr_args+0xc97 > ffs_lock(d5c42958,8,c36c4764,80100,c372c53c,...) at ffs_lock+0x96 > VOP_LOCK1_APV(c09374a0,d5c42958,c05d89e9,c09477c0,c372c53c,...) at > VOP_LOCK1_APV+0x9a > _vn_lock(c372c53c,80100,c08d4ec2,88c,c0877c6e,...) at _vn_lock+0x46 > vrele(c372c53c,d5c429d8,c372c4a4,0,0,...) at vrele+0x12a > unionfs_noderem(c372c430,c36c46c0,d5c42a44,c06764fc,d5c42a20,...) at > unionfs_noderem+0x1e5 > unionfs_reclaim(d5c42a20,d5c42a20,0,0,c372c4a4,...) at > unionfs_reclaim+0x1b > vgonel(c372c4a4,0,c08d4ec2,9c5,c372c4a4,...) at vgonel+0x100 > vrecycle(c372c430,c36c46c0,d5c42aa4,c0675c29,d5c42a8c,...) at > vrecycle+0x6a > unionfs_inactive(d5c42a8c,d5c42a8c,c08d4ec2,924,c0947780,...) at > unionfs_inactive+0x28 > vinactive(c372c594,d5c42ac0,c08d4ec2,8aa,c3451de0,...) at > vinactive+0x6a > vput(c372c430,ffffffdf,c344ab80,0,c36c46c0,...) at vput+0x205 > kern_statat_vnhook(c36c46c0,0,ffffff9c,28209e1c,0,...) at > kern_statat_vnhook+0xe0 > kern_statat(c36c46c0,0,ffffff9c,28209e1c,0,...) at kern_statat+0x3c > kern_stat(c36c46c0,28209e1c,0,d5c42c18,c0a83a18,...) at > kern_stat+0x36 > stat(c36c46c0,d5c42cf8,8,d5c42d38,c0916cd0,...) at stat+0x2b > syscall(d5c42d38) at syscall+0x176 > Xint0x80_syscall() at Xint0x80_syscall+0x20 > --- syscall (188, FreeBSD ELF32, stat), eip = 0x281c6c2b, esp = > 0xbfbfe96c, ebp = 0xbfbfea68 --- > So far I couldn't notice any deadlock, but the box is not in > production yet. > -Harry you might also want to write Bjoern Zeeb (http://wiki.freebsd.org/BjoernZeeb) with a link to your report. he's the guy maintaining the lor page. cheers. alex From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 21:18:35 2009 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 AF4191065670 for ; Tue, 13 Oct 2009 21:18:35 +0000 (UTC) (envelope-from john@baldwin.cx) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 7FFE88FC13 for ; Tue, 13 Oct 2009 21:18:35 +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 2FD8C46B2A; Tue, 13 Oct 2009 17:18:35 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 7F84A8A01F; Tue, 13 Oct 2009 17:18:34 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 13 Oct 2009 16:44:03 -0400 User-Agent: KMail/1.9.7 References: <4ACE6D84.3000209@gmail.com> <4ACE833A.3030506@uffner.com> <4ACE9DFD.3010207@gmail.com> In-Reply-To: <4ACE9DFD.3010207@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910131644.04358.john@baldwin.cx> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Tue, 13 Oct 2009 17:18:34 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-1.1 required=4.2 tests=AWL,BAYES_00,RDNS_NONE, SUBJECT_FUZZY_TION autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx X-Mailman-Approved-At: Tue, 13 Oct 2009 21:47:18 +0000 Cc: David Ehrmann Subject: Re: 8.0rc1 not recognizing partitions on EPIA SN 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, 13 Oct 2009 21:18:35 -0000 On Thursday 08 October 2009 10:20:45 pm David Ehrmann wrote: > Tom Uffner wrote: > > David Ehrmann wrote: > >> First, I tried to upgrade the normal way. I built my own kernel and > >> installed it, but when I tried to boot it, I got a mountroot> > >> prompt. When I printed the devices, instead of seeing ad0s1a and > >> friends, I saw ad0a and ad0d (just those two for ad0). I was still > >> able to use the old (7.1) kernel fine. Thinking it was something to > >> do with the upgrade, I tried to do a reinstall. I chose the default > >> options, but once it got to the "last chance..." screen, this happened: > >> > >> Unable to find device node for /dev/ad0s1b in /dev! > >> The creation of filesystems will be aborted. > > > > this is becoming an FAQ for 8.0 > > > > the short answer is "dangerously dedicated" partitions are not supported > > by the 8.0 installer. back up your data. zero the MBR & partition table > > with dd, and re-slice & partition your disk. after the install, restore > > from your backups. > > > > search the freebsd-current archives for full details. > dd did the trick. > > I understand why this was done, but at the same time, upgrading is now > impractical for some users, and what looks like a fresh installation > (repartitioned, resliced) can even fail. Is there a change that could > be made to the partitioning process that would fix this? E-mail marcel@. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 21:50:25 2009 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 9F6CE1065672 for ; Tue, 13 Oct 2009 21:50:25 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 2FB338FC16 for ; Tue, 13 Oct 2009 21:50:24 +0000 (UTC) Received: from lstewart-laptop.caia.swin.edu.au (216-239-45-4.google.com [216.239.45.4]) (authenticated bits=0) by lauren.room52.net (8.14.3/8.14.3) with ESMTP id n9DLoGHu052230 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Oct 2009 08:50:18 +1100 (EST) (envelope-from lstewart@freebsd.org) Message-ID: <4AD4F611.6080504@freebsd.org> Date: Tue, 13 Oct 2009 14:50:09 -0700 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.23 (X11/20090909) MIME-Version: 1.0 To: Jung-uk Kim References: <20091011142256.GA3770@roadrunner.spoerlein.net> <200910131133.16487.jkim@FreeBSD.org> In-Reply-To: <200910131133.16487.jkim@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RDNS_DYNAMIC, SPF_SOFTFAIL autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lauren.room52.net Cc: freebsd-acpi@freebsd.org, current@freebsd.org Subject: Re: ACPI Warning: Converted Buffer to expected String 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, 13 Oct 2009 21:50:25 -0000 Jung-uk Kim wrote: [snip] > by new ACPICA. However, if you see "ACPI Error", that's something to > worry about, e.g., cannot convert predefined types. > So I should be worried about this line from my Toshiba R600 laptop's dmesg? ACPI Error: Package List length (0xC) larger than NumElements count (0x4), truncated Cheers, Lawrence From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 22:16:13 2009 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from [127.0.0.1] (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 03D611065672; Tue, 13 Oct 2009 22:16:13 +0000 (UTC) (envelope-from jkim@FreeBSD.org) From: Jung-uk Kim To: freebsd-current@FreeBSD.org Date: Tue, 13 Oct 2009 18:15:40 -0400 User-Agent: KMail/1.6.2 References: <20091011142256.GA3770@roadrunner.spoerlein.net> <200910131133.16487.jkim@FreeBSD.org> <4AD4F611.6080504@freebsd.org> In-Reply-To: <4AD4F611.6080504@freebsd.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200910131815.53053.jkim@FreeBSD.org> Cc: Lawrence Stewart , freebsd-acpi@freebsd.org Subject: Re: ACPI Warning: Converted Buffer to expected String 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, 13 Oct 2009 22:16:13 -0000 On Tuesday 13 October 2009 05:50 pm, Lawrence Stewart wrote: > Jung-uk Kim wrote: > > [snip] > > > by new ACPICA. However, if you see "ACPI Error", that's > > something to worry about, e.g., cannot convert predefined types. > > So I should be worried about this line from my Toshiba R600 > laptop's dmesg? > > ACPI Error: Package List length (0xC) larger than NumElements count > (0x4), truncated Strictly speaking, it is an error because ACPI specification says so (hence the error message). However, no exception is returned because of Windows compatibility according to the comments in the source. If everything is working fine, just ignore it. :-) Jung-uk Kim From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 22:50:08 2009 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 85AEB1065672; Tue, 13 Oct 2009 22:50:08 +0000 (UTC) (envelope-from robert.moore@intel.com) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by mx1.freebsd.org (Postfix) with ESMTP id 4D0188FC08; Tue, 13 Oct 2009 22:50:08 +0000 (UTC) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 13 Oct 2009 15:05:58 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.44,553,1249282800"; d="scan'208";a="457177756" Received: from orsmsx604.amr.corp.intel.com ([10.22.226.87]) by orsmga002.jf.intel.com with ESMTP; 13 Oct 2009 15:27:19 -0700 Received: from orsmsx503.amr.corp.intel.com ([10.22.226.47]) by orsmsx604.amr.corp.intel.com ([10.250.113.17]) with mapi; Tue, 13 Oct 2009 15:21:35 -0700 From: "Moore, Robert" To: Jung-uk Kim , "freebsd-current@FreeBSD.org" Date: Tue, 13 Oct 2009 15:21:35 -0700 Thread-Topic: ACPI Warning: Converted Buffer to expected String Thread-Index: AcpMUuduf35f3KlTS0mYY13PceygFwAAGP8w Message-ID: <4911F71203A09E4D9981D27F9D8308583B31B180@orsmsx503.amr.corp.intel.com> References: <20091011142256.GA3770@roadrunner.spoerlein.net> <200910131133.16487.jkim@FreeBSD.org> <4AD4F611.6080504@freebsd.org> <200910131815.53053.jkim@FreeBSD.org> In-Reply-To: <200910131815.53053.jkim@FreeBSD.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Mailman-Approved-At: Tue, 13 Oct 2009 22:56:42 +0000 Cc: Lawrence Stewart , "freebsd-acpi@freebsd.org" Subject: RE: ACPI Warning: Converted Buffer to expected String 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, 13 Oct 2009 22:50:08 -0000 Probably should be dropped down to a warning. This is usually caused by the BIOS modifying the package length on the fly.= No ASL compiler would do this. >-----Original Message----- >From: owner-freebsd-acpi@freebsd.org [mailto:owner-freebsd- >acpi@freebsd.org] On Behalf Of Jung-uk Kim >Sent: Tuesday, October 13, 2009 3:16 PM >To: freebsd-current@FreeBSD.org >Cc: Lawrence Stewart; freebsd-acpi@freebsd.org >Subject: Re: ACPI Warning: Converted Buffer to expected String > >On Tuesday 13 October 2009 05:50 pm, Lawrence Stewart wrote: >> Jung-uk Kim wrote: >> >> [snip] >> >> > by new ACPICA. However, if you see "ACPI Error", that's >> > something to worry about, e.g., cannot convert predefined types. >> >> So I should be worried about this line from my Toshiba R600 >> laptop's dmesg? >> >> ACPI Error: Package List length (0xC) larger than NumElements count >> (0x4), truncated > >Strictly speaking, it is an error because ACPI specification says so >(hence the error message). However, no exception is returned because >of Windows compatibility according to the comments in the source. > >If everything is working fine, just ignore it. :-) > >Jung-uk Kim >_______________________________________________ >freebsd-acpi@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-acpi >To unsubscribe, send any mail to "freebsd-acpi-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 23:03:36 2009 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 E489A106566B for ; Tue, 13 Oct 2009 23:03:36 +0000 (UTC) (envelope-from delphij@delphij.net) Received: from tarsier.delphij.net (delphij-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:2c9::2]) by mx1.freebsd.org (Postfix) with ESMTP id 95D238FC0C for ; Tue, 13 Oct 2009 23:03:36 +0000 (UTC) Received: from tarsier.geekcn.org (tarsier.geekcn.org [211.166.10.233]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tarsier.delphij.net (Postfix) with ESMTPS id BD7AC5C025 for ; Wed, 14 Oct 2009 07:03:35 +0800 (CST) Received: from localhost (tarsier.geekcn.org [211.166.10.233]) by tarsier.geekcn.org (Postfix) with ESMTP id 94CA855CD148; Wed, 14 Oct 2009 07:03:35 +0800 (CST) X-Virus-Scanned: amavisd-new at geekcn.org Received: from tarsier.geekcn.org ([211.166.10.233]) by localhost (mail.geekcn.org [211.166.10.233]) (amavisd-new, port 10024) with ESMTP id gnQq-h4dlhqZ; Wed, 14 Oct 2009 07:03:26 +0800 (CST) Received: from charlie.delphij.net (adsl-76-237-33-60.dsl.pltn13.sbcglobal.net [76.237.33.60]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tarsier.geekcn.org (Postfix) with ESMTPSA id 17ED955CD14D; Wed, 14 Oct 2009 07:03:25 +0800 (CST) DomainKey-Signature: a=rsa-sha1; s=default; d=delphij.net; c=nofws; q=dns; h=message-id:date:from:reply-to:organization:user-agent: mime-version:to:subject:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=q7JoA3R9EfOiW7gsmUzJglbeZjO7+f4nPWCnJMKPthTrdbM5nm0I/5C1KisqrgDfw 4skbOlTDElghDDVXbwGtw== Message-ID: <4AD5073B.5030100@delphij.net> Date: Tue, 13 Oct 2009 16:03:23 -0700 From: Xin LI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.23 (X11/20091004) MIME-Version: 1.0 To: FreeBSD Current X-Enigmail-Version: 0.96.0 OpenPGP: id=18EDEBA0; url=http://www.delphij.net/delphij.asc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: sftp broken? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: d@delphij.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2009 23:03:37 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Anyone noticed that sftp does not work anymore in recent -CURRENT? i.e. > sftp freefall.freebsd.org Connecting to freefall.freebsd.org... ls sftp> ls Segmentation fault The backtrace shows that the access violation happen inside libc (glob*) but I have not yet got a clue why this would ever happen. Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.13 (FreeBSD) iEYEARECAAYFAkrVBzoACgkQi+vbBBjt66ByMQCfYEmnGHZXQILM2pzaF4mkSjgB q0wAoLeLRT5jJWwkaIHNdKeBjU+7vdek =fe9C -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 23:28:30 2009 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 8173C1065679; Tue, 13 Oct 2009 23:28:30 +0000 (UTC) (envelope-from franson@gmail.com) Received: from mail-iw0-f189.google.com (mail-iw0-f189.google.com [209.85.223.189]) by mx1.freebsd.org (Postfix) with ESMTP id 2AC768FC46; Tue, 13 Oct 2009 23:28:29 +0000 (UTC) Received: by iwn27 with SMTP id 27so5286933iwn.7 for ; Tue, 13 Oct 2009 16:28:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=fRSL8vsrL4+Lq7b8XFkTNIc28SdJ0S0lTch1Gd5wTRI=; b=VnmX13Pgu8zzaW9q+21BPkfRup2rVP2D0o6dIqt0LIO/H3Ouz62tO2EurUlB52gHCl Ar0oVU0z8pLAg04hTf5zmiLaTfc32W61cJKTJBDYvrVN82tUDz7287OV51xFINC+wIY/ OKxOmxWOgiFGYL9KK6J5lcFIXzeANK4iVn9fU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=OUd4O8JVy8I2PchrBQtxBqIKRVVnrTMQhvd4PR03H2NqCwzHdfeEF18QZuTq8ldqop 9IJcUS9hdnfg0tvZWEMtD+kpYuouKYmfXXouOvUYdyQozqmSnsG+KdODMdKmzYlfTTOG 7wrG0wAzGxzAjyqr6go+avdJvT50E5EZZkJsM= MIME-Version: 1.0 Sender: franson@gmail.com Received: by 10.231.123.216 with SMTP id q24mr2390733ibr.43.1255476509349; Tue, 13 Oct 2009 16:28:29 -0700 (PDT) In-Reply-To: <86vdijdu0r.fsf@ds4.des.no> References: <200910122344.n9CNijv9037645@freebsd-current.sentex.ca> <86vdijdu0r.fsf@ds4.des.no> Date: Wed, 14 Oct 2009 07:28:29 +0800 X-Google-Sender-Auth: 0711d74f432db147 Message-ID: From: quickembed To: =?ISO-8859-1?Q?Dag=2DErling_Sm=F8rgrav?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Tue, 13 Oct 2009 23:33:10 +0000 Cc: arm@freebsd.org, FreeBSD Tinderbox , current@freebsd.org Subject: Re: [head tinderbox] failure on arm/arm 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, 13 Oct 2009 23:28:30 -0000 Then it should be indicated how to "link". 2009/10/14 Dag-Erling Sm=F8rgrav : > quickembed writes: >> this error shows you have not indicate how to compile libgssapi.a file. >> CC is for .c file, you need to tell what's for .a (assembly) file. > > No, the command line is correct. =A0Assembler sources end in .s or .S; .a > is a static library. > > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no > From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 23:43:05 2009 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 A615A106566B; Tue, 13 Oct 2009 23:43:05 +0000 (UTC) (envelope-from lstewart@freebsd.org) Received: from lauren.room52.net (lauren.room52.net [210.50.193.198]) by mx1.freebsd.org (Postfix) with ESMTP id 1B2108FC17; Tue, 13 Oct 2009 23:43:04 +0000 (UTC) Received: from lstewart-laptop.caia.swin.edu.au (216-239-45-4.google.com [216.239.45.4]) (authenticated bits=0) by lauren.room52.net (8.14.3/8.14.3) with ESMTP id n9DNgtmn055721 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Oct 2009 10:42:57 +1100 (EST) (envelope-from lstewart@freebsd.org) Message-ID: <4AD51077.1030603@freebsd.org> Date: Tue, 13 Oct 2009 16:42:47 -0700 From: Lawrence Stewart User-Agent: Thunderbird 2.0.0.23 (X11/20090909) MIME-Version: 1.0 To: Jung-uk Kim References: <20091011142256.GA3770@roadrunner.spoerlein.net> <200910131133.16487.jkim@FreeBSD.org> <4AD4F611.6080504@freebsd.org> <200910131815.53053.jkim@FreeBSD.org> In-Reply-To: <200910131815.53053.jkim@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RDNS_DYNAMIC, SPF_SOFTFAIL autolearn=disabled version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on lauren.room52.net Cc: freebsd-acpi@freebsd.org, freebsd-current@freebsd.org Subject: Re: ACPI Warning: Converted Buffer to expected String 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, 13 Oct 2009 23:43:05 -0000 Jung-uk Kim wrote: > On Tuesday 13 October 2009 05:50 pm, Lawrence Stewart wrote: >> Jung-uk Kim wrote: >> >> [snip] >> >>> by new ACPICA. However, if you see "ACPI Error", that's >>> something to worry about, e.g., cannot convert predefined types. >> So I should be worried about this line from my Toshiba R600 >> laptop's dmesg? >> >> ACPI Error: Package List length (0xC) larger than NumElements count >> (0x4), truncated > > Strictly speaking, it is an error because ACPI specification says so > (hence the error message). However, no exception is returned because > of Windows compatibility according to the comments in the source. > Ok thanks for explaining. > If everything is working fine, just ignore it. :-) When I boot this particular laptop into windows and then back into FreeBSD (even after a power down in between), I get a reproducible panic while the kernel is booting and probing devices which can only be fixed by going into the BIOS config screen and restoring to defaults. I suspect the Windows drivers are leaving the hardware in some fancy state the FreeBSD kernel doesn't like. I have a hunch it is ACPI related. Is there some way I can tell? The panic/backtrace is always the same as follows: Slab at 0xffffff00025d5b18, freei 3 = 0. panic: Duplicate free of item 0xffffff00025f8c00 from zone 0xffffff00b697d400(1024) Backtrace at the ddb prompt looks like this: db> bt kdb_enter()+0x3d panic()+0x17b uma_dbg_free()+0x171 uma_zfree_arg()+0x68 free()+0xbd device_set_driver()+0x8e device_attach()+0x19b bus_generic_attach()+0x1a acpi_pci_attach()+0x147 device_attach()+0x69 bus_generic_attach()+0x1a acpi_pcib_attach()+0x1a7 acpi_pcib_acpi_attach()+0x1a5 device_attach()+0x69 bus_generic_attach()+0x1a acpi_attach()+0x9e4 device_attach()+0x69 bus_generic_attach()+0x1a device_attach()+0x69 root_bus_configure()+0x28 configure()+0xa mi_startup()+0x59 btext()+0x2c Cheers, Lawrence From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 23:47:53 2009 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 C2E561065672; Tue, 13 Oct 2009 23:47:53 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 814248FC1D; Tue, 13 Oct 2009 23:47:53 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id A1B3A6D41B; Tue, 13 Oct 2009 23:47:52 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 3901384513; Wed, 14 Oct 2009 01:47:52 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: quickembed References: <200910122344.n9CNijv9037645@freebsd-current.sentex.ca> <86vdijdu0r.fsf@ds4.des.no> Date: Wed, 14 Oct 2009 01:47:52 +0200 In-Reply-To: (quickembed@gmail.com's message of "Wed, 14 Oct 2009 07:28:29 +0800") Message-ID: <86my3uetzr.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: arm@freebsd.org, FreeBSD Tinderbox , current@freebsd.org Subject: Re: [head tinderbox] failure on arm/arm 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, 13 Oct 2009 23:47:53 -0000 quickembed writes: > Dag-Erling Sm=C3=B8rgrav writes: > > quickembed writes: > > > this error shows you have not indicate how to compile libgssapi.a > > > file. CC is for .c file, you need to tell what's for .a > > > (assembly) file. > > No, the command line is correct. Assembler sources end in .s or .S; > > .a is a static library. > Then it should be indicated how to "link". No. The Makefile is fine. One of the source files was missing an #include that contained inline functions or macros, which the compiler then assumed were external functions. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 23:54:12 2009 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 39D81106566B for ; Tue, 13 Oct 2009 23:54:12 +0000 (UTC) (envelope-from bsd@acd.homelinux.org) Received: from office.acapsecurity.com (rrcs-67-52-121-82.west.biz.rr.com [67.52.121.82]) by mx1.freebsd.org (Postfix) with ESMTP id 1A4378FC1A for ; Tue, 13 Oct 2009 23:54:11 +0000 (UTC) Received: from acd.homelinux.org (unknown [10.0.15.5]) by office.acapsecurity.com (Postfix) with ESMTP id 0EEE95C24 for ; Tue, 13 Oct 2009 16:41:10 -0700 (PDT) Received: by acd.homelinux.org (Postfix, from userid 1001) id 805284429; Tue, 13 Oct 2009 17:41:09 -0600 (MDT) From: bsduser To: freebsd-current@freebsd.org References: <86051.1254232666@critter.freebsd.dk> <20091013174201.GC67082@weongyo> Date: Tue, 13 Oct 2009 17:41:09 -0600 In-Reply-To: <20091013174201.GC67082@weongyo> (Weongyo Jeong's message of "Tue, 13 Oct 2009 10:42:01 -0700") Message-ID: <86iqei7tgq.fsf@jodie.vectavision.com> User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Subject: Re: if_rum dies on transmit... 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, 13 Oct 2009 23:54:12 -0000 Weongyo Jeong writes: > On Tue, Sep 29, 2009 at 01:57:46PM +0000, Poul-Henning Kamp wrote: >> >> Has anybody else seen if_rum die when you try to transmit a file over >> a TCP connection ? >> >> If I try to print across the network, upload a file with ftp or anything >> else of that general tenor, if_rum seems to hang the output queue and >> stops transmitting packets. >> >> Restarting wpa_supplicant mostly resolves the issue, but it does not >> on its own discover the problem. >> >> According to tcpdump(8), packets are still received. >> >> Any ideas ? > > Could you please test with attached patch? > > regards, > Weongyo Jeong > > I had the same issues with if_rum at least while using WPA and your patch made them go away.... ( although removing and plugging back in does not quite work ) # scp INDEX-8* cookie:/usr/ports INDEX-8 100% 19MB 2.1MB/s 00:09 INDEX-8.db 100% 34MB 2.4MB/s 00:14 before the patch this would just hang. Another quick test using rsync on a bunch of files worked flawless too. usbconfig list: ugen7.2: at usbus7, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON The adapter is a WUSB54GC and yes, you made my day :-) From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 00:06:45 2009 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 0464F1065696; Wed, 14 Oct 2009 00:06:45 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id B5E158FC19; Wed, 14 Oct 2009 00:06:44 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 09C826D41C; Wed, 14 Oct 2009 00:06:44 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id C766984537; Wed, 14 Oct 2009 02:06:43 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: quickembed References: <200910122344.n9CNijv9037645@freebsd-current.sentex.ca> <86vdijdu0r.fsf@ds4.des.no> <86my3uetzr.fsf@ds4.des.no> Date: Wed, 14 Oct 2009 02:06:43 +0200 In-Reply-To: (quickembed@gmail.com's message of "Wed, 14 Oct 2009 07:53:23 +0800") Message-ID: <86aazuet4c.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: arm@freebsd.org, FreeBSD Tinderbox , current@freebsd.org Subject: Re: [head tinderbox] failure on arm/arm 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, 14 Oct 2009 00:06:45 -0000 quickembed writes: > should not it say "unresolved external function...." etc if the > compiler can not find the function body? Yes, that's exactly what it does: /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function 'gsskrb5_extract_= authz_data_from_sec_context': /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit declara= tion of function 'der_get_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit declara= tion of function 'der_free_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit declara= tion of function 'der_length_oid' /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit declara= tion of function 'der_put_oid' DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 00:35:07 2009 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 E2FAF1065670 for ; Wed, 14 Oct 2009 00:35:07 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id A5BC18FC13 for ; Wed, 14 Oct 2009 00:35:07 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 8DEF66D41B; Wed, 14 Oct 2009 00:35:06 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 4EF54844C2; Wed, 14 Oct 2009 02:35:06 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: d@delphij.net References: <4AD5073B.5030100@delphij.net> Date: Wed, 14 Oct 2009 02:35:06 +0200 In-Reply-To: <4AD5073B.5030100@delphij.net> (Xin LI's message of "Tue, 13 Oct 2009 16:03:23 -0700") Message-ID: <8663aiert1.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Cc: FreeBSD Current Subject: Re: sftp 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: Wed, 14 Oct 2009 00:35:08 -0000 --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Xin LI writes: > The backtrace shows that the access violation happen inside libc > (glob*) but I have not yet got a clue why this would ever happen. It's trying to dereference a NULL function pointer: (gdb) frame 1 #1 0x0000000800ef9920 in glob2 (pathbuf=3D0x7fffffff5660,=20 pathend=3D0x7fffffff56a8, pathend_last=3D0x7fffffff7658,=20 pattern=3D0x7fffffff76a8, pglob=3D0x7fffffffd8d0, limit=3D0x7fffffffd72= 0) at /usr/src/lib/libc/gen/glob.c:844 844 return((*pglob->gl_lstat)(buf, sb)); (gdb) p pglob $1 =3D (glob_t *) 0x7fffffffd8d0 (gdb) p *pglob $2 =3D {gl_pathc =3D 0, gl_matchc =3D 0, gl_offs =3D 0, gl_flags =3D 216,=20 gl_pathv =3D 0x0, gl_errfunc =3D 0, gl_closedir =3D 0x408bfb ,=20 gl_readdir =3D 0x408b50 , gl_opendir =3D 0x408b20 ,=20 gl_lstat =3D 0, gl_stat =3D 0x7fffffffda00} The problem is that OpenSSH wants to use its own version of glob(3), but we don't compile it or link it in, so it calls ours with a struct pglob that has the wrong layout. The attached patch should fix that, I will commit it when I've tested it more thoroughly. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no --=-=-= Content-Type: text/x-patch Content-Disposition: inline; filename=openssh-glob.diff Index: crypto/openssh/ssh_namespace.h =================================================================== --- crypto/openssh/ssh_namespace.h (revision 197801) +++ crypto/openssh/ssh_namespace.h (working copy) @@ -223,6 +223,8 @@ #define get_u32 ssh_get_u32 #define get_u64 ssh_get_u64 #define getrrsetbyname ssh_getrrsetbyname +#define glob ssh_glob +#define globfree ssh_globfree #define host_hash ssh_host_hash #define hostfile_read_key ssh_hostfile_read_key #define hpdelim ssh_hpdelim Index: secure/lib/libssh/Makefile =================================================================== --- secure/lib/libssh/Makefile (revision 197801) +++ secure/lib/libssh/Makefile (working copy) @@ -19,7 +19,7 @@ # compiled directly into sshd instead. # Portability layer -SRCS+= bsd-misc.c fmt_scaled.c getrrsetbyname.c \ +SRCS+= bsd-misc.c fmt_scaled.c getrrsetbyname.c glob.c \ openssl-compat.c port-tun.c strtonum.c vis.c xcrypt.c xmmap.c # FreeBSD additions SRCS+= version.c --=-=-=-- From owner-freebsd-current@FreeBSD.ORG Tue Oct 13 23:53:24 2009 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 AB0EF1065679; Tue, 13 Oct 2009 23:53:24 +0000 (UTC) (envelope-from franson@gmail.com) Received: from mail-iw0-f189.google.com (mail-iw0-f189.google.com [209.85.223.189]) by mx1.freebsd.org (Postfix) with ESMTP id 548298FC0A; Tue, 13 Oct 2009 23:53:24 +0000 (UTC) Received: by iwn27 with SMTP id 27so5296583iwn.7 for ; Tue, 13 Oct 2009 16:53:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type:content-transfer-encoding; bh=9WPWNqt0/8SOPg8A7FVMecz7C43AWaCmBNvQmufZkC8=; b=HG4sSF7641BoxLAI37Q/ODl+JcotkWTzUh6+j9LU0vUAxgfWaghzaLhc6yAc5g6H+v qoot/ZCdwRDYYhW7RS/bD/IC8AtfQixmWd1MjlHP2H5pt1/rkjvox+39dezFYIGLoO6u RUG5wPUUBsFZhJfkSDTXg0jRwiqpHAUgBKEOA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=MVsrdTGn2TMSMmXtqmEKTBK04ErZetNNw6NKjApLcyA+jTgZrIhY/2ovakVrF+XVcv 2XpI6bJp6L1nkDCBcjRoU9jDyMvBZym6IQLDSA2XLSY3R7TgUODVqyJoDmRVbVDbI7vs oRYUA82qjBrpWcMaGnOlH4O1Nj4YNvTLjxuVo= MIME-Version: 1.0 Sender: franson@gmail.com Received: by 10.231.26.131 with SMTP id e3mr4168337ibc.0.1255478003828; Tue, 13 Oct 2009 16:53:23 -0700 (PDT) In-Reply-To: <86my3uetzr.fsf@ds4.des.no> References: <200910122344.n9CNijv9037645@freebsd-current.sentex.ca> <86vdijdu0r.fsf@ds4.des.no> <86my3uetzr.fsf@ds4.des.no> Date: Wed, 14 Oct 2009 07:53:23 +0800 X-Google-Sender-Auth: 57018901cf515f27 Message-ID: From: quickembed To: =?ISO-8859-1?Q?Dag=2DErling_Sm=F8rgrav?= Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Wed, 14 Oct 2009 01:37:17 +0000 Cc: arm@freebsd.org, FreeBSD Tinderbox , current@freebsd.org Subject: Re: [head tinderbox] failure on arm/arm 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, 13 Oct 2009 23:53:24 -0000 should not it say "unresolved external function...." etc if the compiler can not find the function body? 2009/10/14 Dag-Erling Sm=F8rgrav : > quickembed writes: >> Dag-Erling Sm=F8rgrav writes: >> > quickembed writes: >> > > this error shows you have not indicate how to compile libgssapi.a >> > > file. =A0CC is for .c file, you need to tell what's for .a >> > > (assembly) file. >> > No, the command line is correct. =A0Assembler sources end in .s or .S; >> > .a is a static library. >> Then it should be indicated how to "link". > > No. =A0The Makefile is fine. =A0One of the source files was missing an > #include that contained inline functions or macros, which the compiler > then assumed were external functions. > > DES > -- > Dag-Erling Sm=F8rgrav - des@des.no > From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 06:28:35 2009 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 4F967106568D; Wed, 14 Oct 2009 06:28:35 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206049004.chello.pl [87.206.49.4]) by mx1.freebsd.org (Postfix) with ESMTP id 9316E8FC1F; Wed, 14 Oct 2009 06:28:34 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 0A9ED45CAC; Wed, 14 Oct 2009 08:28:33 +0200 (CEST) Received: from localhost (chello087206049004.chello.pl [87.206.49.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id ED95F45B36; Wed, 14 Oct 2009 08:28:27 +0200 (CEST) Date: Wed, 14 Oct 2009 08:28:27 +0200 From: Pawel Jakub Dawidek To: Andriy Gapon Message-ID: <20091014062827.GC1696@garage.freebsd.pl> References: <4AD3220B.5030502@icyb.net.ua> <86ws30ikfw.fsf@gmail.com> <4AD45A8D.4070605@icyb.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Pk6IbRAofICFmK5e" Content-Disposition: inline In-Reply-To: <4AD45A8D.4070605@icyb.net.ua> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: freebsd-fs@FreeBSD.ORG, Anonymous , freebsd-current@FreeBSD.ORG Subject: Re: zfs boot vs loader 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, 14 Oct 2009 06:28:35 -0000 --Pk6IbRAofICFmK5e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Oct 13, 2009 at 01:46:37PM +0300, Andriy Gapon wrote: >=20 > Thanks to all who replied! > I think that I figured it out with your help. >=20 > 'unload' does indeed unload zpool.cache and the latter is needed for prop= er zfs > root mounting. > 'boot /other/kernel' executes some loader scripts and zpool.cache gets lo= aded in > this case (because of the settings in defaults/loader.conf). > When doing manual 'load xxx' and then just 'boot' no loader scripts are e= xecuted > and zpool.cache does not get loaded. In this case one has to load it manu= ally > using the suggested 'load -t xxx' approach. Could you repeat what you were doing but with vfs.zfs.debug set to 1 from the loader? You should see some messages about missing file, maybe we should do them visible always and not after increasing debug level? --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --Pk6IbRAofICFmK5e Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFK1W+KForvXbEpPzQRAsAXAJ9LWdtKzOwrlZAfq6yVOZCnGWB8JgCfWSUr tqaZYC/lZtc5Do9/Yf9z6M8= =A5Tp -----END PGP SIGNATURE----- --Pk6IbRAofICFmK5e-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 06:32:20 2009 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 CA7D3106566B; Wed, 14 Oct 2009 06:32:20 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from dd12710.kasserver.com (dd12710.kasserver.com [85.13.134.233]) by mx1.freebsd.org (Postfix) with ESMTP id 5B4148FC12; Wed, 14 Oct 2009 06:32:20 +0000 (UTC) Received: from current.Sisis.de (cazador.sisis.de [193.31.11.193]) by dd12710.kasserver.com (Postfix) with ESMTP id 0B43818648725; Wed, 14 Oct 2009 08:32:20 +0200 (CEST) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id n9E6WLv2002353; Wed, 14 Oct 2009 08:32:21 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Wed, 14 Oct 2009 08:32:21 +0200 From: Matthias Apitz To: Martin Wilke Message-ID: <20091014063221.GA2301@current.Sisis.de> References: <20091011062419.GA2168@current.Sisis.de> <3a142e750910111214rb75f185k12b2cc7e1aba59d9@mail.gmail.com> <20091012130914.GA4180@current.Sisis.de> <20091013153815.GA88394@bsdcrew.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20091013153815.GA88394@bsdcrew.de> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) Cc: kde-freebsd@kde.org, freebsd-current@freebsd.org Subject: Re: [kde-freebsd] 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 06:32:20 -0000 El día Tuesday, October 13, 2009 a las 05:38:15PM +0200, Martin Wilke escribió: > > # uname -a > > FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r197801: Tue > > Oct 6 13:57:38 CEST 2009 > > guru@vm-azul.Sisis.de:/usr/obj/usr/src/sys/REBELION-HEAD i386 > > > > When kernel and user land have been on 9-CURRENT, I removed /usr/ports, > > checked them out with CVS and build all my ports, especially KDE3. > > > > I don't see how an old library or binary can cause this. Only some ABI > > change which is not supported in the KDE sources... > > > > Don't know if someone from FreeBSD's KDE team can (or will) comment on it. It > > seems to me that they all went away (to KDE4 :-)). > > > > Thx > > unfortunately you're right, we're a small team, > we spend all our energy to KDE4. Sorry but > so is the life. > > - - Martin Hi Martin, I understand the situation and I fully appreciate your work (and the work of others) to bring KDE to FreeBSD. Don't get me wrong with the following I'd like to say. I think only supporting KDE4 is not a good idea. IMHO, KDE4 is a bit heading in the wrong direction. KDE4 is unusable for a lot of (older) hardware and is unusable, at least, for smaller laptops or netbooks, just because of the resources it is consuming. If the KDE team is leaving KDE3, and I don't expect further development, but only compability with upcoming FreeBSD ABI changes (or whatever), than we will not have KDE3 anymore from 9-CURRENT (or even from 8.0-RELEASE) anymore. Which would be a real pity :-( I'm willing to nail this small issue down. I've already compiled the arts-1.5.10_2,1 port with --enable-debug=full and will test it the upcoming weekend. Do you have any hints for me on debugging? I have had already a look into the code where it crashes in soundserver/kmedia2.cc: ... unsigned long Arts::PlayObject_private_base::_IID = Arts::MCOPUtils::makeIID("Arts::PlayObject_private"); Arts::PlayObject_base *Arts::PlayObject_base::_create(const std::string& subClass) { Arts::Object_skel *skel = Arts::ObjectManager::the()->create(subClass); assert(skel); Arts::PlayObject_base *castedObject = (Arts::PlayObject_base *)skel->_cast(Arts::PlayObject_base::_IID); assert(castedObject); return castedObject; } ... but can't see anything what could cause this SIGSEGV; as well I have fetched the 8.0-RC1 precompiled package arts-1.5.10_2,1.tbz and will give it a try in 9-CURRENT. Will let you know what I can find out. Thanks matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 06:40:09 2009 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 0210110656A9 for ; Wed, 14 Oct 2009 06:40:09 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mail.cksoft.de (mail.cksoft.de [195.88.108.3]) by mx1.freebsd.org (Postfix) with ESMTP id 871CB8FC08 for ; Wed, 14 Oct 2009 06:40:08 +0000 (UTC) Received: from localhost (amavis.fra.cksoft.de [192.168.74.71]) by mail.cksoft.de (Postfix) with ESMTP id 12BD841C6EA; Wed, 14 Oct 2009 08:40:07 +0200 (CEST) X-Virus-Scanned: amavisd-new at cksoft.de Received: from mail.cksoft.de ([195.88.108.3]) by localhost (amavis.fra.cksoft.de [192.168.74.71]) (amavisd-new, port 10024) with ESMTP id DKhHJPaPluEm; Wed, 14 Oct 2009 08:40:06 +0200 (CEST) Received: by mail.cksoft.de (Postfix, from userid 66) id 3390341C6FC; Wed, 14 Oct 2009 08:40:06 +0200 (CEST) Received: from maildrop.int.zabbadoz.net (maildrop.int.zabbadoz.net [10.111.66.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.int.zabbadoz.net (Postfix) with ESMTP id 04AC24448E6; Wed, 14 Oct 2009 06:37:57 +0000 (UTC) Date: Wed, 14 Oct 2009 06:37:57 +0000 (UTC) From: "Bjoern A. Zeeb" X-X-Sender: bz@maildrop.int.zabbadoz.net To: Alexander Best In-Reply-To: Message-ID: <20091014063657.Q5956@maildrop.int.zabbadoz.net> References: X-OpenPGP-Key: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Harald Schmalzbauer , freebsd-current@freebsd.org Subject: Re: Where to report LORs? (ffs and unionfs LORs included 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, 14 Oct 2009 06:40:09 -0000 On Tue, 13 Oct 2009, Alexander Best wrote: > Harald Schmalzbauer schrieb am 2009-10-10: >> Alexander Best schrieb am 07.07.2009 21:33 (localtime): >>> try http://sources.zabbadoz.net/freebsd/lor.html > >> I still see a unionfs LOR with RELENG_8 which is not listed, so I'd >> like to report it again. >> lock order reversal: >> 1st 0xc372c488 unionfs (unionfs) @ >> /FlashBSD/src/sys/fs/unionfs/union_subr.c:356 >> 2nd 0xc372c594 ufs (ufs) @ /FlashBSD/src/sys/kern/vfs_subr.c:2188 >> KDB: stack backtrace: >> db_trace_self_wrapper(c0616390,c08cd5d5,c3416770,c3416500,d5c42864,.. >> .) at db_trace_self_wrapper+0x26 >> _witness_debugger(c08cd5d5,c372c594,c08c0703,c3416500,c08d4ec2,...) >> at _witness_debugger+0x49 >> witness_checkorder(c372c594,9,c08d4ec2,88c,0,...) at >> witness_checkorder+0x6ec >> __lockmgr_args(c372c594,80100,c372c5b0,0,0,...) at >> __lockmgr_args+0xc97 >> ffs_lock(d5c42958,8,c36c4764,80100,c372c53c,...) at ffs_lock+0x96 >> VOP_LOCK1_APV(c09374a0,d5c42958,c05d89e9,c09477c0,c372c53c,...) at >> VOP_LOCK1_APV+0x9a >> _vn_lock(c372c53c,80100,c08d4ec2,88c,c0877c6e,...) at _vn_lock+0x46 >> vrele(c372c53c,d5c429d8,c372c4a4,0,0,...) at vrele+0x12a >> unionfs_noderem(c372c430,c36c46c0,d5c42a44,c06764fc,d5c42a20,...) at >> unionfs_noderem+0x1e5 >> unionfs_reclaim(d5c42a20,d5c42a20,0,0,c372c4a4,...) at >> unionfs_reclaim+0x1b >> vgonel(c372c4a4,0,c08d4ec2,9c5,c372c4a4,...) at vgonel+0x100 >> vrecycle(c372c430,c36c46c0,d5c42aa4,c0675c29,d5c42a8c,...) at >> vrecycle+0x6a >> unionfs_inactive(d5c42a8c,d5c42a8c,c08d4ec2,924,c0947780,...) at >> unionfs_inactive+0x28 >> vinactive(c372c594,d5c42ac0,c08d4ec2,8aa,c3451de0,...) at >> vinactive+0x6a >> vput(c372c430,ffffffdf,c344ab80,0,c36c46c0,...) at vput+0x205 >> kern_statat_vnhook(c36c46c0,0,ffffff9c,28209e1c,0,...) at >> kern_statat_vnhook+0xe0 >> kern_statat(c36c46c0,0,ffffff9c,28209e1c,0,...) at kern_statat+0x3c >> kern_stat(c36c46c0,28209e1c,0,d5c42c18,c0a83a18,...) at >> kern_stat+0x36 >> stat(c36c46c0,d5c42cf8,8,d5c42d38,c0916cd0,...) at stat+0x2b >> syscall(d5c42d38) at syscall+0x176 >> Xint0x80_syscall() at Xint0x80_syscall+0x20 >> --- syscall (188, FreeBSD ELF32, stat), eip = 0x281c6c2b, esp = >> 0xbfbfe96c, ebp = 0xbfbfea68 --- > >> So far I couldn't notice any deadlock, but the box is not in >> production yet. > >> -Harry > > you might also want to write Bjoern Zeeb (http://wiki.freebsd.org/BjoernZeeb) > with a link to your report. he's the guy maintaining the lor page. preferably use the reference already give in this thread at the top: http://sources.zabbadoz.net/freebsd/lor.html /bz -- Bjoern A. Zeeb It will not break if you know what you are doing. From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 07:05:44 2009 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 C0EF8106566B; Wed, 14 Oct 2009 07:05:44 +0000 (UTC) (envelope-from bland@FreeBSD.org) Received: from mail1.asahi-net.or.jp (mail1.asahi-net.or.jp [202.224.39.197]) by mx1.freebsd.org (Postfix) with ESMTP id 86D5C8FC0A; Wed, 14 Oct 2009 07:05:44 +0000 (UTC) Received: from hub.bbnest.net (w133033.ppp.asahi-net.or.jp [121.1.133.33]) by mail1.asahi-net.or.jp (Postfix) with ESMTP id D7E6D7C18B; Wed, 14 Oct 2009 15:46:03 +0900 (JST) Received: from hub.bbnest.net (localhost [127.0.0.1]) by hub.bbnest.net (8.14.3/8.14.3) with ESMTP id n9E6jwe0076875 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 14 Oct 2009 15:45:58 +0900 (JST) (envelope-from bland@FreeBSD.org) Received: (from www@localhost) by hub.bbnest.net (8.14.3/8.14.3/Submit) id n9E6jwH3076874; Wed, 14 Oct 2009 15:45:58 +0900 (JST) (envelope-from bland@FreeBSD.org) X-Authentication-Warning: hub.bbnest.net: www set sender to bland@FreeBSD.org using -f To: =?UTF-8?Q?Dag-Erling_Sm=C3=B8rgrav?= MIME-Version: 1.0 Date: Wed, 14 Oct 2009 15:45:58 +0900 From: Alexander Nedotsukov In-Reply-To: <86aazuet4c.fsf@ds4.des.no> References: <200910122344.n9CNijv9037645@freebsd-current.sentex.ca> <86vdijdu0r.fsf@ds4.des.no> <86my3uetzr.fsf@ds4.des.no> <86aazuet4c.fsf@ds4.des.no> Message-ID: X-Sender: bland@FreeBSD.org User-Agent: RoundCube Webmail/0.2a Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 X-DSPAM-Result: Whitelisted X-DSPAM-Processed: Wed Oct 14 15:46:03 2009 X-DSPAM-Confidence: 0.9991 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 4ad573ab768763761837599 Cc: arm@FreeBSD.org, quickembed , FreeBSD Tinderbox , current@FreeBSD.org Subject: Re: [head tinderbox] failure on arm/arm 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, 14 Oct 2009 07:05:44 -0000 Heh. You just repeat my mistake (presumably with a bit of help from my side though). Those warning lines are really provoking :-) While missed #include issue still true it was not a source of build failure. libgssapi_krb5 now have libgssapi as a dependency but stay first in the _prebuild_libs list and nothing said build framework why it must build it in a different order. I committed the fix yesterday: http://svn.freebsd.org/viewvc/base?view=revision&revision=198020 Alexander. ps. I noticed that mails from tinderbox.freebsd.org contains link to not existed tinderbox.des.no host. On Wed, 14 Oct 2009 02:06:43 +0200, Dag-Erling Smørgrav wrote: > quickembed writes: >> should not it say "unresolved external function...." etc if the >> compiler can not find the function body? > > Yes, that's exactly what it does: > > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c: In function > 'gsskrb5_extract_authz_data_from_sec_context': > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:591: warning: implicit > declaration of function 'der_get_oid' > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:601: warning: implicit > declaration of function 'der_free_oid' > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:614: warning: implicit > declaration of function 'der_length_oid' > /src/kerberos5/lib/libgssapi_krb5/gss_krb5.c:622: warning: implicit > declaration of function 'der_put_oid' > > DES From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 07:36:38 2009 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 375F71065670 for ; Wed, 14 Oct 2009 07:36:38 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe15.swip.net [212.247.155.193]) by mx1.freebsd.org (Postfix) with ESMTP id 91BCE8FC0A for ; Wed, 14 Oct 2009 07:36:37 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=pGLkceISAAAA:8 a=8WeOH9NI7pJRFFGyxY4A:9 a=UPSk1wJxiMMfolcfla_Lh05p5gcA:4 a=MSl-tDqOz04A:10 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe15.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 576518663; Wed, 14 Oct 2009 09:36:35 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Wed, 14 Oct 2009 09:35:46 +0200 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: <86051.1254232666@critter.freebsd.dk> <20091013174201.GC67082@weongyo> <86iqei7tgq.fsf@jodie.vectavision.com> In-Reply-To: <86iqei7tgq.fsf@jodie.vectavision.com> X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910140935.46509.hselasky@c2i.net> Cc: bsduser Subject: Re: if_rum dies on transmit... 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, 14 Oct 2009 07:36:38 -0000 On Wednesday 14 October 2009 01:41:09 bsduser wrote: > Weongyo Jeong writes: > > On Tue, Sep 29, 2009 at 01:57:46PM +0000, Poul-Henning Kamp wrote: > >> Has anybody else seen if_rum die when you try to transmit a file over > >> a TCP connection ? > >> > >> If I try to print across the network, upload a file with ftp or anything > >> else of that general tenor, if_rum seems to hang the output queue and > >> stops transmitting packets. > >> > >> Restarting wpa_supplicant mostly resolves the issue, but it does not > >> on its own discover the problem. > >> > >> According to tcpdump(8), packets are still received. > >> > >> Any ideas ? > > > > Could you please test with attached patch? > > > > regards, > > Weongyo Jeong > > I had the same issues with if_rum at least while using WPA and your patch > made them go away.... ( although removing and plugging back in does not > quite work ) > > # scp INDEX-8* cookie:/usr/ports > INDEX-8 100% 19MB 2.1MB/s 00:09 > INDEX-8.db 100% 34MB 2.4MB/s 00:14 > > before the patch this would just hang. > > Another quick test using rsync on a bunch of files worked flawless too. > > usbconfig list: > > ugen7.2: at usbus7, cfg=0 > md=HOST spd=HIGH (480Mbps) pwr=ON > > The adapter is a WUSB54GC and yes, you made my day :-) Weongyo: Is the problem that some ifqueues go full and then the USB transfers are not restarted properly? Probably the other wlan network adapters have the same problem too and should be patched similarly. --HPS From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 10:49:57 2009 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 AD5DB106566B for ; Wed, 14 Oct 2009 10:49:57 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay3.uni-muenster.de (ZIVM-EXRELAY3.UNI-MUENSTER.DE [128.176.192.20]) by mx1.freebsd.org (Postfix) with ESMTP id 4399A8FC1C for ; Wed, 14 Oct 2009 10:49:56 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,557,1249250400"; d="scan'208";a="15836140" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER03.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay3.uni-muenster.de with ESMTP; 14 Oct 2009 12:49:55 +0200 Received: by ZIVMAILUSER03.UNI-MUENSTER.DE (Postfix, from userid 149459) id 5FFC01B0751; Wed, 14 Oct 2009 12:49:55 +0200 (CEST) Date: Wed, 14 Oct 2009 12:49:54 +0200 (CEST) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: buffers not syncing correctly during shutdown 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, 14 Oct 2009 10:49:57 -0000 hi there, to keep it short: 1. mount a removable device (e.g. an usb stick) (better use -r to prevent data loss) 2. unplug the device (without unmounting it) 3. `shutdown -r now` what happens is that the usual shutdown routine gets processed until all buffers are synced, but then the system stalls. after resetting the system all devices (which were supposed to be synced) are marked dirty and are being fsck'ed. cheers. alex oh...and i'm running FreeBSD otaku 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r197914: Sat Oct 10 02:58:19 CEST 2009 root@otaku:/usr/obj/usr/src/sys/ARUNDEL i386 From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 11:21:52 2009 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 51F4C106568B for ; Wed, 14 Oct 2009 11:21:52 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay3.uni-muenster.de (ZIVM-EXRELAY3.UNI-MUENSTER.DE [128.176.192.20]) by mx1.freebsd.org (Postfix) with ESMTP id DD0CE8FC19 for ; Wed, 14 Oct 2009 11:21:51 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,557,1249250400"; d="scan'208";a="15838290" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER04.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay3.uni-muenster.de with ESMTP; 14 Oct 2009 13:21:51 +0200 Received: by ZIVMAILUSER04.UNI-MUENSTER.DE (Postfix, from userid 149459) id ECA4E1B07BE; Wed, 14 Oct 2009 13:21:50 +0200 (CEST) Date: Wed, 14 Oct 2009 13:21:50 +0200 (CEST) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Subject: panic when mounting device >= 2 times 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, 14 Oct 2009 11:21:52 -0000 could somebody have a look at this PR please: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/108968 this still exists in -CURRENT. cheers. alex From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 11:59:01 2009 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 35149106568B for ; Wed, 14 Oct 2009 11:59:01 +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 7A84B8FC17 for ; Wed, 14 Oct 2009 11:59:00 +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 OAA01491; Wed, 14 Oct 2009 14:58:56 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4AD5BD00.4050700@icyb.net.ua> Date: Wed, 14 Oct 2009 14:58:56 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: Alexander Best References: In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: panic when mounting device >= 2 times 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, 14 Oct 2009 11:59:01 -0000 on 14/10/2009 14:21 Alexander Best said the following: > could somebody have a look at this PR please: > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/108968 > > this still exists in -CURRENT. This is because of serious and long-standing brokenness (probably from time of introduction of GEOM) in g_vfs_open/g_vfs_close. The essence: 1. we allow multiple concurrent read-only mounts of a device 2. but even a read-only mount mangles bufobj of device vnode 3. Bug! Trivial fix with POLA violation - prohibit concurrent RO mounts. Non-trivial fix - _somehow_ avoid changing or depending on device vnode bufobj. See this for even more evil example of this problem: http://lists.freebsd.org/pipermail/freebsd-fs/2009-February/005676.html -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 12:33:26 2009 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 6DE70106566C for ; Wed, 14 Oct 2009 12:33:26 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from mx.utwente.nl (mx1.utsp.utwente.nl [130.89.2.12]) by mx1.freebsd.org (Postfix) with ESMTP id E05638FC12 for ; Wed, 14 Oct 2009 12:33:25 +0000 (UTC) Received: from nox.student.utwente.nl (nox.student.utwente.nl [130.89.165.91]) by mx.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id n9ECXAeR028088; Wed, 14 Oct 2009 14:33:10 +0200 From: Pieter de Goeje To: freebsd-current@freebsd.org, Matthias Apitz Date: Wed, 14 Oct 2009 14:33:10 +0200 User-Agent: KMail/1.9.10 References: <20091011062419.GA2168@current.Sisis.de> <20091013153815.GA88394@bsdcrew.de> <20091014063221.GA2301@current.Sisis.de> In-Reply-To: <20091014063221.GA2301@current.Sisis.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910141433.10715.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact icts.servicedesk@utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: kde-freebsd@kde.org, Martin Wilke Subject: Re: [kde-freebsd] 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV 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, 14 Oct 2009 12:33:26 -0000 On Wednesday 14 October 2009 08:32:21 Matthias Apitz wrote: > I think only supporting KDE4 is not a good idea. IMHO, KDE4 is a bit > heading in the wrong direction. KDE4 is unusable for a lot of (older) > hardware and is unusable, at least, for smaller laptops or netbooks, > just because of the resources it is consuming. If the KDE team is > leaving KDE3, and I don't expect further development, but only > compability with upcoming FreeBSD ABI changes (or whatever), than we > will not have KDE3 anymore from 9-CURRENT (or even from 8.0-RELEASE) > anymore. Which would be a real pity :-( I'm suprised someone actually uses artsd. As a fellow KDE3 user on 9-CURRENT (on beefy hardware btw), I didn't have this issue because I always disable artsd because I don't want sound notifications. As long as people are using KDE3 I don't think it will die because people just like you will find the problem(s) and fix it. That said, I couldn't reproduce the problem (artsd works fine if I enable it). Uname: FreeBSD 9.0-CURRENT #2: Fri Oct 9 08:37:37 CEST 2009 i386 - Pieter > > I'm willing to nail this small issue down. I've already compiled the > arts-1.5.10_2,1 port with --enable-debug=full and will test it the > upcoming weekend. Do you have any hints for me on debugging? > I have had already a look into the code where it crashes in > soundserver/kmedia2.cc: > > ... > unsigned long Arts::PlayObject_private_base::_IID = > Arts::MCOPUtils::makeIID("Arts::PlayObject_private"); > > Arts::PlayObject_base *Arts::PlayObject_base::_create(const std::string& > subClass) { > Arts::Object_skel *skel = > Arts::ObjectManager::the()->create(subClass); assert(skel); > Arts::PlayObject_base *castedObject = (Arts::PlayObject_base > *)skel->_cast(Arts::PlayObject_base::_IID); assert(castedObject); > return castedObject; > } > ... > > but can't see anything what could cause this SIGSEGV; > > as well I have fetched the 8.0-RC1 precompiled package arts-1.5.10_2,1.tbz > and will give it a try in 9-CURRENT. > > Will let you know what I can find out. > > Thanks > > matthias From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 12:44:12 2009 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 A564E106566B; Wed, 14 Oct 2009 12:44:12 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from dd12710.kasserver.com (dd12710.kasserver.com [85.13.134.233]) by mx1.freebsd.org (Postfix) with ESMTP id 5FB7D8FC1B; Wed, 14 Oct 2009 12:44:12 +0000 (UTC) Received: from current.Sisis.de (cazador.sisis.de [193.31.11.193]) by dd12710.kasserver.com (Postfix) with ESMTP id 7187E18648752; Wed, 14 Oct 2009 14:44:13 +0200 (CEST) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id n9ECiAPJ004636; Wed, 14 Oct 2009 14:44:10 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Wed, 14 Oct 2009 14:44:10 +0200 From: Matthias Apitz To: Pieter de Goeje Message-ID: <20091014124410.GA4606@current.Sisis.de> References: <20091011062419.GA2168@current.Sisis.de> <20091013153815.GA88394@bsdcrew.de> <20091014063221.GA2301@current.Sisis.de> <200910141433.10715.pieter@degoeje.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <200910141433.10715.pieter@degoeje.nl> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) Cc: kde-freebsd@kde.org, freebsd-current@freebsd.org, Martin Wilke Subject: Re: [kde-freebsd] 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 12:44:12 -0000 El día Wednesday, October 14, 2009 a las 02:33:10PM +0200, Pieter de Goeje escribió: > On Wednesday 14 October 2009 08:32:21 Matthias Apitz wrote: > > I think only supporting KDE4 is not a good idea. IMHO, KDE4 is a bit > > heading in the wrong direction. KDE4 is unusable for a lot of (older) > > hardware and is unusable, at least, for smaller laptops or netbooks, > > just because of the resources it is consuming. If the KDE team is > > leaving KDE3, and I don't expect further development, but only > > compability with upcoming FreeBSD ABI changes (or whatever), than we > > will not have KDE3 anymore from 9-CURRENT (or even from 8.0-RELEASE) > > anymore. Which would be a real pity :-( > > I'm suprised someone actually uses artsd. As a fellow KDE3 user on 9-CURRENT > (on beefy hardware btw), I didn't have this issue because I always disable (btw: I'm using KDE3 on 8-CURRENT on my beefy laptop too); > artsd because I don't want sound notifications. As long as people are using > KDE3 I don't think it will die because people just like you will find the > problem(s) and fix it. > > That said, I couldn't reproduce the problem (artsd works fine if I enable it). > Uname: FreeBSD 9.0-CURRENT #2: Fri Oct 9 08:37:37 CEST 2009 i386 what is the SVN rev number of your kernel (mine is r197801) and how aRts came to your system, via /usr/ports or how? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 13:06:47 2009 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 267BC106566C; Wed, 14 Oct 2009 13:06:47 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from mx.utwente.nl (mx1.utsp.utwente.nl [130.89.2.12]) by mx1.freebsd.org (Postfix) with ESMTP id 971678FC12; Wed, 14 Oct 2009 13:06:46 +0000 (UTC) Received: from nox.student.utwente.nl (nox.student.utwente.nl [130.89.165.91]) by mx.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id n9ED4KeR016873; Wed, 14 Oct 2009 15:04:20 +0200 From: Pieter de Goeje To: Matthias Apitz Date: Wed, 14 Oct 2009 15:04:19 +0200 User-Agent: KMail/1.9.10 References: <20091011062419.GA2168@current.Sisis.de> <200910141433.10715.pieter@degoeje.nl> <20091014124410.GA4606@current.Sisis.de> In-Reply-To: <20091014124410.GA4606@current.Sisis.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200910141504.19965.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact icts.servicedesk@utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: kde-freebsd@kde.org, freebsd-current@freebsd.org, Martin Wilke Subject: Re: [kde-freebsd] 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV 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, 14 Oct 2009 13:06:47 -0000 On Wednesday 14 October 2009 14:44:10 Matthias Apitz wrote: > El d=EDa Wednesday, October 14, 2009 a las 02:33:10PM +0200, Pieter de Go= eje=20 escribi=F3: > > On Wednesday 14 October 2009 08:32:21 Matthias Apitz wrote: > > > I think only supporting KDE4 is not a good idea. IMHO, KDE4 is a bit > > > heading in the wrong direction. KDE4 is unusable for a lot of (older) > > > hardware and is unusable, at least, for smaller laptops or netbooks, > > > just because of the resources it is consuming. If the KDE team is > > > leaving KDE3, and I don't expect further development, but only > > > compability with upcoming FreeBSD ABI changes (or whatever), than we > > > will not have KDE3 anymore from 9-CURRENT (or even from 8.0-RELEASE) > > > anymore. Which would be a real pity :-( > > > > I'm suprised someone actually uses artsd. As a fellow KDE3 user on > > 9-CURRENT (on beefy hardware btw), I didn't have this issue because I > > always disable > > (btw: I'm using KDE3 on 8-CURRENT on my beefy laptop too); > > > artsd because I don't want sound notifications. As long as people are > > using KDE3 I don't think it will die because people just like you will > > find the problem(s) and fix it. > > > > That said, I couldn't reproduce the problem (artsd works fine if I enab= le > > it). Uname: FreeBSD 9.0-CURRENT #2: Fri Oct 9 08:37:37 CEST 2009 i386 > > what is the SVN rev number of your kernel (mine is r197801) and how aRts > came to your system, via /usr/ports or how? I can't give you an exact revision (sources were obtained with csup) but=20 r197869 should be pretty close. Arts was build using ports/audio/arts=20 (version 1.5.10_2,1). Another PC running RELENG_8 (amd64) from Sep. 24 also has a working arts (s= ame=20 version, also compiled/installed via ports). =2D Pieter From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 13:10:29 2009 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 28154106566B for ; Wed, 14 Oct 2009 13:10:29 +0000 (UTC) (envelope-from gary.jennejohn@freenet.de) Received: from mout7.freenet.de (mout7.freenet.de [IPv6:2001:748:100:40::2:9]) by mx1.freebsd.org (Postfix) with ESMTP id B88928FC1C for ; Wed, 14 Oct 2009 13:10:28 +0000 (UTC) Received: from [195.4.92.27] (helo=17.mx.freenet.de) by mout7.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #92) id 1My3cZ-0004ij-Ky; Wed, 14 Oct 2009 15:10:27 +0200 Received: from tfcfa.t.pppool.de ([89.55.252.250]:13480 helo=ernst.jennejohn.org) by 17.mx.freenet.de with esmtpa (ID gary.jennejohn@freenet.de) (port 25) (Exim 4.69 #94) id 1My3cZ-0005DK-AO; Wed, 14 Oct 2009 15:10:27 +0200 Date: Wed, 14 Oct 2009 15:10:26 +0200 From: Gary Jennejohn To: Alexander Best Message-ID: <20091014151026.699a5765@ernst.jennejohn.org> In-Reply-To: References: X-Mailer: Claws Mail 3.7.2 (GTK+ 2.16.2; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: buffers not syncing correctly during shutdown X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gary.jennejohn@freenet.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 13:10:29 -0000 On Wed, 14 Oct 2009 12:49:54 +0200 (CEST) Alexander Best wrote: > hi there, > > to keep it short: > > 1. mount a removable device (e.g. an usb stick) (better use -r to prevent data > loss) > 2. unplug the device (without unmounting it) > 3. `shutdown -r now` > > what happens is that the usual shutdown routine gets processed until all > buffers are synced, but then the system stalls. > > after resetting the system all devices (which were supposed to be synced) are > marked dirty and are being fsck'ed. > > cheers. > alex > > oh...and i'm running FreeBSD otaku 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r197914: > Sat Oct 10 02:58:19 CEST 2009 root@otaku:/usr/obj/usr/src/sys/ARUNDEL > i386 > I'm inclined to say that umount'ing the file systems is failing because you pulled the USB stick out without doing umount. Of course, that results in all file systems still being marked dirty. Obviously, this pathological case isn't being handled. I personally don't see why it ever should be handled. This is UNIX not Windows and users should be smart enough to know that they umount such devices before removing them otherwise nasty things can happen. --- Gary Jennejohn From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 13:13:37 2009 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 BEAAB1065670 for ; Wed, 14 Oct 2009 13:13:37 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 79CF88FC17 for ; Wed, 14 Oct 2009 13:13:37 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1My3fM-0004sf-OV for freebsd-current@freebsd.org; Wed, 14 Oct 2009 15:13:20 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Oct 2009 15:13:20 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 14 Oct 2009 15:13:20 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Wed, 14 Oct 2009 15:13:00 +0200 Lines: 7 Message-ID: References: <20091014151026.699a5765@ernst.jennejohn.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.23 (X11/20090928) In-Reply-To: <20091014151026.699a5765@ernst.jennejohn.org> Sender: news Subject: Re: buffers not syncing correctly during shutdown 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, 14 Oct 2009 13:13:37 -0000 Gary Jennejohn wrote: > I personally don't see why it ever should be handled. This is UNIX not > Windows and users should be smart enough to know that they umount such > devices before removing them otherwise nasty things can happen. Yes, but this is 2009 not 1978. From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 13:30:45 2009 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 ACFBD106568D for ; Wed, 14 Oct 2009 13:30:45 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay3.uni-muenster.de (ZIVM-EXRELAY3.UNI-MUENSTER.DE [128.176.192.20]) by mx1.freebsd.org (Postfix) with ESMTP id 41A678FC13 for ; Wed, 14 Oct 2009 13:30:44 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,557,1249250400"; d="scan'208";a="15848491" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER01.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay3.uni-muenster.de with ESMTP; 14 Oct 2009 15:30:43 +0200 Received: by ZIVMAILUSER01.UNI-MUENSTER.DE (Postfix, from userid 149459) id 928411B0766; Wed, 14 Oct 2009 15:30:43 +0200 (CEST) Date: Wed, 14 Oct 2009 15:30:43 +0200 (CEST) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Message-ID: In-Reply-To: <20091014151026.699a5765@ernst.jennejohn.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: buffers not syncing correctly during shutdown 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, 14 Oct 2009 13:30:45 -0000 Gary Jennejohn schrieb am 2009-10-14: > On Wed, 14 Oct 2009 12:49:54 +0200 (CEST) > Alexander Best wrote: > > hi there, > > to keep it short: > > 1. mount a removable device (e.g. an usb stick) (better use -r to > > prevent data > > loss) > > 2. unplug the device (without unmounting it) > > 3. `shutdown -r now` > > what happens is that the usual shutdown routine gets processed > > until all > > buffers are synced, but then the system stalls. > > after resetting the system all devices (which were supposed to be > > synced) are > > marked dirty and are being fsck'ed. > > cheers. > > alex > > oh...and i'm running FreeBSD otaku 9.0-CURRENT FreeBSD 9.0-CURRENT > > #0 r197914: > > Sat Oct 10 02:58:19 CEST 2009 > > root@otaku:/usr/obj/usr/src/sys/ARUNDEL > > i386 > I'm inclined to say that umount'ing the file systems is failing > because > you pulled the USB stick out without doing umount. Of course, that > results in all file systems still being marked dirty. Obviously, > this > pathological case isn't being handled. > I personally don't see why it ever should be handled. This is UNIX > not > Windows and users should be smart enough to know that they umount > such > devices before removing them otherwise nasty things can happen. > --- > Gary Jennejohn this is 2009 and not the 70s/80s. the amount or non-removable devices is declining day by day. eventually all storage devices will become removable and freebsd should keep up with this development. i don't think labelling this obvious bug as a grand unix feature is valid. also there are other scenarios where this problem can occur. if the device produces i/o errors you won't be able to unmount it even with the -f switch. alex From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 13:35:29 2009 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 6351510656A6 for ; Wed, 14 Oct 2009 13:35:29 +0000 (UTC) (envelope-from a_best01@uni-muenster.de) Received: from zivm-exrelay1.uni-muenster.de (ZIVM-EXRELAY1.UNI-MUENSTER.DE [128.176.192.14]) by mx1.freebsd.org (Postfix) with ESMTP id EC4B08FC31 for ; Wed, 14 Oct 2009 13:35:28 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.44,557,1249250400"; d="scan'208";a="285465774" Received: from zivmaildisp1.uni-muenster.de (HELO ZIVMAILUSER01.UNI-MUENSTER.DE) ([128.176.188.85]) by zivm-relay1.uni-muenster.de with ESMTP; 14 Oct 2009 15:35:27 +0200 Received: by ZIVMAILUSER01.UNI-MUENSTER.DE (Postfix, from userid 149459) id 4C2141B0766; Wed, 14 Oct 2009 15:35:27 +0200 (CEST) Date: Wed, 14 Oct 2009 15:35:26 +0200 (CEST) From: Alexander Best Sender: Organization: Westfaelische Wilhelms-Universitaet Muenster To: Andriy Gapon Message-ID: In-Reply-To: <4AD5BD00.4050700@icyb.net.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-current@FreeBSD.org Subject: Re: panic when mounting device >= 2 times 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, 14 Oct 2009 13:35:29 -0000 Andriy Gapon schrieb am 2009-10-14: > on 14/10/2009 14:21 Alexander Best said the following: > > could somebody have a look at this PR please: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/108968 > > this still exists in -CURRENT. > This is because of serious and long-standing brokenness (probably > from time of > introduction of GEOM) in g_vfs_open/g_vfs_close. > The essence: > 1. we allow multiple concurrent read-only mounts of a device > 2. but even a read-only mount mangles bufobj of device vnode > 3. Bug! > Trivial fix with POLA violation - prohibit concurrent RO mounts. > Non-trivial fix - _somehow_ avoid changing or depending on device > vnode bufobj. > See this for even more evil example of this problem: > http://lists.freebsd.org/pipermail/freebsd-fs/2009-February/005676.html thanks a lot for the hint. unfortunately i'm not a programmer and thus won't be able to help with this problem. :-( cheers. alex From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 13:43:29 2009 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 A1C0F1065694 for ; Wed, 14 Oct 2009 13:43:29 +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 E47038FC36 for ; Wed, 14 Oct 2009 13:43:28 +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 QAA03575; Wed, 14 Oct 2009 16:43:23 +0300 (EEST) (envelope-from avg@icyb.net.ua) Message-ID: <4AD5D57A.9090900@icyb.net.ua> Date: Wed, 14 Oct 2009 16:43:22 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090825) MIME-Version: 1.0 To: gary.jennejohn@freenet.de References: <20091014151026.699a5765@ernst.jennejohn.org> In-Reply-To: <20091014151026.699a5765@ernst.jennejohn.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Alexander Best , freebsd-current@FreeBSD.org Subject: Re: buffers not syncing correctly during shutdown 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, 14 Oct 2009 13:43:29 -0000 on 14/10/2009 16:10 Gary Jennejohn said the following: > > I'm inclined to say that umount'ing the file systems is failing because > you pulled the USB stick out without doing umount. Of course, that > results in all file systems still being marked dirty. Obviously, this > pathological case isn't being handled. > > I personally don't see why it ever should be handled. This is UNIX not > Windows and users should be smart enough to know that they umount such > devices before removing them otherwise nasty things can happen. There was a specific project funded by FreeBSD Foundation to handle issues like this. UNIX does not have to have deficiencies in comparison with Windows, and mistakes / emergency situations do happen. Developer who worked on the mentioned above project has expressed interest in resolving this issue. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 13:54:04 2009 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 2CE491065670 for ; Wed, 14 Oct 2009 13:54:04 +0000 (UTC) (envelope-from mlobo@digiart.art.br) Received: from sv4.hmnoc.net (sv4.hmnoc.net [63.247.76.174]) by mx1.freebsd.org (Postfix) with ESMTP id E86CC8FC08 for ; Wed, 14 Oct 2009 13:54:03 +0000 (UTC) Received: from localhost ([127.0.0.1]:50279 helo=squirrel.sv4.hmnoc.net) by sv4.hmnoc.net with esmtp (Exim 4.69) (envelope-from ) id 1My4Ig-0001jY-DY for freebsd-current@freebsd.org; Wed, 14 Oct 2009 10:53:58 -0300 Received: from 200.249.56.17 (proxying for unknown) (SquirrelMail authenticated user mlobo@digiart.art.br) by squirrel.sv4.hmnoc.net with HTTP; Wed, 14 Oct 2009 10:53:58 -0300 (BRT) Message-ID: <18175.200.249.56.17.1255528438.squirrel@squirrel.sv4.hmnoc.net> In-Reply-To: <20091014151026.699a5765@ernst.jennejohn.org> References: <20091014151026.699a5765@ernst.jennejohn.org> Date: Wed, 14 Oct 2009 10:53:58 -0300 (BRT) From: "Mario Lobo" To: freebsd-current@freebsd.org User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sv4.hmnoc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - digiart.art.br Subject: Re: buffers not syncing correctly during shutdown 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, 14 Oct 2009 13:54:04 -0000 > On Wed, 14 Oct 2009 12:49:54 +0200 (CEST) > Alexander Best wrote: > >> hi there, >> >> to keep it short: >> >> 1. mount a removable device (e.g. an usb stick) (better use -r to >> prevent data >> loss) >> 2. unplug the device (without unmounting it) >> 3. `shutdown -r now` >> >> what happens is that the usual shutdown routine gets processed until all >> buffers are synced, but then the system stalls. >> >> after resetting the system all devices (which were supposed to be >> synced) are >> marked dirty and are being fsck'ed. >> >> cheers. >> alex >> >> oh...and i'm running FreeBSD otaku 9.0-CURRENT FreeBSD 9.0-CURRENT #0 >> r197914: >> Sat Oct 10 02:58:19 CEST 2009 >> root@otaku:/usr/obj/usr/src/sys/ARUNDEL >> i386 >> > > I'm inclined to say that umount'ing the file systems is failing because > you pulled the USB stick out without doing umount. Of course, that > results in all file systems still being marked dirty. Obviously, this > pathological case isn't being handled. > > I personally don't see why it ever should be handled. This is UNIX not > Windows and users should be smart enough to know that they umount such > devices before removing them otherwise nasty things can happen. > > --- > Gary Jennejohn > _______________________________________________ > 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 must add that even windows has a "Safely Remove Hardware" before unplugging the usb device. Mario From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 16:37:36 2009 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 D71121065672 for ; Wed, 14 Oct 2009 16:37:36 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id 974C28FC16 for ; Wed, 14 Oct 2009 16:37:36 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id 538B56D41B; Wed, 14 Oct 2009 16:37:35 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 19D7A84513; Wed, 14 Oct 2009 18:37:35 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Mario Lobo" References: <20091014151026.699a5765@ernst.jennejohn.org> <18175.200.249.56.17.1255528438.squirrel@squirrel.sv4.hmnoc.net> Date: Wed, 14 Oct 2009 18:37:34 +0200 In-Reply-To: <18175.200.249.56.17.1255528438.squirrel@squirrel.sv4.hmnoc.net> (Mario Lobo's message of "Wed, 14 Oct 2009 10:53:58 -0300 (BRT)") Message-ID: <86vdiix775.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: buffers not syncing correctly during shutdown 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, 14 Oct 2009 16:37:36 -0000 "Mario Lobo" writes: > I must add that even windows has a "Safely Remove Hardware" before > unplugging the usb device. What it really means is "sync the filesystem and tell me if there are any open or locked files". In most cases, you can yank the USB stick out without adverse consequences. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 17:04:08 2009 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 72566106566C for ; Wed, 14 Oct 2009 17:04:08 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 1C8998FC27 for ; Wed, 14 Oct 2009 17:04:07 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id n9EH47rg073522 for ; Wed, 14 Oct 2009 11:04:07 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id n9EH47mp073519 for ; Wed, 14 Oct 2009 11:04:07 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 14 Oct 2009 11:04:07 -0600 (MDT) From: Warren Block To: current@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (wonkity.com [127.0.0.1]); Wed, 14 Oct 2009 11:04:07 -0600 (MDT) Cc: Subject: Why does hal think my USB devices are fixed? 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, 14 Oct 2009 17:04:08 -0000 Fixed as opposed to removable. hal used to see these USB devices--USB memory sticks, memory cards in a reader--as removable devices. Which they are. Same computer, same config that used to automount these devices as removable, but now FreeBSD 8.0-RC1 and hal says they are fixed devices: org.freedesktop.hal.storage.mount-fixed no <-- (action, result). Is this be due to the USB system? -Warren Block * Rapid City, South Dakota USA From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 17:16:15 2009 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 EB9981065672 for ; Wed, 14 Oct 2009 17:16:15 +0000 (UTC) (envelope-from mlobo@digiart.art.br) Received: from sv4.hmnoc.net (sv4.hmnoc.net [63.247.76.174]) by mx1.freebsd.org (Postfix) with ESMTP id C28938FC21 for ; Wed, 14 Oct 2009 17:16:15 +0000 (UTC) Received: from localhost ([127.0.0.1]:37110 helo=squirrel.sv4.hmnoc.net) by sv4.hmnoc.net with esmtp (Exim 4.69) (envelope-from ) id 1My7SQ-0002di-NI; Wed, 14 Oct 2009 14:16:14 -0300 Received: from 200.249.56.17 (proxying for unknown) (SquirrelMail authenticated user mlobo@digiart.art.br) by squirrel.sv4.hmnoc.net with HTTP; Wed, 14 Oct 2009 14:16:14 -0300 (BRT) Message-ID: <26594.200.249.56.17.1255540574.squirrel@squirrel.sv4.hmnoc.net> In-Reply-To: <86vdiix775.fsf@ds4.des.no> References: <20091014151026.699a5765@ernst.jennejohn.org> <18175.200.249.56.17.1255528438.squirrel@squirrel.sv4.hmnoc.net> <86vdiix775.fsf@ds4.des.no> Date: Wed, 14 Oct 2009 14:16:14 -0300 (BRT) From: "Mario Lobo" To: Dag-Erling =?iso-8859-1?Q?Sm=C3=B8rgrav?= User-Agent: SquirrelMail/1.4.8 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sv4.hmnoc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - digiart.art.br Cc: freebsd-current@freebsd.org Subject: Re: buffers not syncing correctly during shutdown 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, 14 Oct 2009 17:16:16 -0000 > "Mario Lobo" writes: >> I must add that even windows has a "Safely Remove Hardware" before >> unplugging the usb device. > > What it really means is "sync the filesystem and tell me if there are > any open or locked files". In most cases, you can yank the USB stick > out without adverse consequences. > > DES > -- > Dag-Erling Smørgrav - des@des.no > That IS true ! but like you said, "most cases" <> "all cases". Once, on a company I was doing work at, I clicked on "Safely Remove Hardware" and it said "can´t do it. device busy", although there was (apparently) nothing using any files from the stick. I yanked it out anyway. result: the 3 files I edited from the stick were gone :(. Since I don´t know when I am gonna hit a case that doesn´t belong to "most", I always try to remember to unmount (i.e. Safely Remove Hardware) the stick before unplugging it. Mario From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 17:44:15 2009 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 DA162106566B for ; Wed, 14 Oct 2009 17:44:15 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe15.tele2.se [212.247.155.193]) by mx1.freebsd.org (Postfix) with ESMTP id 6A0408FC1C for ; Wed, 14 Oct 2009 17:44:15 +0000 (UTC) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=iN285EWJes0A:10 a=MnI1ikcADjEx7bvsp0jZvQ==:17 a=zIoiMrX23M3wnObPpqAA:9 a=4LmpdXKJXd4fB1a86v7RZc1tQJYA:4 Received: from [188.126.201.140] (account mc467741@c2i.net HELO laptop.adsl.tele2.no) by mailfe15.swip.net (CommuniGate Pro SMTP 5.2.16) with ESMTPA id 576787078; Wed, 14 Oct 2009 19:44:13 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Wed, 14 Oct 2009 19:45:08 +0200 User-Agent: KMail/1.11.4 (FreeBSD/9.0-CURRENT; KDE/4.2.4; i386; ; ) References: In-Reply-To: X-Face: (%:6u[ldzJ`0qjD7sCkfdMmD*RxpOwEEQ+KWt[{J#x6ow~JO:,zwp.(t; @Aq :4:&nFCgDb8[3oIeTb^'",;u{5{}C9>"PuY\)!=#\u9SSM-nz8+SR~B\!qBv MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910141945.09311.hselasky@c2i.net> Cc: Warren Block Subject: Re: Why does hal think my USB devices are fixed? 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, 14 Oct 2009 17:44:15 -0000 On Wednesday 14 October 2009 19:04:07 Warren Block wrote: > Fixed as opposed to removable. hal used to see these USB > devices--USB memory sticks, memory cards in a reader--as removable > devices. Which they are. > > Same computer, same config that used to automount these devices as > removable, but now FreeBSD 8.0-RC1 and hal says they are fixed devices: > > org.freedesktop.hal.storage.mount-fixed no <-- (action, result). > > Is this be due to the USB system? Hi Warren, The fixed/removable information is transferred to the PC using a SCSI INQUIRY command. What the device reports or what the CAM layer reports to HAL is not up to the USB stack. The most significant bit of second byte of the INQUIRY response decides if the medium is removable or not. See: ustorage_fs_inquiry() in src/sys/dev/usb/storage/ustorage_fs.c --HPS From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 17:46:47 2009 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 D92E81065698 for ; Wed, 14 Oct 2009 17:46:47 +0000 (UTC) (envelope-from marcus@marcuscom.com) Received: from creme-brulee.marcuscom.com (marcuscom-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::1279]) by mx1.freebsd.org (Postfix) with ESMTP id 725CD8FC2A for ; Wed, 14 Oct 2009 17:46:47 +0000 (UTC) Received: from [IPv6:2001:470:1f00:2464::4] (shumai.marcuscom.com [IPv6:2001:470:1f00:2464::4]) by creme-brulee.marcuscom.com (8.14.3/8.14.3) with ESMTP id n9EHlVkO004554; Wed, 14 Oct 2009 13:47:31 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Warren Block In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-MnxCRU8VYfv/TRaQFHTx" Organization: MarcusCom, Inc. Date: Wed, 14 Oct 2009 13:46:59 -0400 Message-Id: <1255542419.22880.131.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on creme-brulee.marcuscom.com Cc: current@freebsd.org Subject: Re: Why does hal think my USB devices are fixed? 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, 14 Oct 2009 17:46:47 -0000 --=-MnxCRU8VYfv/TRaQFHTx Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2009-10-14 at 11:04 -0600, Warren Block wrote: > Fixed as opposed to removable. hal used to see these USB=20 > devices--USB memory sticks, memory cards in a reader--as removable=20 > devices. Which they are. >=20 > Same computer, same config that used to automount these devices as=20 > removable, but now FreeBSD 8.0-RC1 and hal says they are fixed devices: >=20 > org.freedesktop.hal.storage.mount-fixed no <-- (action, result). >=20 > Is this be due to the USB system? I have stopped development of hal-0.5.11. I have put a lot of work into the upcoming 0.5.13 release to fix numerous issues with USB detection. I have been getting good results on -CURRENT with various USB sticks. You may want to give that a try. You can get the port from the ports module at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi . Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-MnxCRU8VYfv/TRaQFHTx Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEABECAAYFAkrWDpIACgkQb2iPiv4Uz4dByACcCPzd5AomAKwkZzbm8GqPeg+u +2QAnip+EHcpcWGG7XEYFs6sPao9kBxs =RF/S -----END PGP SIGNATURE----- --=-MnxCRU8VYfv/TRaQFHTx-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 17:53:00 2009 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 B65D7106568B for ; Wed, 14 Oct 2009 17:53:00 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from mail-yw0-f197.google.com (mail-yw0-f197.google.com [209.85.211.197]) by mx1.freebsd.org (Postfix) with ESMTP id 70FDE8FC14 for ; Wed, 14 Oct 2009 17:53:00 +0000 (UTC) Received: by ywh35 with SMTP id 35so77548ywh.7 for ; Wed, 14 Oct 2009 10:52:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=yLXuQY0A+57Rxy8aU6hSX37sStypRGlle3YBNcb8ruw=; b=NM+2btbFv3lXEAdEsMjFCyfCf+V9qvTlutx9YkCe4tW/Rcc0SRy9m/KKUk+4Wqv7ur onsoXrjtxt0411YipFsYzquXLfVUODsaxWPFBFgDwRcdHCw7uuIBHYRyqRPAJhxD+lA/ dQxGHBOl99sFXYbspQF6C+3SPNKEQ4OjZMsCk= 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=TyPHT7+pDXtm0czUYXl6Bs2FrdSG4mgkaW8lyOkqFoVspqRk9HDOWtwuOjNPhxWXLj 6S/RAIUajbz06v/hyP1r0JOT6LpAtJgMq19cnUyOXsW0N2rnF4gB6PYrvT6fvZV3PxOG mqQP28D+SiAiPVKt6ZtAWb34yn16z4q4VBVp8= MIME-Version: 1.0 Received: by 10.150.63.13 with SMTP id l13mr15380660yba.5.1255541342842; Wed, 14 Oct 2009 10:29:02 -0700 (PDT) In-Reply-To: References: Date: Wed, 14 Oct 2009 12:29:02 -0500 Message-ID: <6201873e0910141029r75cad42fk55c92cf25bbef340@mail.gmail.com> From: Adam Vande More To: Warren Block Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org Subject: Re: Why does hal think my USB devices are fixed? 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, 14 Oct 2009 17:53:00 -0000 On Wed, Oct 14, 2009 at 12:04 PM, Warren Block wrote: > Fixed as opposed to removable. hal used to see these USB devices--USB > memory sticks, memory cards in a reader--as removable devices. Which they > are. > > Same computer, same config that used to automount these devices as > removable, but now FreeBSD 8.0-RC1 and hal says they are fixed devices: > > org.freedesktop.hal.storage.mount-fixed no <-- (action, result). > > Is this be due to the USB system? > > -Warren Block * Rapid City, South Dakota USA > _______________________________________________ > 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" > It's a config option in /usr/ports/sysutils/hal -- Adam Vande More From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 17:53:41 2009 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 42573106568D for ; Wed, 14 Oct 2009 17:53:41 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-yx0-f184.google.com (mail-yx0-f184.google.com [209.85.210.184]) by mx1.freebsd.org (Postfix) with ESMTP id E720B8FC24 for ; Wed, 14 Oct 2009 17:53:40 +0000 (UTC) Received: by mail-yx0-f184.google.com with SMTP id 14so79413yxe.7 for ; Wed, 14 Oct 2009 10:53:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=yqa52FX8afweNbT8f0XX+79yeLPmGqRgwfTmxK2c+dQ=; b=xaViuO+YtT5ra/0yhXhgWvwvZ1hQ1VRURZejr4wV386mCbyoN2crVb7E0OfLk3Uo53 55PpbEeUgOPc5iN9hPy7UMtUZVseR6olQNSfZPiIsGbg3ezCutqEukVerbBtas9MQKi4 VjIvvJDZnHtCqwmNhzgX2ndBR6bXVbvx7yBz0= 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=vFVEVgQmSqC21v3SsCtUZbsf4d2lue/y1S14wdJkslujpbmiyr8WdxDHO+hl2NU6wl vwwfne8brYO4a5G8qvQuq1wsIKTW48UyANMhFFmjDFoGiyC3y2furMsOMPDXSlSo15gf 9KET1NUZK54HRaRZBliy6aKMaWPSMBsovCORU= MIME-Version: 1.0 Received: by 10.150.166.7 with SMTP id o7mr15366494ybe.224.1255542820423; Wed, 14 Oct 2009 10:53:40 -0700 (PDT) In-Reply-To: <26594.200.249.56.17.1255540574.squirrel@squirrel.sv4.hmnoc.net> References: <20091014151026.699a5765@ernst.jennejohn.org> <18175.200.249.56.17.1255528438.squirrel@squirrel.sv4.hmnoc.net> <86vdiix775.fsf@ds4.des.no> <26594.200.249.56.17.1255540574.squirrel@squirrel.sv4.hmnoc.net> Date: Wed, 14 Oct 2009 10:53:40 -0700 Message-ID: From: Freddie Cash To: freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: buffers not syncing correctly during shutdown 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, 14 Oct 2009 17:53:41 -0000 2009/10/14 Mario Lobo > > "Mario Lobo" writes: > >> I must add that even windows has a "Safely Remove Hardware" before > >> unplugging the usb device. > > > > What it really means is "sync the filesystem and tell me if there are > > any open or locked files". In most cases, you can yank the USB stick > > out without adverse consequences. > > > > DES > > -- > > Dag-Erling Sm=E7=B9=AArgrav - des@des.no > > > That IS true ! but like you said, "most cases" <> "all cases". Once, on a > company I was doing work at, I clicked on "Safely Remove Hardware" and it > said "can=E6=84=92 do it. device busy", although there was (apparently) n= othing > using any files from the stick. I yanked it out anyway. result: the 3 > files I edited from the stick were gone :(. Since I don=E6=84=92 know whe= n I am > gonna hit a case that doesn=E6=84=92 belong to "most", I always try to re= member > to unmount (i.e. Safely Remove Hardware) the stick before unplugging it. > > How Windows deals with USB removable storage depends on how you configure the storage policy for the individual device, and globally for all removabl= e storage devices. The default in Windows XP is "Optimise for performance", which requires the use of the "Safely remove hardware" feature. This enables write caching on the device, which can lead to data loss if you remove the device before dat= a is actually flushed/written. You can change it to "Optimise for quick removal", which disables write caching, so you can remove the device at pretty much any time. It's all done via the Policies tab in the Device Properties, accessible via the Device Manager or by right-clicking->Properties on the device in Window= s Explorer. I believe the default was switched at some point, though, so that the Safel= y Remove isn't always needed. --=20 Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 17:56:04 2009 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 1A2011065692 for ; Wed, 14 Oct 2009 17:56:04 +0000 (UTC) (envelope-from shuvaev@physik.uni-wuerzburg.de) Received: from mailrelay.rz.uni-wuerzburg.de (mailrelay.rz.uni-wuerzburg.de [132.187.3.28]) by mx1.freebsd.org (Postfix) with ESMTP id C14098FC15 for ; Wed, 14 Oct 2009 17:56:02 +0000 (UTC) Received: from virusscan.mail (localhost [127.0.0.1]) by mailrelay.mail (Postfix) with ESMTP id E7D595BA8C for ; Wed, 14 Oct 2009 19:56:00 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by virusscan.mail (Postfix) with ESMTP id E3F265B97B for ; Wed, 14 Oct 2009 19:56:00 +0200 (CEST) X-Virus-Scanned: by amavisd-new at uni-wuerzburg.de Received: from mail.physik.uni-wuerzburg.de (wthp192.physik.uni-wuerzburg.de [132.187.40.192]) by mailmaster.uni-wuerzburg.de (Postfix) with ESMTP id C1E805CD7B for ; Wed, 14 Oct 2009 19:56:00 +0200 (CEST) Received: from wep4035 ([132.187.37.35]) by mail.physik.uni-wuerzburg.de (Lotus Domino Release 8.0.2FP1HF244) with ESMTP id 2009101419555976-162763 ; Wed, 14 Oct 2009 19:55:59 +0200 Received: by wep4035 (sSMTP sendmail emulation); Wed, 14 Oct 2009 19:56:00 +0200 Date: Wed, 14 Oct 2009 19:56:00 +0200 From: Alexey Shuvaev To: freebsd-current@FreeBSD.org Message-ID: <20091014175600.GA55864@wep4035.physik.uni-wuerzburg.de> Mail-Followup-To: freebsd-current@FreeBSD.org References: <20091014151026.699a5765@ernst.jennejohn.org> Mime-Version: 1.0 In-Reply-To: User-Agent: Mutt/1.4.2.3i Organization: Universitaet Wuerzburg X-MIMETrack: Itemize by SMTP Server on domino1/uni-wuerzburg(Release 8.0.2FP1HF244 | April 7, 2009) at 10/14/2009 07:55:59 PM, Serialize by Router on domino1/uni-wuerzburg(Release 8.0.2FP1HF244 | April 7, 2009) at 10/14/2009 07:56:00 PM, Serialize complete at 10/14/2009 07:56:00 PM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Cc: Subject: Re: buffers not syncing correctly during shutdown 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, 14 Oct 2009 17:56:04 -0000 On Wed, Oct 14, 2009 at 03:13:00PM +0200, Ivan Voras wrote: > Gary Jennejohn wrote: > > >I personally don't see why it ever should be handled. This is UNIX not > >Windows and users should be smart enough to know that they umount such > >devices before removing them otherwise nasty things can happen. > > Yes, but this is 2009 not 1978. > Well, the other side of being in 2009 is that filesystems have evolved too. For example, I have UFS2 + SU on most of my removable media (sticks and external hard drives). I was always interested how this new "feature" of FreeBSD, to allow removable media disappear almost silently, plays in this case? I've had one case when I lost my external hard drive during tar -xvf ports.tar.bz2 into it. I haven't touched it at the moment (voltage spikes?). It was quite funny trying to browse through the half-cached content then... have spent ~5 minutes before noticing kernel message. Re-plugging the drive has brought it back, with dirty filesystem, of course. Maybe it would be better if the system paniced then :/) Anyway, my point is that removing the media with most of modern filesystems on it without unmounting is an operator error. IMHO, the system should warn such an operators in one or the other way... 0.00$, Alexey. From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 18:02:10 2009 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 EAE2B1065670 for ; Wed, 14 Oct 2009 18:02:10 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id A82558FC16 for ; Wed, 14 Oct 2009 18:02:10 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id n9EI2AJ8073799; Wed, 14 Oct 2009 12:02:10 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id n9EI2ATi073796; Wed, 14 Oct 2009 12:02:10 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 14 Oct 2009 12:02:10 -0600 (MDT) From: Warren Block To: Adam Vande More In-Reply-To: <6201873e0910141029r75cad42fk55c92cf25bbef340@mail.gmail.com> Message-ID: References: <6201873e0910141029r75cad42fk55c92cf25bbef340@mail.gmail.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-902635197-242327288-1255543330=:73752" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (wonkity.com [127.0.0.1]); Wed, 14 Oct 2009 12:02:10 -0600 (MDT) Cc: current@freebsd.org Subject: Re: Why does hal think my USB devices are fixed? 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, 14 Oct 2009 18:02:11 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---902635197-242327288-1255543330=:73752 Content-Type: TEXT/PLAIN; format=flowed; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT On Wed, 14 Oct 2009, Adam Vande More wrote: > On Wed, Oct 14, 2009 at 12:04 PM, Warren Block wrote: > Fixed as opposed to removable.  hal used to see these USB > devices--USB memory sticks, memory cards in a reader--as > removable devices.  Which they are. > > Same computer, same config that used to automount these devices > as removable, but now FreeBSD 8.0-RC1 and hal says they are > fixed devices: > > org.freedesktop.hal.storage.mount-fixed no <-- (action, result). > > Is this be due to the USB system? > > It's a config option in /usr/ports/sysutils/hal "fixed mountpoints" is off, but I think that's "fixed" as in "use the same mountpoint every time", not fixed as in non-removable. -Warren Block * Rapid City, South Dakota USA ---902635197-242327288-1255543330=:73752-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 18:46:46 2009 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 7C26E1065670 for ; Wed, 14 Oct 2009 18:46:46 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 3C52F8FC13 for ; Wed, 14 Oct 2009 18:46:45 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id n9EIkja7073944; Wed, 14 Oct 2009 12:46:45 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id n9EIkjc0073941; Wed, 14 Oct 2009 12:46:45 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 14 Oct 2009 12:46:45 -0600 (MDT) From: Warren Block To: Joe Marcus Clarke In-Reply-To: <1255542419.22880.131.camel@shumai.marcuscom.com> Message-ID: References: <1255542419.22880.131.camel@shumai.marcuscom.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (wonkity.com [127.0.0.1]); Wed, 14 Oct 2009 12:46:45 -0600 (MDT) Cc: current@freebsd.org Subject: Re: Why does hal think my USB devices are fixed? 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, 14 Oct 2009 18:46:46 -0000 On Wed, 14 Oct 2009, Joe Marcus Clarke wrote: > On Wed, 2009-10-14 at 11:04 -0600, Warren Block wrote: >> Fixed as opposed to removable. hal used to see these USB >> devices--USB memory sticks, memory cards in a reader--as removable >> devices. Which they are. >> >> Same computer, same config that used to automount these devices as >> removable, but now FreeBSD 8.0-RC1 and hal says they are fixed devices: >> >> org.freedesktop.hal.storage.mount-fixed no <-- (action, result). >> >> Is this due to the USB system? > > I have stopped development of hal-0.5.11. I have put a lot of work into > the upcoming 0.5.13 release to fix numerous issues with USB detection. > I have been getting good results on -CURRENT with various USB sticks. > You may want to give that a try. You can get the port from the ports > module at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi . That's a definite improvement. USB sticks work fine, or at least the three I have here work fine. The memory card reader still comes up as fixed. This is a Sandisk SDDRX3-3in1 with multiple slots. da0 and da1 always come up, along with the s1 slice of whichever memory card is loaded. -Warren Block * Rapid City, South Dakota USA From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 18:53:30 2009 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 6B6D0106566C for ; Wed, 14 Oct 2009 18:53:30 +0000 (UTC) (envelope-from marcus@marcuscom.com) Received: from creme-brulee.marcuscom.com (marcuscom-pt.tunnel.tserv1.fmt.ipv6.he.net [IPv6:2001:470:1f00:ffff::1279]) by mx1.freebsd.org (Postfix) with ESMTP id F28168FC1B for ; Wed, 14 Oct 2009 18:53:29 +0000 (UTC) Received: from [IPv6:2001:470:1f00:2464::4] (shumai.marcuscom.com [IPv6:2001:470:1f00:2464::4]) by creme-brulee.marcuscom.com (8.14.3/8.14.3) with ESMTP id n9EIsF6B005208; Wed, 14 Oct 2009 14:54:15 -0400 (EDT) (envelope-from marcus@marcuscom.com) From: Joe Marcus Clarke To: Warren Block In-Reply-To: References: <1255542419.22880.131.camel@shumai.marcuscom.com> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-JaqPWDXBCkTuqqiZTcte" Organization: MarcusCom, Inc. Date: Wed, 14 Oct 2009 14:53:42 -0400 Message-Id: <1255546422.22880.136.camel@shumai.marcuscom.com> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,NO_RELAYS autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on creme-brulee.marcuscom.com Cc: current@freebsd.org Subject: Re: Why does hal think my USB devices are fixed? 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, 14 Oct 2009 18:53:30 -0000 --=-JaqPWDXBCkTuqqiZTcte Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Wed, 2009-10-14 at 12:46 -0600, Warren Block wrote: > On Wed, 14 Oct 2009, Joe Marcus Clarke wrote: >=20 > > On Wed, 2009-10-14 at 11:04 -0600, Warren Block wrote: > >> Fixed as opposed to removable. hal used to see these USB > >> devices--USB memory sticks, memory cards in a reader--as removable > >> devices. Which they are. > >> > >> Same computer, same config that used to automount these devices as > >> removable, but now FreeBSD 8.0-RC1 and hal says they are fixed devices= : > >> > >> org.freedesktop.hal.storage.mount-fixed no <-- (action, result). > >> > >> Is this due to the USB system? > > > > I have stopped development of hal-0.5.11. I have put a lot of work int= o > > the upcoming 0.5.13 release to fix numerous issues with USB detection. > > I have been getting good results on -CURRENT with various USB sticks. > > You may want to give that a try. You can get the port from the ports > > module at http://www.marcuscom.com:8080/cgi-bin/cvsweb.cgi . >=20 > That's a definite improvement. USB sticks work fine, or at least the=20 > three I have here work fine. The memory card reader still comes up as=20 > fixed. This is a Sandisk SDDRX3-3in1 with multiple slots. da0 and da1=20 > always come up, along with the s1 slice of whichever memory card is=20 > loaded. I don't have any card readers, but as Hans pointed out, this part will come from the SCSI subsystem. If CAM says the device is not removable, then hal will go with that. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-JaqPWDXBCkTuqqiZTcte Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEABECAAYFAkrWHjUACgkQb2iPiv4Uz4dexgCfYH8fCtCKLmRcXL7g/iw62b9m XlUAnRTlVQo44v5oDQIMfvWSHQaPa00W =JHJL -----END PGP SIGNATURE----- --=-JaqPWDXBCkTuqqiZTcte-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 18:55:55 2009 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 9429D1065698 for ; Wed, 14 Oct 2009 18:55:55 +0000 (UTC) (envelope-from svein-listmail@stillbilde.net) Received: from mail.stillbilde.net (d80.iso100.no [81.175.61.195]) by mx1.freebsd.org (Postfix) with SMTP id C50E88FC26 for ; Wed, 14 Oct 2009 18:55:53 +0000 (UTC) Received: from [192.168.4.2] (unknown [192.168.4.2]) (Authenticated sender: svein) by mail.stillbilde.net (Familien Skogens mail) with ESMTPSA id 9D89C22; Wed, 14 Oct 2009 20:55:56 +0200 (CEST) Message-ID: <4AD61EB8.4020506@stillbilde.net> Date: Wed, 14 Oct 2009 20:55:52 +0200 From: "Svein Skogen (listmail account)" User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: Freddie Cash References: <20091014151026.699a5765@ernst.jennejohn.org> <18175.200.249.56.17.1255528438.squirrel@squirrel.sv4.hmnoc.net> <86vdiix775.fsf@ds4.des.no> <26594.200.249.56.17.1255540574.squirrel@squirrel.sv4.hmnoc.net> In-Reply-To: X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: buffers not syncing correctly during shutdown 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, 14 Oct 2009 18:55:55 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Freddie Cash wrote: > I believe the default was switched at some point, though, so that the S= afely > Remove isn't always needed. I believe this was changed around SP2 for XP, and Vista has always had quick-removal for the devices it undestands to be external (eSATA still gets detected as non-hotswappable unless you registry-magic-it). However, this doesn't protect against pebcak-yanking the device you have documents open from. It really doesn't. Just trust me, I've tried. ;) Maybe this is something FreeBSD should consider? Maybe a hack in "mount" to allow the mount-option "is-removable", that tells the OS "don't bother write-cache this" and "cleanse the cache when user yanks hardware"= ? //Svein - -- - --------+-------------------+------------------------------- /"\ |Svein Skogen | svein@d80.iso100.no \ / |Solberg =C3=98stli 9 | PGP Key: 0xE5E76831 X |2020 Skedsmokorset | svein@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | svein@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listmail@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +-------------------+------------------------------- |msn messenger: | Mobile Phone: +47 907 03 575 |svein@jernhuset.no | RIPE handle: SS16503-RIPE - --------+-------------------+------------------------------- If you really are in a hurry, mail me at svein-mobile@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. - ------------------------------------------------------------ Picture Gallery: https://gallery.stillbilde.net/v/svein/ - ------------------------------------------------------------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkrWHrgACgkQODUnwSLUlKTUUACgiUcE2LpKOq/xqvRpd+/IbC8+ wOYAn1F3oH8akMqBj2cXu1c6xetEXyQ9 =3DZF4S -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 19:56:02 2009 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 4069E106566C for ; Wed, 14 Oct 2009 19:56:02 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id BEA828FC18 for ; Wed, 14 Oct 2009 19:56:01 +0000 (UTC) Received: by ewy18 with SMTP id 18so142033ewy.43 for ; Wed, 14 Oct 2009 12:56:00 -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=ELmiDeMYTNNqZp2UPTtngdl44NfJ8F3fyF2RIjWQRN0=; b=cw9Nqh7cSwfhAC7D+dl07ywAVdrdbkCIYFtGSMOCA/qHZ3+rCU0xrAp9ON0rXFlrlJ BRgSlH+gceGvv0dHZa216YKVu7nLLBuy4QSzGgnql+jqLdnV9+hMMmSv0mOhu6ATmprP jcrdhbMgnkf4fN3KMGNDYSd+Jzuxuew5PznYw= 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=GOo7HZMO6K/LgjEBFcr+vjNTLTrXxLuLrDtUUYbqrotU7h0/JDROsiHGPujUxJ3bxb DogVh9g+e7KMp5ITm+IptuFOdrlLK6FV0CffQXOIjJMPDLdPSqAvMQHvhH9pSP2UT1L8 jzhnb5lITcpB+vbcy8lbLO5j8IquFGPfZdU6k= Received: by 10.216.87.3 with SMTP id x3mr3003181wee.132.1255550160753; Wed, 14 Oct 2009 12:56:00 -0700 (PDT) Received: from weongyo ([174.35.1.224]) by mx.google.com with ESMTPS id g11sm124479gve.5.2009.10.14.12.55.57 (version=SSLv3 cipher=RC4-MD5); Wed, 14 Oct 2009 12:55:59 -0700 (PDT) Received: by weongyo (sSMTP sendmail emulation); Wed, 14 Oct 2009 12:56:31 -0700 From: Weongyo Jeong Date: Wed, 14 Oct 2009 12:56:31 -0700 To: Hans Petter Selasky Message-ID: <20091014195631.GD67082@weongyo> Mail-Followup-To: Hans Petter Selasky , freebsd-current@freebsd.org, bsduser References: <86051.1254232666@critter.freebsd.dk> <20091013174201.GC67082@weongyo> <86iqei7tgq.fsf@jodie.vectavision.com> <200910140935.46509.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200910140935.46509.hselasky@c2i.net> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: bsduser , freebsd-current@freebsd.org Subject: Re: if_rum dies on transmit... 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: Wed, 14 Oct 2009 19:56:02 -0000 On Wed, Oct 14, 2009 at 09:35:46AM +0200, Hans Petter Selasky wrote: > On Wednesday 14 October 2009 01:41:09 bsduser wrote: > > Weongyo Jeong writes: > > > On Tue, Sep 29, 2009 at 01:57:46PM +0000, Poul-Henning Kamp wrote: > > >> Has anybody else seen if_rum die when you try to transmit a file over > > >> a TCP connection ? > > >> > > >> If I try to print across the network, upload a file with ftp or anything > > >> else of that general tenor, if_rum seems to hang the output queue and > > >> stops transmitting packets. > > >> > > >> Restarting wpa_supplicant mostly resolves the issue, but it does not > > >> on its own discover the problem. > > >> > > >> According to tcpdump(8), packets are still received. > > >> > > >> Any ideas ? > > > > > > Could you please test with attached patch? > > > > > > regards, > > > Weongyo Jeong > > > > I had the same issues with if_rum at least while using WPA and your patch > > made them go away.... ( although removing and plugging back in does not > > quite work ) > > > > # scp INDEX-8* cookie:/usr/ports > > INDEX-8 100% 19MB 2.1MB/s 00:09 > > INDEX-8.db 100% 34MB 2.4MB/s 00:14 > > > > before the patch this would just hang. > > > > Another quick test using rsync on a bunch of files worked flawless too. > > > > usbconfig list: > > > > ugen7.2: at usbus7, cfg=0 > > md=HOST spd=HIGH (480Mbps) pwr=ON > > > > The adapter is a WUSB54GC and yes, you made my day :-) > > Weongyo: > > Is the problem that some ifqueues go full and then the USB transfers are not > restarted properly? Probably the other wlan network adapters have the same > problem too and should be patched similarly. Yes and I think other USB wireless devices should be fixed also. I'll do it as soon as possible. regards, Weongyo Jeong From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 20:10:26 2009 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 B8E67106566C for ; Wed, 14 Oct 2009 20:10:26 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com [209.85.220.222]) by mx1.freebsd.org (Postfix) with ESMTP id 41F5C8FC20 for ; Wed, 14 Oct 2009 20:10:25 +0000 (UTC) Received: by fxm22 with SMTP id 22so178456fxm.36 for ; Wed, 14 Oct 2009 13:10:25 -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=vEMXEoSH6mTMnzVm3CcFOVecsUmwT9eN+R0nU1PTvQA=; b=frDCD+wDsUThrUmbDnHDnQwORTyHllgKmwozW5k4sF8hrx2XrnlUydfH+cSsPkA6ai SyPDyZVtqTJiaaNHi+NCF1U5NZYLqr+ASEYwwpGzq7ijZDjPcSS63Ez0KPglzw46v/e6 HyVH2Wpqj4BXny4naHHAYghbojh0DgYV4a+7c= 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=eY1B29W7T+B5g2Y98R3OPbUiMcksP2jCqGxt0IFTxDUWnj8d+SJHzlxTUmHNdiQJRQ mOZv2WlHRYLx8OqeUT1E0r+y+2q/ibi2FqeENFLBFNUD1ExFEU3Ln2awy0BBA2l1n8bU r9wP3AtBh67uP4sv/OVkSjQoNatpNbLpShGew= Received: by 10.204.154.203 with SMTP id p11mr7462787bkw.180.1255551024929; Wed, 14 Oct 2009 13:10:24 -0700 (PDT) Received: from weongyo ([174.35.1.224]) by mx.google.com with ESMTPS id b17sm358895fka.43.2009.10.14.13.10.22 (version=SSLv3 cipher=RC4-MD5); Wed, 14 Oct 2009 13:10:23 -0700 (PDT) Received: by weongyo (sSMTP sendmail emulation); Wed, 14 Oct 2009 13:10:59 -0700 From: Weongyo Jeong Date: Wed, 14 Oct 2009 13:10:59 -0700 To: bsduser Message-ID: <20091014201059.GE67082@weongyo> Mail-Followup-To: bsduser , freebsd-current@freebsd.org References: <86051.1254232666@critter.freebsd.dk> <20091013174201.GC67082@weongyo> <86iqei7tgq.fsf@jodie.vectavision.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86iqei7tgq.fsf@jodie.vectavision.com> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: freebsd-current@freebsd.org Subject: Re: if_rum dies on transmit... 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: Wed, 14 Oct 2009 20:10:26 -0000 On Tue, Oct 13, 2009 at 05:41:09PM -0600, bsduser wrote: > Weongyo Jeong writes: > > > On Tue, Sep 29, 2009 at 01:57:46PM +0000, Poul-Henning Kamp wrote: > >> > >> Has anybody else seen if_rum die when you try to transmit a file over > >> a TCP connection ? > >> > >> If I try to print across the network, upload a file with ftp or anything > >> else of that general tenor, if_rum seems to hang the output queue and > >> stops transmitting packets. > >> > >> Restarting wpa_supplicant mostly resolves the issue, but it does not > >> on its own discover the problem. > >> > >> According to tcpdump(8), packets are still received. > >> > >> Any ideas ? > > > > Could you please test with attached patch? > > > > regards, > > Weongyo Jeong > > > > > > I had the same issues with if_rum at least while using WPA and your patch made > them go away.... ( although removing and plugging back in does not quite > work ) > > # scp INDEX-8* cookie:/usr/ports > INDEX-8 100% 19MB 2.1MB/s 00:09 > INDEX-8.db 100% 34MB 2.4MB/s 00:14 > > before the patch this would just hang. > > Another quick test using rsync on a bunch of files worked flawless too. > > usbconfig list: > > ugen7.2: at usbus7, cfg=0 > md=HOST spd=HIGH (480Mbps) pwr=ON > > The adapter is a WUSB54GC and yes, you made my day :-) Patched at r198098. Thank you for testing! regards, Weongyo Jeong From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 20:24:18 2009 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 05247106568F for ; Wed, 14 Oct 2009 20:24:18 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id AE1A68FC26 for ; Wed, 14 Oct 2009 20:24:17 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApoEAAPQ1UqDaFvI/2dsb2JhbADacoQuBIFbiRI X-IronPort-AV: E=Sophos;i="4.44,561,1249272000"; d="scan'208";a="51625694" Received: from darling.cs.uoguelph.ca ([131.104.91.200]) by esa-jnhn-pri.mail.uoguelph.ca with ESMTP; 14 Oct 2009 16:24:16 -0400 Received: from localhost (localhost.localdomain [127.0.0.1]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id EF58F9400D4; Wed, 14 Oct 2009 16:24:15 -0400 (EDT) X-Virus-Scanned: amavisd-new at darling.cs.uoguelph.ca Received: from darling.cs.uoguelph.ca ([127.0.0.1]) by localhost (darling.cs.uoguelph.ca [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KwckiPZG9CgI; Wed, 14 Oct 2009 16:24:14 -0400 (EDT) Received: from muncher.cs.uoguelph.ca (muncher.cs.uoguelph.ca [131.104.91.102]) by darling.cs.uoguelph.ca (Postfix) with ESMTP id ACCE79400A6; Wed, 14 Oct 2009 16:24:14 -0400 (EDT) Received: from localhost (rmacklem@localhost) by muncher.cs.uoguelph.ca (8.11.7p3+Sun/8.11.6) with ESMTP id n9EKUmx02790; Wed, 14 Oct 2009 16:30:48 -0400 (EDT) X-Authentication-Warning: muncher.cs.uoguelph.ca: rmacklem owned process doing -bs Date: Wed, 14 Oct 2009 16:30:48 -0400 (EDT) From: Rick Macklem X-X-Sender: rmacklem@muncher.cs.uoguelph.ca To: Daniel Braniss In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: 8.0RC1 and BOOTP_NFSV3 regression? 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, 14 Oct 2009 20:24:18 -0000 On Sun, 4 Oct 2009, Daniel Braniss wrote: > I'm not sure when this happened, but a kernel compiled with > BOOTP_NFSV3 fails when the server is not FreeBSD (ie NetAPP). > > before, with the option set, only when kernel_options="nfsv3" was set > it would fail/panic, this way, I could control which diskless, shearing the > same kernel, would boot with nfsv3 and which not, dependig on the server. > > there is hope! before it would panic when receiving a v3 file handle, now > it fails, but panics later when no init is found :-) > > is anyone with enough nfs v2/v3 knowledge willing to fix this? > Just fyi, the change of using NFSv3 by default resulted in this. The poster has confirmed that using "nfsv2" as an explicit option, allows the boot to work against a non-FreeBSD server. The problem is that nfs_setup_diskless() in sys/nfsclient/nfs_diskless.c assumed an NFSv2 type file handle, and then sys/nfsclient/nfs_vfsops.c sets the file handle size to NFSX_V3FH (which is the size of a FreeBSD server's NFSv3 file handle). At a glance, changing nfs_setup_diskless() to set the file handle size based on the length of boot.nfsroot.nfshandle is easy, but then it gets interesting... - In lib/libstand/nfs.c, there is NFSv2 code that fills in boot.nfsroot.nfshandle and adding/converting this to use NFSv3 wouldn't be too hard (more work than the above, but..). --> But I can't see how it can be told to use NFSv2 vs NFSv3? (Does anyone know of a way or would trying NFSv3 and then falling back to NFSv2 make sense?) I don't have a diskless NFS setup, so I'm going to have to depend upon others to do testing. (The poster is willing to do some testing in about 2 weeks.) I don't think this can be done for 8.0. If the change is considered a regression that needs to be fixed for 8.0, taking NFSMNT_NFSV3 out of the default flags in nfs_setup_diskless() would but it back the way FreeBSD7 behaves. I'll let others decide if this should be done. rick From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 20:34:53 2009 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 E1AB71065676 for ; Wed, 14 Oct 2009 20:34:53 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id A0F838FC0A for ; Wed, 14 Oct 2009 20:34:53 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id A2AB06D41B; Wed, 14 Oct 2009 20:34:52 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id 692B2844A0; Wed, 14 Oct 2009 22:34:52 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: "Mario Lobo" References: <20091014151026.699a5765@ernst.jennejohn.org> <18175.200.249.56.17.1255528438.squirrel@squirrel.sv4.hmnoc.net> <86vdiix775.fsf@ds4.des.no> <26594.200.249.56.17.1255540574.squirrel@squirrel.sv4.hmnoc.net> Date: Wed, 14 Oct 2009 22:34:52 +0200 In-Reply-To: <26594.200.249.56.17.1255540574.squirrel@squirrel.sv4.hmnoc.net> (Mario Lobo's message of "Wed, 14 Oct 2009 14:16:14 -0300 (BRT)") Message-ID: <86my3tyas3.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: buffers not syncing correctly during shutdown 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, 14 Oct 2009 20:34:54 -0000 "Mario Lobo" writes: > That IS true ! but like you said, "most cases" <> "all cases". Once, on a > company I was doing work at, I clicked on "Safely Remove Hardware" and it > said "can=C2=B4t do it. device busy", although there was (apparently) not= hing > using any files from the stick. I yanked it out anyway. result: the 3 > files I edited from the stick were gone :(. Since I don=C2=B4t know when = I am > gonna hit a case that doesn=C2=B4t belong to "most", I always try to reme= mber > to unmount (i.e. Safely Remove Hardware) the stick before unplugging it. Always a good idea - but my point was that Windows's "safely remove hardware" feature should not be construed as an excuse for FreeBSD to hang or crash when you remove a disk or memory stick. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 20:38:48 2009 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 BF3521065672 for ; Wed, 14 Oct 2009 20:38:48 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 7D4C98FC1C for ; Wed, 14 Oct 2009 20:38:48 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id n9EKclVm074281; Wed, 14 Oct 2009 14:38:47 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id n9EKcljX074278; Wed, 14 Oct 2009 14:38:47 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 14 Oct 2009 14:38:47 -0600 (MDT) From: Warren Block To: Joe Marcus Clarke In-Reply-To: <1255546422.22880.136.camel@shumai.marcuscom.com> Message-ID: References: <1255542419.22880.131.camel@shumai.marcuscom.com> <1255546422.22880.136.camel@shumai.marcuscom.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (wonkity.com [127.0.0.1]); Wed, 14 Oct 2009 14:38:47 -0600 (MDT) Cc: current@freebsd.org Subject: Re: Why does hal think my USB devices are fixed? 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, 14 Oct 2009 20:38:48 -0000 On Wed, 14 Oct 2009, Joe Marcus Clarke wrote: > > I don't have any card readers, but as Hans pointed out, this part will > come from the SCSI subsystem. If CAM says the device is not removable, > then hal will go with that. Light sledgehammering in /usr/local/share/hal/fdi/preprobe/20thirdparty and the card reader can be made to work: First, stop hal trying to automount a card twice, once for the redundant "computer_storage" version of a disk: 10-ignore-computer_storage.fdi : true Then set some options for the card reader: 20-check-media.fdi : storage.media_check_enabled true true hal still sometimes doesn't notice new cards being connected, and the card reader's USB cable has to be reconnected. But at this point, it's at least as good as it was under 7-STABLE. -Warren Block * Rapid City, South Dakota USA From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 20:46:25 2009 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 54F8F106568D for ; Wed, 14 Oct 2009 20:46:25 +0000 (UTC) (envelope-from bsd@acd.homelinux.org) Received: from office.acapsecurity.com (rrcs-67-52-121-82.west.biz.rr.com [67.52.121.82]) by mx1.freebsd.org (Postfix) with ESMTP id 3471D8FC1A for ; Wed, 14 Oct 2009 20:46:24 +0000 (UTC) Received: from acd.homelinux.org (unknown [10.0.15.5]) by office.acapsecurity.com (Postfix) with ESMTP id D7D5E5C06; Wed, 14 Oct 2009 13:46:23 -0700 (PDT) Received: by acd.homelinux.org (Postfix, from userid 1001) id 4C2BA2587; Wed, 14 Oct 2009 14:46:23 -0600 (MDT) From: Axel To: freebsd-current@freebsd.org In-Reply-To: <20091014201059.GE67082@weongyo> (Weongyo Jeong's message of "Wed, 14 Oct 2009 13:10:59 -0700") Date: Wed, 14 Oct 2009 14:34:40 -0600 Lines: 60 References: <86051.1254232666@critter.freebsd.dk> <20091013174201.GC67082@weongyo> <86iqei7tgq.fsf@jodie.vectavision.com> <20091014201059.GE67082@weongyo> User-Agent: Gnus/5.110009 (No Gnus v0.9) Emacs/22.3 (berkeley-unix) X-From-Line: nobody Wed Oct 14 14:34:40 2009 Message-ID: <86pr8pg0v4.fsf@jodie.vectavision.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Weongyo Jeong Subject: Re: if_rum dies on transmit... 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, 14 Oct 2009 20:46:25 -0000 Weongyo Jeong writes: > On Tue, Oct 13, 2009 at 05:41:09PM -0600, bsduser wrote: >> Weongyo Jeong writes: >> >> > On Tue, Sep 29, 2009 at 01:57:46PM +0000, Poul-Henning Kamp wrote: >> >> >> >> Has anybody else seen if_rum die when you try to transmit a file over >> >> a TCP connection ? >> >> >> >> If I try to print across the network, upload a file with ftp or anything >> >> else of that general tenor, if_rum seems to hang the output queue and >> >> stops transmitting packets. >> >> >> >> Restarting wpa_supplicant mostly resolves the issue, but it does not >> >> on its own discover the problem. >> >> >> >> According to tcpdump(8), packets are still received. >> >> >> >> Any ideas ? >> > >> > Could you please test with attached patch? >> > >> > regards, >> > Weongyo Jeong >> > >> > >> >> I had the same issues with if_rum at least while using WPA and your patch made >> them go away.... ( although removing and plugging back in does not quite >> work ) >> >> # scp INDEX-8* cookie:/usr/ports >> INDEX-8 100% 19MB 2.1MB/s 00:09 >> INDEX-8.db 100% 34MB 2.4MB/s 00:14 >> >> before the patch this would just hang. >> >> Another quick test using rsync on a bunch of files worked flawless too. >> >> usbconfig list: >> >> ugen7.2: at usbus7, cfg=0 >> md=HOST spd=HIGH (480Mbps) pwr=ON >> >> The adapter is a WUSB54GC and yes, you made my day :-) > > Patched at r198098. Thank you for testing! > > regards, > Weongyo Jeong For the records, I patched svn r197304 on an amd64 but am fairly sure it'll work the same on later revisions. Thanks very much for you work, -- Axel (bsd@acd.homelinux.org). From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 20:47:08 2009 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 C7C12106566C for ; Wed, 14 Oct 2009 20:47:08 +0000 (UTC) (envelope-from pjd@garage.freebsd.pl) Received: from mail.garage.freebsd.pl (chello087206049004.chello.pl [87.206.49.4]) by mx1.freebsd.org (Postfix) with ESMTP id A98398FC16 for ; Wed, 14 Oct 2009 20:47:06 +0000 (UTC) Received: by mail.garage.freebsd.pl (Postfix, from userid 65534) id 6DDD245EE6; Wed, 14 Oct 2009 22:47:04 +0200 (CEST) Received: from localhost (chello087206049004.chello.pl [87.206.49.4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.garage.freebsd.pl (Postfix) with ESMTP id 35C2845E90; Wed, 14 Oct 2009 22:46:59 +0200 (CEST) Date: Wed, 14 Oct 2009 22:46:57 +0200 From: Pawel Jakub Dawidek To: Andriy Gapon Message-ID: <20091014204657.GB1727@garage.freebsd.pl> References: <4AD5BD00.4050700@icyb.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="l76fUT7nc3MelDdI" Content-Disposition: inline In-Reply-To: <4AD5BD00.4050700@icyb.net.ua> User-Agent: Mutt/1.4.2.3i X-PGP-Key-URL: http://people.freebsd.org/~pjd/pjd.asc X-OS: FreeBSD 9.0-CURRENT i386 X-Spam-Checker-Version: SpamAssassin 3.0.4 (2005-06-05) on mail.garage.freebsd.pl X-Spam-Level: X-Spam-Status: No, score=-0.6 required=4.5 tests=BAYES_00,RCVD_IN_SORBS_DUL autolearn=no version=3.0.4 Cc: Alexander Best , freebsd-current@FreeBSD.org Subject: Re: panic when mounting device >= 2 times 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, 14 Oct 2009 20:47:08 -0000 --l76fUT7nc3MelDdI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Oct 14, 2009 at 02:58:56PM +0300, Andriy Gapon wrote: > on 14/10/2009 14:21 Alexander Best said the following: > > could somebody have a look at this PR please: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dkern/108968 > >=20 > > this still exists in -CURRENT. >=20 > This is because of serious and long-standing brokenness (probably from ti= me of > introduction of GEOM) in g_vfs_open/g_vfs_close. > The essence: > 1. we allow multiple concurrent read-only mounts of a device > 2. but even a read-only mount mangles bufobj of device vnode > 3. Bug! > Trivial fix with POLA violation - prohibit concurrent RO mounts. > Non-trivial fix - _somehow_ avoid changing or depending on device vnode b= ufobj. I've this patch that is suppose to fix it: http://people.freebsd.org/~pjd/patches/geom_vfs.c.patch But AFAIR its not complete. I think it is still possible to remount one of the read-only mounts to read-write. Another possibility that comes to my mind is to keep list/array of consumers in bo_private instead of using one consumer only. This would be better in terms of access management. --=20 Pawel Jakub Dawidek http://www.wheel.pl pjd@FreeBSD.org http://www.FreeBSD.org FreeBSD committer Am I Evil? Yes, I Am! --l76fUT7nc3MelDdI Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) iD8DBQFK1jjBForvXbEpPzQRAit3AJ4y3sElFfuPMggRCMGKLgsWKZbt4ACbB6ZJ oI3aIbx6SYuHNjP3Nq1wLKI= =925B -----END PGP SIGNATURE----- --l76fUT7nc3MelDdI-- From owner-freebsd-current@FreeBSD.ORG Wed Oct 14 22:09:11 2009 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 60DEC106568D for ; Wed, 14 Oct 2009 22:09:11 +0000 (UTC) (envelope-from gavin@FreeBSD.org) Received: from mail-gw2.york.ac.uk (mail-gw2.york.ac.uk [144.32.128.247]) by mx1.freebsd.org (Postfix) with ESMTP id D20E98FC15 for ; Wed, 14 Oct 2009 22:09:10 +0000 (UTC) Received: from mail-gw7.york.ac.uk (mail-gw7.york.ac.uk [144.32.129.30]) by mail-gw2.york.ac.uk (8.13.6/8.13.6) with ESMTP id n9EM8fS5028900; Wed, 14 Oct 2009 23:08:41 +0100 (BST) Received: from ury.york.ac.uk ([144.32.108.81]) by mail-gw7.york.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.68) (envelope-from ) id 1MyC1R-0000EE-SL; Wed, 14 Oct 2009 23:08:41 +0100 Received: from ury.york.ac.uk (localhost.york.ac.uk [127.0.0.1]) by ury.york.ac.uk (8.14.3/8.14.3) with ESMTP id n9EM8fHJ076723; Wed, 14 Oct 2009 23:08:41 +0100 (BST) (envelope-from gavin@FreeBSD.org) Received: from localhost (gavin@localhost) by ury.york.ac.uk (8.14.3/8.14.3/Submit) with ESMTP id n9EM8dpI076706; Wed, 14 Oct 2009 23:08:39 +0100 (BST) (envelope-from gavin@FreeBSD.org) X-Authentication-Warning: ury.york.ac.uk: gavin owned process doing -bs Date: Wed, 14 Oct 2009 23:08:39 +0100 (BST) From: Gavin Atkinson X-X-Sender: gavin@ury.york.ac.uk To: Weongyo Jeong In-Reply-To: <20091014201059.GE67082@weongyo> Message-ID: <20091014230715.E96894@ury.york.ac.uk> References: <86051.1254232666@critter.freebsd.dk> <20091013174201.GC67082@weongyo> <86iqei7tgq.fsf@jodie.vectavision.com> <20091014201059.GE67082@weongyo> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-York-MailScanner: Found to be clean X-York-MailScanner-From: gavin@freebsd.org Cc: bsduser , freebsd-current@FreeBSD.org Subject: Re: if_rum dies on transmit... 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, 14 Oct 2009 22:09:11 -0000 On Wed, 14 Oct 2009, Weongyo Jeong wrote: > On Tue, Oct 13, 2009 at 05:41:09PM -0600, bsduser wrote: >> Weongyo Jeong writes: >> >>> On Tue, Sep 29, 2009 at 01:57:46PM +0000, Poul-Henning Kamp wrote: >>>> >>>> Has anybody else seen if_rum die when you try to transmit a file over >>>> a TCP connection ? >>>> >>>> If I try to print across the network, upload a file with ftp or anything >>>> else of that general tenor, if_rum seems to hang the output queue and >>>> stops transmitting packets. >>> >>> Could you please test with attached patch? >>> >> >> I had the same issues with if_rum at least while using WPA and your patch made >> them go away.... ( although removing and plugging back in does not quite >> work ) >> >> # scp INDEX-8* cookie:/usr/ports >> INDEX-8 100% 19MB 2.1MB/s 00:09 >> INDEX-8.db 100% 34MB 2.4MB/s 00:14 >> >> before the patch this would just hang. >> >> Another quick test using rsync on a bunch of files worked flawless too. >> >> usbconfig list: >> >> ugen7.2: at usbus7, cfg=0 >> md=HOST spd=HIGH (480Mbps) pwr=ON >> >> The adapter is a WUSB54GC and yes, you made my day :-) > > Patched at r198098. Thank you for testing! Many thanks for this! Do you know if this patch is likely to fix the panics seen with rum(4) or is this likely to only fix the TX hangs? Thanks, Gavin From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 01:13:44 2009 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 EF962106566B; Thu, 15 Oct 2009 01:13:44 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id D61E88FC1A; Thu, 15 Oct 2009 01:13:44 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n9F1DiO9000091; Wed, 14 Oct 2009 18:13:44 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 14 Oct 2009 18:12:41 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ARP Changes Thread-Index: AcpNNJf6RjDjdETRRwma32MIH3lQ0Q== From: "Li, Qing" To: , Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: Re: ARP 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, 15 Oct 2009 01:13:45 -0000 > > I know that arp has changed a lot in FreeBSD 8. I am wondering if one > change was by design? In older versions of FreeBSD, if you ping a = host > that is on a local network but is down, after a few seconds ping = displays: > ping: sendto: Host is down > ping: sendto: Host is down > This turned out to be a regression bug. A wrong variable is used and the incomplete entry was timing out too fast. So the ARP probe = continues indefinitely ... =20 > > Using arp to display the arp table shows: > > host.domain (x.x.x.x) at (incomplete) on em0 [ethernet] I wasn't returning incomplete entries, but now I am ... I have a patch for both issues, but I need to clean up the code because that wrong variable is used elsewhere in the same module. I should be able to commit a permanent fix by tomorrow. -- Qing From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 04:34:24 2009 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 E1E30106566C for ; Thu, 15 Oct 2009 04:34:24 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail3.es.net [IPv6:2001:400:4c01::2]) by mx1.freebsd.org (Postfix) with ESMTP id B3D9B8FC15 for ; Thu, 15 Oct 2009 04:34:24 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id n9F4YM8A013900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 14 Oct 2009 21:34:23 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 6B42D1CC37; Wed, 14 Oct 2009 21:34:22 -0700 (PDT) To: Warren Block In-reply-to: Your message of "Wed, 14 Oct 2009 14:38:47 MDT." Date: Wed, 14 Oct 2009 21:34:22 -0700 From: "Kevin Oberman" Message-Id: <20091015043422.6B42D1CC37@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2009-10-15_02:2009-09-29, 2009-10-15, 2009-10-14 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-0910140280 Cc: current@freebsd.org Subject: Re: Why does hal think my USB devices are fixed? 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, 15 Oct 2009 04:34:25 -0000 > Date: Wed, 14 Oct 2009 14:38:47 -0600 (MDT) > From: Warren Block > Sender: owner-freebsd-current@freebsd.org > > On Wed, 14 Oct 2009, Joe Marcus Clarke wrote: > > > > I don't have any card readers, but as Hans pointed out, this part will > > come from the SCSI subsystem. If CAM says the device is not removable, > > then hal will go with that. > > Light sledgehammering in /usr/local/share/hal/fdi/preprobe/20thirdparty > and the card reader can be made to work: > > First, stop hal trying to automount a card twice, once for the redundant > "computer_storage" version of a disk: > > 10-ignore-computer_storage.fdi : > > > > > > > true > > > > > Then set some options for the card reader: > > 20-check-media.fdi : > > > > > > storage.media_check_enabled > > true > true > > > > > hal still sometimes doesn't notice new cards being connected, and the > card reader's USB cable has to be reconnected. But at this point, it's > at least as good as it was under 7-STABLE. Doing something to access the device seems to cause it to be "noticed". I use 'fsck -p' on the device, but I suspect dd(1) or most anything else that touches the device will do it. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 05:25:07 2009 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 63F291065695; Thu, 15 Oct 2009 05:25:07 +0000 (UTC) (envelope-from i.a.zhuravlev@cbtnet.ru) Received: from mx2.cbtnet.ru (mail.cbtnet.ru [188.128.41.250]) by mx1.freebsd.org (Postfix) with ESMTP id 061648FC16; Thu, 15 Oct 2009 05:25:06 +0000 (UTC) Received: from ilya.ispsystem.net (unknown [82.146.37.104]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx2.cbtnet.ru (Eserv/3.4126) with ESMTP id C3E24175CBC; Thu, 15 Oct 2009 14:41:58 +0900 (IRKST) Message-ID: <4AD6AC54.1010202@cbtnet.ru> Date: Thu, 15 Oct 2009 14:00:04 +0900 From: Ilya Zhuravlev User-Agent: Thunderbird 2.0.0.23 (X11/20090926) MIME-Version: 1.0 To: Weongyo Jeong , current@freebsd.org References: <86051.1254232666@critter.freebsd.dk> <20091013174201.GC67082@weongyo> In-Reply-To: <20091013174201.GC67082@weongyo> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Re: if_rum dies on transmit... 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, 15 Oct 2009 05:25:07 -0000 Weongyo Jeong wrote: > On Tue, Sep 29, 2009 at 01:57:46PM +0000, Poul-Henning Kamp wrote: > >> Has anybody else seen if_rum die when you try to transmit a file over >> a TCP connection ? >> >> If I try to print across the network, upload a file with ftp or anything >> else of that general tenor, if_rum seems to hang the output queue and >> stops transmitting packets. >> >> Restarting wpa_supplicant mostly resolves the issue, but it does not >> on its own discover the problem. >> >> According to tcpdump(8), packets are still received. >> >> Any ideas ? >> > > Could you please test with attached patch? > > regards, > Weongyo Jeong > > Thanks, it stopped issues with my Dlink DWA-110 wbr, Ilya From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 06:25:58 2009 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 987951065670; Thu, 15 Oct 2009 06:25:58 +0000 (UTC) (envelope-from qing.li@bluecoat.com) Received: from whisker.bluecoat.com (whisker.bluecoat.com [216.52.23.28]) by mx1.freebsd.org (Postfix) with ESMTP id BA1CA8FC21; Thu, 15 Oct 2009 06:25:57 +0000 (UTC) Received: from bcs-mail03.internal.cacheflow.com ([10.2.2.95]) by whisker.bluecoat.com (8.14.2/8.14.2) with ESMTP id n9F6Puki027688; Wed, 14 Oct 2009 23:25:57 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Wed, 14 Oct 2009 23:17:27 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: ARP Changes Thread-Index: AcpNNJf6RjDjdETRRwma32MIH3lQ0QAKpMwR References: From: "Li, Qing" To: "Li, Qing" , , , Cc: freebsd-net@freebsd.org, freebsd-current@freebsd.org Subject: RE: ARP 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, 15 Oct 2009 06:25:58 -0000 I have committed the fix into the -current branch, svn r198111. Please give it a try and I plan to MFC the patch into 8.0 release branch in 3 days. Thank you for the report. -- Qing -----Original Message----- From: owner-freebsd-current@freebsd.org on behalf of Li, Qing Sent: Wed 10/14/2009 6:12 PM To: lab@gta.com; qingli@freebsd.org Cc: freebsd-net@freebsd.org; freebsd-current@freebsd.org Subject: Re: ARP Changes =20 > > I know that arp has changed a lot in FreeBSD 8. I am wondering if one > change was by design? In older versions of FreeBSD, if you ping a = host > that is on a local network but is down, after a few seconds ping = displays: > ping: sendto: Host is down > ping: sendto: Host is down > This turned out to be a regression bug. A wrong variable is used and the incomplete entry was timing out too fast. So the ARP probe = continues indefinitely ... =20 > > Using arp to display the arp table shows: > > host.domain (x.x.x.x) at (incomplete) on em0 [ethernet] I wasn't returning incomplete entries, but now I am ... I have a patch for both issues, but I need to clean up the code because that wrong variable is used elsewhere in the same module. I should be able to commit a permanent fix by tomorrow. -- Qing _______________________________________________ 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" From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 08:00:33 2009 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 1E218106568B; Thu, 15 Oct 2009 08:00:33 +0000 (UTC) (envelope-from guru@unixarea.de) Received: from dd12710.kasserver.com (dd12710.kasserver.com [85.13.134.233]) by mx1.freebsd.org (Postfix) with ESMTP id A08E18FC1B; Thu, 15 Oct 2009 08:00:32 +0000 (UTC) Received: from current.Sisis.de (cazador.sisis.de [193.31.11.193]) by dd12710.kasserver.com (Postfix) with ESMTP id D589C1865ADB9; Thu, 15 Oct 2009 10:00:32 +0200 (CEST) Received: (from guru@localhost) by current.Sisis.de (8.14.3/8.14.3/Submit) id n9F80Zt6002082; Thu, 15 Oct 2009 10:00:35 +0200 (CEST) (envelope-from guru@unixarea.de) X-Authentication-Warning: current.Sisis.de: guru set sender to guru@unixarea.de using -f Date: Thu, 15 Oct 2009 10:00:35 +0200 From: Matthias Apitz To: Martin Wilke , kde-freebsd@kde.org, freebsd-current@freebsd.org Message-ID: <20091015080034.GA2045@current.Sisis.de> References: <20091011062419.GA2168@current.Sisis.de> <3a142e750910111214rb75f185k12b2cc7e1aba59d9@mail.gmail.com> <20091012130914.GA4180@current.Sisis.de> <20091013153815.GA88394@bsdcrew.de> <20091014063221.GA2301@current.Sisis.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20091014063221.GA2301@current.Sisis.de> User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 8.0-CURRENT (i386) Cc: Subject: Re: [kde-freebsd] 9-CURRENT (r197801) && artsd of kde-3.5.10_2 gives SIGSEGV X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matthias Apitz List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 08:00:33 -0000 El día Wednesday, October 14, 2009 a las 08:32:21AM +0200, Matthias Apitz escribió: > ... > > as well I have fetched the 8.0-RC1 precompiled package arts-1.5.10_2,1.tbz > and will give it a try in 9-CURRENT. > > Will let you know what I can find out. Hello, This morning I tried the 8.0-RC1 version of the pre-compiled package arts-1.5.10_2,1.tbz from the FreeBSD server: it crashes as well. So the problem is perhaps outside this package. While I was thinking what could be wrong I stumbled over the following small clash: as I said, I installed 8.0-RC1 base system and updated /usr/src from SVN and later after 9-CURRENT was build and installed I updated /usr/ports from CVS. The problem is that for the SVN checkout one must build the port /usr/ports/devel/subversion-freebsd; I compared the time when I did the SVN checkout (Oct 6, 11:xx) against the times in /var/db/pkg and it turned out that the following ports and have been installed *before* 9-CURRENT kernel/user-land: # ls -l */+CONTENTS | fgrep 'Oct 6 11' -rw-r--r-- 1 root wheel 7938 Oct 6 11:48 apr-ipv6-gdbm-db42-1.3.8.1.3.9/+CONTENTS -rw-r--r-- 1 root wheel 7368 Oct 6 11:44 autoconf-2.62/+CONTENTS -rw-r--r-- 1 root wheel 606 Oct 6 11:44 autoconf-wrapper-20071109/+CONTENTS -rw-r--r-- 1 root wheel 9579 Oct 6 11:44 automake-1.9.6_3/+CONTENTS -rw-r--r-- 1 root wheel 304 Oct 6 11:44 automake-wrapper-20071109/+CONTENTS -rw-r--r-- 1 root wheel 107102 Oct 6 11:46 db42-4.2.52_5/+CONTENTS -rw-r--r-- 1 root wheel 801 Oct 6 11:28 expat-2.0.1/+CONTENTS -rw-r--r-- 1 root wheel 1238 Oct 6 11:44 gdbm-1.8.3_3/+CONTENTS -rw-r--r-- 1 root wheel 33428 Oct 6 11:26 gettext-0.17_1/+CONTENTS -rw-r--r-- 1 root wheel 2795 Oct 6 11:26 gmake-3.81_3/+CONTENTS -rw-r--r-- 1 root wheel 2670 Oct 6 11:44 help2man-1.36.4_3/+CONTENTS -rw-r--r-- 1 root wheel 2856 Oct 6 11:23 libiconv-1.13.1/+CONTENTS -rw-r--r-- 1 root wheel 4625 Oct 6 11:19 libtool-2.2.6a/+CONTENTS -rw-r--r-- 1 root wheel 4011 Oct 6 11:44 m4-1.4.13,1/+CONTENTS -rw-r--r-- 1 root wheel 31411 Oct 6 11:28 neon28-0.28.4/+CONTENTS -rw-r--r-- 1 root wheel 1271 Oct 6 11:44 p5-gettext-1.05_2/+CONTENTS -rw-r--r-- 1 root wheel 314648 Oct 6 11:40 perl-5.8.9_3/+CONTENTS -rw-r--r-- 1 root wheel 573 Oct 6 11:27 pkg-config-0.23_1/+CONTENTS -rw-r--r-- 1 root wheel 376893 Oct 6 11:43 python26-2.6.2_3/+CONTENTS -rw-r--r-- 1 root wheel 1063 Oct 6 11:28 sqlite3-3.6.14.2/+CONTENTS -rw-r--r-- 1 root wheel 27342 Oct 6 11:50 subversion-freebsd-1.6.5/+CONTENTS esp. libtool-2.2.6a let me think that this procedure (i.e. building subversion-freebsd before updating to 9-CURRENT) could cause the clash. I will recompile the above ports and if this does not help re-install all and remove /usr/local/* and /var/db/pkg/* before starting with compiling the ports after the SVN and CVS parts are done. matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e - w http://www.unixarea.de/ Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 08:11:35 2009 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 7418B106568D for ; Thu, 15 Oct 2009 08:11:35 +0000 (UTC) (envelope-from matthias.andree@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id D1A3A8FC15 for ; Thu, 15 Oct 2009 08:11:34 +0000 (UTC) Received: (qmail invoked by alias); 15 Oct 2009 08:11:33 -0000 Received: from kokosnoot.wur.nl (EHLO balu.cs.uni-paderborn.de) [137.224.252.10] by mail.gmx.net (mp069) with SMTP; 15 Oct 2009 10:11:33 +0200 X-Authenticated: #428038 X-Provags-ID: V01U2FsdGVkX19Pv2h6WKZP59jmFCKmm4wLuHtxRvohxgO+vmFxv2 DEFdRnlgeVUK9q Received: from localhost ([127.0.0.1]) by balu.cs.uni-paderborn.de with esmtp (Exim 4.69) (envelope-from ) id KRJQR7-0001DG-QS for freebsd-current@freebsd.org; Thu, 15 Oct 2009 10:11:32 +0200 Message-ID: <4AD6D933.1070804@gmx.de> Date: Thu, 15 Oct 2009 10:11:31 +0200 From: Matthias Andree User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <20091014151026.699a5765@ernst.jennejohn.org> In-Reply-To: <20091014151026.699a5765@ernst.jennejohn.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.53 Subject: Re: buffers not syncing correctly during shutdown 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, 15 Oct 2009 08:11:35 -0000 Gary Jennejohn schrieb: > On Wed, 14 Oct 2009 12:49:54 +0200 (CEST) > Alexander Best wrote: > >> hi there, >> >> to keep it short: >> >> 1. mount a removable device (e.g. an usb stick) (better use -r to prevent data >> loss) >> 2. unplug the device (without unmounting it) >> 3. `shutdown -r now` >> >> what happens is that the usual shutdown routine gets processed until all >> buffers are synced, but then the system stalls. >> >> after resetting the system all devices (which were supposed to be synced) are >> marked dirty and are being fsck'ed. >> >> cheers. >> alex >> >> oh...and i'm running FreeBSD otaku 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r197914: >> Sat Oct 10 02:58:19 CEST 2009 root@otaku:/usr/obj/usr/src/sys/ARUNDEL >> i386 >> > > I'm inclined to say that umount'ing the file systems is failing because > you pulled the USB stick out without doing umount. Of course, that > results in all file systems still being marked dirty. Obviously, this > pathological case isn't being handled. > > I personally don't see why it ever should be handled. This is UNIX not > Windows and users should be smart enough to know that they umount such > devices before removing them otherwise nasty things can happen. 1. If the device for one file system is gone, why would I mark *other* file systems dirty? There is no reason to do so. 2. If a file system was mounted read-only, and its device is removed, there are by definition ZERO dirty buffers that we need to synch on shutdown, so why does the premature unplug-readonly-before-unmount spoil the shutdown? From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 09:35:33 2009 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 D2039106566C for ; Thu, 15 Oct 2009 09:35:33 +0000 (UTC) (envelope-from christian@nertenher.de) Received: from mail-fx0-f222.google.com (mail-fx0-f222.google.com [209.85.220.222]) by mx1.freebsd.org (Postfix) with ESMTP id 71F298FC1D for ; Thu, 15 Oct 2009 09:35:32 +0000 (UTC) Received: by fxm22 with SMTP id 22so829383fxm.36 for ; Thu, 15 Oct 2009 02:35:32 -0700 (PDT) MIME-Version: 1.0 Sender: christian@nertenher.de Received: by 10.223.75.136 with SMTP id y8mr2130292faj.69.1255599332198; Thu, 15 Oct 2009 02:35:32 -0700 (PDT) In-Reply-To: <309b65830910130912u7fd303e9kffa1b248188b9194@mail.gmail.com> References: <309b65830910060054g16a099abxb8e203a46aa9e89c@mail.gmail.com> <4AD2BCD9.2090904@sandstorm.net> <309b65830910130912u7fd303e9kffa1b248188b9194@mail.gmail.com> From: Christian Schmidt Date: Thu, 15 Oct 2009 11:35:11 +0200 X-Google-Sender-Auth: 0abffa4795f7d462 Message-ID: <309b65830910150235w59857e83r23887193c36561f0@mail.gmail.com> To: john hood , freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: Boot issues with a Dell Inspiron 530 and 8.0 RC1 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, 15 Oct 2009 09:35:33 -0000 On Tue, Oct 13, 2009 at 18:12, Christian Schmidt wrot= e: > On Mon, Oct 12, 2009 at 07:21, john hood wrote: >> Christian Schmidt wrote: > [...] >>> I am seeing a strange issue with my Dell Inspiron 530 with 8.0 RC1-p1 >>> at around 50-75% percent of all boots. It all boils down to GENERIC >>> throwing the following: >>> >>> AP #1 (PHY #1) failed! >>> panic y/n? [y] panic: bye-bye >>> cpuid =3D 0 > [...] >> We have 3 of these machines. >> >> In my experience, keyboard activity triggers the problem. =C2=A0If I boo= t the >> machine without any keyboard presses/releases between the time the loade= r >> starts the kernel and some time later, definitely by the time the USB >> keyboard driver attaches, then I don't get this problem. =C2=A0This incl= udes any >> key-up (and maybe key repeat) events you may generate after typing a key= at >> the boot menu, or after typing enter at the OK prompt, or pressing a key= to >> bypass the autoboot timeout that counts down by seconds. >> >> If you let the machine start from cold without touching the keyboard, wh= at >> happens? > > That is a very interesting point you are making. Indeed, it never > occured to me that I am usually hammering down on F1 and 1 to boot > faster (yeah yeah, I know ;-)). I let the machine boot through without > that a couple of times and it seemed to have worked for about a 100% > of those cases. I will keep testing but I think we have a hot > contender. :-) > Okay, after testing that for a couple of days I can confirm that it never-ever happens when I leave the keyboard alone during the boot-phase. As a workaround, I can live with not touching the keyboard. Nethertheless, this seems to be a bug that deserves fixing, isn't it? Thank you for your help. :-) Christian From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 09:47:33 2009 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 023521065670 for ; Thu, 15 Oct 2009 09:47:33 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from lo.gmane.org (lo.gmane.org [80.91.229.12]) by mx1.freebsd.org (Postfix) with ESMTP id 7FD758FC0A for ; Thu, 15 Oct 2009 09:47:32 +0000 (UTC) Received: from list by lo.gmane.org with local (Exim 4.50) id 1MyMvf-00039v-0P for freebsd-current@freebsd.org; Thu, 15 Oct 2009 11:47:27 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 15 Oct 2009 11:47:26 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 15 Oct 2009 11:47:26 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Thu, 15 Oct 2009 11:47:10 +0200 Lines: 41 Message-ID: References: <20091014151026.699a5765@ernst.jennejohn.org> <20091014175600.GA55864@wep4035.physik.uni-wuerzburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.23 (X11/20090928) In-Reply-To: <20091014175600.GA55864@wep4035.physik.uni-wuerzburg.de> Sender: news Subject: Re: buffers not syncing correctly during shutdown 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, 15 Oct 2009 09:47:33 -0000 Alexey Shuvaev wrote: > On Wed, Oct 14, 2009 at 03:13:00PM +0200, Ivan Voras wrote: >> Gary Jennejohn wrote: >> >>> I personally don't see why it ever should be handled. This is UNIX not >>> Windows and users should be smart enough to know that they umount such >>> devices before removing them otherwise nasty things can happen. >> Yes, but this is 2009 not 1978. >> > Well, the other side of being in 2009 is that filesystems have evolved too. > For example, I have UFS2 + SU on most of my removable media (sticks and > external hard drives). I was always interested how > this new "feature" of FreeBSD, to allow removable media disappear almost > silently, plays in this case? I see what you mean - UFS+SU is definitely not suitable for this environment. UFS without SU (mounted "normal" or "sync") OTOH is better. Windows mounts removable devices sync (unless told otherwise) since sometime around Win98SE. > I've had one case when I lost my external hard drive during > tar -xvf ports.tar.bz2 into it. I haven't touched it at the moment > (voltage spikes?). It was quite funny trying to browse through > the half-cached content then... have spent ~5 minutes before noticing > kernel message. > Re-plugging the drive has brought it back, with dirty filesystem, of course. > Maybe it would be better if the system paniced then :/) This would not help since the newly inserted device would get its own descriptor structure, whose pointer is obviously different from the old one... > Anyway, my point is that removing the media with most of > modern filesystems on it without unmounting is an operator error. > IMHO, the system should warn such an operators in one or the other way... Warn about what? That the media has been removed? AFAIK USB does this right now. Or you are suggesting another message from the file system layer saying: "see, about that in-transit data you are thinking about... well, it's gone now." :) From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 06:24:01 2009 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 EACA51065676 for ; Thu, 15 Oct 2009 06:24:01 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id 875368FC08 for ; Thu, 15 Oct 2009 06:24:01 +0000 (UTC) Received: by ewy18 with SMTP id 18so520592ewy.43 for ; Wed, 14 Oct 2009 23:24:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=xh56UlSqTYAwuSCcv1rKJTf9IZrkM2Eiqf9xZaPh7vI=; b=LgbYiYmqrwHW9Y0QlOhngWlqrGnuSIL9bLj0TcHGm9B2242G42LHi4wGIySofi+O0E EsHB581yIEhd7talsxKbBJHx1PPjCYFs3P3eIkvhuHpliF12DpAwvzfDrlMJXO0KKWjC g+6hrM0Qq5HZxipcnpZ9g7eKyVoQZ/scQyn1A= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=QYtGIzAxWShZmC2YH1WyR46x649W/1sOz+qYl1jfgSvK/Sh0hG3UCLqtXIVPsmQ7N9 b+y5q0aGyCH+vRYfVAc41nZO8rOVfTaoH2QoQzlIfo4vubUW1+FjB+Cl1AjNcfa1+bsN P5RuTDwcmK275iVcHNXw28exLFtdsTRIAJrHs= MIME-Version: 1.0 Received: by 10.211.142.11 with SMTP id u11mr523456ebn.8.1255587840508; Wed, 14 Oct 2009 23:24:00 -0700 (PDT) Date: Thu, 15 Oct 2009 02:24:00 -0400 Message-ID: From: grarpamp To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Thu, 15 Oct 2009 11:31:24 +0000 Subject: vmstat -m/-z field parsing 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, 15 Oct 2009 06:24:02 -0000 Some of the 'first' columns in the output contain spaces which makes it hard to parse the data out. Unless I'm missing the reason, I propose they be changed to underscores '_' as per the rest of the ouput. Thanks. The ones I see with my GENERIC kernel plus: 2 1 0xc0f77000 13c50c zfs.ko 3 2 0xc10b4000 3cec opensolaris.ko 4 1 0xc10b8000 11ea4 geom_eli.ko 5 2 0xc10ca000 25af0 crypto.ko 6 2 0xc10f0000 ac20 zlib.ko 7 1 0xc10fb000 7224 snd_ich.ko 8 2 0xc1103000 56740 sound.ko are: # vmstat -m... CAM SIM CAM XPT CAM dev queue CAM periph CAM queue NFS FHA eli data # vmstat -z 128 Bucket 16 Bucket 32 Bucket 64 Bucket DP fakepg FFS inode FFS1 dinode FFS2 dinode KMAP ENTRY L VFS Cache MAC labels MAP ENTRY S VFS Cache SG fakepg UMA Hash UMA Kegs UMA RCntSlabs UMA Slabs UMA Zones VM OBJECT umtx pi From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 12:28:20 2009 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 24F9D1065679; Thu, 15 Oct 2009 12:28:20 +0000 (UTC) (envelope-from valin@buchlovice.org) Received: from smtp-sfn.sitkom.cz (smtp-sfn.sitkom.cz [88.146.175.4]) by mx1.freebsd.org (Postfix) with ESMTP id DD0148FC0C; Thu, 15 Oct 2009 12:28:19 +0000 (UTC) Received: from osiris.buchlovice.sfn (valin-osiris-lan.brestek.sfn [10.8.20.3]) by smtp-sfn.sitkom.cz (Postfix) with ESMTP id 96F851FA69E; Thu, 15 Oct 2009 14:08:55 +0200 (CEST) Message-ID: <4AD710D6.70404@buchlovice.org> Date: Thu, 15 Oct 2009 14:08:54 +0200 From: =?UTF-8?B?UmFkZWsgVmFsw6HFoWVr?= User-Agent: Thunderbird 2.0.0.23 (X11/20091015) MIME-Version: 1.0 To: freebsd-fs@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: GPT boot with ZFS RAIDZ "ZFS: i/o error - all block copies unavailable" 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, 15 Oct 2009 12:28:20 -0000 Hi, I want to ask if there is something new in adding support to gptzfsboot/zfsboot for reading gang-blocks? From Sun's docs: Gang blocks When there is not enough contiguous space to write a complete block, the ZIO pipeline will break the I/O up into smaller 'gang blocks' which can later be assembled transparently to appear as complete blocks. Everything works fine for me, until I rewrite kernel/world after system upgrade to latest one (releng_8). After this am I no longer able to boot from zfs raidz1 pool with following messages: >/ ZFS: i/o error - all block copies unavailable />/ ZFS: can't read MOS />/ ZFS: unexpected object set type lld />/ ZFS: unexpected object set type lld />/ />/ FreeBSD/i386 boot />/ Default: z:/boot/kernel/kernel />/ boot: />/ ZFS: unexpected object set type lld />/ />/ FreeBSD/i386 boot />/ Default: tank:/boot/kernel/kernel />/ boot: // /I presume it's the same issue as talked in june-2009 current mailing list http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008589.html Any success in that matter? Thnx for answer. vaLin From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 12:44:56 2009 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 5BDD7106568D for ; Thu, 15 Oct 2009 12:44:56 +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 2CEE78FC12 for ; Thu, 15 Oct 2009 12:44:56 +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 CE6F546B1A; Thu, 15 Oct 2009 08:44:55 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 1A7F28A01F; Thu, 15 Oct 2009 08:44:55 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 15 Oct 2009 07:41:41 -0400 User-Agent: KMail/1.9.7 References: <6729ad0409e449f8dbda69ecd8feb618.squirrel@webmail.lerctr.org> <20091012134159.8f6e4d66.taku@tackymt.homeip.net> In-Reply-To: <20091012134159.8f6e4d66.taku@tackymt.homeip.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910150741.41569.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 15 Oct 2009 08:44:55 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Taku YAMAMOTO , Larry Rosenman Subject: Re: Scheduler weirdness 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, 15 Oct 2009 12:44:56 -0000 On Monday 12 October 2009 12:41:59 am Taku YAMAMOTO wrote: > On Sun, 11 Oct 2009 17:59:52 -0500 > "Larry Rosenman" wrote: > > > > > Ok, running RELENG_8 from Friday (10/9/2009). > > > > If I have 4 Folding-at-home processes running (they nice themselves) the > > system is slow as a dog. > > Ah, I reminded a local patch regarding SCHED_ULE against niced threads. > Something like this: > > --- sys/kern/sched_ule.c.orig 2009-04-29 12:26:30.000000000 +0900 > +++ sys/kern/sched_ule.c 2009-04-30 08:13:30.951440396 +0900 > @@ -1406,7 +1406,7 @@ sched_priority(struct thread *td) > * score. Negative nice values make it easier for a thread to be > * considered interactive. > */ > - score = imax(0, sched_interact_score(td) - td->td_proc->p_nice); > + score = imax(0, sched_interact_score(td) + td->td_proc->p_nice); > if (score < sched_interact) { > pri = PRI_MIN_REALTIME; > pri += ((PRI_MAX_REALTIME - PRI_MIN_REALTIME) / sched_interact) Thanks, I've committed this after Jeff reviewed it and will MFC it soon. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 12:44:58 2009 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 27684106566B for ; Thu, 15 Oct 2009 12:44:58 +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 EDB638FC1E for ; Thu, 15 Oct 2009 12:44:57 +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 9E53146B03; Thu, 15 Oct 2009 08:44:57 -0400 (EDT) Received: from jhbbsd.hudson-trading.com (unknown [209.249.190.8]) by bigwig.baldwin.cx (Postfix) with ESMTPA id 847038A01B; Thu, 15 Oct 2009 08:44:56 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 15 Oct 2009 07:47:54 -0400 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200910150747.55101.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Thu, 15 Oct 2009 08:44:56 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,RDNS_NONE autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: grarpamp Subject: Re: vmstat -m/-z field parsing 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, 15 Oct 2009 12:44:58 -0000 On Thursday 15 October 2009 2:24:00 am grarpamp wrote: > Some of the 'first' columns in the > output contain spaces which makes > it hard to parse the data out. Unless I'm > missing the reason, I propose they be > changed to underscores '_' as > per the rest of the ouput. Thanks. You can also just not use whitespace for your field separator. For example with awk and sort: vmstat -z | awk -F '[:,]' '/ITEM/ { next } /^$/ { next } // { printf "%s:\t%d\n", $1, $2 * ($4 + $5) }' | sort -t: -k 2 -n (This computes the total size of allocated memory (both used and free items) for a zone and sorts the list so the biggest zones are last.) -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 13:14:38 2009 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 780B6106566B for ; Thu, 15 Oct 2009 13:14:38 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 151058FC15 for ; Thu, 15 Oct 2009 13:14:37 +0000 (UTC) Received: from [192.168.1.4] (adsl-154-199-198.ard.bellsouth.net [72.154.199.198]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n9FDEU3o031872 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 15 Oct 2009 09:14:32 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Radek =?iso-8859-2?Q?Val=E1=B9ek?= In-Reply-To: <4AD710D6.70404@buchlovice.org> References: <4AD710D6.70404@buchlovice.org> Content-Type: multipart/mixed; boundary="=-fMS+j1G984RTPd8ikE1K" Organization: FreeBSD Date: Thu, 15 Oct 2009 08:14:25 -0500 Message-Id: <1255612465.2356.808.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, SPF_SOFTFAIL autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: GPT boot with ZFS RAIDZ "ZFS: i/o error - all block copies unavailable" 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, 15 Oct 2009 13:14:38 -0000 --=-fMS+j1G984RTPd8ikE1K Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 8bit On Thu, 2009-10-15 at 14:08 +0200, Radek Valá¹ek wrote: > Hi, > > I want to ask if there is something new in adding support to > gptzfsboot/zfsboot for reading gang-blocks? I've been thinking of trying to fix this, but haven't really come up with a repeatable way to test it. I might be able to come up with at least a hack to allow booting in the short term, but if you can try this patch so that we can verify that the issue is indeed gang blocks. This doesn't fix anything yet, but it should report when it finds a gang block. I know that it is tricky to test when you can't boot, but if you can apply this patch and reinstall gptzfsboot, it should tell us for sure that gang blocks are the issue. I assume that you have a partition layout something like mine: balrog% gpart show => 34 1953525101 ada0 GPT (932G) 34 128 1 freebsd-boot (64K) 162 8388608 2 freebsd-swap (4.0G) 8388770 1945136365 3 freebsd-zfs (928G) If so, all you should need to do is get this built and then: #gpart bootcode -p /boot/gptzfsboot -i 1 ada0 substituting appropriate partition index and device info obviously. robert. > From Sun's docs: > > Gang blocks > > When there is not enough contiguous space to write a complete block, the ZIO > pipeline will break the I/O up into smaller 'gang blocks' which can later be > assembled transparently to appear as complete blocks. > > Everything works fine for me, until I rewrite kernel/world after system > upgrade to latest one (releng_8). After this am I no longer able to boot > from zfs raidz1 pool with following messages: > > >/ ZFS: i/o error - all block copies unavailable > />/ ZFS: can't read MOS > />/ ZFS: unexpected object set type lld > />/ ZFS: unexpected object set type lld > />/ > />/ FreeBSD/i386 boot > />/ Default: z:/boot/kernel/kernel > />/ boot: > />/ ZFS: unexpected object set type lld > />/ > />/ FreeBSD/i386 boot > />/ Default: tank:/boot/kernel/kernel > />/ boot: > // > /I presume it's the same issue as talked in june-2009 current mailing > list > http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008589.html > > Any success in that matter? > > Thnx for answer. > > vaLin > _______________________________________________ > 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" -- Robert Noland FreeBSD --=-fMS+j1G984RTPd8ikE1K Content-Disposition: attachment; filename="zfs-report-gb.patch" Content-Type: text/x-patch; name="zfs-report-gb.patch"; charset="us-ascii" Content-Transfer-Encoding: 7bit diff --git a/sys/boot/zfs/zfsimpl.c b/sys/boot/zfs/zfsimpl.c index ff567a4..a2893bf 100644 --- a/sys/boot/zfs/zfsimpl.c +++ b/sys/boot/zfs/zfsimpl.c @@ -920,6 +920,11 @@ zio_read(spa_t *spa, const blkptr_t *bp, void *buf) if (!dva->dva_word[0] && !dva->dva_word[1]) continue; + if (DVA_GET_GANG(dva)) { + printf("ZFS: i/o error - gang block unimplemented!\n"); + continue; + } + vdevid = DVA_GET_VDEV(dva); offset = DVA_GET_OFFSET(dva); STAILQ_FOREACH(vdev, &spa->spa_vdevs, v_childlink) --=-fMS+j1G984RTPd8ikE1K-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 13:41:18 2009 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 9150910656C1; Thu, 15 Oct 2009 13:41:18 +0000 (UTC) (envelope-from jiashiun@gmail.com) Received: from mail-px0-f186.google.com (mail-px0-f186.google.com [209.85.216.186]) by mx1.freebsd.org (Postfix) with ESMTP id 58A988FC2B; Thu, 15 Oct 2009 13:41:18 +0000 (UTC) Received: by pxi16 with SMTP id 16so54340pxi.3 for ; Thu, 15 Oct 2009 06:41:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:cc:content-type; bh=gLBl2L3uA7Vozt1a7VXXNpGR6E89IFB+DB7maJOSp8I=; b=EhWjA6cmkrTXwcRYsGK/mZy/n2wDzU4vzigzNDPfgyq+TfOHR6qGI2EJ/nEC2eSXsy vWhCgvLHS4pufsCRXr0d1S92QRjhsFZHNpFFxt1iwVdDXLd8fQcDg8mbkdl1wS2vqT+Z rbdjAFx2mWolmGghnRgWdzZShU80J83nrwWQs= 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; b=MIOJibQ8N2ZPZNzz5cHmpM8PfnPFy2lyfoAf3cvKMpfw3SfSI4DJp1Fn+KhyeX0Owr CzvXERcWxRKM3lqPDRh2L0AweZ1NZxTbp6e+gMFehxFp13oKM9Jm/OS06J4Y7IfAJP7L ZI/hbDNk8bbTpExULArY365N6RyAquOgKrEII= MIME-Version: 1.0 Received: by 10.143.84.2 with SMTP id m2mr4927wfl.4.1255612625071; Thu, 15 Oct 2009 06:17:05 -0700 (PDT) In-Reply-To: <20090731081723.GB54196@mech-cluster241.men.bris.ac.uk> References: <20090730171820.GA1043@mech-cluster241.men.bris.ac.uk> <20090730172701.GA1043@mech-cluster241.men.bris.ac.uk> <20090731081723.GB54196@mech-cluster241.men.bris.ac.uk> From: Jia-Shiun Li Date: Thu, 15 Oct 2009 21:16:45 +0800 Message-ID: <1d6d20bc0910150616k271e0a7ex4ce2bfd42c3e2ff3@mail.gmail.com> To: Anton Shterenlikht Content-Type: text/plain; charset=UTF-8 Cc: gecko@freebsd.org, Marcel Moolenaar , freebsd-ia64@freebsd.org, freebsd-current@freebsd.org Subject: Re: firefox-2 causes panic on ia64 8.0-beta2 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, 15 Oct 2009 13:41:18 -0000 On Fri, Jul 31, 2009 at 4:17 PM, Anton Shterenlikht wrote: > > good?? or dear me.. all I ever wanted is to use FBSD, I'm a mechanical > engineer, nuts and bolts, etc. Look what I've dragged myself into.. > > Seriously though, are there any SSL/https web browsers known to > work on ia64? Does firefox3 or firefox35 work for you? Jia-Shiun. From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 14:06:43 2009 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 D08FE106566B for ; Thu, 15 Oct 2009 14:06:43 +0000 (UTC) (envelope-from ticso@cicely7.cicely.de) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) by mx1.freebsd.org (Postfix) with ESMTP id 3C0EC8FC12 for ; Thu, 15 Oct 2009 14:06:42 +0000 (UTC) Received: from cicely5.cicely.de ([10.1.1.7]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id n9FE6c3A042189 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 15 Oct 2009 16:06:39 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by cicely5.cicely.de (8.14.2/8.14.2) with ESMTP id n9FE6ZDf030195 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 15 Oct 2009 16:06:35 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id n9FE6Z9x064590; Thu, 15 Oct 2009 16:06:35 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id n9FE6Xcv064589; Thu, 15 Oct 2009 16:06:33 +0200 (CEST) (envelope-from ticso) Date: Thu, 15 Oct 2009 16:06:33 +0200 From: Bernd Walter To: Hans Petter Selasky Message-ID: <20091015140633.GD62588@cicely7.cicely.de> References: <200910141945.09311.hselasky@c2i.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200910141945.09311.hselasky@c2i.net> X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED=-1.8, BAYES_00=-2.599 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on spamd.cicely.de Cc: Warren Block , freebsd-current@freebsd.org Subject: Re: Why does hal think my USB devices are fixed? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ticso@cicely.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 14:06:43 -0000 On Wed, Oct 14, 2009 at 07:45:08PM +0200, Hans Petter Selasky wrote: > On Wednesday 14 October 2009 19:04:07 Warren Block wrote: > > Fixed as opposed to removable. hal used to see these USB > > devices--USB memory sticks, memory cards in a reader--as removable > > devices. Which they are. > > > > Same computer, same config that used to automount these devices as > > removable, but now FreeBSD 8.0-RC1 and hal says they are fixed devices: > > > > org.freedesktop.hal.storage.mount-fixed no <-- (action, result). > > > > Is this be due to the USB system? > > Hi Warren, > > The fixed/removable information is transferred to the PC using a SCSI INQUIRY > command. What the device reports or what the CAM layer reports to HAL is not > up to the USB stack. This is a different thing. SCSI inquiry tells about removeable media. Just some examples: USB flash sticks are removeable drives with unremoveable media. USB harddisks are removeable drives with unremoveable media. USB card readers are removeable drives with removeable media. (Plain old) Floppy drives are unremoveable drives with removeable media. SCSI harddisks are unremoveable drives with unremoveable media. But even this is not correct anymore. SATA and SCSI devices can be external and powered off at any time. In the result this means that every drive might be removeable today. > The most significant bit of second byte of the INQUIRY response decides if the > medium is removable or not. > > See: ustorage_fs_inquiry() in src/sys/dev/usb/storage/ustorage_fs.c > > --HPS > > _______________________________________________ > 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" -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 15:57:39 2009 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 CB80D106566B; Thu, 15 Oct 2009 15:57:39 +0000 (UTC) (envelope-from mexas@bristol.ac.uk) Received: from dirj.bris.ac.uk (dirj.bris.ac.uk [137.222.10.78]) by mx1.freebsd.org (Postfix) with ESMTP id 828958FC13; Thu, 15 Oct 2009 15:57:39 +0000 (UTC) Received: from seis.bris.ac.uk ([137.222.10.93]) by dirj.bris.ac.uk with esmtp (Exim 4.69) (envelope-from ) id 1MyShp-0007dI-2E; Thu, 15 Oct 2009 16:57:37 +0100 Received: from mech-cluster241.men.bris.ac.uk ([137.222.187.241]) by seis.bris.ac.uk with esmtp (Exim 4.67) (envelope-from ) id 1MyShn-0001T1-Rg; Thu, 15 Oct 2009 16:57:32 +0100 Received: from mech-cluster241.men.bris.ac.uk (localhost [127.0.0.1]) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3) with ESMTP id n9FFvV9o093412; Thu, 15 Oct 2009 16:57:31 +0100 (BST) (envelope-from mexas@bristol.ac.uk) Received: (from mexas@localhost) by mech-cluster241.men.bris.ac.uk (8.14.3/8.14.3/Submit) id n9FFvVrc093411; Thu, 15 Oct 2009 16:57:31 +0100 (BST) (envelope-from mexas@bristol.ac.uk) X-Authentication-Warning: mech-cluster241.men.bris.ac.uk: mexas set sender to mexas@bristol.ac.uk using -f Date: Thu, 15 Oct 2009 16:57:31 +0100 From: Anton Shterenlikht To: Jia-Shiun Li Message-ID: <20091015155731.GA91743@mech-cluster241.men.bris.ac.uk> References: <20090730171820.GA1043@mech-cluster241.men.bris.ac.uk> <20090730172701.GA1043@mech-cluster241.men.bris.ac.uk> <20090731081723.GB54196@mech-cluster241.men.bris.ac.uk> <1d6d20bc0910150616k271e0a7ex4ce2bfd42c3e2ff3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1d6d20bc0910150616k271e0a7ex4ce2bfd42c3e2ff3@mail.gmail.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-Spam-Score: -1.5 X-Spam-Level: - Cc: gecko@freebsd.org, Marcel Moolenaar , Anton Shterenlikht , freebsd-ia64@freebsd.org, freebsd-current@freebsd.org Subject: Re: firefox-2 causes panic on ia64 8.0-beta2 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, 15 Oct 2009 15:57:39 -0000 On Thu, Oct 15, 2009 at 09:16:45PM +0800, Jia-Shiun Li wrote: > On Fri, Jul 31, 2009 at 4:17 PM, Anton Shterenlikht wrote: > > > > good?? or dear me.. all I ever wanted is to use FBSD, I'm a mechanical > > engineer, nuts and bolts, etc. Look what I've dragged myself into.. > > > > Seriously though, are there any SSL/https web browsers known to > > work on ia64? > > Does firefox3 or firefox35 work for you? no, problems with xpcom. It's been submitted as a bug ages ago. At present security/nss doesn't build either, so I cannot get kazehakase either. thank you anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423 From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 17:28:46 2009 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 86B931065670; Thu, 15 Oct 2009 17:28:46 +0000 (UTC) (envelope-from weongyo.jeong@gmail.com) Received: from mail-ew0-f218.google.com (mail-ew0-f218.google.com [209.85.219.218]) by mx1.freebsd.org (Postfix) with ESMTP id 469FA8FC17; Thu, 15 Oct 2009 17:28:44 +0000 (UTC) Received: by ewy18 with SMTP id 18so1036457ewy.43 for ; Thu, 15 Oct 2009 10:28:43 -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=AQT+AoNTnGqwkaISS1lQ/bCgiD4xhRnEIdj1PEpb77Q=; b=AH7ZLHgjgLMDEph6Yz4ZWxdzGejStUIfb/pTukPnDN9k7fJipiDoXHehCgzNxDqo2j ugg0Kd8BBGciY4qdOfDWi58gtDmIGddCNF8zTjuCWnPH2iAdVh3lOyAPiHAJzxb24RLA e0S8ROLgkqbWaMWIgtkLiCRExtAHVM+retRzs= 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=XCAz07CDuFOZzfgvchr37/ixkBCANXSr+py3WUOnhpmiMEOrnege13PjiESJRWXCLE nvmzp2pShZ/YACWO+5woAv3rfr5SEebiXQ0vYigS7R0j4U63LjJw9Vi2dR7L5/30gD4j ugR6fmDJ8nBwXtkpD5HGxLmRaP5fCQQ4Qa7n4= Received: by 10.216.86.206 with SMTP id w56mr100581wee.1.1255627723407; Thu, 15 Oct 2009 10:28:43 -0700 (PDT) Received: from weongyo ([174.35.1.224]) by mx.google.com with ESMTPS id m5sm627705gve.26.2009.10.15.10.28.39 (version=SSLv3 cipher=RC4-MD5); Thu, 15 Oct 2009 10:28:41 -0700 (PDT) Received: by weongyo (sSMTP sendmail emulation); Thu, 15 Oct 2009 10:29:14 -0700 From: Weongyo Jeong Date: Thu, 15 Oct 2009 10:29:14 -0700 To: Gavin Atkinson Message-ID: <20091015172914.GF67082@weongyo> Mail-Followup-To: Gavin Atkinson , bsduser , freebsd-current@freebsd.org References: <86051.1254232666@critter.freebsd.dk> <20091013174201.GC67082@weongyo> <86iqei7tgq.fsf@jodie.vectavision.com> <20091014201059.GE67082@weongyo> <20091014230715.E96894@ury.york.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091014230715.E96894@ury.york.ac.uk> User-Agent: Mutt/1.4.2.3i Organization: CDNetworks. X-Operation-Sytem: FreeBSD Cc: bsduser , freebsd-current@freebsd.org Subject: Re: if_rum dies on transmit... 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: Thu, 15 Oct 2009 17:28:46 -0000 On Wed, Oct 14, 2009 at 11:08:39PM +0100, Gavin Atkinson wrote: > On Wed, 14 Oct 2009, Weongyo Jeong wrote: > >On Tue, Oct 13, 2009 at 05:41:09PM -0600, bsduser wrote: > >>Weongyo Jeong writes: > >> > >>>On Tue, Sep 29, 2009 at 01:57:46PM +0000, Poul-Henning Kamp wrote: > >>>> > >>>>Has anybody else seen if_rum die when you try to transmit a file over > >>>>a TCP connection ? > >>>> > >>>>If I try to print across the network, upload a file with ftp or anything > >>>>else of that general tenor, if_rum seems to hang the output queue and > >>>>stops transmitting packets. > >>> > >>>Could you please test with attached patch? > >>> > >> > >>I had the same issues with if_rum at least while using WPA and your patch > >>made > >>them go away.... ( although removing and plugging back in does not quite > >>work ) > >> > >># scp INDEX-8* cookie:/usr/ports > >>INDEX-8 100% 19MB 2.1MB/s > >>00:09 > >>INDEX-8.db 100% 34MB 2.4MB/s > >>00:14 > >> > >>before the patch this would just hang. > >> > >>Another quick test using rsync on a bunch of files worked flawless too. > >> > >>usbconfig list: > >> > >>ugen7.2: at usbus7, cfg=0 > >>md=HOST spd=HIGH (480Mbps) pwr=ON > >> > >>The adapter is a WUSB54GC and yes, you made my day :-) > > > >Patched at r198098. Thank you for testing! > > Many thanks for this! > > Do you know if this patch is likely to fix the panics seen with rum(4) or > is this likely to only fix the TX hangs? AFAIK this patch only fixes TX hangs. I didn't see PRs yet related with the panics but I think it could affect user's panic a little bit. regards. Weongyo Jeong From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 18:33:39 2009 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 CE30E1065672 for ; Thu, 15 Oct 2009 18:33:39 +0000 (UTC) (envelope-from oberman@es.net) Received: from mailgw.es.net (mail1.es.net [IPv6:2001:400:201:1::2]) by mx1.freebsd.org (Postfix) with ESMTP id B375E8FC26 for ; Thu, 15 Oct 2009 18:33:39 +0000 (UTC) Received: from ptavv.es.net (ptavv.es.net [IPv6:2001:400:910::29]) by mailgw.es.net (8.14.3/8.14.3) with ESMTP id n9FIXcNv021039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 15 Oct 2009 11:33:38 -0700 Received: from ptavv.es.net (ptavv.es.net [127.0.0.1]) by ptavv.es.net (Tachyon Server) with ESMTP id 37FBB1CC44; Thu, 15 Oct 2009 11:33:38 -0700 (PDT) To: Christian Schmidt In-reply-to: Your message of "Thu, 15 Oct 2009 11:35:11 +0200." <309b65830910150235w59857e83r23887193c36561f0@mail.gmail.com> Date: Thu, 15 Oct 2009 11:33:38 -0700 From: "Kevin Oberman" Message-Id: <20091015183338.37FBB1CC44@ptavv.es.net> X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5, 1.2.40, 4.0.166 definitions=2009-10-15_12:2009-09-29, 2009-10-15, 2009-10-15 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=5.0.0-0908210000 definitions=main-0910150078 Cc: john hood , freebsd-current@freebsd.org Subject: Re: Boot issues with a Dell Inspiron 530 and 8.0 RC1 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, 15 Oct 2009 18:33:40 -0000 > From: Christian Schmidt > Date: Thu, 15 Oct 2009 11:35:11 +0200 > Sender: owner-freebsd-current@freebsd.org > > On Tue, Oct 13, 2009 at 18:12, Christian Schmidt wrote: > > On Mon, Oct 12, 2009 at 07:21, john hood wrote: > >> Christian Schmidt wrote: > > [...] > >>> I am seeing a strange issue with my Dell Inspiron 530 with 8.0 RC1-p1 > >>> at around 50-75% percent of all boots. It all boils down to GENERIC > >>> throwing the following: > >>> > >>> AP #1 (PHY #1) failed! > >>> panic y/n? [y] panic: bye-bye > >>> cpuid = 0 > > [...] > >> We have 3 of these machines. > >> > >> In my experience, keyboard activity triggers the problem.  If I boot the > >> machine without any keyboard presses/releases between the time the loader > >> starts the kernel and some time later, definitely by the time the USB > >> keyboard driver attaches, then I don't get this problem.  This includes any > >> key-up (and maybe key repeat) events you may generate after typing a key at > >> the boot menu, or after typing enter at the OK prompt, or pressing a key to > >> bypass the autoboot timeout that counts down by seconds. > >> > >> If you let the machine start from cold without touching the keyboard, what > >> happens? > > > > That is a very interesting point you are making. Indeed, it never > > occured to me that I am usually hammering down on F1 and 1 to boot > > faster (yeah yeah, I know ;-)). I let the machine boot through without > > that a couple of times and it seemed to have worked for about a 100% > > of those cases. I will keep testing but I think we have a hot > > contender. :-) > > > > Okay, after testing that for a couple of days I can confirm that it > never-ever happens when I leave the keyboard alone during the > boot-phase. As a workaround, I can live with not touching the > keyboard. Nethertheless, this seems to be a bug that deserves fixing, > isn't it? FWIW, I've seen this at least as far back as V5 and I think I have seen it on V4. I have no idea if it happened in V3. That was too long ago. IT would be nice to see this fixed, but I think we have all lived with it for a long time and most have either learned not to type stuff before the device probes have ended or they have never happened to trigger it. In my case, it seems like it is OK to type after the keyboard probe is completed. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634 Key fingerprint:059B 2DDF 031C 9BA3 14A4 EADA 927D EBB3 987B 3751 From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 19:04:00 2009 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 51CAD1065672; Thu, 15 Oct 2009 19:04:00 +0000 (UTC) (envelope-from rnoland@FreeBSD.org) Received: from gizmo.2hip.net (gizmo.2hip.net [64.74.207.195]) by mx1.freebsd.org (Postfix) with ESMTP id 1895D8FC20; Thu, 15 Oct 2009 19:04:00 +0000 (UTC) Received: from [192.168.1.4] (adsl-154-199-198.ard.bellsouth.net [72.154.199.198]) (authenticated bits=0) by gizmo.2hip.net (8.14.3/8.14.3) with ESMTP id n9FJ3uDU033665 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 15 Oct 2009 15:03:56 -0400 (EDT) (envelope-from rnoland@FreeBSD.org) From: Robert Noland To: Radek =?iso-8859-2?Q?Val=E1=B9ek?= In-Reply-To: <4AD710D6.70404@buchlovice.org> References: <4AD710D6.70404@buchlovice.org> Content-Type: multipart/mixed; boundary="=-a2tiU1GGu1eRIpNGphrs" Organization: FreeBSD Date: Thu, 15 Oct 2009 14:03:50 -0500 Message-Id: <1255633430.2175.12.camel@balrog.2hip.net> Mime-Version: 1.0 X-Mailer: Evolution 2.26.3 FreeBSD GNOME Team Port X-Spam-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00, RCVD_IN_SORBS_DUL, RDNS_DYNAMIC, SPF_SOFTFAIL autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on gizmo.2hip.net Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: GPT boot with ZFS RAIDZ "ZFS: i/o error - all block copies unavailable" 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, 15 Oct 2009 19:04:00 -0000 --=-a2tiU1GGu1eRIpNGphrs Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 8bit On Thu, 2009-10-15 at 14:08 +0200, Radek Valá¹ek wrote: > Hi, > > I want to ask if there is something new in adding support to > gptzfsboot/zfsboot for reading gang-blocks? Ok, I can't figure out any way to test this... beyond the fact that it builds and doesn't break my currently working setup. Can you give this a try? It should still report if it finds gang blocks, but hopefully now will read them as well. robert. > From Sun's docs: > > Gang blocks > > When there is not enough contiguous space to write a complete block, the ZIO > pipeline will break the I/O up into smaller 'gang blocks' which can later be > assembled transparently to appear as complete blocks. > > Everything works fine for me, until I rewrite kernel/world after system > upgrade to latest one (releng_8). After this am I no longer able to boot > from zfs raidz1 pool with following messages: > > >/ ZFS: i/o error - all block copies unavailable > />/ ZFS: can't read MOS > />/ ZFS: unexpected object set type lld > />/ ZFS: unexpected object set type lld > />/ > />/ FreeBSD/i386 boot > />/ Default: z:/boot/kernel/kernel > />/ boot: > />/ ZFS: unexpected object set type lld > />/ > />/ FreeBSD/i386 boot > />/ Default: tank:/boot/kernel/kernel > />/ boot: > // > /I presume it's the same issue as talked in june-2009 current mailing > list > http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008589.html > > Any success in that matter? > > Thnx for answer. > > vaLin > _______________________________________________ > 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" -- Robert Noland FreeBSD --=-a2tiU1GGu1eRIpNGphrs Content-Disposition: attachment; filename="zfs-gang-block.patch" Content-Type: text/x-patch; name="zfs-gang-block.patch"; charset="us-ascii" Content-Transfer-Encoding: 7bit diff --git a/sys/boot/zfs/zfsimpl.c b/sys/boot/zfs/zfsimpl.c index ff567a4..6a18b44 100644 --- a/sys/boot/zfs/zfsimpl.c +++ b/sys/boot/zfs/zfsimpl.c @@ -53,6 +53,8 @@ static char *zfs_temp_buf, *zfs_temp_end, *zfs_temp_ptr; #define TEMP_SIZE (1*SPA_MAXBLOCKSIZE) +static int zio_read(spa_t *spa, const blkptr_t *bp, void *buf); + static void zfs_init(void) { @@ -897,6 +899,33 @@ ilog2(int n) } static int +zio_read_gang(spa_t *spa, const blkptr_t *bp, const dva_t *dva, void *buf) +{ + zio_gbh_phys_t zio_gb; + vdev_t *vdev; + int vdevid; + off_t offset; + int i; + + vdevid = DVA_GET_VDEV(dva); + offset = DVA_GET_OFFSET(dva); + STAILQ_FOREACH(vdev, &spa->spa_vdevs, v_childlink) + if (vdev->v_id == vdevid) + break; + if (!vdev || !vdev->v_read) + return (EIO); + if (vdev->v_read(vdev, bp, &zio_gb, offset, SPA_GANGBLOCKSIZE)) + return (EIO); + + for (i = 0; i < SPA_GBH_NBLKPTRS; i++) { + if (zio_read(spa, &zio_gb.zg_blkptr[i], buf)) + return (EIO); + } + + return (0); +} + +static int zio_read(spa_t *spa, const blkptr_t *bp, void *buf) { int cpfunc = BP_GET_COMPRESS(bp); @@ -920,20 +949,26 @@ zio_read(spa_t *spa, const blkptr_t *bp, void *buf) if (!dva->dva_word[0] && !dva->dva_word[1]) continue; - vdevid = DVA_GET_VDEV(dva); - offset = DVA_GET_OFFSET(dva); - STAILQ_FOREACH(vdev, &spa->spa_vdevs, v_childlink) - if (vdev->v_id == vdevid) - break; - if (!vdev || !vdev->v_read) - continue; - if (vdev->v_read(vdev, bp, pbuf, offset, psize)) - continue; + if (DVA_GET_GANG(dva)) { + printf("ZFS: gang block detected!\n"); + if (zio_read_gang(spa, bp, dva, buf)) + return (EIO); + } else { + vdevid = DVA_GET_VDEV(dva); + offset = DVA_GET_OFFSET(dva); + STAILQ_FOREACH(vdev, &spa->spa_vdevs, v_childlink) + if (vdev->v_id == vdevid) + break; + if (!vdev || !vdev->v_read) + continue; + if (vdev->v_read(vdev, bp, pbuf, offset, psize)) + continue; - if (cpfunc != ZIO_COMPRESS_OFF) { - if (zio_decompress_data(cpfunc, pbuf, psize, - buf, lsize)) - return (EIO); + if (cpfunc != ZIO_COMPRESS_OFF) { + if (zio_decompress_data(cpfunc, pbuf, psize, + buf, lsize)) + return (EIO); + } } return (0); diff --git a/sys/cddl/boot/zfs/zfsimpl.h b/sys/cddl/boot/zfs/zfsimpl.h index a0b7b72..688bb5c 100644 --- a/sys/cddl/boot/zfs/zfsimpl.h +++ b/sys/cddl/boot/zfs/zfsimpl.h @@ -374,6 +374,24 @@ typedef struct vdev_label { #define VDEV_LABEL_END_SIZE (2 * sizeof (vdev_label_t)) #define VDEV_LABELS 4 +/* + * Gang block headers are self-checksumming and contain an array + * of block pointers. + */ +#define SPA_GANGBLOCKSIZE SPA_MINBLOCKSIZE +#define SPA_GBH_NBLKPTRS ((SPA_GANGBLOCKSIZE - \ + sizeof (zio_block_tail_t)) / sizeof (blkptr_t)) +#define SPA_GBH_FILLER ((SPA_GANGBLOCKSIZE - \ + sizeof (zio_block_tail_t) - \ + (SPA_GBH_NBLKPTRS * sizeof (blkptr_t))) /\ + sizeof (uint64_t)) + +typedef struct zio_gbh { + blkptr_t zg_blkptr[SPA_GBH_NBLKPTRS]; + uint64_t zg_filler[SPA_GBH_FILLER]; + zio_block_tail_t zg_tail; +} zio_gbh_phys_t; + enum zio_checksum { ZIO_CHECKSUM_INHERIT = 0, ZIO_CHECKSUM_ON, --=-a2tiU1GGu1eRIpNGphrs-- From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 19:37:35 2009 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 A53BE106566C; Thu, 15 Oct 2009 19:37:35 +0000 (UTC) (envelope-from valin@buchlovice.org) Received: from smtp-sfn.sitkom.cz (smtp-sfn.sitkom.cz [88.146.175.4]) by mx1.freebsd.org (Postfix) with ESMTP id 63EEE8FC08; Thu, 15 Oct 2009 19:37:35 +0000 (UTC) Received: from osiris.buchlovice.sfn (osiris.buchlovice.sfn [10.6.193.10]) by smtp-sfn.sitkom.cz (Postfix) with ESMTP id 4F99D1FA69D; Thu, 15 Oct 2009 21:37:34 +0200 (CEST) Message-ID: <4AD779FC.1070204@buchlovice.org> Date: Thu, 15 Oct 2009 21:37:32 +0200 From: =?ISO-8859-2?Q?Radek_Val=E1=B9ek?= User-Agent: Thunderbird 2.0.0.23 (X11/20091015) MIME-Version: 1.0 To: Robert Noland References: <4AD710D6.70404@buchlovice.org> <1255633430.2175.12.camel@balrog.2hip.net> In-Reply-To: <1255633430.2175.12.camel@balrog.2hip.net> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit Cc: freebsd-fs@freebsd.org, freebsd-current@freebsd.org Subject: Re: GPT boot with ZFS RAIDZ "ZFS: i/o error - all block copies unavailable" 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, 15 Oct 2009 19:37:35 -0000 Robert Noland napsal(a): > On Thu, 2009-10-15 at 14:08 +0200, Radek Valá¹ek wrote: > >> Hi, >> >> I want to ask if there is something new in adding support to >> gptzfsboot/zfsboot for reading gang-blocks? >> > > Ok, I can't figure out any way to test this... beyond the fact that it > builds and doesn't break my currently working setup. Can you give this > a try? It should still report if it finds gang blocks, but hopefully > now will read them as well. > > robert. > > Big thanks for the patches Robert, I will definitely test them as soon as possible (tomorrow) and report the results immediately to list. I can repeat this issue probably at any time (up to cca 30 times tested with the same result), so don't bother about the broken booting, I'm prepared for it... vaLin >> From Sun's docs: >> >> Gang blocks >> >> When there is not enough contiguous space to write a complete block, the ZIO >> pipeline will break the I/O up into smaller 'gang blocks' which can later be >> assembled transparently to appear as complete blocks. >> >> Everything works fine for me, until I rewrite kernel/world after system >> upgrade to latest one (releng_8). After this am I no longer able to boot >> from zfs raidz1 pool with following messages: >> >> >/ ZFS: i/o error - all block copies unavailable >> />/ ZFS: can't read MOS >> />/ ZFS: unexpected object set type lld >> />/ ZFS: unexpected object set type lld >> />/ >> />/ FreeBSD/i386 boot >> />/ Default: z:/boot/kernel/kernel >> />/ boot: >> />/ ZFS: unexpected object set type lld >> />/ >> />/ FreeBSD/i386 boot >> />/ Default: tank:/boot/kernel/kernel >> />/ boot: >> // >> /I presume it's the same issue as talked in june-2009 current mailing >> list >> http://lists.freebsd.org/pipermail/freebsd-current/2009-June/008589.html >> >> Any success in that matter? >> >> Thnx for answer. >> >> vaLin >> _______________________________________________ >> 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" >> From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 19:57:49 2009 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 064B9106566B for ; Thu, 15 Oct 2009 19:57:49 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id BBB0E8FC1D for ; Thu, 15 Oct 2009 19:57:48 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id n9FJvjgg079101; Thu, 15 Oct 2009 13:57:45 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id n9FJvjVU079098; Thu, 15 Oct 2009 13:57:45 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 15 Oct 2009 13:57:45 -0600 (MDT) From: Warren Block To: Kevin Oberman In-Reply-To: <20091015043422.6B42D1CC37@ptavv.es.net> Message-ID: References: <20091015043422.6B42D1CC37@ptavv.es.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (wonkity.com [127.0.0.1]); Thu, 15 Oct 2009 13:57:45 -0600 (MDT) Cc: current@freebsd.org Subject: Re: Why does hal think my USB devices are fixed? 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, 15 Oct 2009 19:57:49 -0000 On Wed, 14 Oct 2009, Kevin Oberman wrote: >> Date: Wed, 14 Oct 2009 14:38:47 -0600 (MDT) >> From: Warren Block >> Then set some options for the card reader: >> >> 20-check-media.fdi : >> >> >> >> >> >> >> true >> true >> >> >> My extraneous line removed from the XML above... >> hal still sometimes doesn't notice new cards being connected, and the >> card reader's USB cable has to be reconnected. But at this point, it's >> at least as good as it was under 7-STABLE. > > Doing something to access the device seems to cause it to be "noticed". > I use 'fsck -p' on the device, but I suspect dd(1) or most anything else > that touches the device will do it. This Sandisk reader appears as two devices. The CompactFlash slot is one device (da0) and the SD/MMC/MS/clock radio slot is another (da1). Using the alternate slot seems to be when it loses track. For example, use an MMC card (da1s1), works fine. Load a CF, and /dev still only has da0, da1, and da1s1. No da1s1 appears. fsck -p /dev/da0 gives 'fsck: Could not determine filesystem type', and various other attempts like 'true > /dev/da0' don't wake it up. But 'usbconfig -u 3 -a 3 reset' works every time, and is less messy than pulling the cable. -Warren Block * Rapid City, South Dakota USA From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 19:48:01 2009 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 8EC251065676 for ; Thu, 15 Oct 2009 19:48:01 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from ey-out-1920.google.com (ey-out-1920.google.com [74.125.78.145]) by mx1.freebsd.org (Postfix) with ESMTP id F3F048FC19 for ; Thu, 15 Oct 2009 19:48:00 +0000 (UTC) Received: by ey-out-1920.google.com with SMTP id 3so266073eyh.18 for ; Thu, 15 Oct 2009 12:48:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=LrUsAbH8cXTZm3YCGW9WGfCYaClIaMgFQPGOLPPMmKg=; b=JpWt/TXRSeo6Fvfj59tO2k4V0Bn+xLNLUycR8bq4+wUYT4WVYfPL3e2vLwBHMOiLza m/PhJw9ZhInngQyMFQz1+m1U9vF+IHHdU+m/q4N9FB9ZJgttjV4rSCrOMKUqR62lhFRq PfqoTtyNmg/J+3TsfQX/TwAaOW9n8gPvkpYhc= 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=OsqN7ODNezLvsvwfZEHkUjIKs2o7MJAMYW3cEvzo2hWe8wIPoM4BbinsYvrA2MyxsY llIdEqTzmfLzMFb97Q1OYkx9kSScmksobE7ne7YnemWgJfAGHZeHx4BwDe+2aB2bzKYf JddS6gOy6cOPhOuSs2qgTsYb7ZuhDW5YHo0UQ= MIME-Version: 1.0 Received: by 10.211.130.15 with SMTP id h15mr9629622ebn.82.1255636079895; Thu, 15 Oct 2009 12:47:59 -0700 (PDT) In-Reply-To: <200910150747.55101.jhb@freebsd.org> References: <200910150747.55101.jhb@freebsd.org> Date: Thu, 15 Oct 2009 15:47:59 -0400 Message-ID: From: grarpamp To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Thu, 15 Oct 2009 20:21:33 +0000 Subject: Re: vmstat -m/-z field parsing 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, 15 Oct 2009 19:48:01 -0000 Sure, it's a workaround for vmstat -z, but not easy for vmstat -m which has no handy colons/commas to key from. Shouldn't stats be easy to parse in order to be useful to many rather than a test of a few users script fu ? :) So why not hunt up, check for potential new collisions to fix and change the strings in a lint run? See below... Thank you for pointing out that I had to do 'size * (used + free)', not just 'used'. And for the fu tips too :) I guess 'free' are not returned to the system for other uses then. Are there detailed docs on what all the fields mean in the various tools... vmstat -z/-m, systat -vm, netstat -m, top, ps. Most docs seem to just list the field names a command line switch will display, instead what sense to make of them. /me, grokking with wild abandon... # sys/vm/uma_core.c: args.name = "UMA Kegs"; args.name = "UMA Zones"; struct uma_bucket_zone bucket_zones[] = { { NULL, "16 Bucket", 16 }, { NULL, "32 Bucket", 32 }, { NULL, "64 Bucket", 64 }, { NULL, "128 Bucket", 128 }, { NULL, NULL, 0} }; # find -s sys -type f | xargs egrep MALLOC_DEFINE | sed -E 's/,[^,]{1,}$//' | egrep '".* .*"' sys/arm/xscale/pxa/pxa_smi.c:MALLOC_DEFINE(M_PXASMI, "PXA SMI" sys/arm/xscale/pxa/pxa_space.c:MALLOC_DEFINE(M_PXATAG, "PXA bus_space tags" sys/cam/cam_periph.c:MALLOC_DEFINE(M_CAMPERIPH, "CAM periph" sys/cam/cam_queue.c:MALLOC_DEFINE(M_CAMQ, "CAM queue" sys/cam/cam_queue.c:MALLOC_DEFINE(M_CAMDEVQ, "CAM dev queue" sys/cam/cam_queue.c:MALLOC_DEFINE(M_CAMCCBQ, "CAM ccb queue" sys/cam/cam_sim.c:MALLOC_DEFINE(M_CAMSIM, "CAM SIM" sys/cam/cam_xpt.c:MALLOC_DEFINE(M_CAMXPT, "CAM XPT" sys/cam/scsi/scsi_low.c:MALLOC_DEFINE(M_SCSILOW, "SCSI low" sys/cam/scsi/scsi_sa.c:MALLOC_DEFINE(M_SCSISA, "SCSI sa" sys/cam/scsi/scsi_ses.c:MALLOC_DEFINE(M_SCSISES, "SCSI SES" sys/cam/scsi/scsi_targ_bh.c:MALLOC_DEFINE(M_SCSIBH, "SCSI bh" sys/compat/linux/linux_futex.c:MALLOC_DEFINE(M_FUTEX_WP, "futex wp" sys/dev/ahci/ahci.c:MALLOC_DEFINE(M_AHCI, "AHCI driver" sys/dev/siis/siis.c:MALLOC_DEFINE(M_SIIS, "SIIS driver" sys/dev/sound/midi/midi.c:MALLOC_DEFINE(M_MIDI, "midi buffers" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSRVCACHE, "NFSD srvcache" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSDCLIENT, "NFSD V4client" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSDSTATE, "NFSD V4state", "NFSD V4 State (Openowner, Open, Lockowner sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSDLOCK, "NFSD V4lock" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSDLOCKFILE, "NFSD lckfile" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSSTRING, "NFSD string" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSUSERGROUP, "NFSD usrgroup" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSDREQ, "NFS req" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSFH, "NFS fh" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSCLOWNER, "NFSCL owner" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSCLOPEN, "NFSCL open" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSCLDELEG, "NFSCL deleg" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSCLCLIENT, "NFSCL client" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSCLLOCKOWNER, "NFSCL lckown" sys/fs/nfs/nfs_commonport.c:MALLOC_DEFINE(M_NEWNFSCLLOCK, "NFSCL lck" sys/fs/tmpfs/tmpfs_vfsops.c:MALLOC_DEFINE(M_TMPFSMNT, "tmpfs mount" sys/fs/tmpfs/tmpfs_vfsops.c:MALLOC_DEFINE(M_TMPFSNAME, "tmpfs name" sys/fs/unionfs/union_subr.c:static MALLOC_DEFINE(M_UNIONFSHASH, "UNIONFS hash" sys/fs/unionfs/union_subr.c:MALLOC_DEFINE(M_UNIONFSNODE, "UNIONFS node" sys/fs/unionfs/union_subr.c:MALLOC_DEFINE(M_UNIONFSPATH, "UNIONFS path" sys/fs/unionfs/union_vfsops.c:static MALLOC_DEFINE(M_UNIONFSMNT, "UNIONFS mount" sys/geom/eli/g_eli.c:MALLOC_DEFINE(M_ELI, "eli data" sys/gnu/fs/xfs/FreeBSD/xfs_mountops.c:MALLOC_DEFINE(M_XFSNODE, "XFS node" sys/kern/kern_cons.c:static MALLOC_DEFINE(M_TTYCONS, "tty console" sys/kern/kern_fail.c:MALLOC_DEFINE(M_FAIL_POINT, "Fail Points" sys/kern/subr_bus.c:static MALLOC_DEFINE(M_BUS_SC, "bus-sc", "Bus data structures sys/nfsserver/nfs_fha.c:static MALLOC_DEFINE(M_NFS_FHA, "NFS FHA" # find -s sys -type f | xargs egrep uma_zcreate | sed 's/,.*$//' | egrep '".* .*"' sys/arm/arm/pmap.c: pvzone = uma_zcreate("PV ENTRY" sys/arm/arm/pmap.c: l2zone = uma_zcreate("L2 Table" sys/arm/arm/pmap.c: l2table_zone = uma_zcreate("L2 Table" sys/compat/ndis/subr_ntoskrnl.c: mdl_zone = uma_zcreate("Windows MDL" sys/compat/ndis/subr_ntoskrnl.c: iw_zone = uma_zcreate("Windows WorkItem" sys/dev/en/midway.c: sc->map_zone = uma_zcreate("en dma maps" sys/dev/en/midway.c: en_vcc_zone = uma_zcreate("EN vccs" sys/dev/fatm/if_fatm.c: sc->vcc_zone = uma_zcreate("FATM vccs" sys/dev/hatm/if_hatm.c: if ((sc->vcc_zone = uma_zcreate("HE vccs" sys/dev/iscsi/initiator/iscsi.c: printf("iscsi_initiator: uma_zcreate failed"); sys/dev/patm/if_patm_attach.c: if ((sc->vcc_zone = uma_zcreate("PATM vccs" sys/dev/patm/if_patm_attach.c: if ((sc->tx_mapzone = uma_zcreate("PATM tx maps" sys/fs/tmpfs/tmpfs_vfsops.c: tmp->tm_dirent_pool = uma_zcreate("TMPFS dirent" sys/fs/tmpfs/tmpfs_vfsops.c: tmp->tm_node_pool = uma_zcreate("TMPFS node" sys/fs/udf/udf_vfsops.c: udf_zone_node = uma_zcreate("UDF Node zone" sys/fs/udf/udf_vfsops.c: udf_zone_ds = uma_zcreate("UDF Dirstream zone" sys/ia64/ia64/pmap.c: pvzone = uma_zcreate("PV ENTRY" sys/ia64/ia64/pmap.c: ptezone = uma_zcreate("PT ENTRY" sys/kern/kern_umtx.c: umtx_pi_zone = uma_zcreate("umtx pi" sys/kern/vfs_cache.c: cache_zone_small = uma_zcreate("S VFS Cache" sys/kern/vfs_cache.c: cache_zone_large = uma_zcreate("L VFS Cache" sys/mips/mips/pmap.c: pvzone = uma_zcreate("PV ENTRY" sys/netgraph/netflow/netflow.c: priv->zone = uma_zcreate("NetFlow cache" sys/netgraph/ng_base.c: ng_qzone = uma_zcreate("NetGraph items" sys/netgraph/ng_base.c: ng_qdzone = uma_zcreate("NetGraph data items" sys/netinet/ipfw/ip_fw2.c: ipfw_dyn_rule_zone = uma_zcreate("IPFW dynamic rule" sys/powerpc/aim/mmu_oea.c: moea_upvo_zone = uma_zcreate("UPVO entry" sys/powerpc/aim/mmu_oea.c: moea_mpvo_zone = uma_zcreate("MPVO entry" sys/powerpc/aim/mmu_oea64.c: moea64_upvo_zone = uma_zcreate("UPVO entry" sys/powerpc/aim/mmu_oea64.c: moea64_mpvo_zone = uma_zcreate("MPVO entry" sys/powerpc/booke/pmap.c: pvzone = uma_zcreate("PV ENTRY" sys/security/mac/mac_label.c: zone_label = uma_zcreate("MAC labels" sys/sun4v/sun4v/pmap.c: pvzone = uma_zcreate("PV ENTRY" sys/ufs/ffs/ffs_vfsops.c: uma_inode = uma_zcreate("FFS inode" sys/ufs/ffs/ffs_vfsops.c: uma_ufs1 = uma_zcreate("FFS1 dinode" sys/ufs/ffs/ffs_vfsops.c: uma_ufs2 = uma_zcreate("FFS2 dinode" sys/vm/device_pager.c: fakepg_zone = uma_zcreate("DP fakepg" sys/vm/sg_pager.c: fakepg_zone = uma_zcreate("SG fakepg" sys/vm/uma_core.c: slabzone = uma_zcreate("UMA Slabs" sys/vm/uma_core.c: slabrefzone = uma_zcreate("UMA RCntSlabs" sys/vm/uma_core.c: hashzone = uma_zcreate("UMA Hash" sys/vm/vm_map.c: kmapentzone = uma_zcreate("KMAP ENTRY" sys/vm/vm_map.c: mapentzone = uma_zcreate("MAP ENTRY" sys/vm/vm_object.c: obj_zone = uma_zcreate("VM OBJECT" From owner-freebsd-current@FreeBSD.ORG Thu Oct 15 20:24:44 2009 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 DED691065698; Thu, 15 Oct 2009 20:24:43 +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 B99798FC22; Thu, 15 Oct 2009 20:24:43 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9FKOgnQ002773; Thu, 15 Oct 2009 16:24:42 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9FKOgF8002766; Thu, 15 Oct 2009 20:24:42 GMT (envelope-from tinderbox@freebsd.org) Date: Thu, 15 Oct 2009 20:24:42 GMT Message-Id: <200910152024.n9FKOgF8002766@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, 15 Oct 2009 20:24:44 -0000 TB --- 2009-10-15 19:00:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-15 19:00:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2009-10-15 19:00:00 - cleaning the object tree TB --- 2009-10-15 19:00:20 - cvsupping the source tree TB --- 2009-10-15 19:00:20 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2009-10-15 19:00:52 - building world TB --- 2009-10-15 19:00:52 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-15 19:00:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-15 19:00:52 - TARGET=pc98 TB --- 2009-10-15 19:00:52 - TARGET_ARCH=i386 TB --- 2009-10-15 19:00:52 - TZ=UTC TB --- 2009-10-15 19:00:52 - __MAKE_CONF=/dev/null TB --- 2009-10-15 19:00:52 - cd /src TB --- 2009-10-15 19:00:52 - /usr/bin/make -B buildworld >>> World build started on Thu Oct 15 19:00:52 UTC 2009 >>> 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 Oct 15 19:58:52 UTC 2009 TB --- 2009-10-15 19:58:52 - generating LINT kernel config TB --- 2009-10-15 19:58:52 - cd /src/sys/pc98/conf TB --- 2009-10-15 19:58:52 - /usr/bin/make -B LINT TB --- 2009-10-15 19:58:52 - building LINT kernel TB --- 2009-10-15 19:58:52 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-15 19:58:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-15 19:58:52 - TARGET=pc98 TB --- 2009-10-15 19:58:52 - TARGET_ARCH=i386 TB --- 2009-10-15 19:58:52 - TZ=UTC TB --- 2009-10-15 19:58:52 - __MAKE_CONF=/dev/null TB --- 2009-10-15 19:58:52 - cd /src TB --- 2009-10-15 19:58:52 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Thu Oct 15 19:58:52 UTC 2009 >>> 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 Thu Oct 15 20:19:49 UTC 2009 TB --- 2009-10-15 20:19:49 - building GENERIC kernel TB --- 2009-10-15 20:19:49 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-15 20:19:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-15 20:19:49 - TARGET=pc98 TB --- 2009-10-15 20:19:49 - TARGET_ARCH=i386 TB --- 2009-10-15 20:19:49 - TZ=UTC TB --- 2009-10-15 20:19:49 - __MAKE_CONF=/dev/null TB --- 2009-10-15 20:19:49 - cd /src TB --- 2009-10-15 20:19:49 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Thu Oct 15 20:19:49 UTC 2009 >>> 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 nexus.o(.text+0x2d3): In function `nexus_describe_intr': /src/sys/i386/i386/nexus.c:538: undefined reference to `intr_describe' *** Error code 1 Stop in /obj/pc98/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-15 20:24:42 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-15 20:24:42 - ERROR: failed to build GENERIC kernel TB --- 2009-10-15 20:24:42 - 3851.48 user 751.77 system 5082.26 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Fri Oct 16 01:24:54 2009 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 A8CEC106566C for ; Fri, 16 Oct 2009 01:24:54 +0000 (UTC) (envelope-from glen.j.barber@gmail.com) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id 127A48FC12 for ; Fri, 16 Oct 2009 01:24:53 +0000 (UTC) Received: by fxm6 with SMTP id 6so1840910fxm.43 for ; Thu, 15 Oct 2009 18:24:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=z4QOYzWLeJZWk+1iE+mzsYGdgs0iag/zDDgxD97kIQo=; b=mNiGszihaOsuyr/mQnMyFg1iNgP6ppER6K/InubTwFgd+kizFy2Vgicj+IguIR4jJm l5rHUeWBR47w7ZGUguvdLO8ddy2SYJI9UapKxrj89i3jkntICADhTyLe3W6Z5HgiH6/9 I9GSiOeiQ1U5uZ9me3qXPdtlMlX9Rnx4nuqlg= 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:content-transfer-encoding; b=CpUkplPbDF5ML5Y91l+wj05GQoGn+zid+PJb0ChSvPtQJkQ73ueYOb1YvuPwbl5aXo hLkIqCNgoD/xDKjy2p1ycHhKpwEm0rnv7PG8imrB82GwR+kFNFEWDCW10V+Zn7d4vPVu 6Gu77p2SH2Mbf+OXfP6O2LI/D0fHaTPUXyqik= MIME-Version: 1.0 Received: by 10.223.143.15 with SMTP id s15mr138274fau.77.1255656292483; Thu, 15 Oct 2009 18:24:52 -0700 (PDT) In-Reply-To: <20091015172914.GF67082@weongyo> References: <86051.1254232666@critter.freebsd.dk> <20091013174201.GC67082@weongyo> <86iqei7tgq.fsf@jodie.vectavision.com> <20091014201059.GE67082@weongyo> <20091014230715.E96894@ury.york.ac.uk> <20091015172914.GF67082@weongyo> Date: Thu, 15 Oct 2009 21:24:52 -0400 Message-ID: <4ad871310910151824q13842e1en53a3a682f85c1dd8@mail.gmail.com> From: Glen Barber To: Weongyo Jeong , freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: if_rum dies on transmit... 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, 16 Oct 2009 01:24:54 -0000 Hello, On Thu, Oct 15, 2009 at 1:29 PM, Weongyo Jeong wr= ote: [snip] >> Do you know if this patch is likely to fix the panics seen with rum(4) o= r >> is this likely to only fix the TX hangs? > > AFAIK this patch only fixes TX hangs. =A0I didn't see PRs yet related wit= h > the panics but I think it could affect user's panic a little bit. > I applied this patch to -STABLE and it seems to have fixed my panic problems with rum(4). So far, 1+ hour uptime on AC power and 20+ minutes on battery, which is unusual. rum(4) was one of the potential culprits I was trying to isolate. Thank you! FreeBSD pegasus 8.0-RC1 FreeBSD 8.0-RC1 #8 r198161M: Thu Oct 15 20:09:20 EDT 2009 root@pegasus:/usr/obj/usr/src/sys/PEGASUS i386 --=20 Glen Barber From owner-freebsd-current@FreeBSD.ORG Fri Oct 16 03:44:25 2009 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 3EB6C1065670; Fri, 16 Oct 2009 03:44:25 +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 179878FC0A; Fri, 16 Oct 2009 03:44:24 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9G3iOli059376; Thu, 15 Oct 2009 23:44:24 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9G3iOTZ059369; Fri, 16 Oct 2009 03:44:24 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 16 Oct 2009 03:44:24 GMT Message-Id: <200910160344.n9G3iOTZ059369@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: Fri, 16 Oct 2009 03:44:25 -0000 TB --- 2009-10-16 02:20:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-16 02:20:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2009-10-16 02:20:00 - cleaning the object tree TB --- 2009-10-16 02:20:24 - cvsupping the source tree TB --- 2009-10-16 02:20:24 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2009-10-16 02:20:50 - building world TB --- 2009-10-16 02:20:50 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-16 02:20:50 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-16 02:20:50 - TARGET=pc98 TB --- 2009-10-16 02:20:50 - TARGET_ARCH=i386 TB --- 2009-10-16 02:20:50 - TZ=UTC TB --- 2009-10-16 02:20:50 - __MAKE_CONF=/dev/null TB --- 2009-10-16 02:20:50 - cd /src TB --- 2009-10-16 02:20:50 - /usr/bin/make -B buildworld >>> World build started on Fri Oct 16 02:20:50 UTC 2009 >>> 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 Fri Oct 16 03:18:45 UTC 2009 TB --- 2009-10-16 03:18:45 - generating LINT kernel config TB --- 2009-10-16 03:18:45 - cd /src/sys/pc98/conf TB --- 2009-10-16 03:18:45 - /usr/bin/make -B LINT TB --- 2009-10-16 03:18:45 - building LINT kernel TB --- 2009-10-16 03:18:45 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-16 03:18:45 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-16 03:18:45 - TARGET=pc98 TB --- 2009-10-16 03:18:45 - TARGET_ARCH=i386 TB --- 2009-10-16 03:18:45 - TZ=UTC TB --- 2009-10-16 03:18:45 - __MAKE_CONF=/dev/null TB --- 2009-10-16 03:18:45 - cd /src TB --- 2009-10-16 03:18:45 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Fri Oct 16 03:18:45 UTC 2009 >>> 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 Fri Oct 16 03:39:28 UTC 2009 TB --- 2009-10-16 03:39:28 - building GENERIC kernel TB --- 2009-10-16 03:39:28 - MAKEOBJDIRPREFIX=/obj TB --- 2009-10-16 03:39:28 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2009-10-16 03:39:28 - TARGET=pc98 TB --- 2009-10-16 03:39:28 - TARGET_ARCH=i386 TB --- 2009-10-16 03:39:28 - TZ=UTC TB --- 2009-10-16 03:39:28 - __MAKE_CONF=/dev/null TB --- 2009-10-16 03:39:28 - cd /src TB --- 2009-10-16 03:39:28 - /usr/bin/make -B buildkernel KERNCONF=GENERIC >>> Kernel build for GENERIC started on Fri Oct 16 03:39:28 UTC 2009 >>> 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 nexus.o(.text+0x2d3): In function `nexus_describe_intr': /src/sys/i386/i386/nexus.c:538: undefined reference to `intr_describe' *** Error code 1 Stop in /obj/pc98/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2009-10-16 03:44:24 - WARNING: /usr/bin/make returned exit code 1 TB --- 2009-10-16 03:44:24 - ERROR: failed to build GENERIC kernel TB --- 2009-10-16 03:44:24 - 3846.02 user 756.86 system 5063.27 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Fri Oct 16 08:28:21 2009 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 445A1106568D; Fri, 16 Oct 2009 08:28:21 +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 210578FC17; Fri, 16 Oct 2009 08:28:19 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA09373; Fri, 16 Oct 2009 11:28:17 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1MyiAb-0006oi-EE; Fri, 16 Oct 2009 11:28:17 +0300 Message-ID: <4AD82E91.3030703@icyb.net.ua> Date: Fri, 16 Oct 2009 11:28:01 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090823) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <4AD3220B.5030502@icyb.net.ua> <86ws30ikfw.fsf@gmail.com> <4AD45A8D.4070605@icyb.net.ua> <20091014062827.GC1696@garage.freebsd.pl> In-Reply-To: <20091014062827.GC1696@garage.freebsd.pl> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: freebsd-fs@FreeBSD.org, Anonymous , freebsd-current@FreeBSD.org Subject: Re: zfs boot vs loader 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, 16 Oct 2009 08:28:21 -0000 on 14/10/2009 09:28 Pawel Jakub Dawidek said the following: > On Tue, Oct 13, 2009 at 01:46:37PM +0300, Andriy Gapon wrote: >> Thanks to all who replied! >> I think that I figured it out with your help. >> >> 'unload' does indeed unload zpool.cache and the latter is needed for proper zfs >> root mounting. >> 'boot /other/kernel' executes some loader scripts and zpool.cache gets loaded in >> this case (because of the settings in defaults/loader.conf). >> When doing manual 'load xxx' and then just 'boot' no loader scripts are executed >> and zpool.cache does not get loaded. In this case one has to load it manually >> using the suggested 'load -t xxx' approach. > > Could you repeat what you were doing but with vfs.zfs.debug set to 1 > from the loader? You should see some messages about missing file, maybe > we should do them visible always and not after increasing debug level? Yes, I tried this and got the following message: spa_config_load:92[1]: Cannot open /boot/zfs/zpool.cache Perhaps it's a good idea indeed to be more verbose about this. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Fri Oct 16 08:32:18 2009 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 2B3A2106568F; Fri, 16 Oct 2009 08:32:18 +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 3A4C78FC1A; Fri, 16 Oct 2009 08:32:16 +0000 (UTC) Received: from porto.topspin.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id LAA09436; Fri, 16 Oct 2009 11:32:15 +0300 (EEST) (envelope-from avg@icyb.net.ua) Received: from localhost.topspin.kiev.ua ([127.0.0.1]) by porto.topspin.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1MyiER-0006p0-77; Fri, 16 Oct 2009 11:32:15 +0300 Message-ID: <4AD82F80.2050302@icyb.net.ua> Date: Fri, 16 Oct 2009 11:32:00 +0300 From: Andriy Gapon User-Agent: Thunderbird 2.0.0.23 (X11/20090823) MIME-Version: 1.0 To: Pawel Jakub Dawidek References: <4AD5BD00.4050700@icyb.net.ua> <20091014204657.GB1727@garage.freebsd.pl> In-Reply-To: <20091014204657.GB1727@garage.freebsd.pl> X-Enigmail-Version: 0.96.0 Content-Type: text/plain; charset=KOI8-U Content-Transfer-Encoding: 7bit Cc: Alexander Best , freebsd-current@FreeBSD.org Subject: Re: panic when mounting device >= 2 times 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, 16 Oct 2009 08:32:18 -0000 on 14/10/2009 23:46 Pawel Jakub Dawidek said the following: > I've this patch that is suppose to fix it: > > http://people.freebsd.org/~pjd/patches/geom_vfs.c.patch > > But AFAIR its not complete. I think it is still possible to remount one > of the read-only mounts to read-write. > > Another possibility that comes to my mind is to keep list/array of > consumers in bo_private instead of using one consumer only. This would > be better in terms of access management. This looks very good for at least preventing the most common accidents. I've been thinking about something like creating a cloned vnode for the device vnode and giving a private copy to each filesystem. But I currently lack a lot knowledge in this area, so I can't even say if it could be feasible, let alone implement it. -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Fri Oct 16 08:38:41 2009 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 F1FBD106566B; Fri, 16 Oct 2009 08:38:41 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (skuns.zoral.com.ua [91.193.166.194]) by mx1.freebsd.org (Postfix) with ESMTP id 467F68FC18; Fri, 16 Oct 2009 08:38:40 +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 n9G8c8ZS037672 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 16 Oct 2009 11:38:08 +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.3/8.14.3) with ESMTP id n9G8c8YU018385; Fri, 16 Oct 2009 11:38:08 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.3/8.14.3/Submit) id n9G8c8Vd018378; Fri, 16 Oct 2009 11:38:08 +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: Fri, 16 Oct 2009 11:38:08 +0300 From: Kostik Belousov To: Andriy Gapon Message-ID: <20091016083808.GO27077@deviant.kiev.zoral.com.ua> References: <4AD5BD00.4050700@icyb.net.ua> <20091014204657.GB1727@garage.freebsd.pl> <4AD82F80.2050302@icyb.net.ua> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="+wSiqF7c0ySQ2tNi" Content-Disposition: inline In-Reply-To: <4AD82F80.2050302@icyb.net.ua> 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=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Alexander Best , freebsd-current@freebsd.org, Pawel Jakub Dawidek Subject: Re: panic when mounting device >= 2 times 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, 16 Oct 2009 08:38:42 -0000 --+wSiqF7c0ySQ2tNi Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 16, 2009 at 11:32:00AM +0300, Andriy Gapon wrote: > on 14/10/2009 23:46 Pawel Jakub Dawidek said the following: > > I've this patch that is suppose to fix it: > >=20 > > http://people.freebsd.org/~pjd/patches/geom_vfs.c.patch > >=20 > > But AFAIR its not complete. I think it is still possible to remount one > > of the read-only mounts to read-write. > >=20 > > Another possibility that comes to my mind is to keep list/array of > > consumers in bo_private instead of using one consumer only. This would > > be better in terms of access management. >=20 > This looks very good for at least preventing the most common accidents. > I've been thinking about something like creating a cloned vnode for the d= evice > vnode and giving a private copy to each filesystem. But I currently lack = a lot > knowledge in this area, so I can't even say if it could be feasible, let = alone > implement it. I suspect this is pretty much bad idea. The reason is that buffer list is managed by buffer object that has 1:1 correspondence with the vnode. You will end up with aliased buffers. Actually, this could happen without the proposed change as well, I believe. It is enough to mount devfs several times and then use different devfs vnodes for the same device. But since people usually mount filesystems using /dev, this does not happen in practice. For multiple ro mounts to work, we need to find a way to push the buffer object to cdev. --+wSiqF7c0ySQ2tNi Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (FreeBSD) iEYEARECAAYFAkrYMPAACgkQC3+MBN1Mb4j9pACdFiiomSB6/hKkk81VuQ1ELERr Qz8AnAt3rNHt2F/URcnAsR9hO0+bIijn =oyl6 -----END PGP SIGNATURE----- --+wSiqF7c0ySQ2tNi-- From owner-freebsd-current@FreeBSD.ORG Fri Oct 16 16:10:47 2009 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 055811065670 for ; Fri, 16 Oct 2009 16:10:47 +0000 (UTC) (envelope-from christian@nertenher.de) Received: from mail-fx0-f210.google.com (mail-fx0-f210.google.com [209.85.220.210]) by mx1.freebsd.org (Postfix) with ESMTP id 9B40C8FC0C for ; Fri, 16 Oct 2009 16:10:46 +0000 (UTC) Received: by fxm6 with SMTP id 6so2520541fxm.43 for ; Fri, 16 Oct 2009 09:10:45 -0700 (PDT) MIME-Version: 1.0 Sender: christian@nertenher.de Received: by 10.223.57.22 with SMTP id a22mr298741fah.4.1255709445268; Fri, 16 Oct 2009 09:10:45 -0700 (PDT) In-Reply-To: <20091015183338.37FBB1CC44@ptavv.es.net> References: <309b65830910150235w59857e83r23887193c36561f0@mail.gmail.com> <20091015183338.37FBB1CC44@ptavv.es.net> From: Christian Schmidt Date: Fri, 16 Oct 2009 18:10:25 +0200 X-Google-Sender-Auth: ed3a6019c60500e6 Message-ID: <309b65830910160910v5081b098tfec440db48bb08a8@mail.gmail.com> To: Kevin Oberman Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: john hood , freebsd-current@freebsd.org Subject: Re: Boot issues with a Dell Inspiron 530 and 8.0 RC1 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, 16 Oct 2009 16:10:47 -0000 On Thu, Oct 15, 2009 at 20:33, Kevin Oberman wrote: >> From: Christian Schmidt >> Date: Thu, 15 Oct 2009 11:35:11 +0200 >> Sender: owner-freebsd-current@freebsd.org >> >> On Tue, Oct 13, 2009 at 18:12, Christian Schmidt w= rote: >> > On Mon, Oct 12, 2009 at 07:21, john hood wrote: >> >> Christian Schmidt wrote: >> > [...] >> >>> I am seeing a strange issue with my Dell Inspiron 530 with 8.0 RC1-p= 1 >> >>> at around 50-75% percent of all boots. It all boils down to GENERIC >> >>> throwing the following: >> >>> >> >>> AP #1 (PHY #1) failed! >> >>> panic y/n? [y] panic: bye-bye >> >>> cpuid =3D 0 >> > [...] >> >> We have 3 of these machines. >> >> >> >> In my experience, keyboard activity triggers the problem. =C2=A0If I = boot the >> >> machine without any keyboard presses/releases between the time the lo= ader >> >> starts the kernel and some time later, definitely by the time the USB >> >> keyboard driver attaches, then I don't get this problem. =C2=A0This i= ncludes any >> >> key-up (and maybe key repeat) events you may generate after typing a = key at >> >> the boot menu, or after typing enter at the OK prompt, or pressing a = key to >> >> bypass the autoboot timeout that counts down by seconds. >> >> >> >> If you let the machine start from cold without touching the keyboard,= what >> >> happens? >> > >> > That is a very interesting point you are making. Indeed, it never >> > occured to me that I am usually hammering down on F1 and 1 to boot >> > faster (yeah yeah, I know ;-)). I let the machine boot through without >> > that a couple of times and it seemed to have worked for about a 100% >> > of those cases. I will keep testing but I think we have a hot >> > contender. :-) >> > >> >> Okay, after testing that for a couple of days I can confirm that it >> never-ever happens when I leave the keyboard alone during the >> boot-phase. As a workaround, I can live with not touching the >> keyboard. Nethertheless, this seems to be a bug that deserves fixing, >> isn't it? > > FWIW, I've seen this at least as far back as V5 and I think I have seen > it on V4. I have no idea if it happened in V3. That was too long ago. > > IT would be nice to see this fixed, but I think we have all lived with > it for a long time and most have either learned not to type stuff before > the device probes have ended or they have never happened to trigger it. > > In my case, it seems like it is OK to type after the keyboard probe is > completed. Okay, I'll take that as the closing statement. :-) Now that I know what the problem is I can just work around it. Thanks for the useful hints! Cheers, Christian From owner-freebsd-current@FreeBSD.ORG Fri Oct 16 16:55:46 2009 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 78F94106566B; Fri, 16 Oct 2009 16:55:46 +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 429F98FC22; Fri, 16 Oct 2009 16:55:46 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9GGtj7p094899; Fri, 16 Oct 2009 12:55:45 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9GGtjuI094898; Fri, 16 Oct 2009 16:55:45 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 16 Oct 2009 16:55:45 GMT Message-Id: <200910161655.n9GGtjuI094898@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: Fri, 16 Oct 2009 16:55:46 -0000 TB --- 2009-10-16 16:20:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-16 16:20:00 - starting HEAD tinderbox run for i386/i386 TB --- 2009-10-16 16:20:00 - cleaning the object tree TB --- 2009-10-16 16:20:26 - cvsupping the source tree TB --- 2009-10-16 16:20:26 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2009-10-16 16:55:45 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-10-16 16:55:45 - ERROR: unable to cvsup the source tree TB --- 2009-10-16 16:55:45 - 0.80 user 11.19 system 2145.43 real http://tinderbox.des.no/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Fri Oct 16 16:57:52 2009 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 5A74B106568F; Fri, 16 Oct 2009 16:57:52 +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 236AD8FC14; Fri, 16 Oct 2009 16:57:52 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.3/8.14.3) with ESMTP id n9GGvpWK094907; Fri, 16 Oct 2009 12:57:51 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.3/8.14.3/Submit) id n9GGvpqG094906; Fri, 16 Oct 2009 16:57:51 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 16 Oct 2009 16:57:51 GMT Message-Id: <200910161657.n9GGvpqG094906@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: Fri, 16 Oct 2009 16:57:52 -0000 TB --- 2009-10-16 16:20:00 - tinderbox 2.6 running on freebsd-current.sentex.ca TB --- 2009-10-16 16:20:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2009-10-16 16:20:00 - cleaning the object tree TB --- 2009-10-16 16:20:28 - cvsupping the source tree TB --- 2009-10-16 16:20:28 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile TB --- 2009-10-16 16:57:51 - WARNING: /usr/bin/csup returned exit code 1 TB --- 2009-10-16 16:57:51 - ERROR: unable to cvsup the source tree TB --- 2009-10-16 16:57:51 - 0.84 user 12.70 system 2271.34 real http://tinderbox.des.no/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Fri Oct 16 17:09:31 2009 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 DD1291065672 for ; Fri, 16 Oct 2009 17:09:31 +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 BAA788FC1A for ; Fri, 16 Oct 2009 17:09:31 +0000 (UTC) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 53B0B46B06 for ; Fri, 16 Oct 2009 13:09:31 -0400 (EDT) Date: Fri, 16 Oct 2009 18:09:31 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: current@FreeBSD.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: Subject: dtrace profile timers still unstable? 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, 16 Oct 2009 17:09:31 -0000 In the past, I've had little luck using the DTrace profile timers on FreeBSD for much without crashes, and this morning was no different. I attempted to use the following(ish) script: profile-1ms { @data[stack()] = count(); } The result was: spin lock 0x849747d8 (cyclic cpu) held by 0x85442b40 (tid 100539) too long panic: spin lock held too long 0 doadump () at pcpu.h:246 #1 0x8089b5bf in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:416 #2 0x8089b8a2 in panic (fmt=Variable "fmt" is not available. ) at /usr/src/sys/kern/kern_shutdown.c:579 #3 0x8088afaf in _mtx_lock_spin_failed (m=0x0) at /usr/src/sys/kern/kern_mutex.c:490 #4 0x8088b035 in _mtx_lock_spin (m=0x849747d8, tid=2220091648, opts=0, file=0x8a717a45 "/usr/src/sys/modules/cyclic/../../cddl/dev/cyclic/cyclic.c", line=574) at /usr/src/sys/kern/kern_mutex.c:526 #5 0x8088b7d1 in _mtx_lock_spin_flags (m=0x849747d8, opts=0, file=0x8a717a45 "/usr/src/sys/modules/cyclic/../../cddl/dev/cyclic/cyclic.c", line=574) at /usr/src/sys/kern/kern_mutex.c:246 #6 0x8a716f97 in cyclic_clock () from /boot/kernel/cyclic.ko #7 0x80bce876 in lapic_handle_timer (frame=0x842c6c34) at /usr/src/sys/i386/i386/local_apic.c:777 #8 0x80bc61cf in Xtimerint () at apic_vector.s:108 #9 0x80bba455 in acpi_cpu_c1 () at /usr/src/sys/i386/acpica/acpi_machdep.c:554 #10 0x804ff24c in acpi_cpu_idle () at /usr/src/sys/dev/acpica/acpi_cpu.c:921 #11 0x80bcff2b in cpu_idle_acpi (busy=1) at /usr/src/sys/i386/i386/machdep.c:1236 #12 0x80bd18db in cpu_idle (busy=1) at /usr/src/sys/i386/i386/machdep.c:1324 #13 0x808bf81e in sched_idletd (dummy=0x0) at /usr/src/sys/kern/sched_ule.c:2562 In the past, I've had similar experiences, although possibly different panics. I wonder if we should just disable the profile provider in 8.0 to prevent similar footshooting by others? Or perhaps someone with some dtrace internals interest could investigate? (I've seen panics with it pretty deterministically on i386 and amd64) Robert N M Watson Computer Laboratory University of Cambridge From owner-freebsd-current@FreeBSD.ORG Fri Oct 16 23:40:34 2009 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 0EFDE1065676 for ; Fri, 16 Oct 2009 23:40:34 +0000 (UTC) (envelope-from oliver@akephalos.de) Received: from mailout03.t-online.de (mailout03.t-online.de [194.25.134.81]) by mx1.freebsd.org (Postfix) with ESMTP id C30078FC1E for ; Fri, 16 Oct 2009 23:40:33 +0000 (UTC) Received: from fwd11.aul.t-online.de by mailout03.t-online.de with smtp id 1MywAL-0004v2-01; Sat, 17 Oct 2009 01:24:57 +0200 Received: from [192.168.1.122] (Xpx9emZYwtd0sHp2Xug1u8bO6taqkcdCPEvVViIcZYikwdFHiSh+eTTjMhcGcCWAKyHcmRPLjm@[91.21.104.219]) by fwd11.t-online.de with esmtp id 1MywAJ-0HqWno0; Sat, 17 Oct 2009 01:24:55 +0200 Message-Id: <79B5A43C-06EB-4F91-ADF9-D4D0AAFBF992@akephalos.de> From: "O.Herold" To: "freebsd-current@freebsd.org" Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit X-Mailer: iPod Mail (7C145) Mime-Version: 1.0 (iPod Mail 7C145) Date: Sat, 17 Oct 2009 01:22:48 +0200 X-ID: Xpx9emZYwtd0sHp2Xug1u8bO6taqkcdCPEvVViIcZYikwdFHiSh+eTTjMhcGcCWAKyHcmRPLjm X-TOI-MSGID: 7d498f73-4acd-46d5-8dfc-07af14053483 X-Mailman-Approved-At: Fri, 16 Oct 2009 23:45:44 +0000 Subject: if_rum dies on transmit... 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, 16 Oct 2009 23:40:34 -0000 Thanks, works like a charm. I could test it for several hours while downloading lots of packages on two different machines (i386 & AMD64). Cheers, Oliver Herold pro bono publico From owner-freebsd-current@FreeBSD.ORG Sat Oct 17 08:26:21 2009 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 09456106566B for ; Sat, 17 Oct 2009 08:26:21 +0000 (UTC) (envelope-from lists@mawer.org) Received: from mail-pz0-f202.google.com (mail-pz0-f202.google.com [209.85.222.202]) by mx1.freebsd.org (Postfix) with ESMTP id DF0B58FC0A for ; Sat, 17 Oct 2009 08:26:19 +0000 (UTC) Received: by pzk40 with SMTP id 40so2214090pzk.7 for ; Sat, 17 Oct 2009 01:26:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.140.203.12 with SMTP id a12mr948172rvg.213.1255767979274; Sat, 17 Oct 2009 01:26:19 -0700 (PDT) In-Reply-To: <200910131644.04358.john@baldwin.cx> References: <4ACE6D84.3000209@gmail.com> <4ACE833A.3030506@uffner.com> <4ACE9DFD.3010207@gmail.com> <200910131644.04358.john@baldwin.cx> Date: Sat, 17 Oct 2009 19:26:19 +1100 Message-ID: From: Antony Mawer To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: David Ehrmann , freebsd-current@freebsd.org Subject: Re: 8.0rc1 not recognizing partitions on EPIA SN 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, 17 Oct 2009 08:26:21 -0000 On Wed, Oct 14, 2009 at 7:44 AM, John Baldwin wrote: > On Thursday 08 October 2009 10:20:45 pm David Ehrmann wrote: >> Tom Uffner wrote: >> > David Ehrmann wrote: >> >> First, I tried to upgrade the normal way. =A0I built my own kernel an= d >> >> installed it, but when I tried to boot it, I got a mountroot> >> >> prompt. =A0When I printed the devices, instead of seeing ad0s1a and >> >> friends, I saw ad0a and ad0d (just those two for ad0). =A0I was still >> >> able to use the old (7.1) kernel fine. =A0Thinking it was something t= o >> >> do with the upgrade, I tried to do a reinstall. =A0I chose the defaul= t >> >> options, but once it got to the "last chance..." screen, this happene= d: >> >> >> >> Unable to find device node for /dev/ad0s1b in /dev! >> >> The creation of filesystems will be aborted. >> > >> > this is becoming an FAQ for 8.0 >> > >> > the short answer is "dangerously dedicated" partitions are not support= ed >> > by the 8.0 installer. back up your data. zero the MBR & partition tabl= e >> > with dd, and re-slice & partition your disk. after the install, restor= e >> > from your backups. >> > >> > search the freebsd-current archives for full details. >> dd did the trick. >> >> I understand why this was done, but at the same time, upgrading is now >> impractical for some users, and what looks like a fresh installation >> (repartitioned, resliced) can even fail. =A0Is there a change that could >> be made to the partitioning process that would fix this? > > E-mail marcel@. Am I correct in reading this as saying that -any- system which was setup as dangerously dedicated will be unbootable under 8.0, and the only way to fix is to basically repartition and reinstall...? If so ... !!! --Antony From owner-freebsd-current@FreeBSD.ORG Sat Oct 17 15:36:40 2009 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 1832A106568B for ; Sat, 17 Oct 2009 15:36:40 +0000 (UTC) (envelope-from des@des.no) Received: from tim.des.no (tim.des.no [194.63.250.121]) by mx1.freebsd.org (Postfix) with ESMTP id CCB748FC15 for ; Sat, 17 Oct 2009 15:36:39 +0000 (UTC) Received: from ds4.des.no (des.no [84.49.246.2]) by smtp.des.no (Postfix) with ESMTP id D80BD6D41B; Sat, 17 Oct 2009 15:36:38 +0000 (UTC) Received: by ds4.des.no (Postfix, from userid 1001) id A23BD84514; Sat, 17 Oct 2009 17:36:38 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: Antony Mawer References: <4ACE6D84.3000209@gmail.com> <4ACE833A.3030506@uffner.com> <4ACE9DFD.3010207@gmail.com> <200910131644.04358.john@baldwin.cx> Date: Sat, 17 Oct 2009 17:36:38 +0200 In-Reply-To: (Antony Mawer's message of "Sat, 17 Oct 2009 19:26:19 +1100") Message-ID: <86ljja3ud5.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.95 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: John Baldwin , David Ehrmann , freebsd-current@freebsd.org Subject: Re: 8.0rc1 not recognizing partitions on EPIA SN 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, 17 Oct 2009 15:36:40 -0000 Antony Mawer writes: > Am I correct in reading this as saying that -any- system which was > setup as dangerously dedicated will be unbootable under 8.0, and the > only way to fix is to basically repartition and reinstall...? If so > ... !!! You brought it upon yourself by setting it up that way in the first place. It's called *dangerously* dedicated for a reason. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sat Oct 17 17:21:32 2009 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 82E381065672; Sat, 17 Oct 2009 17:21:32 +0000 (UTC) (envelope-from freebsd@levsha.org.ua) Received: from expo.ukrweb.net (mail.univua.net [91.202.128.78]) by mx1.freebsd.org (Postfix) with ESMTP id 0FCA38FC18; Sat, 17 Oct 2009 17:21:31 +0000 (UTC) Received: from levsha by expo.ukrweb.net with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1MzCh5-000O1G-9q; Sat, 17 Oct 2009 20:03:51 +0300 Date: Sat, 17 Oct 2009 20:03:51 +0300 From: Mykola Dzham To: jfv@freebsd.org Message-ID: <20091017170351.GZ29771@expo.ukrweb.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD/7.0-STABLE (i386) User-Agent: Mutt/1.5.18 (2008-05-17) Cc: current@freebsd.org Subject: page fault in igb driver on 8.0-RC1 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, 17 Oct 2009 17:21:32 -0000 Hi! On hight network load system panics: GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 GET BUF: dmamap load failure - 12 Fatal trap 12: page fault while in kernel mode cpuid = 2; apic id = 02 fault virtual address = 0x0 fault code = supervisor read data, page not present instruction pointer = 0x20:0xffffffff8025e4a5 stack pointer = 0x28:0xffffff87312f3a60 frame pointer = 0x28:0xffffff87312f3a80 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, long 1, def32 0, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 0 (igb0 taskq) trap number = 12 panic: page fault cpuid = 2 KDB: stack backtrace: db_trace_self_wrapper() at 0xffffffff80185baa = db_trace_self_wrapper+0x2a panic() at 0xffffffff8020e992 = panic+0x182 trap_fatal() at 0xffffffff8040eefd = trap_fatal+0x2ad trap_pfault() at 0xffffffff8040f27d = trap_pfault+0x22d trap() at 0xffffffff8040fbff = trap+0x3cf calltrap() at 0xffffffff803f6e13 = calltrap+0x8 --- trap 0xc, rip = 0xffffffff8025e4a5, rsp = 0xffffff87312f3a60, rbp = 0xffffff87312f3a80 --- mb_free_ext() at 0xffffffff8025e4a5 = mb_free_ext+0x15 igb_get_buf() at 0xffffffff80a3a6e5 = igb_get_buf+0x2e5 igb_rxeof() at 0xffffffff80a3abd5 = igb_rxeof+0x425 igb_handle_rx() at 0xffffffff80a3b14b = igb_handle_rx+0x3b taskqueue_run() at 0xffffffff80243ec1 = taskqueue_run+0x91 taskqueue_thread_loop() at 0xffffffff8024404f = taskqueue_thread_loop+0x3f fork_exit() at 0xffffffff801ea9b2 = fork_exit+0x112 fork_trampoline() at 0xffffffff803f72ee = fork_trampoline+0xe --- trap 0, rip = 0, rsp = 0xffffff87312f3d30, rbp = 0 --- Uptime: 1h46m18s Cannot dump. Device not defined or unavailable. System is amd64 8.0-RC1 r197974 Tue Oct 13 23:00:17 EEST 2009 dmesg part about network cards: found-> vendor=0x8086, dev=0x10a7, revid=0x02 domain=0, bus=8, slot=0, func=0 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=a, irq=56 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit MSI-X supports 10 messages in map 0x1c pci0:8:0:0: reprobing on driver added igb0: port 0x2000-0x201f mem 0xd8020000-0xd803ffff,0xd8000000-0xd801ffff,0xd8080000-0xd8083fff irq 56 at device 0.0 on pci8 igb0: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xd8020000 igb0: Reserved 0x4000 bytes for rid 0x1c type 3 at 0xd8080000 igb0: attempting to allocate 3 MSI-X vectors (10 supported) msi: routing MSI-X IRQ 256 to local APIC 7 vector 48 msi: routing MSI-X IRQ 257 to local APIC 0 vector 48 msi: routing MSI-X IRQ 258 to local APIC 1 vector 49 igb0: using IRQs 256-258 for MSI-X igb0: Using MSIX interrupts with 3 vectors igb0: [MPSAFE] igb0: [ITHREAD] igb0: [MPSAFE] igb0: [ITHREAD] igb0: [MPSAFE] igb0: [ITHREAD] igb0: bpf attached igb0: Ethernet address: 00:30:48:c6:c4:54 found-> vendor=0x8086, dev=0x10a7, revid=0x02 domain=0, bus=8, slot=0, func=1 class=02-00-00, hdrtype=0x00, mfdev=1 cmdreg=0x0007, statreg=0x0010, cachelnsz=8 (dwords) lattimer=0x00 (0 ns), mingnt=0x00 (0 ns), maxlat=0x00 (0 ns) intpin=b, irq=70 powerspec 2 supports D0 D3 current D0 MSI supports 1 message, 64 bit MSI-X supports 10 messages in map 0x1c pci0:8:0:1: reprobing on driver added igb1: port 0x2020-0x203f mem 0xd8060000-0xd807ffff,0xd8040000-0xd805ffff,0xd8084000-0xd8087fff irq 70 at device 0.1 on pci8 igb1: Reserved 0x20000 bytes for rid 0x10 type 3 at 0xd8060000 igb1: Reserved 0x4000 bytes for rid 0x1c type 3 at 0xd8084000 igb1: attempting to allocate 3 MSI-X vectors (10 supported) msi: routing MSI-X IRQ 259 to local APIC 2 vector 49 msi: routing MSI-X IRQ 260 to local APIC 3 vector 49 msi: routing MSI-X IRQ 261 to local APIC 4 vector 49 igb1: using IRQs 259-261 for MSI-X igb1: Using MSIX interrupts with 3 vectors igb1: [MPSAFE] igb1: [ITHREAD] igb1: [MPSAFE] igb1: [ITHREAD] igb1: [MPSAFE] igb1: [ITHREAD] igb1: bpf attached igb1: Ethernet address: 00:30:48:c6:c4:55 I have no kernel dump (dump device disabled by default now), but i can reproduce problem with enabled kernel dump and with debug kernel if required. -- LEFT-(UANIC|RIPE) JID: levsha@jabber.net.ua PGP fingerprint: 1BCD 7C80 2E04 7282 C944 B0E0 7E67 619E 4E72 9280 From owner-freebsd-current@FreeBSD.ORG Sat Oct 17 21:00:44 2009 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 A1A78106568D for ; Sat, 17 Oct 2009 21:00:44 +0000 (UTC) (envelope-from oliver@namp.de) Received: from grisu.qmail-ldap.de (grisu.qmail-ldap.de [78.46.218.233]) by mx1.freebsd.org (Postfix) with ESMTP id 04F3D8FC1E for ; Sat, 17 Oct 2009 21:00:43 +0000 (UTC) Received: (qmail 84765 invoked from network); 17 Oct 2009 21:07:21 -0000 Received: from unknown (HELO mail.kuehlbox.de) (oliver@namp.de@[78.46.218.233]) (envelope-sender ) by grisu.qmail-ldap.de (qmail-ldap-1.03) with SMTP for ; 17 Oct 2009 21:07:21 -0000 Received: from: grisu.qmail-ldap.de ([78.46.218.233]) by HSF smtp proxy MIME-Version: 1.0 X-Priority: Normal X-Mailer: AtMail 1.03 Message-ID: <61410.1255813638@namp.de> To: X-Origin: 93.104.175.105 X-Atmail-Account: oliver@namp.de Date: Sat, 17 Oct 2009 23:07:18 +0200 From: Oliver Fakler Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: 8.0 RC1 freeze while WPA ath0 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: oliver@namp.de List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2009 21:00:44 -0000 =20 Hi there, i have a problem on 8.0 RC1 while connecting to wlan with wpa Problem occurs while testing the wpa connection manual: bodo# wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf=20 CTRL-EVENT-SCAN-RESULTS=20 CTRL-EVENT-SCAN-RESULTS=20 Trying to associate with 00:23:69:a2:c0:fb (SSID=3D'Linksys' freq=3D2412 MHz) my wpa_supplicat.conf: network=3D{ ssid=3D"Linksys" psk=3D"xxxxx" } some ath0 informations: Oct 17 22:30:37 bodo kernel: ath0: mem 0xfaef0000-0xfaefffff irq 16 at device 5.0 on pci1 Oct 17 22:30:37 bodo kernel: ath0: [ITHREAD] Oct 17 22:30:37 bodo kernel: ath0: AR5416 mac 13.10 RF2133 phy 8.1 maybe somebody have an idea? cheers Oliver From owner-freebsd-current@FreeBSD.ORG Sat Oct 17 22:23:21 2009 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 E84C81065692; Sat, 17 Oct 2009 22:23:20 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-qy0-f192.google.com (mail-qy0-f192.google.com [209.85.221.192]) by mx1.freebsd.org (Postfix) with ESMTP id 8538A8FC22; Sat, 17 Oct 2009 22:23:20 +0000 (UTC) Received: by qyk30 with SMTP id 30so2538526qyk.7 for ; Sat, 17 Oct 2009 15:23:19 -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:references:mime-version:content-type :content-disposition:in-reply-to:user-agent; bh=2/FiMBK+NMaOYHiGudmKu8lt6iYnPm4P110AQfwLYKk=; b=ZvWVuXklNDwfPMwHT+UHaL4Ycwdbm64HfizV8rovYBoUGdZXDkgBZpLKLfJ/8nlLmF Y9UW1/Ae7lc0srTag4Pf04iWtFoUWLm61D2XGixm4PY3tWXeHbTr2g0eLdvXQom4vopQ 8NYfea19+5SMogngXIysTle9JTdY5zKqdFvC8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Ow0F7ZLmgd9GYKLXsTARwMGEFz8OJQzzQLSxUGU7hxJXGSNnaHbIFnBbSaSmWlrQ5G TBRekGc7tAXwNW1I8qPV1+rhEFVSeqZXgxFXU+ITC54Yhl2pyBPsvKuoEqI8fvYkMalf oUAf4clh0RIQ+shL6QQQsg/gpNYE0VZ7GUxas= Received: by 10.224.90.67 with SMTP id h3mr1821608qam.240.1255818199699; Sat, 17 Oct 2009 15:23:19 -0700 (PDT) Received: from pyunyh@gmail.com ([174.35.1.224]) by mx.google.com with ESMTPS id 20sm2142488qyk.9.2009.10.17.15.23.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 17 Oct 2009 15:23:18 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Sat, 17 Oct 2009 15:23:14 -0700 From: Pyun YongHyeon Date: Sat, 17 Oct 2009 15:23:14 -0700 To: Mykola Dzham Message-ID: <20091017222314.GB19204@michelle.cdnetworks.com> References: <20091017170351.GZ29771@expo.ukrweb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20091017170351.GZ29771@expo.ukrweb.net> User-Agent: Mutt/1.4.2.3i Cc: jfv@freebsd.org, current@freebsd.org Subject: Re: page fault in igb driver on 8.0-RC1 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2009 22:23:21 -0000 On Sat, Oct 17, 2009 at 08:03:51PM +0300, Mykola Dzham wrote: > Hi! > On hight network load system panics: > > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > GET BUF: dmamap load failure - 12 > I believe this type of message should not be in fast path and it should be rate-limited. > > Fatal trap 12: page fault while in kernel mode > cpuid = 2; apic id = 02 > fault virtual address = 0x0 > fault code = supervisor read data, page not present > instruction pointer = 0x20:0xffffffff8025e4a5 > stack pointer = 0x28:0xffffff87312f3a60 > frame pointer = 0x28:0xffffff87312f3a80 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 0 (igb0 taskq) > trap number = 12 > panic: page fault > cpuid = 2 > KDB: stack backtrace: > db_trace_self_wrapper() at 0xffffffff80185baa = > db_trace_self_wrapper+0x2a > panic() at 0xffffffff8020e992 = panic+0x182 > trap_fatal() at 0xffffffff8040eefd = trap_fatal+0x2ad > trap_pfault() at 0xffffffff8040f27d = trap_pfault+0x22d > trap() at 0xffffffff8040fbff = trap+0x3cf > calltrap() at 0xffffffff803f6e13 = calltrap+0x8 > --- trap 0xc, rip = 0xffffffff8025e4a5, rsp = 0xffffff87312f3a60, rbp = > 0xffffff87312f3a80 --- > mb_free_ext() at 0xffffffff8025e4a5 = mb_free_ext+0x15 > igb_get_buf() at 0xffffffff80a3a6e5 = igb_get_buf+0x2e5 > igb_rxeof() at 0xffffffff80a3abd5 = igb_rxeof+0x425 > igb_handle_rx() at 0xffffffff80a3b14b = igb_handle_rx+0x3b > taskqueue_run() at 0xffffffff80243ec1 = taskqueue_run+0x91 > taskqueue_thread_loop() at 0xffffffff8024404f = > taskqueue_thread_loop+0x3f > fork_exit() at 0xffffffff801ea9b2 = fork_exit+0x112 > fork_trampoline() at 0xffffffff803f72ee = fork_trampoline+0xe > --- trap 0, rip = 0, rsp = 0xffffff87312f3d30, rbp = 0 --- > Uptime: 1h46m18s > Cannot dump. Device not defined or unavailable. > > System is amd64 8.0-RC1 r197974 Tue Oct 13 23:00:17 EEST 2009 > Hmm, I remember some user already reported similar issues for igb(4). At that time I briefly looked over possible code paths for the issue and saw some questionable handling of mbufs under resource shortage cases and I sent my concerns to Jack but it seems he lost the mail. Unfortunately I don't have igb(4) hardwares so I guess it's somewhat hard for me to fix the issue but I'll try to read the code again if time permit. From owner-freebsd-current@FreeBSD.ORG Sat Oct 17 23:05:08 2009 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 6F6B51065670 for ; Sat, 17 Oct 2009 23:05:08 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 333498FC1C for ; Sat, 17 Oct 2009 23:05:07 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.3/8.14.3) with ESMTP id n9HN578Z089765 for ; Sat, 17 Oct 2009 17:05:07 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.3/8.14.3/Submit) with ESMTP id n9HN57oK089762 for ; Sat, 17 Oct 2009 17:05:07 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 17 Oct 2009 17:05:07 -0600 (MDT) From: Warren Block To: current@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (wonkity.com [127.0.0.1]); Sat, 17 Oct 2009 17:05:07 -0600 (MDT) Cc: Subject: Restarting devd 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, 17 Oct 2009 23:05:08 -0000 Immediately after boot, devd restart fails: # /etc/rc.d/devd restart Stopping devd. Starting devd. devd: devd already running, pid: 398 /etc/rc.d/devd: WARNING: failed to start devd And it's right, devd is not running. Remove the stale pidfile /var/run/devd.pid, and '/etc/rc.d/devd start' goes fine. In fact, after that initial pidfile is removed, restarts are no longer a problem: # /etc/rc.d/devd restart Stopping devd. Starting devd. So why is it a problem with the first run of devd, but not afterwards? Something with /etc/rc.d/devd, or maybe something more general with /etc/rc.subr? FreeBSD lightning 8.0-RC1 FreeBSD 8.0-RC1 #6: Wed Oct 14 18:44:38 MDT 2009 root@lightning:/usr/obj/usr/src/sys/LIGHTNING i386 -Warren Block * Rapid City, South Dakota USA