gmane.os.freebsd.stable
http://blog.gmane.org/gmane.os.freebsd.stable
hourly11901-01-01T00:00+00:00Gmanehttp://gmane.org/img/gmane-25t.png
http://gmane.org
Proposed MFC to hastctl: compact 'status' and introduce 'list' command
http://comments.gmane.org/gmane.os.freebsd.stable/86469
<pre>Dear colleagues,
is there any objection for MFCing the change introduced in
http://svnweb.freebsd.org/changeset/base/248291
(the most major change: compacting output of `hastctl status' to one-liner per
provider; old output is retained as `list' command)
to at least stable/9 ?
The reason I'm asking is that it could lead to changes in hast-related scripts
which one use in production.
If no objections are received I'm (with the generous support from trociny,
thank you Mikolaj!) tend to merge it after, say, 2 weeks.
Thanks!
</pre>Dmitry Morozovsky2013-05-23T20:54:56Swap Warning Message?
http://comments.gmane.org/gmane.os.freebsd.stable/86466
<pre>Updated 9.1 to 9 stable on an old PII with 256 MB of memory.
(FreeBSD runs fine on this machine). After updating have
been getting the following warning on startup:
warning: total configured swap (524288 pages) exceeds maximum recommended
amount (497056 pages).
warning: increase kern.maxswzone or reduce amount of swap space.
I allocated 2.0 GB of swap when I installed. This was not a problem
in the past.
Should I ignore this warning or do I need to do something?
</pre>Michael Gass2013-05-23T12:55:20em2: watchdog timeout -- resetting
http://comments.gmane.org/gmane.os.freebsd.stable/86460
<pre>Hello, I have a server pfsense in bridge mode to function as transparent
FW, the problem is that once I connect the pfsense between my router core
and my core switch catalyst a few seconds begin to appear several messages
like these:
em2: watchdog timeout - resetting
em2: watchdog timeout - resetting
em2: watchdog timeout - resetting
em2: watchdog timeout - resetting
And the connection falls back repeatedly and indefinitely.
Searching on google did some tweaks:
hw.em.rxd = "4096"
hw.em.txd = "4096"
hw.em.tx_int_delay = "250"
hw.em.rx_int_delay = "250"
hw.em.tx_abs_int_delay = "250"
hw.em.rx_abs_int_delay = "250"
hw.em.enable_msix = "0"
hw.em.msix_queues = "2"
hw.em.rx_process_limit = "-1"
hw.em.fc_setting = "0"
hw.em.num_queues = 1
I tried several variations, but also without success.
My infrastructure:
(7301 cisco router) ------ em1 (pfsense bridge0) em2 ------ sw core cisco
catalyst
I tried also a fresh installation of pfsense 2.0.3 without success.
My network card is an Intel ® PRO/1000 MT Dual Port Server Adapter PCI-X on
a 32-bit PCI slot, operating bridge in 1 <-> em2.
Motherboard ASUS P8H61-V and CPU corei5, I tried disabling all onboard
devices, also without success.
I have 4 nics identical, tested one per one all without success also.
I am using the latest bios from ASUS site, I tried various combinations of
bios, also without success.
I tried to activate the device polling unsuccessfully to solve the problem.
I tried disable acpi on boot menu but the ser without acpi wont boot.
I tried disable TOE, FLOW CONTROL, no sucess.
This is a link to a troughput 60 Mbits with multiple VLANs (more than 200)
Wisp provider.
I tested the same server same hardware but using linux (debian 6) did the
bridges, and everything worked properly!, so it is clear that this is a
problem software (in intel em driver?)
Tested on another server (P5VD2MX + Core2Duo) but with the same NIC, and
the problem occurs in the same way.
I realized that it generates a huge number of interruptions em2 over 200
thousand.
#vmstat -i
interrupt total rate
irq16: em1 12891 40
irq17: em2 546630 1713
irq19: atapci0 5181 16
irq23: ehci0 ehci1 1049 3
cpu0: timer 637069 1997
irq256: em0 1557 4
cpu3: timer 636939 1996
cpu2: timer 636939 1996
cpu1: timer 636938 1996
Total 3115193 9765
Data for debug:
[2.0.3-RELEASE] [root< at >pfsense.localdomain] / root (1): sysctl hw.em
hw.em.eee_setting: 0
hw.em.rx_process_limit: 100
hw.em.enable_msix: 0
hw.em.sbp: 0
hw.em.smart_pwr_down: 0
hw.em.txd: 4096
hw.em.rxd: 4096
hw.em.rx_abs_int_delay: 66
hw.em.tx_abs_int_delay: 66
hw.em.rx_int_delay: 0
hw.em.tx_int_delay: 0
[2.0.3-RELEASE] [root< at >pfsense.localdomain] / root (3): sysctl dev.em.2
dev.em.2.% desc: Intel (R) PRO/1000 Legacy Network Connection 1.0.4
dev.em.2.% driver: in
dev.em.2.% location: slot = 0 function = 1
dev.em.2.% pnpinfo: vendor = 0x8086 device = 0x1079 subvendor = 0x8086
subdevice = 0x1179 class = 0x020000
dev.em.2.% parent: PCI4
dev.em.2.nvm: -1
dev.em.2.rx_int_delay: 0
dev.em.2.tx_int_delay: 0
dev.em.2.rx_abs_int_delay: 66
dev.em.2.tx_abs_int_delay: 66
dev.em.2.rx_processing_limit: 100
dev.em.2.flow_control: 0
dev.em.2.mbuf_alloc_fail: 0
dev.em.2.cluster_alloc_fail: 0
dev.em.2.dropped: 0
dev.em.2.tx_dma_fail: 0
dev.em.2.tx_desc_fail1: 0
dev.em.2.tx_desc_fail2: 0
dev.em.2.rx_overruns: 0
dev.em.2.watchdog_timeouts: 0
dev.em.2.device_control: 1076888137
dev.em.2.rx_control: 32794
dev.em.2.fc_high_water: 47104
dev.em.2.fc_low_water: 45604
dev.em.2.fifo_workaround: 0
dev.em.2.fifo_reset: 0
dev.em.2.txd_head: 243
dev.em.2.txd_tail: 243
dev.em.2.rxd_head: 1374
dev.em.2.rxd_tail: 1373
dev.em.2.mac_stats.excess_coll: 0
dev.em.2.mac_stats.single_coll: 0
dev.em.2.mac_stats.multiple_coll: 0
dev.em.2.mac_stats.late_coll: 0
dev.em.2.mac_stats.collision_count: 0
dev.em.2.mac_stats.symbol_errors: 0
dev.em.2.mac_stats.sequence_errors: 0
dev.em.2.mac_stats.defer_count: 0
dev.em.2.mac_stats.missed_packets: 0
dev.em.2.mac_stats.recv_no_buff: 0
dev.em.2.mac_stats.recv_undersize: 0
dev.em.2.mac_stats.recv_fragmented: 0
dev.em.2.mac_stats.recv_oversize: 0
dev.em.2.mac_stats.recv_jabber: 0
dev.em.2.mac_stats.recv_errs: 0
dev.em.2.mac_stats.crc_errs: 0
dev.em.2.mac_stats.alignment_errs: 0
dev.em.2.mac_stats.coll_ext_errs: 0
dev.em.2.mac_stats.xon_recvd: 0
dev.em.2.mac_stats.xon_txd: 0
dev.em.2.mac_stats.xoff_recvd: 0
dev.em.2.mac_stats.xoff_txd: 0
dev.em.2.mac_stats.total_pkts_recvd: 6681156
dev.em.2.mac_stats.good_pkts_recvd: 6681156
dev.em.2.mac_stats.bcast_pkts_recvd: 17313
dev.em.2.mac_stats.mcast_pkts_recvd: 156511
dev.em.2.mac_stats.rx_frames_64: 1199707
dev.em.2.mac_stats.rx_frames_65_127: 2110104
dev.em.2.mac_stats.rx_frames_128_255: 396 862
dev.em.2.mac_stats.rx_frames_256_511: 196001
dev.em.2.mac_stats.rx_frames_512_1023: 138581
dev.em.2.mac_stats.rx_frames_1024_1522: 2639901
dev.em.2.mac_stats.good_octets_recvd: 4439337234
dev.em.2.mac_stats.good_octets_txd: 15529
dev.em.2.mac_stats.total_pkts_txd: 143
dev.em.2.mac_stats.good_pkts_txd: 143
dev.em.2.mac_stats.bcast_pkts_txd: 104
dev.em.2.mac_stats.mcast_pkts_txd: 39
dev.em.2.mac_stats.tx_frames_64: 48
dev.em.2.mac_stats.tx_frames_65_127: 69
dev.em.2.mac_stats.tx_frames_128_255: 20
dev.em.2.mac_stats.tx_frames_256_511: 6
dev.em.2.mac_stats.tx_frames_512_1023: 0
dev.em.2.mac_stats.tx_frames_1024_1522: 0
dev.em.2.mac_stats.tso_txd: 0
dev.em.2.mac_stats.tso_ctx_fail: 0
#uname -a
FreeBSD pfsense.localdomain 8.1-RELEASE-p13 FreeBSD 8.1-RELEASE-p13 #1: Fri
Apr 12 10:58:43 EDT 2013
root< at >snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8
amd64
# Pciconf-lvc:
em1 < at > pci0: 4:0:0: class = 0x020000 card = 0x11798086 chip = 0x10798086 rev
= 0x03 hdr = 0x00
class = network
subclass = ethernet
cap 01 [dc] = powerspec 2 supports D0 D3 current D0
cap 07 [e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split
transaction
em2 < at > pci0: 4:0:1: class = 0x020000 card = 0x11798086 chip = 0x10798086 rev
= 0x03 hdr = 0x00
class = network
subclass = ethernet
cap 01 [dc] = powerspec 2 supports D0 D3 current D0
cap 07 [e4] = PCI-X 64-bit supports 133MHz, 2048 burst read, 1 split
transaction
dmesg
Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:58:43 EDT 2013
root< at >snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8
amd64
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM) i5-2310 CPU < at > 2.90GHz (2892.73-MHz K8-class CPU)
Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a Stepping =
7
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0x179ae3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,<b17>,SSE4.1,SSE4.2,POPCNT,<b24>,AESNI,XSAVE,<b28>>
AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
AMD Features2=0x1<LAHF>
TSC: P-state invariant
real memory = 8589934592 (8192 MB)
avail memory = 7952838656 (7584 MB)
ACPI APIC Table: <ALASKA A M I>
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
ioapic0 <Version 2.0> irqs 0-23 on motherboard
wlan: mac acl policy registered
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
padlock0: No ACE support.
acpi0: <ALASKA A M I> on motherboard
acpi0: [ITHREAD]
ACPI Error (psargs-0464): [RAMB] Namespace lookup failure, AE_NOT_FOUND
ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW]
(Region) (20100331/nsinit-442)
acpi0: Power Button (fixed)
acpi0: reservation of 67, 1 (4) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on
acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xf000-0xf03f mem
0xf7800000-0xf7bfffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
pci0: <simple comms> at device 22.0 (no driver attached)
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xf7f04000-0xf7f043ff irq 23
at device 26.0 on pci0
ehci0: [ITHREAD]
usbus0: EHCI version 1.0
usbus0: <EHCI (generic) USB 2.0 controller> on ehci0
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib2
em0: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xe000-0xe01f mem
0xf7e20000-0xf7e3ffff,0xf7e00000-0xf7e1ffff irq 16 at device 0.0 on pci2
em0: Using an MSI interrupt
em0: [FILTER]
pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci3
pci4: <ACPI PCI bus> on pcib4
em1: <Intel(R) PRO/1000 Legacy Network Connection 1.0.4> port 0xd040-0xd07f
mem 0xf7d20000-0xf7d3ffff,0xf7cc0000-0xf7cfffff irq 16 at device 0.0 on pci4
em1: [FILTER]
em2: <Intel(R) PRO/1000 Legacy Network Connection 1.0.4> port 0xd000-0xd03f
mem 0xf7d00000-0xf7d1ffff,0xf7c40000-0xf7c7ffff irq 17 at device 0.1 on pci4
em2: [FILTER]
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xf7f03000-0xf7f033ff irq 23
at device 29.0 on pci0
ehci1: [ITHREAD]
usbus1: EHCI version 1.0
usbus1: <EHCI (generic) USB 2.0 controller> on ehci1
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel AHCI controller> port
0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem
0xf7f02000-0xf7f027ff irq 19 at device 31.2 on pci0
atapci0: [ITHREAD]
atapci0: AHCI v1.30 controller with 4 3Gbps ports, PM not supported
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
acpi_button0: <Power Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_tz1: <Thermal Zone> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
atrtc0: Warning: Couldn't map I/O.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
ppc0: cannot reserve I/O port range
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
est2: <Enhanced SpeedStep Frequency Control> on cpu2
p4tcc2: <CPU Frequency Thermal Control> on cpu2
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
est3: <Enhanced SpeedStep Frequency Control> on cpu3
p4tcc3: <CPU Frequency Thermal Control> on cpu3
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
usbus0: 480Mbps High Speed USB v2.0
usbus1: 480Mbps High Speed USB v2.0
ad4: 476940MB <Seagate ST3500418AS CC35> at ata2-master UDMA100 SATA 3Gb/s
ugen0.1: <Intel> at usbus0
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
acd0: DVDR <ATAPI iHAS124 C/LL02> at ata3-master UDMA100 SATA 1.5Gb/s
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Root mount waiting for: usbus1 usbus0
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
Root mount waiting for: usbus1 usbus0
ugen0.2: <vendor 0x8087> at usbus0
uhub2: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on
usbus0
ugen1.2: <vendor 0x8087> at usbus1
uhub3: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on
usbus1
Root mount waiting for: usbus1 usbus0
uhub2: 4 ports with 4 removable, self powered
uhub3: 6 ports with 6 removable, self powered
ugen0.3: <USB> at usbus0
ukbd0: <USB USB Keykoard, class 0/0, rev 1.10/1.10, addr 3> on usbus0
kbd2 at ukbd0
uhid0: <USB USB Keykoard, class 0/0, rev 1.10/1.10, addr 3> on usbus0
Trying to mount root from ufs:/dev/ad4s1a
pflog0: promiscuous mode enabled
em2: link state changed to UP
bridge0: promiscuous mode enabled
pflog0: promiscuous mode disabled
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...0 0 0 done
All buffers synced.
Copyright (c) 1992-2010 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.1-RELEASE-p13 #1: Fri Apr 12 10:58:43 EDT 2013
root< at >snapshots-8_1-amd64.builders.pfsense.org:/usr/obj.pfSense/usr/pfSensesrc/src/sys/pfSense_SMP.8
amd64
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Core(TM) i5-2310 CPU < at > 2.90GHz (2892.72-MHz K8-class CPU)
Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a Stepping =
7
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Features2=0x179ae3bf<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,<b17>,SSE4.1,SSE4.2,POPCNT,<b24>,AESNI,XSAVE,<b28>>
AMD Features=0x28100800<SYSCALL,NX,RDTSCP,LM>
AMD Features2=0x1<LAHF>
TSC: P-state invariant
real memory = 8589934592 (8192 MB)
avail memory = 7952838656 (7584 MB)
ACPI APIC Table: <ALASKA A M I>
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
ioapic0 <Version 2.0> irqs 0-23 on motherboard
wlan: mac acl policy registered
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
padlock0: No ACE support.
acpi0: <ALASKA A M I> on motherboard
acpi0: [ITHREAD]
ACPI Error (psargs-0464): [RAMB] Namespace lookup failure, AE_NOT_FOUND
ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW]
(Region) (20100331/nsinit-442)
acpi0: Power Button (fixed)
acpi0: reservation of 67, 1 (4) failed
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
acpi_hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on
acpi0
Timecounter "HPET" frequency 14318180 Hz quality 900
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
vgapci0: <VGA-compatible display> port 0xf000-0xf03f mem
0xf7800000-0xf7bfffff,0xe0000000-0xefffffff irq 16 at device 2.0 on pci0
pci0: <simple comms> at device 22.0 (no driver attached)
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xf7f04000-0xf7f043ff irq 23
at device 26.0 on pci0
ehci0: [ITHREAD]
usbus0: EHCI version 1.0
usbus0: <EHCI (generic) USB 2.0 controller> on ehci0
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci2: <ACPI PCI bus> on pcib2
em0: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xe000-0xe01f mem
0xf7e20000-0xf7e3ffff,0xf7e00000-0xf7e1ffff irq 16 at device 0.0 on pci2
em0: Using an MSI interrupt
em0: [FILTER]
pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.4 on pci0
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci3
pci4: <ACPI PCI bus> on pcib4
em1: <Intel(R) PRO/1000 Legacy Network Connection 1.0.4> port 0xd040-0xd07f
mem 0xf7d20000-0xf7d3ffff,0xf7cc0000-0xf7cfffff irq 16 at device 0.0 on pci4
em1: [FILTER]
em2: <Intel(R) PRO/1000 Legacy Network Connection 1.0.4> port 0xd000-0xd03f
mem 0xf7d00000-0xf7d1ffff,0xf7c40000-0xf7c7ffff irq 17 at device 0.1 on pci4
em2: [FILTER]
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xf7f03000-0xf7f033ff irq 23
at device 29.0 on pci0
ehci1: [ITHREAD]
usbus1: EHCI version 1.0
usbus1: <EHCI (generic) USB 2.0 controller> on ehci1
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel AHCI controller> port
0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf060-0xf07f mem
0xf7f02000-0xf7f027ff irq 19 at device 31.2 on pci0
atapci0: [ITHREAD]
atapci0: AHCI v1.30 controller with 4 3Gbps ports, PM not supported
ata2: <ATA channel 0> on atapci0
ata2: [ITHREAD]
ata3: <ATA channel 1> on atapci0
ata3: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
acpi_button0: <Power Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_tz1: <Thermal Zone> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
atrtc0: Warning: Couldn't map I/O.
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
ppc0: cannot reserve I/O port range
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
est2: <Enhanced SpeedStep Frequency Control> on cpu2
p4tcc2: <CPU Frequency Thermal Control> on cpu2
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
est3: <Enhanced SpeedStep Frequency Control> on cpu3
p4tcc3: <CPU Frequency Thermal Control> on cpu3
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
usbus0: 480Mbps High Speed USB v2.0
usbus1: 480Mbps High Speed USB v2.0
ad4: 476940MB <Seagate ST3500418AS CC35> at ata2-master UDMA100 SATA 3Gb/s
ugen0.1: <Intel> at usbus0
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
acd0: DVDR <ATAPI iHAS124 C/LL02> at ata3-master UDMA100 SATA 1.5Gb/s
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
Root mount waiting for: usbus1 usbus0
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
Root mount waiting for: usbus1 usbus0
ugen0.2: <vendor 0x8087> at usbus0
uhub2: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on
usbus0
ugen1.2: <vendor 0x8087> at usbus1
uhub3: <vendor 0x8087 product 0x0024, class 9/0, rev 2.00/0.00, addr 2> on
usbus1
uhub2: 4 ports with 4 removable, self powered
uhub3: 6 ports with 6 removable, self powered
Root mount waiting for: usbus0
ugen0.3: <USB> at usbus0
ukbd0: <USB USB Keykoard, class 0/0, rev 1.10/1.10, addr 3> on usbus0
kbd2 at ukbd0
uhid0: <USB USB Keykoard, class 0/0, rev 1.10/1.10, addr 3> on usbus0
Trying to mount root from ufs:/dev/ad4s1a
pflog0: promiscuous mode enabled
em2: link state changed to UP
bridge0: promiscuous mode enabled
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"
</pre>Giorgio Emanuel2013-05-22T03:01:38OpenSSH in -STABLE
http://comments.gmane.org/gmane.os.freebsd.stable/86458
<pre>Hi. Are there any plans to get OpenSSH 6.2 in 9-STABLE? I'd like to
check out the new AES-GCM stuff without going to -CURRENT on this
system. If there are no plans, is there a possibility? Thanks
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"
</pre>usaopp< at >hushmail.com2013-05-22T01:42:39Unexpected reboot/crash on 8.2-RELEASE.
http://comments.gmane.org/gmane.os.freebsd.stable/86449
<pre>I had an unexpected reboot of my Dell R610 today around 2:05-06pm today.
I do not know if it crashed or if it was power cycled.
This machine is running:
FreeBSD gunsight1.neutralgood.org 8.2-RELEASE FreeBSD 8.2-RELEASE #1: Thu Dec 8 21:58:59 UTC 2011 root< at >:/usr/obj/usr/src/sys/GENERIC amd64
It's a stock 8.2-RELEASE kernel except I had to tweak it near the top of
vfs_mountroot() to delay before attempting to mount the root filesystem.
(Without my tweak it attempts to mount root before the USB drive is finished
getting attached.)
The dmesg shows this at the reboot:
mfi0: 24272 (422106527s/0x0020/info) - Patrol Read complete
mfi0: 24273 (422172000s/0x0020/info) - Patrol Read started
mfi0: 24318 (422192750s/0x0020/info) - Patrol Read complete
mfi0: 24319 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028)
mfi0: 24320 (boot + 3s/0x0020/info) - Firmware version 1.22.12-0952
mfi0: 24321 (boot + 3s/0x0020/info) - Firmware initialization started (PCI ID 0060/1000/1f0c/1028)
mfi0: 24322 (boot + 3s/0x0020/info) - Firmware version 1.22.12-0952
Does this mean the machine did not lose power? I ask because my datacenter
had some sort of power incident and I'm not sure if the server lost power
or not. But if the kernel message buffer from before the incident is still
present then the machine never lost power, correct? The datacenter's power
incident I'm told happened somewhere around the time of the reboot so I
have to ask.
It looks like I didn't have dumps enabled. That's ... not helpful.
The machine has been stable for:
2:05PM up 472 days, 21 mins, 7 users, load averages: 0.01, 0.02, 0.00
http://www.neutralgood.org/~kpn/dmesg.boot
Here's various stats I usually keep displayed. This is the last from
before the reboot:
http://www.neutralgood.org/~kpn/status.txt
I've got all the power savings features turned off in the BIOS and, like
I said, the machine has been stable for all this time. However, one thing
to note from a couple of days ago:
May 14 00:49:13 gunsight1 -- MARK --
May 14 01:00:45 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 35 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 65 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 95 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 125 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 155 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 185 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 215 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 245 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 275 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 305 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 335 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 365 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 395 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 425 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 455 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 485 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 515 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 545 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 575 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 605 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 635 SECONDS
May 14 01:11:36 gunsight1 kernel: mfi0: COMMAND 0xffffff80009d1310 TIMEOUT AFTER 665 SECONDS
May 14 01:19:36 gunsight1 -- MARK --
May 14 01:39:36 gunsight1 -- MARK --
May 14 01:59:37 gunsight1 -- MARK --
May 14 02:10:55 gunsight1 kernel: mfi0: 24089 (421826400s/0x0020/info) - Patrol Read started
</pre>kpneal< at >pobox.com2013-05-19T01:45:21Is there a library issue between 9.0 and 9.1 -ThreadRuneLocale ?
http://comments.gmane.org/gmane.os.freebsd.stable/86448
<pre>Cannot update my ports. Run portsnap followed by
portmaster -a and various ports will not update.
Keep getting error msg of
Undefined symbol: "_ThreadRuneLocale"
This happens for instance in updating to png-1.5.15 or
to freetype2.
Are there library issues between 9.0 and 9.1?
I am running 9.0-stable on an i386
Last time I updated was in March and that went well.
Do I need to uninstall all my ports and start over?
Do I need to move up to 9.1?
</pre>Michael Gass2013-05-18T18:49:09Command line not responding
http://comments.gmane.org/gmane.os.freebsd.stable/86438
<pre>Running 9.0-Stable on an i386.
Whenever I type a command at the prompt I get
the output
/usr/local/lib/libintl.so.9: Undefined symbol "_ThreadRuneLocale"
and nothing else - the command will not run. Just the
above output. Commands like "ls" and "exit" work, but not much
else. This happends whether I am logged in a user or as root.
Cannot even halt the system from the command line.
Started to happen after trying to update the freetype2 port.
Got an error msg while updating libXft-2.1.14. From that point
on I cannot use the command line.
I have no idea what to try. Any suggestions.
</pre>Michael Gass2013-05-17T17:56:53[HEADS UP] New pkgng git location
http://comments.gmane.org/gmane.os.freebsd.stable/86430
<pre>Pkg has moved from http://github.com/pkgng/pkgng to
http://github.com/freebsd/pkg
Please update any links or git checkouts you have.
You can update your git checkout with:
</pre>Bryan Drewery2013-05-17T01:43:23still mbuf leak in 9.0 / 9.1?
http://comments.gmane.org/gmane.os.freebsd.stable/86421
<pre>Hi list,
since we activated 10gbe on ixgbe cards + jumbo frames(9k) on 9.0 and now on 9.1 we recognize that after a random period of time, sometimes a week, sometimes only a day, the
system doesn't send any packets out. The phenomenon is that you can't login via ssh, nfs and istgt is not operative. Yet you can login on the console and execute commands.
A clean shutdown isn't possible though. It hangs after vnode cleaning, normally you would see detaching of usb devices here, or other devices maybe?
I've read the other post on this ML about mbuf leak in the arp handling code in if_ether.c line 558. We don't see any of those notices in dmesg so I don't think that glebius fix would apply for us.
I'm collecting system and memory information every hour.
Script looks like this.
less /etc/periodic/hourly/100.report-memory.sh
#!/bin/sh
reporttimestamp=`date +%d-%m-%Y-%H-%M`
reportname=${reporttimestamp}.txt
cd /root/memory-mon
top -b > $reportname
echo "" >> $reportname
vmstat -m >> $reportname
echo "" >> $reportname
vmstat -z >> $reportname
echo "" >> $reportname
netstat -Q >> $reportname
echo "" >> $reportname
netstat -n -x >> $reportname
echo "" >> $reportname
netstat -m >> $reportname
/usr/bin/perl /usr/local/bin/zfs-stats -a >> $reportname
When you grep for mbuf or mbuf usage you will see this for example:
root< at >freenas:/root/memory-mon #grep mbuf_packet: *
14-05-2013-14-09.txt:mbuf_packet: 256, 0, 9246, 2786,201700429, 0, 0
14-05-2013-15-09.txt:mbuf_packet: 256, 0, 9256, 2776,201773122, 0, 0
14-05-2013-16-09.txt:mbuf_packet: 256, 0, 9266, 2766,201871553, 0, 0
14-05-2013-17-09.txt:mbuf_packet: 256, 0, 9276, 2756,201915405, 0, 0
14-05-2013-18-09.txt:mbuf_packet: 256, 0, 9286, 2746,201927956, 0, 0
14-05-2013-19-09.txt:mbuf_packet: 256, 0, 9296, 2352,201935681, 0, 0
14-05-2013-20-09.txt:mbuf_packet: 256, 0, 9306, 2342,201943754, 0, 0
14-05-2013-21-09.txt:mbuf_packet: 256, 0, 9316, 2332,201950961, 0, 0
14-05-2013-22-09.txt:mbuf_packet: 256, 0, 9326, 2450,201958150, 0, 0
14-05-2013-23-09.txt:mbuf_packet: 256, 0, 9336, 2440,201967178, 0, 0
15-05-2013-00-09.txt:mbuf_packet: 256, 0, 9346, 2430,201974561, 0, 0
15-05-2013-01-09.txt:mbuf_packet: 256, 0, 9356, 2420,201982105, 0, 0
15-05-2013-02-09.txt:mbuf_packet: 256, 0, 9366, 2410,201989463, 0, 0
15-05-2013-03-09.txt:mbuf_packet: 256, 0, 9378, 1502,203019168, 0, 0
15-05-2013-04-09.txt:mbuf_packet: 256, 0, 9384, 1624,205953601, 0, 0
15-05-2013-05-09.txt:mbuf_packet: 256, 0, 9394, 1870,205959258, 0, 0
15-05-2013-06-09.txt:mbuf_packet: 256, 0, 9404, 2500,205969396, 0, 0
15-05-2013-07-09.txt:mbuf_packet: 256, 0, 9414, 3386,207945161, 0, 0
15-05-2013-08-09.txt:mbuf_packet: 256, 0, 9424, 3376,208094689, 0, 0
15-05-2013-09-09.txt:mbuf_packet: 256, 0, 9434, 2982,208172465, 0, 0
15-05-2013-10-09.txt:mbuf_packet: 256, 0, 9444, 3100,208270369, 0, 0
and
root< at >freenas:/root/memory-mon #grep "mbufs in use" *
14-05-2013-14-09.txt:58444/5816/64260 mbufs in use (current/cache/total)
14-05-2013-15-09.txt:58455/5805/64260 mbufs in use (current/cache/total)
14-05-2013-16-09.txt:58464/5796/64260 mbufs in use (current/cache/total)
14-05-2013-17-09.txt:58475/5785/64260 mbufs in use (current/cache/total)
14-05-2013-18-09.txt:58484/5776/64260 mbufs in use (current/cache/total)
14-05-2013-19-09.txt:58493/5767/64260 mbufs in use (current/cache/total)
14-05-2013-20-09.txt:58503/5757/64260 mbufs in use (current/cache/total)
14-05-2013-21-09.txt:58513/5747/64260 mbufs in use (current/cache/total)
14-05-2013-22-09.txt:58523/5737/64260 mbufs in use (current/cache/total)
14-05-2013-23-09.txt:58533/5727/64260 mbufs in use (current/cache/total)
15-05-2013-00-09.txt:58543/5717/64260 mbufs in use (current/cache/total)
15-05-2013-01-09.txt:58554/5706/64260 mbufs in use (current/cache/total)
15-05-2013-02-09.txt:58563/5697/64260 mbufs in use (current/cache/total)
15-05-2013-03-09.txt:58639/5621/64260 mbufs in use (current/cache/total)
15-05-2013-04-09.txt:58581/5679/64260 mbufs in use (current/cache/total)
15-05-2013-05-09.txt:58591/5669/64260 mbufs in use (current/cache/total)
15-05-2013-06-09.txt:58602/5658/64260 mbufs in use (current/cache/total)
15-05-2013-07-09.txt:58613/5647/64260 mbufs in use (current/cache/total)
15-05-2013-08-09.txt:58623/6027/64650 mbufs in use (current/cache/total)
15-05-2013-09-09.txt:58634/6016/64650 mbufs in use (current/cache/total)
15-05-2013-10-09.txt:58645/6005/64650 mbufs in use (current/cache/total)
This increasing number of used mbuf_packets and mbufs in use makes me nervous.
See the complete reports http://knownhosts.org:/reports-14-15.tgz
Thanks for help,
-dennis
--------------BEGIN System information---------------
It's a stock FreeBSD 9.1, yet the hostname is called freenas. Don't be confused.
igb0: flags=8c02<BROADCAST,OACTIVE,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
ether 00:25:90:34:c1:12
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
igb1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
ether 00:25:90:34:c1:13
inet 172.16.1.6 netmask 0xfffff000 broadcast 172.16.15.255
inet6 fe80::225:90ff:fe34:c113%igb1 prefixlen 64 scopeid 0x2
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
ix0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
ether 00:1b:21:cc:12:8b
inet 10.254.254.242 netmask 0xfffffffc broadcast 10.254.254.243
inet6 fe80::21b:21ff:fecc:128b%ix0 prefixlen 64 scopeid 0xb
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect (10Gbase-Twinax <full-duplex>)
status: active
ix1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
ether 00:1b:21:cc:12:8a
inet 10.254.254.254 netmask 0xfffffffc broadcast 10.254.254.255
inet6 fe80::21b:21ff:fecc:128a%ix1 prefixlen 64 scopeid 0xc
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect (10Gbase-Twinax <full-duplex>)
status: active
ix2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 9000
options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
ether 00:1b:21:cc:12:b3
inet 10.254.254.246 netmask 0xfffffffc broadcast 10.254.254.247
inet6 fe80::21b:21ff:fecc:12b3%ix2 prefixlen 64 scopeid 0xd
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: no carrier
ix3: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=401bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,VLAN_HWTSO>
ether 00:1b:21:cc:12:b2
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect
status: no carrier
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0xf
inet 127.0.0.1 netmask 0xff000000
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
#dmesg
…..
mfi0: 21294 (421879975s/0x0008/info) - Battery started charging
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
ix1: link state changed to DOWN
ix1: link state changed to UP
I should add that the servers that are directly connected to this freebsd server reboot every night. This is why you see ix0 UP/DOWN
messages in dmesg.
------------- END System information------------
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"</pre>dennis berger2013-05-15T09:00:23FreeBSD Quarterly Status Report, January-March 2013
http://comments.gmane.org/gmane.os.freebsd.stable/86420
<pre>FreeBSD Quarterly Status Report, January-March 2013
Introduction
This report covers FreeBSD-related projects between January and March
2013. This is the first of four reports planned for 2013.
Highlights from this status report include the busy preparations of
8.4-RELEASE, restoration of binary package building, steady progress of
several porting efforts, like work on the FreeBSD ports of xorg, GNOME,
KDE, and Xfce, bringing FreeBSD to Cubieboard and Hackberry boards,
development of ARM and AMD GPU support, improving performance of
UFS/FFS and callouts, and introducing a multipath TCP implementation
for the network stack.
Thanks to all the reporters for the excellent work! This report
contains 31 entries and we hope you enjoy reading it.
The deadline for submissions covering the period between April and June
2013 is July 7th, 2013.
__________________________________________________________________
Projects
* FreeNAS
* Kernel Information in Process Core Dumps
* Native iSCSI Stack
FreeBSD Team Reports
* FreeBSD Bugmeister Team
* FreeBSD Core Team
* FreeBSD Port Managers
* FreeBSD Postmaster Team
* FreeBSD Release Engineering Team
Kernel
* AMD GPU Kernel Mode-Setting (KMS) Support
* Atomic "close-on-exec"
* callout(9) Improvements
* Multipath TCP (MPTCP) for FreeBSD
* racct: Block IO Accounting
* Read-only Port of NetBSD's UDF File System
* TCP-AO Authentication Option
* UFS/FFS Performance Work
Documentation
* Improving the Documentation Project Infrastructre
* The entities Documentation Branch
* The FreeBSD Japanese Documentation Project
Architectures
* FreeBSD on Cubieboard
* FreeBSD/arm Superpages for ARMv7
* FreeBSD/ARM Toolchain Improvements
Ports
* FreeBSD Haskell Ports
* GNOME/FreeBSD
* KDE/FreeBSD
* PyPy
* Wine32 on FreeBSD/amd64
* Xfce/FreeBSD
* xorg on FreeBSD
Miscellaneous
* BXR.SU -- Super User's BSD Cross Reference
* mdoc.su -- Short Manual Page URLs
__________________________________________________________________
AMD GPU Kernel Mode-Setting (KMS) Support
URL: https://wiki.freebsd.org/AMD_GPU
Contact: Jean-Sébastien Pédron <dumbbell< at >FreeBSD.org>
Contact: J.R. Oldroyd <jr< at >opal.com>
Contact: Konstantin Belousov <kib< at >FreeBSD.org>
The project progressed well since February:
* Konstantin committed is TTM port to 10-CURRENT.
* With the help of John Baldwin (jhb) and Andriy Gapon (avg), the
Video BIOS situation greatly improved: the radeonkms driver reads
the BIOS shadow copy if the video card is the primary one, or query
the PCI expansion ROM otherwise. In the end, this code will be
probably committed to the PCI driver so that other video drivers
benefit from it.
* Andriy also reported several problems with the I2C code. Now that
they are fixed, the monitors plugged into DVI and HDMI connectors
are detected and their EDID is read correctly. VGA connector is not
tested so far.
* There is a locking problem in either TTM or the Radeon driver which
prevents OpenGL from working properly. Jean-Sébastien is currently
tracking this down.
* J.R. Oldroyd started to work on a 9-STABLE backport of the driver
which is now working quite well. He had to backport some features
from the VM which may need further refinement by the VM folks.
Yakaz lended Jean-Sébastien a computer which allows him to test a
RV630-based discrete card and, in the future, other PCIe cards. Several
users already kindly tested the driver. Big thanks to all those
contributors!
In its current state, the driver allows to have a simple X session (no
OpenGL), run common applications, watch movies, change the resolution
and enable additional monitors with xrandr(1). The most blocking issue
now is the OpenGL deadlock which prevents to run modern
compositors/desktop environment, games and WebGL demos. We are not
ready for a "Call For Testers" yet.
Open tasks:
1. Test multiple cards configurations for Video BIOS issues,
especially Intel integrated card + Radeon discrete card, and AMD
integrated card (IGP) + Radeon discrete card. No need to check
configurations with one shared connector though, it is not
supported right now.
__________________________________________________________________
Atomic "close-on-exec"
URL: https://wiki.freebsd.org/AtomicCloseOnExec
Contact: Jilles Tjoelker <jilles< at >FreeBSD.org>
If threads or signal handlers call fork() and exec(), file descriptors
may be passed undesirably to child processes, which may lead to hangs
(if a pipe is not closed), exceeding the file descriptor limit and
security problems (if the child process has lower privilege). One
solution is various new APIs that set the "close-on-exec" flag
atomically with allocating a file descriptor. Some existing software
will use the new features if present or will even refuse to compile
without them.
Various parts have been present for some time.
In first quarter of 2013, extensions to recvmsg(), socket(),
socketpair() and posix_openpt() have been added.
__________________________________________________________________
BXR.SU -- Super User's BSD Cross Reference
URL: http://bxr.su/
URL: http://lists.freebsd.org/pipermail/freebsd-hackers/2013-April/042334.html
Contact: Constantine A. Murenin <cnst++< at >FreeBSD.org>
Super User's BSD Cross Reference (BXR.SU) is a new source-code search
engine that covers the complete kernel and non-GNU userland source
trees of FreeBSD, NetBSD, OpenBSD, and DragonFly BSD.
BXR.SU is optimised to be very fast, has daily updates of all the
trees, and also acts as a deterministic URL shortener.
BXR.SU is based on an OpenGrok fork, but it is more than just OpenGrok.
We have fixed a number of annoyances, eliminated features that just
never worked right from the outright, and provided integration with
tools like CVSweb (including great mirrors like allbsd.org), FreeBSD's
ViewVC (SVN), as well as GitHub and Gitweb from git.freebsd.your.org,
plus a tad of other improvements, including a complete rewrite of an
mdoc parser. Last, but definitely not least, is an extensive set of
nginx rewrite rules that makes it a breeze to use BXR.SU as a
deterministic URL compactor for referencing BSD source code. For
example, the http://bxr.su/f/kern/sched_ule.c URL will automatically
redirect to http://bxr.su/FreeBSD/sys/kern/sched_ule.c through nginx.
Note that according to the release schedule of BXR.SU, there is no IPv4
glue until 2013-04-24; otherwise, the service is available via both
IPv4 and IPv6. See the 2013-04-01 announcement on the freebsd-hackers
mailing list for more details.
Open tasks:
1. Find up-to-date git repositories (served with Gitweb) of NetBSD and
OpenBSD.
2. Find a Gitweb mirror of FreeBSD that is faster than GitHub and
Gitorious.
__________________________________________________________________
callout(9) Improvements
URL: http://people.freebsd.org/~davide/asia/callout_paper.pdf
URL: http://people.freebsd.org/~davide/asia/calloutng.pdf
URL: http://svnweb.freebsd.org/base?view=revision&revision=247777
Contact: Davide Italiano <davide< at >FreeBSD.org>
Contact: Alexander Motin <mav< at >FreeBSD.org>
In FreeBSD, timers are provided by the callout facility, which allows
to register a function with an argument to be called at specified
future time. The subsystem suffered of some problems, such as the
impossibility of handling high-resolution events or its inherent
periodic structure, which may lead to spurious wakeups and higher power
consumption. Some consumers, such as high-speed networking, VoIP and
other real-time applications need a better precision than the one
currently allowed. Also, especially with the ubiquity of laptops in the
last years, the energy wasted by interrupts waking CPUs from sleep may
be a sensitive factor. Recent changes in the subsystem addressed those
long-standing issues as well as introduced a new programming interface
to take advantage of the new features.
Open tasks:
1. Evaluating if it is worth to migrate any of the other callout(9)
consumers to the new interface.
2. Move callout consumers still using the legacy timeout()/untimeout()
interface to callout_*() in order to get rid of redundant code and
clean up KPI.
__________________________________________________________________
FreeBSD Bugmeister Team
Contact: Eitan Adler <eadler< at >FreeBSD.org>
Contact: Gavin Atkinson <gavin< at >FreeBSD.org>
Contact: Oleksandr Tymoshenko <gonzo< at >FreeBSD.org>
The FreeBSD Bugmeister Team are continuing to evaluate options for
alternate bug trackers and have narrowed their choices to two
possibilities: Bugzilla and roundup.
The number of non-ports PRs have remained relatively static over the
last three months, with as many coming in as being closed. The number
of ports PRs have increased recently, largely due to the ports freeze
for the upcoming 8.4-RELEASE.
The Bugmeister team continue work on trying to make the contents of the
GNATS PR database cleaner, more accessible and easier for committers to
find and resolve PRs, by tagging PRs to indicate the areas involved,
and by ensuring that there is sufficient info within each PR to resolve
each issue.
As always, anybody interested in helping out with the PR queue is
welcome to join us in #freebsd-bugbusters on EFnet. We are always
looking for additional help, whether your interests lie in triaging
incoming PRs, generating patches to resolve existing problems, or
simply helping with the database housekeeping (identifying duplicate
PRs, ones that have already been resolved, etc). This is a great way of
getting more involved with FreeBSD!
Open tasks:
1. Finalize the decision of which new bug tracker to use.
2. Get more users involved with triaging PRs as they come in.
3. Assist committers with closing PRs.
__________________________________________________________________
FreeBSD Core Team
Contact: Core Team <core< at >FreeBSD.org>
At the end of 2012, the Core Team approved using Google Analytics on
the Project web site to enable the Documentation Engineering Team to
collect statistics on its usage for better profiling. In the first
quarter of 2013, the Core Team worked with the Documentation
Engineering Team to finalize the associated policies.
Due to some debates around the political correctness of quotes added
for the fortune(6) utility, the corresponding data file has been
removed from the base system in -CURRENT.
In light of the security incident, the liaison role between the Core
Team and the Security Team has been restored, with Gavin Atkinson
assuming this role. The Core Team work hard on resolving the current
situation of the binary package building cluster and the associated
security problems in tight cooperation with the Ports Management Team,
Cluster Administators, and the FreeBSD Foundation Board. The compromise
page is kept updated on the results.
The FreeBSD Project submitted an application for Google Summer of Code
this year again.
There was access granted for 2 new committers and 1 commit bit was
taken for safekeeping in this quarter.
__________________________________________________________________
FreeBSD Haskell Ports
URL: http://wiki.freebsd.org/Haskell
URL: https://github.com/freebsd-haskell/freebsd-haskell/
Contact: Gábor Páli <pgj< at >FreeBSD.org>
Contact: Ashish Shukla <ashish< at >FreeBSD.org>
We are proud to announce FreeBSD Haskell Team has updated existing
ports to their latest stable versions. We also added number of new
ports, which brings the count of Haskell ports in FreeBSD ports tree to
more than 400, featuring many popular software, e.g. xmonad, git-annex,
pandoc or various web framework implementations. All of these updates
will be available as part of the upcoming 8.4-RELEASE. We also came to
know that Haskell ports are also being used successfully on
DragonFlyBSD's dports tree.
In our development repository, there was some optional support added
for LLVM-based code generation using the GHC LLVM backend. This works
mostly on FreeBSD too, though some of the ports would need fixing so it
is still considered experimental.
Open tasks:
1. Try to build GHC with clang (as system compiler).
2. Commit pending Haskell ports to the FreeBSD ports tree.
3. Add more ports to the Ports Collection.
__________________________________________________________________
FreeBSD on Cubieboard
Contact: Ganbold Tsagaankhuu <ganbold< at >FreeBSD.org>
Contact: Oleksandr Tymoshenko <gonzo< at >FreeBSD.org>
Initial support of Allwinner A10 SoC is committed to -CURRENT. FreeBSD
is now running on boards such as Cubieboard, Hackberry and it supports
following peripherals:
* USB EHCI
* GPIO
Open tasks:
1. Get EMAC Ethernet driver working. Need more help from network
driver experts.
2. Implement more drivers.
__________________________________________________________________
FreeBSD Port Managers
URL: http://www.FreeBSD.org/ports/
URL: http://www.freebsd.org/doc/en/articles/contributing-ports/
URL: http://portsmon.freebsd.org/
URL: http://www.freebsd.org/portmgr/
URL: http://blogs.freebsdish.org/portmgr/
URL: http://www.twitter.com/freebsd_portmgr/
URL: http://www.facebook.com/portmgr
Contact: Thomas Abthorpe <portmgr-secretary< at >FreeBSD.org>
Contact: Port Management Team <portmgr< at >FreeBSD.org>
The ports tree contains approximately 24,300 ports, while the PR count
still is close to 1600.
In the first quarter we added 4 new committers, took in 1 commit bit
for safe keeping, and re-instated 1 commit bit.
In February, Mark Linimon (linimon) stepped down from his duties in the
team. Mark had been the longest serving member of the team. Mark had
spent many long hours refactoring and documenting the portbuild
software to ensure that pointyhat services could be restored.
After a security review, redports.org was turned back on, restoring
Tinderbox services to contributors, along with post commit QATs. In
addition, pointyhat infrastructure had also undergone a review and work
begain on restoring the package build system.
Erwin Lansing (erwin) and Martin Wilke (miwi) took on the principle
roles of getting the portbuild software installed and running on
pointyhat. As a result of all their hard work, portmgr< at > was finally
able to resume doing -exp runs, preparing packages for the upcoming 8.4
release, as well as getting a set of 9.1 packages retroactively
prepared.
After many long years of being the defacto standard for the Project,
CVS support for the ports tree officially ended on February 28.
The ports tree was tagged with RELEASE_7_EOL, to coincide with the end
of life for FreeBSD 7.X.
Beat Gaetzi (beat) stepped down from his duties on portmgr< at > in March.
Among his notable contributions, was the task of migrating the Ports
Tree from the old CVS repo to Subversion.
Bryan Drewery (bdrewery) joined the Ports Management team in March,
bringing with him his wealth of knowledge and skill from maintaining
portupgrade, portmaster, assisting with pkgng, as well as co-developing
poudriere.
Open tasks:
1. Most ports PRs are assigned, we now need to focus on testing,
committing and closing.
__________________________________________________________________
FreeBSD Postmaster Team
Contact: David Wolfskill <postmaster< at >FreeBSD.org>
In the first quarter of 2013, the FreeBSD Postmaster Team has
implemented the following items that may be interest of the general
public:
* Changes in configuration of Mailman-managed lists: allow to accept
the application/pkcs7-signature MIME type (in addition to the
application/x-pkcs7-signature MIME type), thus permitting S/MIME
signatures on list mail.
* New lists: freebsd-ops-announce -- announcements of infrastructure
issues, and freebsd-pkg -- discussion of binary package management
and package tools.
__________________________________________________________________
FreeBSD Release Engineering Team
URL: http://www.freebsd.org/releases/8.4R/schedule.html
Contact: FreeBSD Release Engineering Team <re< at >FreeBSD.org>
FreeBSD 8.4-RC1 just got out the door and we are planning RC2. A couple
of critical fixes have come in that will be included in RC2. The
schedule has slipped about 10 days so far. We are expecting the final
release by the end of April. Packages for 8.4 have been provided by a
fully operational package building cluster.
__________________________________________________________________
FreeBSD/arm Superpages for ARMv7
URL: http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf
URL: https://wiki.freebsd.org/ARMSuperpages
URL: https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git
Contact: Zbigniew Bodek <zbb< at >semihalf.com>
Contact: Grzegorz Bernacki <gjb< at >semihalf.com>
Contact: Rafał Jaworowski <raj< at >semihalf.com>
ARM architecture is more and more prevailing, not only in the mobile
and embedded space. Among the more interesting industry trends emerging
in the recent months has been the "ARM server" concept. Some top-tier
companies started developing systems like this already (Dell, HP).
Key to FreeBSD success in these new areas are sophisticated features,
among them are superpages.
The objective of this project is to provide FreeBSD/arm with the
superpages support, which will allow for efficient use of TLB
translations (enlarge TLB coverage), leading to improved performance in
many applications and scalability. Indicated functionality is intended
to work on ARMv7-based processors, however compatibility with ARMv6
will be preserved.
Current support status:
* Port of the pv_entry allocator.
* Switch to "AP[2:1]" access permissions model.
* PTE-based, page-referenced/modified emulation.
* Fixes regarding page replacement strategy.
* Code optimizations and bug fixes.
Next steps:
* Dirty pages management.
* Gradual integration to FreeBSD -CURRENT.
* Further pmap optimizations.
* Fragmentation control management.
* Testing and benchmarking.
Open tasks:
1. Support for multiple page sizes.
2. Implementation of page promotion, demotion and eviction mechanisms.
__________________________________________________________________
FreeBSD/ARM Toolchain Improvements
Contact: Andrew Turner <andrew< at >FreeBSD.org>
Clang has been made the default compiler on ARM. A number of issues
with LLVM and clang have been found, reported, and fixed upstream.
An issue where some ARM EABI applications compiled with clang crash has
been reported upstream with a patch and will be brought into the
FreeBSD tree when it is accepted. The only other issue blocking moving
to the ARM EABI is C++ exceptions fail to work correctly with shared
objects. This will need us to either import libunwind or implement the
functions libgcc_s requires to find the correct unwind table.
Open tasks:
1. Fix exception handling for EABI.
__________________________________________________________________
FreeNAS
URL: http://www.FreeNAS.org/
Contact: Alfred Perlstein <alfred< at >FreeBSD.org>
Contact: Josh Paetzel <jpaetzel< at >FreeBSD.org>
FreeNAS 8.3.1-RELEASE-p2 will hit Sourceforge the second week of April,
and should end up as the last FreeNAS release based on FreeBSD 8.X It's
currently the only Free Open Source NAS product available with any form
of ZFS encryption (provided by GELI).
Open tasks:
1. The team is hard at work on getting a FreeBSD 9.X-based release of
FreeNAS ready. Currently there are several nightly snapshots
available.
2. Add HAST to the webinterface.
3. Migrate to NFSv4.
4. Integrate foundation sponsored kernel iSCSI target.
__________________________________________________________________
GNOME/FreeBSD
URL: http://www.freebsd.org/gnome
URL: http://www.freebsd.org/gnome/docs/develfaq.html
URL: http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom
URL: https://github.com/jlmess77/mate-ports
Contact: FreeBSD GNOME team <gnome< at >FreeBSD.org>
The GNOME/FreeBSD Team has recently merged Glib 2.34, Gtk+ 2.24.17 and
Gtk+ 3.6.4 into ports, the C++ bindings also have got updates. In
additional "low-level" GNOME ports received updates, like libsoup,
gobject-introspection, atk and vala for example. The telepathy stack
and empathy where also updated.
The USE_GNOME macro has received support for :run and :build targets
thanks to Jeremy Messenger (mezz). Currently only libxml2 and libxslt
support these targets.
USE_GNOME=pkgconfig is being deprecated in favor of
USE_PKGCONFIG=build. The former also adds a run dependency on
pkg-config, which is not required. A first pass was done to get rid of
this in the Glib update to 2.34. In cooperation with the X11 Team, the
usage of USE_GNOME=pkgconfig in X components will be removed. After the
fallout from this is handled and stranglers are converted, the
USE_GNOME option will be removed.
In addition USE_GNOME=gnomehack is deprecated and should not be used.
Please replace it with USES=pathfix.
The GNOME development repository has switched from CVS to SVN. CVS will
not get any more updates. Uses can get a new version of the marcusmerge
script that supports SVN from its home page, and should remove the old
CVS checkout "ports" dir.
* SVN anonymous root: svn://creme-brulee.marcuscom.com/ or
svn://sushi.marcuscom.com/ (IPv6)
* ViewVC: http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom
On-going efforts:
* glib 2.36, pango 1.34.0, gtk 3.8.0 and gobject-introspection 1.36.0
where updated in the GNOME development repository.
* Gustau Perez i Querol stepped up and started work on updating the
old GNOME 3.4 ports to 3.6. At the moment of writing these are not
available in the GNOME development repository just yet. For his
efforts, he was awarded a FreeBSD GNOME team membership.
* Jeremy Messenger (mezz) has completed Mate 1.6 which will be
arriving in ports near you when deemed stable enough.
If you want to help with keeping the documentation updated or helping
out in other ways, even if it only parts for the Glib/Gtk/GNOME stack
you are interested in, please contact us!
Open tasks:
1. Update the FreeBSD.org/gnome website, in particular the developer
information about USE_GNOME, maybe put that section in the Porter's
Handbook instead.
2. Merge more updated ports from MC to ports.
3. Testing latest Glib/Gtk releases with existing ports, and import it
into ports when it is ready.
4. After porting GNOME 3.6 run tests and fix bugs.
__________________________________________________________________
Improving the Documentation Project Infrastructre
URL: http://svnweb.freebsd.org/doc/projects/xml-tools/
Contact: Gábor Kövesdán <gabor< at >FreeBSD.org>
There is an on-going work to improve the documentation infrastructure
and modernize our documentation toolchain. The work can be found in the
xml-tools branch and is very near to completion. The improvements
include the following:
* Upgrade to DocBook 4.5.
* Use XSLT instead of DSSSL to render XHTML-based output.
* Generate PDF from PS and simplify image processing.
* Fix make lint and validate the whole documentation set.
* Fix rendering of TOC elements.
* Fix misused link elements that resulted in a corrupt rendering.
* Use more human-friendly publication data and release info
rendering.
* Add support for XInclude in DocBook documents.
* Add support for profiling with attributes.
* Add support for Schematron constraints.
* Add experimental epub support.
* Add experimental support for XSL-FO-based printed output.
* Clean up obsolete SGML constructs.
* Clean up catalogs.
* Drop HTML Tidy since it is not needed any more.
The changes eliminate some dependencies and switch the doc repository
to a real XML toolchain with proper validation and more advanced
rendering tools. The only exceptions are Jade and the DSSSL
stylesheets, which are still needed for printed output.
Open tasks:
1. Fix rendering problems with images in printed formats.
2. Update the Documentation Primer to reflect changes.
__________________________________________________________________
KDE/FreeBSD
URL: http://FreeBSD.kde.org
URL: http://FreeBSD.kde.org/area51.php
Contact: KDE FreeBSD <kde< at >FreeBSD.org>
The KDE/FreeBSD Team is very proud to have Schaich Alonso (aschai)
joining the team. Welcome!
The KDE/FreeBSD Team have continued to improve the experience of KDE
software and Qt under FreeBSD. The latest round of improvements
include:
* Fix problems establishing UDP connections.
The Team have also made many releases and upstreamed many fixes and
patches. The latest round of releases include:
* KDE SC: 4.9.5, 4.10.1 (ports)
* Qt: 5.0.0 (area51) and 4.8.4 (ports)
* PyQt: 4.9.6 (ports); QScintilla 2.7 (ports); SIP: 4.14.2 (area51)
and 4.14.3 (ports)
* KDevelop: 4.4.1 (ports); KDevPlatform: 1.4.1 (ports)
* Calligra: 2.5.5, 2.6.2 (ports)
* Amarok: 2.7.0
* CMake: 2.8.10.2
* Digikam (and KIPI-plugins): 3.1.0 (area51)
* QtCreator: 4.6.1 (ports)
* KDE Telepathy 0.6.0 (area51)
* many smaller ports
As a result -- according to PortScout -- we have 431 ports, of which
93.5% (from 91%) are up-to-date.
The Team are always looking for more testers and porters so please
contact us and visit our home page.
Open tasks:
1. Updating out-of-date ports, see PortScout for a list.
__________________________________________________________________
Kernel Information in Process Core Dumps
Contact: Mikolaj Golub <trociny< at >freebsd.org>
When doing postmortem analysis of a crashed process it is sometimes
very useful to have kernel information about the process at the moment
of the crash, like open file descriptors or resource limits. For a live
process this information can be obtained via sysctl(3) interface e.g.
using procstat(1).
The aim of the project is to add additional notes to a process core
dump, which include process information from the kernel at the moment
of the process crash, teach libprocstat(3) to extract this information
and make procstat(1) use this functionality.
At the moment all necessary code changes are committed to HEAD and are
going to be merge to stable/9 in 1 month.
__________________________________________________________________
mdoc.su -- Short Manual Page URLs
URL: http://mdoc.su/
URL: http://nginx.conf.mdoc.su/mdoc.su.nginx.conf
URL: https://github.com/cnst/mdoc.su
URL: http://lists.freebsd.org/pipermail/freebsd-doc/2013-February/021465.html
Contact: Constantine A. Murenin <cnst++< at >FreeBSD.org>
mdoc.su is a deterministic URL shortener for BSD manual pages, written
entirely in nginx.conf.
Since the original announcement, OS version support has been added
(e.g. /f91/ and /FreeBSD-9.1/ etc.), as well as dynamic multi-flavour
web-pages with multiple links (e.g. http://mdoc.su/f,d/ifnet.9 and
http://mdoc.su/-/mdoc), which even let you specify the versions too
(e.g. http://mdoc.su/f91,n60,o52,d/mdoc).
The source code for the whole site is available under a BSD licence.
Open tasks:
1. Fork it on GitHub (see links)!
__________________________________________________________________
Multipath TCP (MPTCP) for FreeBSD
URL: http://caia.swin.edu.au/urp/newtcp/mptcp/tools.html
URL: http://caia.swin.edu.au/newtcp/mptcp/
URL: http://caia.swin.edu.au/reports/130424A/CAIA-TR-130424A.pdf
URL: https://pub.allbsd.org/FreeBSD-snapshots/
Contact: Nigel Williams <njwilliams< at >swin.edu.au>
Contact: Lawrence Stewart <lastewart< at >swin.edu.au>
Contact: Grenville Armitage <garmitage< at >swin.edu.au>
We have been working to create a BSD-licensed implementation of
Multipath TCP -- a set of TCP extensions that allow for transparent
multipath operation with multiple IP addresses as specified in
experimental RFC6824.
We made our first v0.1 public release on 2013-03-11 and recently
released v0.3 on 2013-04-16. The code is currently considered to be of
alpha quality. We are working towards pushing the code into a FreeBSD
Subversion repository project branch to continue the on-going
development effort in a more publicly accessible location. As part of
this move, we hope to begin releasing regular snapshot installer ISOs
of the MPTCP project branch courtesy of Hiroki Sato and the allbsd.org
daily snapshot infrastructure.
We are about to release a CAIA technical report 130424A entitled
"Design Overview of Multipath TCP version 0.3 for FreeBSD 10" on
2013-04-24 which provides a high-level design and architecture overview
of the v0.3 code release.
Going forward, we expect to continue development and release additional
technical reports and academic papers covering topics such as
performance analysis and multipath congestion control/scheduling.
Open tasks:
1. The code is currently of alpha quality so we welcome all testing
feedback, but please familiarize yourself with the README file and
"Known Limitations" section in particular before jumping in.
__________________________________________________________________
Native iSCSI Stack
URL: https://wiki.freebsd.org/Native%20iSCSI%20target
Contact: Edward Tomasz Napieral/a <trasz< at >FreeBSD.org>
Focus of the project was extended to also include a new iSCSI
initiator. Compared to the old one, it is more reliable, much more
user-friendly, and somewhat faster. It uses exactly the same
configuration file format as the old one to make migration easier.
As for the target side, it was verified to work properly against major
initiators (FreeBSD, Linux, Solaris, Windows and VMWare ESX).
This project is being sponsored by FreeBSD Foundation.
Open tasks:
1. RDMA support, for both the target and the initiator.
2. Performance optimization.
__________________________________________________________________
PyPy
URL: http://wiki.FreeBSD.org/PyPy
Contact: David Naylor <dbn< at >FreeBSD.org>
PyPy has been successfully updated to 2.0-beta1 with 2.0-beta2
finishing translating and other tests. Many major changes were made to
the PyPy port fr the 2.0-beta1 release, these include:
* Reworking the build script.
* Optionally use pypy (when available) for self-translating.
* Refine memory checks.
* Fix the test target.
Although the port is in a healthy state; PyPy on FreeBSD has some rough
edges (see make test for examples of roughness).
Open tasks:
1. Fix failed unit tests.
2. Integrate PyPy into bsd.python.mk.
3. See the project page for more items.
__________________________________________________________________
racct: Block IO Accounting
URL: https://wiki.freebsd.org/RudolfTomori/IOLimits
Contact: Rudolf Tomori <rudot< at >FreeBSD.org>
This project adds the block IO access accounting to the racct/rctl
resource limiting framework, a working prototype implementation is
available.
__________________________________________________________________
Read-only Port of NetBSD's UDF File System
URL: https://github.com/williamdevries/UDF
Contact: Will DeVries <william.devries< at >gmail.com>
An initial read-only port of NetBSD's UDF file system has been largely
completed. (The UDF file system is often used on CD, DVD and Blu-Ray
discs.) This port provides a number of advantages over FreeBSD's
current UDF implementation, which include:
* Support for version 2.60 of the UDF file system specification.
FreeBSD's current implementation only partially supports version
1.5 of the standard, which was released in 1997. Since Windows and
other systems support newer version of this file system, our users
are left without the ability to read some media written by these
systems. In addition, Blu-Ray discs are commonly written using
version 2.50 or 2.60.
* The ability to override the owner and group for all the files and
directories on a UDF volume using mount options.
* The ability to set the owner and group for files and directories
that lack defined owner or group information using mount options.
(The UDF specification allows for files and directories without
owners or groups.)
* The ability to override the mode for all directories and files on a
volume using mount options.
* Support for mounting previous versions of incrementally recorded
media, like CD-Rs.
__________________________________________________________________
TCP-AO Authentication Option
URL: http://svnweb.freebsd.org/base/user/andre/tcp-ao/
Contact: André Oppermann <andre< at >FreeBSD.org>
Work is under way to implement TCP-AO (TCP Authentication Option)
according to RFC5925 and RFC5926. TCP-AO is an extension to TCP-MD5
signatures commonly used in routers to secure BGP routing protocol
sessions against spoofing attacks. The work is under contract and
sponsored by Juniper Networks.
__________________________________________________________________
The entities Documentation Branch
URL: http://svnweb.freebsd.org/doc/projects/entities/
Contact: René Ladan <rene< at >FreeBSD.org>
The entities branch was created to reduce duplication of committer
entities. Currently there is one in authors.ent (with email addresses)
and another one in developers.ent (without email addresses). This seems
to be a leftover from the doc/www split in earlier times. To remedy
this, developers.ent is merged into authors.ent and entities with email
addresses are postfixed as such. Apart from the instructions for the
initial commit, there should be little user-visible changes. Some
related cleanups, like cleaning up team definitions, replacing literal
names by entities from authors.ent, and adding missing names to
authors.ent are also made.
Open tasks:
1. Finish processing of the <email> tag.
2. Send out a CFT.
3. Merge back into head branch.
__________________________________________________________________
The FreeBSD Japanese Documentation Project
URL: http://www.FreeBSD.org/ja/
URL: http://www.jp.FreeBSD.org/doc-jp/
Contact: Hiroki Sato <hrs< at >FreeBSD.org>
Contact: Ryusuke Suzuki <ryusuke< at >FreeBSD.org>
Web page (htdocs): Newsflash and some other updates in the English
version have been translated to keep them up-to-date. Specifically, the
release related contents were updated in this period.
Books: FreeBSD Handbook has constantly been updated since the last
report; particularly, "ports", "desktop" section were largely updated.
Some progress has been made in the "advanced-networking" section,
contributed by a new translator.
"Writing FreeBSD Problem Reports" article is now in sync with the
English version.
Open tasks:
1. Further translation work of outdated documents in ja_JP.eucJP
subtree.
__________________________________________________________________
UFS/FFS Performance Work
URL: http://www.mckusick.com/publications/faster_fsck.pdf
Contact: Kirk McKusick <mckusick< at >mckusick.com>
Some work on the performance of UFS/FFS has been recently committed to
HEAD. The purpose of the corresponding change to the FFS layout policy
is to reduce the running time for a full file system check. It also
reduces the random access time for large files and speeds up the
traversal time for directory tree walks.
The key idea is to reserve a small area in each cylinder group
immediately following the inode blocks for the use of metadata,
specifically indirect blocks and directory contents. The new policy is
to preferentially place metadata in the metadata area and everything
else in the blocks that follow the metadata area.
The size of this area can be set when creating a filesystem using
newfs(8) or changed in an existing filesystem using tunefs(8). Both
utilities use the -k held-for-metadata-blocks option to specify the
amount of space to be held for metadata blocks in each cylinder group.
By default, newfs(8) sets this area to half of minfree (typically 4% of
the data area).
As with all layout policies, it only affect layouts of things allocated
after it is put in place. So these changes will primarily be noticable
on newly created file systems.
File system checks have been sped up by caching the cylinder group maps
in pass1 so that they do not need to be read again in pass5. As this
nearly doubles the memory requirement for fsck(8), the cache is thrown
away if other memory needs in fsck(8) would otherwise fail. Thus, the
memory footprint of fsck(8) remains unchanged in memory constrained
environments. This optimization will be evident on all UFS/FFS
filesystems.
This work was inspired by a paper presented at Usenix's FAST '13.
Open tasks:
1. MFC to 9-STABLE and possibly 8-STABLE should happen by May unless
problems arise with these changes in HEAD.
__________________________________________________________________
Wine32 on FreeBSD/amd64
URL: http://wiki.freebsd.org/i386-Wine
Contact: David Naylor <dbn< at >FreeBSD.org>
The i386-wine port (formally wine-fbsd64) has been added to the ports
collection (as emulators/i386-wine-devel). Although the port can only
be compiled under a x86 32-bit system the resulting package can be
installed on a x86 64-bit system and enable running of 32-bit Microsoft
Windows programs.
Packages for the port are in development and should be announced
shortly on the freebsd-questions and freebsd-emulation mailing lists.
There are some issues with Wine32 on FreeBSD/amd64 -- possibly related
to FreeBSD32_COMPACT, or other general 32/64-bit issues -- that could
do with some focus.
Open tasks:
1. Port wine64 to FreeBSD.
2. Port WoW64 (wine32 and wine64 together) to FreeBSD.
3. Fix 32- and 64-bit issues (such as Intel graphics not
accelerating).
__________________________________________________________________
Xfce/FreeBSD
URL: https://wiki.FreeBSD.org/Xfce
URL: http://people.freebsd.org/~olivierd/patches/midori-0.4.9_0.5.0.diff
Contact: FreeBSD Xfce Team <xfce< at >FreeBSD.org>
The Xfce FreeBSD Team has updated many ports, especially:
* tumbler: 0.1.27 (add new option, COVER)
* Parole: 0.5.0
* xfdesktop: 4.10.2
* Midori: 0.4.9 (full compatible with Vala 0.18), 0.5.0 is available
(see links)
* Orage: 4.8.4
* xfce4-terminal: 0.6.1 (renamed by upstream, previous name was
Terminal)
This last application contains drop-down functionality, new window
slides down from the top of the screen when key (we can define keyboard
shortcut) is pressed.
Open tasks:
1. Replace libxfce4gui (deprecated and not maintained by upstream) by
libxfce4ui in order to enhance support panel plugins for Xfce >=
4.10.
2. Work on Midori Gtk3 port.
3. Fix gtk-xfce-engine with Gtk+ >=3.6.
__________________________________________________________________
xorg on FreeBSD
URL: http://wiki.freebsd.org/Xorg
URL: http://people.freebsd.org/~zeising/xorg-7.7.diff
URL: http://trillian.chruetertee.ch/ports/browser/trunk
URL: http://trillian.chruetertee.ch/ports/browser/branches/xorg-7.7
Contact: FreeBSD X11 Team <x11< at >FreeBSD.org>
Contact: Niclas Zeising <zeising< at >FreeBSD.org>
Contact: Koop Mast <kwm< at >FreeBSD.org>
Most of the work during this period has been in updating, testing and
stabilizing the development repository. A number of xorg applications
and various other leaf ports has been committed as part of this effort.
After this a CFT was sent out asking for help in testing the remaining
bits in development, including updates to all major libraries and
xorg-server.
Currently, the CFT patch has been submitted for an exp-run to iron out
any final bugs. The plan is to merge it sometime after FreeBSD 8.4 is
released and the ports tree is reopened for commits.
Work is also on-going to port new versions of MESA and OpenGL, as well
as a new version of xorg-server, and perhaps in the future, Wayland.
These are considered more long-term goals and are not targeted for the
current update.
Open tasks:
1. Decide how to handle the new and old xorg distributions. In recent
xorg, a lot of legacy driver support has been dropped, therefore we
need to maintain two xorg distributions to not lose a lot of
hardware drivers. Currently, this is done by setting the flag
WITH_NEW_XORG in /etc/make.conf, but a more practical solution is
needed. This is especially important since the flag is not very
user-friendly, and since there currently will be no official
packages for the new distribution.
2. Continue to test and update xorg related ports. There are new
versions of xserver, as well as MESA and related OpenGL libraries
which needs to be ported and eventually integrated into the ports
tree.
3. Port Wayland. The future of graphical environments in open source
operating systems seems to be Wayland. This needs to be ported to
FreeBSD so that a wider audience can test it, and so that it
eventually can be integrated into the ports tree, perhaps as a
replacement for the current xorg.
4. Look into replacements for HAL. HAL is used for hot-plugging of
devices, but it has been long abandoned by Linux. A replacement,
perhaps build on top of devd would be nice to have. This work
should be coordinated with the FreeBSD GNOME and KDE teams.
__________________________________________________________________
_______________________________________________
freebsd-hackers< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe< at >freebsd.org"
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"</pre>Gabor Pali2013-05-12T17:54:05How to get pkgng work through a proxy?
http://comments.gmane.org/gmane.os.freebsd.stable/86415
<pre>Hi,
I have this host (a cloned VM, FreeBSD 9.1 AMD64) behind an Astaro
Web-Proxy:
(blahost </root>) 70 # pkg
update
[12:00] Updating repository catalogue
repo.txz 3%
10KB 0.5KB/s 0.0KB/s - stalled -pkg:
http://pkgng.our.repo/91amd64-91patch/repo.txz: Operation timed out
It's a proxy with authentication.
I'm not sure if it's a fetch(3) problem in general.
Because a single fetch from the same server of a small and large file
does work, though a bit slow.
pkg is 1.0.2
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"
</pre>Rainer Duffner2013-05-14T10:36:44kernel panic: ffs_valloc: dup alloc
http://comments.gmane.org/gmane.os.freebsd.stable/86403
<pre>The core.txt and info files can be found in attached archive (there are 2 crash reports there). If you need vmcores, just let me know where I can upload them.
ASUS K73E
Architecture: i386
OS: FreeBSD 9.1-RELEASE-p3
Please let me know should you need some other information.
Thanks.
Andriy _______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"</pre>Andriy Kornatskyy2013-05-13T09:10:04freebsd-update and /boot/kernel/linker.hints
http://comments.gmane.org/gmane.os.freebsd.stable/86402
<pre>Hi,
since last freebsd-update fetch install I always get this message after freebsd-update fetch:
The following files will be updated as part of updating to 9.1-RELEASE-p3:
/boot/kernel/linker.hints
but freebsd-update install doesn't install anything.
Is there something wrong with my system or is this a bug in freebsd-update?
kind regards
Wolfgang
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"
</pre>Wolfgang Riegler2013-05-13T09:22:41kernel panic: ffs_valloc: dup alloc
http://comments.gmane.org/gmane.os.freebsd.stable/86401
<pre>The core.txt and info files can be found in attached archive. If you need vmcore, just let me know where I can upload it.
ASUS K73E
Architecture: i386
OS: FreeBSD 9.1-RELEASE-p3
Please let me know should you need some other information.
Thanks.
Andriy _______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"</pre>Andriy Kornatskyy2013-05-13T09:14:44Reinstalling boot blocks on a ZFS-only system
http://comments.gmane.org/gmane.os.freebsd.stable/86386
<pre>
So, I've long known and it makes sense that when you're booted from a ZFS volume, you can't mess with the boot-loader. And, I know a few months ago I had a set of commands I would use when booted from a CD that would initialize the network and copy the "release/boot" from somewhere else so that I could install bootblocks and boot-loaders from more recent code. Sadly, I didn't _record_ those commands I was using.
What do "people in the know" do when they want to update the bootblocks of a ZFS-boot system? Or, have too few people followed this path so far that they can boot UFS and do it with less difficulty?
Thanks. Happy for any information.
- Chris
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"
</pre>Chris Ross2013-05-12T20:50:46FreeBSD Quarterly Status Report, January-March 2013
http://comments.gmane.org/gmane.os.freebsd.stable/86384
<pre>FreeBSD Quarterly Status Report, January-March 2013
Introduction
This report covers FreeBSD-related projects between January and March
2013. This is the first of four reports planned for 2013.
Highlights from this status report include the busy preparations of
8.4-RELEASE, restoration of binary package building, steady progress of
several porting efforts, like work on the FreeBSD ports of xorg, GNOME,
KDE, and Xfce, bringing FreeBSD to Cubieboard and Hackberry boards,
development of ARM and AMD GPU support, improving performance of
UFS/FFS and callouts, and introducing a multipath TCP implementation
for the network stack.
Thanks to all the reporters for the excellent work! This report
contains 31 entries and we hope you enjoy reading it.
The deadline for submissions covering the period between April and June
2013 is July 7th, 2013.
__________________________________________________________________
Projects
* FreeNAS
* Kernel Information in Process Core Dumps
* Native iSCSI Stack
FreeBSD Team Reports
* FreeBSD Bugmeister Team
* FreeBSD Core Team
* FreeBSD Port Managers
* FreeBSD Postmaster Team
* FreeBSD Release Engineering Team
Kernel
* AMD GPU Kernel Mode-Setting (KMS) Support
* Atomic "close-on-exec"
* callout(9) Improvements
* Multipath TCP (MPTCP) for FreeBSD
* racct: Block IO Accounting
* Read-only Port of NetBSD's UDF File System
* TCP-AO Authentication Option
* UFS/FFS Performance Work
Documentation
* Improving the Documentation Project Infrastructre
* The entities Documentation Branch
* The FreeBSD Japanese Documentation Project
Architectures
* FreeBSD on Cubieboard
* FreeBSD/arm Superpages for ARMv7
* FreeBSD/ARM Toolchain Improvements
Ports
* FreeBSD Haskell Ports
* GNOME/FreeBSD
* KDE/FreeBSD
* PyPy
* Wine32 on FreeBSD/amd64
* Xfce/FreeBSD
* xorg on FreeBSD
Miscellaneous
* BXR.SU -- Super User's BSD Cross Reference
* mdoc.su -- Short Manual Page URLs
__________________________________________________________________
AMD GPU Kernel Mode-Setting (KMS) Support
URL: https://wiki.freebsd.org/AMD_GPU
Contact: Jean-Sébastien Pédron <dumbbell< at >FreeBSD.org>
Contact: J.R. Oldroyd <jr< at >opal.com>
Contact: Konstantin Belousov <kib< at >FreeBSD.org>
The project progressed well since February:
* Konstantin committed is TTM port to 10-CURRENT.
* With the help of John Baldwin (jhb) and Andriy Gapon (avg), the
Video BIOS situation greatly improved: the radeonkms driver reads
the BIOS shadow copy if the video card is the primary one, or query
the PCI expansion ROM otherwise. In the end, this code will be
probably committed to the PCI driver so that other video drivers
benefit from it.
* Andriy also reported several problems with the I2C code. Now that
they are fixed, the monitors plugged into DVI and HDMI connectors
are detected and their EDID is read correctly. VGA connector is not
tested so far.
* There is a locking problem in either TTM or the Radeon driver which
prevents OpenGL from working properly. Jean-Sébastien is currently
tracking this down.
* J.R. Oldroyd started to work on a 9-STABLE backport of the driver
which is now working quite well. He had to backport some features
from the VM which may need further refinement by the VM folks.
Yakaz lended Jean-Sébastien a computer which allows him to test a
RV630-based discrete card and, in the future, other PCIe cards. Several
users already kindly tested the driver. Big thanks to all those
contributors!
In its current state, the driver allows to have a simple X session (no
OpenGL), run common applications, watch movies, change the resolution
and enable additional monitors with xrandr(1). The most blocking issue
now is the OpenGL deadlock which prevents to run modern
compositors/desktop environment, games and WebGL demos. We are not
ready for a "Call For Testers" yet.
Open tasks:
1. Test multiple cards configurations for Video BIOS issues,
especially Intel integrated card + Radeon discrete card, and AMD
integrated card (IGP) + Radeon discrete card. No need to check
configurations with one shared connector though, it is not
supported right now.
__________________________________________________________________
Atomic "close-on-exec"
URL: https://wiki.freebsd.org/AtomicCloseOnExec
Contact: Jilles Tjoelker <jilles< at >FreeBSD.org>
If threads or signal handlers call fork() and exec(), file descriptors
may be passed undesirably to child processes, which may lead to hangs
(if a pipe is not closed), exceeding the file descriptor limit and
security problems (if the child process has lower privilege). One
solution is various new APIs that set the "close-on-exec" flag
atomically with allocating a file descriptor. Some existing software
will use the new features if present or will even refuse to compile
without them.
Various parts have been present for some time.
In first quarter of 2013, extensions to recvmsg(), socket(),
socketpair() and posix_openpt() have been added.
__________________________________________________________________
BXR.SU -- Super User's BSD Cross Reference
URL: http://bxr.su/
URL: http://lists.freebsd.org/pipermail/freebsd-hackers/2013-April/042334.html
Contact: Constantine A. Murenin <cnst++< at >FreeBSD.org>
Super User's BSD Cross Reference (BXR.SU) is a new source-code search
engine that covers the complete kernel and non-GNU userland source
trees of FreeBSD, NetBSD, OpenBSD, and DragonFly BSD.
BXR.SU is optimised to be very fast, has daily updates of all the
trees, and also acts as a deterministic URL shortener.
BXR.SU is based on an OpenGrok fork, but it is more than just OpenGrok.
We have fixed a number of annoyances, eliminated features that just
never worked right from the outright, and provided integration with
tools like CVSweb (including great mirrors like allbsd.org), FreeBSD's
ViewVC (SVN), as well as GitHub and Gitweb from git.freebsd.your.org,
plus a tad of other improvements, including a complete rewrite of an
mdoc parser. Last, but definitely not least, is an extensive set of
nginx rewrite rules that makes it a breeze to use BXR.SU as a
deterministic URL compactor for referencing BSD source code. For
example, the http://bxr.su/f/kern/sched_ule.c URL will automatically
redirect to http://bxr.su/FreeBSD/sys/kern/sched_ule.c through nginx.
Note that according to the release schedule of BXR.SU, there is no IPv4
glue until 2013-04-24; otherwise, the service is available via both
IPv4 and IPv6. See the 2013-04-01 announcement on the freebsd-hackers
mailing list for more details.
Open tasks:
1. Find up-to-date git repositories (served with Gitweb) of NetBSD and
OpenBSD.
2. Find a Gitweb mirror of FreeBSD that is faster than GitHub and
Gitorious.
__________________________________________________________________
callout(9) Improvements
URL: http://people.freebsd.org/~davide/asia/callout_paper.pdf
URL: http://people.freebsd.org/~davide/asia/calloutng.pdf
URL: http://svnweb.freebsd.org/base?view=revision&revision=247777
Contact: Davide Italiano <davide< at >FreeBSD.org>
Contact: Alexander Motin <mav< at >FreeBSD.org>
In FreeBSD, timers are provided by the callout facility, which allows
to register a function with an argument to be called at specified
future time. The subsystem suffered of some problems, such as the
impossibility of handling high-resolution events or its inherent
periodic structure, which may lead to spurious wakeups and higher power
consumption. Some consumers, such as high-speed networking, VoIP and
other real-time applications need a better precision than the one
currently allowed. Also, especially with the ubiquity of laptops in the
last years, the energy wasted by interrupts waking CPUs from sleep may
be a sensitive factor. Recent changes in the subsystem addressed those
long-standing issues as well as introduced a new programming interface
to take advantage of the new features.
Open tasks:
1. Evaluating if it is worth to migrate any of the other callout(9)
consumers to the new interface.
2. Move callout consumers still using the legacy timeout()/untimeout()
interface to callout_*() in order to get rid of redundant code and
clean up KPI.
__________________________________________________________________
FreeBSD Bugmeister Team
Contact: Eitan Adler <eadler< at >FreeBSD.org>
Contact: Gavin Atkinson <gavin< at >FreeBSD.org>
Contact: Oleksandr Tymoshenko <gonzo< at >FreeBSD.org>
The FreeBSD Bugmeister Team are continuing to evaluate options for
alternate bug trackers and have narrowed their choices to two
possibilities: Bugzilla and roundup.
The number of non-ports PRs have remained relatively static over the
last three months, with as many coming in as being closed. The number
of ports PRs have increased recently, largely due to the ports freeze
for the upcoming 8.4-RELEASE.
The Bugmeister team continue work on trying to make the contents of the
GNATS PR database cleaner, more accessible and easier for committers to
find and resolve PRs, by tagging PRs to indicate the areas involved,
and by ensuring that there is sufficient info within each PR to resolve
each issue.
As always, anybody interested in helping out with the PR queue is
welcome to join us in #freebsd-bugbusters on EFnet. We are always
looking for additional help, whether your interests lie in triaging
incoming PRs, generating patches to resolve existing problems, or
simply helping with the database housekeeping (identifying duplicate
PRs, ones that have already been resolved, etc). This is a great way of
getting more involved with FreeBSD!
Open tasks:
1. Finalize the decision of which new bug tracker to use.
2. Get more users involved with triaging PRs as they come in.
3. Assist committers with closing PRs.
__________________________________________________________________
FreeBSD Core Team
Contact: Core Team <core< at >FreeBSD.org>
At the end of 2012, the Core Team approved using Google Analytics on
the Project web site to enable the Documentation Engineering Team to
collect statistics on its usage for better profiling. In the first
quarter of 2013, the Core Team worked with the Documentation
Engineering Team to finalize the associated policies.
Due to some debates around the political correctness of quotes added
for the fortune(6) utility, the corresponding data file has been
removed from the base system in -CURRENT.
In light of the security incident, the liaison role between the Core
Team and the Security Team has been restored, with Gavin Atkinson
assuming this role. The Core Team work hard on resolving the current
situation of the binary package building cluster and the associated
security problems in tight cooperation with the Ports Management Team,
Cluster Administators, and the FreeBSD Foundation Board. The compromise
page is kept updated on the results.
The FreeBSD Project submitted an application for Google Summer of Code
this year again.
There was access granted for 2 new committers and 1 commit bit was
taken for safekeeping in this quarter.
__________________________________________________________________
FreeBSD Haskell Ports
URL: http://wiki.freebsd.org/Haskell
URL: https://github.com/freebsd-haskell/freebsd-haskell/
Contact: Gábor Páli <pgj< at >FreeBSD.org>
Contact: Ashish Shukla <ashish< at >FreeBSD.org>
We are proud to announce FreeBSD Haskell Team has updated existing
ports to their latest stable versions. We also added number of new
ports, which brings the count of Haskell ports in FreeBSD ports tree to
more than 400, featuring many popular software, e.g. xmonad, git-annex,
pandoc or various web framework implementations. All of these updates
will be available as part of the upcoming 8.4-RELEASE. We also came to
know that Haskell ports are also being used successfully on
DragonFlyBSD's dports tree.
In our development repository, there was some optional support added
for LLVM-based code generation using the GHC LLVM backend. This works
mostly on FreeBSD too, though some of the ports would need fixing so it
is still considered experimental.
Open tasks:
1. Try to build GHC with clang (as system compiler).
2. Commit pending Haskell ports to the FreeBSD ports tree.
3. Add more ports to the Ports Collection.
__________________________________________________________________
FreeBSD on Cubieboard
Contact: Ganbold Tsagaankhuu <ganbold< at >FreeBSD.org>
Contact: Oleksandr Tymoshenko <gonzo< at >FreeBSD.org>
Initial support of Allwinner A10 SoC is committed to -CURRENT. FreeBSD
is now running on boards such as Cubieboard, Hackberry and it supports
following peripherals:
* USB EHCI
* GPIO
Open tasks:
1. Get EMAC Ethernet driver working. Need more help from network
driver experts.
2. Implement more drivers.
__________________________________________________________________
FreeBSD Port Managers
URL: http://www.FreeBSD.org/ports/
URL: http://www.freebsd.org/doc/en/articles/contributing-ports/
URL: http://portsmon.freebsd.org/
URL: http://www.freebsd.org/portmgr/
URL: http://blogs.freebsdish.org/portmgr/
URL: http://www.twitter.com/freebsd_portmgr/
URL: http://www.facebook.com/portmgr
Contact: Thomas Abthorpe <portmgr-secretary< at >FreeBSD.org>
Contact: Port Management Team <portmgr< at >FreeBSD.org>
The ports tree contains approximately 24,300 ports, while the PR count
still is close to 1600.
In the first quarter we added 4 new committers, took in 1 commit bit
for safe keeping, and re-instated 1 commit bit.
In February, Mark Linimon (linimon) stepped down from his duties in the
team. Mark had been the longest serving member of the team. Mark had
spent many long hours refactoring and documenting the portbuild
software to ensure that pointyhat services could be restored.
After a security review, redports.org was turned back on, restoring
Tinderbox services to contributors, along with post commit QATs. In
addition, pointyhat infrastructure had also undergone a review and work
begain on restoring the package build system.
Erwin Lansing (erwin) and Martin Wilke (miwi) took on the principle
roles of getting the portbuild software installed and running on
pointyhat. As a result of all their hard work, portmgr< at > was finally
able to resume doing -exp runs, preparing packages for the upcoming 8.4
release, as well as getting a set of 9.1 packages retroactively
prepared.
After many long years of being the defacto standard for the Project,
CVS support for the ports tree officially ended on February 28.
The ports tree was tagged with RELEASE_7_EOL, to coincide with the end
of life for FreeBSD 7.X.
Beat Gaetzi (beat) stepped down from his duties on portmgr< at > in March.
Among his notable contributions, was the task of migrating the Ports
Tree from the old CVS repo to Subversion.
Bryan Drewery (bdrewery) joined the Ports Management team in March,
bringing with him his wealth of knowledge and skill from maintaining
portupgrade, portmaster, assisting with pkgng, as well as co-developing
poudriere.
Open tasks:
1. Most ports PRs are assigned, we now need to focus on testing,
committing and closing.
__________________________________________________________________
FreeBSD Postmaster Team
Contact: David Wolfskill <postmaster< at >FreeBSD.org>
In the first quarter of 2013, the FreeBSD Postmaster Team has
implemented the following items that may be interest of the general
public:
* Changes in configuration of Mailman-managed lists: allow to accept
the application/pkcs7-signature MIME type (in addition to the
application/x-pkcs7-signature MIME type), thus permitting S/MIME
signatures on list mail.
* New lists: freebsd-ops-announce -- announcements of infrastructure
issues, and freebsd-pkg -- discussion of binary package management
and package tools.
__________________________________________________________________
FreeBSD Release Engineering Team
URL: http://www.freebsd.org/releases/8.4R/schedule.html
Contact: FreeBSD Release Engineering Team <re< at >FreeBSD.org>
FreeBSD 8.4-RC1 just got out the door and we are planning RC2. A couple
of critical fixes have come in that will be included in RC2. The
schedule has slipped about 10 days so far. We are expecting the final
release by the end of April. Packages for 8.4 have been provided by a
fully operational package building cluster.
__________________________________________________________________
FreeBSD/arm Superpages for ARMv7
URL: http://static.usenix.org/events/osdi02/tech/full_papers/navarro/navarro.pdf
URL: https://wiki.freebsd.org/ARMSuperpages
URL: https://github.com/semihalf-bodek-zbigniew/freebsd-arm-superpages.git
Contact: Zbigniew Bodek <zbb< at >semihalf.com>
Contact: Grzegorz Bernacki <gjb< at >semihalf.com>
Contact: Rafał Jaworowski <raj< at >semihalf.com>
ARM architecture is more and more prevailing, not only in the mobile
and embedded space. Among the more interesting industry trends emerging
in the recent months has been the "ARM server" concept. Some top-tier
companies started developing systems like this already (Dell, HP).
Key to FreeBSD success in these new areas are sophisticated features,
among them are superpages.
The objective of this project is to provide FreeBSD/arm with the
superpages support, which will allow for efficient use of TLB
translations (enlarge TLB coverage), leading to improved performance in
many applications and scalability. Indicated functionality is intended
to work on ARMv7-based processors, however compatibility with ARMv6
will be preserved.
Current support status:
* Port of the pv_entry allocator.
* Switch to "AP[2:1]" access permissions model.
* PTE-based, page-referenced/modified emulation.
* Fixes regarding page replacement strategy.
* Code optimizations and bug fixes.
Next steps:
* Dirty pages management.
* Gradual integration to FreeBSD -CURRENT.
* Further pmap optimizations.
* Fragmentation control management.
* Testing and benchmarking.
Open tasks:
1. Support for multiple page sizes.
2. Implementation of page promotion, demotion and eviction mechanisms.
__________________________________________________________________
FreeBSD/ARM Toolchain Improvements
Contact: Andrew Turner <andrew< at >FreeBSD.org>
Clang has been made the default compiler on ARM. A number of issues
with LLVM and clang have been found, reported, and fixed upstream.
An issue where some ARM EABI applications compiled with clang crash has
been reported upstream with a patch and will be brought into the
FreeBSD tree when it is accepted. The only other issue blocking moving
to the ARM EABI is C++ exceptions fail to work correctly with shared
objects. This will need us to either import libunwind or implement the
functions libgcc_s requires to find the correct unwind table.
Open tasks:
1. Fix exception handling for EABI.
__________________________________________________________________
FreeNAS
URL: http://www.FreeNAS.org/
Contact: Alfred Perlstein <alfred< at >FreeBSD.org>
Contact: Josh Paetzel <jpaetzel< at >FreeBSD.org>
FreeNAS 8.3.1-RELEASE-p2 will hit Sourceforge the second week of April,
and should end up as the last FreeNAS release based on FreeBSD 8.X It's
currently the only Free Open Source NAS product available with any form
of ZFS encryption (provided by GELI).
Open tasks:
1. The team is hard at work on getting a FreeBSD 9.X-based release of
FreeNAS ready. Currently there are several nightly snapshots
available.
2. Add HAST to the webinterface.
3. Migrate to NFSv4.
4. Integrate foundation sponsored kernel iSCSI target.
__________________________________________________________________
GNOME/FreeBSD
URL: http://www.freebsd.org/gnome
URL: http://www.freebsd.org/gnome/docs/develfaq.html
URL: http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom
URL: https://github.com/jlmess77/mate-ports
Contact: FreeBSD GNOME team <gnome< at >FreeBSD.org>
The GNOME/FreeBSD Team has recently merged Glib 2.34, Gtk+ 2.24.17 and
Gtk+ 3.6.4 into ports, the C++ bindings also have got updates. In
additional "low-level" GNOME ports received updates, like libsoup,
gobject-introspection, atk and vala for example. The telepathy stack
and empathy where also updated.
The USE_GNOME macro has received support for :run and :build targets
thanks to Jeremy Messenger (mezz). Currently only libxml2 and libxslt
support these targets.
USE_GNOME=pkgconfig is being deprecated in favor of
USE_PKGCONFIG=build. The former also adds a run dependency on
pkg-config, which is not required. A first pass was done to get rid of
this in the Glib update to 2.34. In cooperation with the X11 Team, the
usage of USE_GNOME=pkgconfig in X components will be removed. After the
fallout from this is handled and stranglers are converted, the
USE_GNOME option will be removed.
In addition USE_GNOME=gnomehack is deprecated and should not be used.
Please replace it with USES=pathfix.
The GNOME development repository has switched from CVS to SVN. CVS will
not get any more updates. Uses can get a new version of the marcusmerge
script that supports SVN from its home page, and should remove the old
CVS checkout "ports" dir.
* SVN anonymous root: svn://creme-brulee.marcuscom.com/ or
svn://sushi.marcuscom.com/ (IPv6)
* ViewVC: http://www.marcuscom.com:8080/viewvc/viewvc.cgi/marcuscom
On-going efforts:
* glib 2.36, pango 1.34.0, gtk 3.8.0 and gobject-introspection 1.36.0
where updated in the GNOME development repository.
* Gustau Perez i Querol stepped up and started work on updating the
old GNOME 3.4 ports to 3.6. At the moment of writing these are not
available in the GNOME development repository just yet. For his
efforts, he was awarded a FreeBSD GNOME team membership.
* Jeremy Messenger (mezz) has completed Mate 1.6 which will be
arriving in ports near you when deemed stable enough.
If you want to help with keeping the documentation updated or helping
out in other ways, even if it only parts for the Glib/Gtk/GNOME stack
you are interested in, please contact us!
Open tasks:
1. Update the FreeBSD.org/gnome website, in particular the developer
information about USE_GNOME, maybe put that section in the Porter's
Handbook instead.
2. Merge more updated ports from MC to ports.
3. Testing latest Glib/Gtk releases with existing ports, and import it
into ports when it is ready.
4. After porting GNOME 3.6 run tests and fix bugs.
__________________________________________________________________
Improving the Documentation Project Infrastructre
URL: http://svnweb.freebsd.org/doc/projects/xml-tools/
Contact: Gábor Kövesdán <gabor< at >FreeBSD.org>
There is an on-going work to improve the documentation infrastructure
and modernize our documentation toolchain. The work can be found in the
xml-tools branch and is very near to completion. The improvements
include the following:
* Upgrade to DocBook 4.5.
* Use XSLT instead of DSSSL to render XHTML-based output.
* Generate PDF from PS and simplify image processing.
* Fix make lint and validate the whole documentation set.
* Fix rendering of TOC elements.
* Fix misused link elements that resulted in a corrupt rendering.
* Use more human-friendly publication data and release info
rendering.
* Add support for XInclude in DocBook documents.
* Add support for profiling with attributes.
* Add support for Schematron constraints.
* Add experimental epub support.
* Add experimental support for XSL-FO-based printed output.
* Clean up obsolete SGML constructs.
* Clean up catalogs.
* Drop HTML Tidy since it is not needed any more.
The changes eliminate some dependencies and switch the doc repository
to a real XML toolchain with proper validation and more advanced
rendering tools. The only exceptions are Jade and the DSSSL
stylesheets, which are still needed for printed output.
Open tasks:
1. Fix rendering problems with images in printed formats.
2. Update the Documentation Primer to reflect changes.
__________________________________________________________________
KDE/FreeBSD
URL: http://FreeBSD.kde.org
URL: http://FreeBSD.kde.org/area51.php
Contact: KDE FreeBSD <kde< at >FreeBSD.org>
The KDE/FreeBSD Team is very proud to have Schaich Alonso (aschai)
joining the team. Welcome!
The KDE/FreeBSD Team have continued to improve the experience of KDE
software and Qt under FreeBSD. The latest round of improvements
include:
* Fix problems establishing UDP connections.
The Team have also made many releases and upstreamed many fixes and
patches. The latest round of releases include:
* KDE SC: 4.9.5, 4.10.1 (ports)
* Qt: 5.0.0 (area51) and 4.8.4 (ports)
* PyQt: 4.9.6 (ports); QScintilla 2.7 (ports); SIP: 4.14.2 (area51)
and 4.14.3 (ports)
* KDevelop: 4.4.1 (ports); KDevPlatform: 1.4.1 (ports)
* Calligra: 2.5.5, 2.6.2 (ports)
* Amarok: 2.7.0
* CMake: 2.8.10.2
* Digikam (and KIPI-plugins): 3.1.0 (area51)
* QtCreator: 4.6.1 (ports)
* KDE Telepathy 0.6.0 (area51)
* many smaller ports
As a result -- according to PortScout -- we have 431 ports, of which
93.5% (from 91%) are up-to-date.
The Team are always looking for more testers and porters so please
contact us and visit our home page.
Open tasks:
1. Updating out-of-date ports, see PortScout for a list.
__________________________________________________________________
Kernel Information in Process Core Dumps
Contact: Mikolaj Golub <trociny< at >freebsd.org>
When doing postmortem analysis of a crashed process it is sometimes
very useful to have kernel information about the process at the moment
of the crash, like open file descriptors or resource limits. For a live
process this information can be obtained via sysctl(3) interface e.g.
using procstat(1).
The aim of the project is to add additional notes to a process core
dump, which include process information from the kernel at the moment
of the process crash, teach libprocstat(3) to extract this information
and make procstat(1) use this functionality.
At the moment all necessary code changes are committed to HEAD and are
going to be merge to stable/9 in 1 month.
__________________________________________________________________
mdoc.su -- Short Manual Page URLs
URL: http://mdoc.su/
URL: http://nginx.conf.mdoc.su/mdoc.su.nginx.conf
URL: https://github.com/cnst/mdoc.su
URL: http://lists.freebsd.org/pipermail/freebsd-doc/2013-February/021465.html
Contact: Constantine A. Murenin <cnst++< at >FreeBSD.org>
mdoc.su is a deterministic URL shortener for BSD manual pages, written
entirely in nginx.conf.
Since the original announcement, OS version support has been added
(e.g. /f91/ and /FreeBSD-9.1/ etc.), as well as dynamic multi-flavour
web-pages with multiple links (e.g. http://mdoc.su/f,d/ifnet.9 and
http://mdoc.su/-/mdoc), which even let you specify the versions too
(e.g. http://mdoc.su/f91,n60,o52,d/mdoc).
The source code for the whole site is available under a BSD licence.
Open tasks:
1. Fork it on GitHub (see links)!
__________________________________________________________________
Multipath TCP (MPTCP) for FreeBSD
URL: http://caia.swin.edu.au/urp/newtcp/mptcp/tools.html
URL: http://caia.swin.edu.au/newtcp/mptcp/
URL: http://caia.swin.edu.au/reports/130424A/CAIA-TR-130424A.pdf
URL: https://pub.allbsd.org/FreeBSD-snapshots/
Contact: Nigel Williams <njwilliams< at >swin.edu.au>
Contact: Lawrence Stewart <lastewart< at >swin.edu.au>
Contact: Grenville Armitage <garmitage< at >swin.edu.au>
We have been working to create a BSD-licensed implementation of
Multipath TCP -- a set of TCP extensions that allow for transparent
multipath operation with multiple IP addresses as specified in
experimental RFC6824.
We made our first v0.1 public release on 2013-03-11 and recently
released v0.3 on 2013-04-16. The code is currently considered to be of
alpha quality. We are working towards pushing the code into a FreeBSD
Subversion repository project branch to continue the on-going
development effort in a more publicly accessible location. As part of
this move, we hope to begin releasing regular snapshot installer ISOs
of the MPTCP project branch courtesy of Hiroki Sato and the allbsd.org
daily snapshot infrastructure.
We are about to release a CAIA technical report 130424A entitled
"Design Overview of Multipath TCP version 0.3 for FreeBSD 10" on
2013-04-24 which provides a high-level design and architecture overview
of the v0.3 code release.
Going forward, we expect to continue development and release additional
technical reports and academic papers covering topics such as
performance analysis and multipath congestion control/scheduling.
Open tasks:
1. The code is currently of alpha quality so we welcome all testing
feedback, but please familiarize yourself with the README file and
"Known Limitations" section in particular before jumping in.
__________________________________________________________________
Native iSCSI Stack
URL: https://wiki.freebsd.org/Native%20iSCSI%20target
Contact: Edward Tomasz Napieral/a <trasz< at >FreeBSD.org>
Focus of the project was extended to also include a new iSCSI
initiator. Compared to the old one, it is more reliable, much more
user-friendly, and somewhat faster. It uses exactly the same
configuration file format as the old one to make migration easier.
As for the target side, it was verified to work properly against major
initiators (FreeBSD, Linux, Solaris, Windows and VMWare ESX).
This project is being sponsored by FreeBSD Foundation.
Open tasks:
1. RDMA support, for both the target and the initiator.
2. Performance optimization.
__________________________________________________________________
PyPy
URL: http://wiki.FreeBSD.org/PyPy
Contact: David Naylor <dbn< at >FreeBSD.org>
PyPy has been successfully updated to 2.0-beta1 with 2.0-beta2
finishing translating and other tests. Many major changes were made to
the PyPy port fr the 2.0-beta1 release, these include:
* Reworking the build script.
* Optionally use pypy (when available) for self-translating.
* Refine memory checks.
* Fix the test target.
Although the port is in a healthy state; PyPy on FreeBSD has some rough
edges (see make test for examples of roughness).
Open tasks:
1. Fix failed unit tests.
2. Integrate PyPy into bsd.python.mk.
3. See the project page for more items.
__________________________________________________________________
racct: Block IO Accounting
URL: https://wiki.freebsd.org/RudolfTomori/IOLimits
Contact: Rudolf Tomori <rudot< at >FreeBSD.org>
This project adds the block IO access accounting to the racct/rctl
resource limiting framework, a working prototype implementation is
available.
__________________________________________________________________
Read-only Port of NetBSD's UDF File System
URL: https://github.com/williamdevries/UDF
Contact: Will DeVries <william.devries< at >gmail.com>
An initial read-only port of NetBSD's UDF file system has been largely
completed. (The UDF file system is often used on CD, DVD and Blu-Ray
discs.) This port provides a number of advantages over FreeBSD's
current UDF implementation, which include:
* Support for version 2.60 of the UDF file system specification.
FreeBSD's current implementation only partially supports version
1.5 of the standard, which was released in 1997. Since Windows and
other systems support newer version of this file system, our users
are left without the ability to read some media written by these
systems. In addition, Blu-Ray discs are commonly written using
version 2.50 or 2.60.
* The ability to override the owner and group for all the files and
directories on a UDF volume using mount options.
* The ability to set the owner and group for files and directories
that lack defined owner or group information using mount options.
(The UDF specification allows for files and directories without
owners or groups.)
* The ability to override the mode for all directories and files on a
volume using mount options.
* Support for mounting previous versions of incrementally recorded
media, like CD-Rs.
__________________________________________________________________
TCP-AO Authentication Option
URL: http://svnweb.freebsd.org/base/user/andre/tcp-ao/
Contact: André Oppermann <andre< at >FreeBSD.org>
Work is under way to implement TCP-AO (TCP Authentication Option)
according to RFC5925 and RFC5926. TCP-AO is an extension to TCP-MD5
signatures commonly used in routers to secure BGP routing protocol
sessions against spoofing attacks. The work is under contract and
sponsored by Juniper Networks.
__________________________________________________________________
The entities Documentation Branch
URL: http://svnweb.freebsd.org/doc/projects/entities/
Contact: René Ladan <rene< at >FreeBSD.org>
The entities branch was created to reduce duplication of committer
entities. Currently there is one in authors.ent (with email addresses)
and another one in developers.ent (without email addresses). This seems
to be a leftover from the doc/www split in earlier times. To remedy
this, developers.ent is merged into authors.ent and entities with email
addresses are postfixed as such. Apart from the instructions for the
initial commit, there should be little user-visible changes. Some
related cleanups, like cleaning up team definitions, replacing literal
names by entities from authors.ent, and adding missing names to
authors.ent are also made.
Open tasks:
1. Finish processing of the <email> tag.
2. Send out a CFT.
3. Merge back into head branch.
__________________________________________________________________
The FreeBSD Japanese Documentation Project
URL: http://www.FreeBSD.org/ja/
URL: http://www.jp.FreeBSD.org/doc-jp/
Contact: Hiroki Sato <hrs< at >FreeBSD.org>
Contact: Ryusuke Suzuki <ryusuke< at >FreeBSD.org>
Web page (htdocs): Newsflash and some other updates in the English
version have been translated to keep them up-to-date. Specifically, the
release related contents were updated in this period.
Books: FreeBSD Handbook has constantly been updated since the last
report; particularly, "ports", "desktop" section were largely updated.
Some progress has been made in the "advanced-networking" section,
contributed by a new translator.
"Writing FreeBSD Problem Reports" article is now in sync with the
English version.
Open tasks:
1. Further translation work of outdated documents in ja_JP.eucJP
subtree.
__________________________________________________________________
UFS/FFS Performance Work
URL: http://www.mckusick.com/publications/faster_fsck.pdf
Contact: Kirk McKusick <mckusick< at >mckusick.com>
Some work on the performance of UFS/FFS has been recently committed to
HEAD. The purpose of the corresponding change to the FFS layout policy
is to reduce the running time for a full file system check. It also
reduces the random access time for large files and speeds up the
traversal time for directory tree walks.
The key idea is to reserve a small area in each cylinder group
immediately following the inode blocks for the use of metadata,
specifically indirect blocks and directory contents. The new policy is
to preferentially place metadata in the metadata area and everything
else in the blocks that follow the metadata area.
The size of this area can be set when creating a filesystem using
newfs(8) or changed in an existing filesystem using tunefs(8). Both
utilities use the -k held-for-metadata-blocks option to specify the
amount of space to be held for metadata blocks in each cylinder group.
By default, newfs(8) sets this area to half of minfree (typically 4% of
the data area).
As with all layout policies, it only affect layouts of things allocated
after it is put in place. So these changes will primarily be noticable
on newly created file systems.
File system checks have been sped up by caching the cylinder group maps
in pass1 so that they do not need to be read again in pass5. As this
nearly doubles the memory requirement for fsck(8), the cache is thrown
away if other memory needs in fsck(8) would otherwise fail. Thus, the
memory footprint of fsck(8) remains unchanged in memory constrained
environments. This optimization will be evident on all UFS/FFS
filesystems.
This work was inspired by a paper presented at Usenix's FAST '13.
Open tasks:
1. MFC to 9-STABLE and possibly 8-STABLE should happen by May unless
problems arise with these changes in HEAD.
__________________________________________________________________
Wine32 on FreeBSD/amd64
URL: http://wiki.freebsd.org/i386-Wine
Contact: David Naylor <dbn< at >FreeBSD.org>
The i386-wine port (formally wine-fbsd64) has been added to the ports
collection (as emulators/i386-wine-devel). Although the port can only
be compiled under a x86 32-bit system the resulting package can be
installed on a x86 64-bit system and enable running of 32-bit Microsoft
Windows programs.
Packages for the port are in development and should be announced
shortly on the freebsd-questions and freebsd-emulation mailing lists.
There are some issues with Wine32 on FreeBSD/amd64 -- possibly related
to FreeBSD32_COMPACT, or other general 32/64-bit issues -- that could
do with some focus.
Open tasks:
1. Port wine64 to FreeBSD.
2. Port WoW64 (wine32 and wine64 together) to FreeBSD.
3. Fix 32- and 64-bit issues (such as Intel graphics not
accelerating).
__________________________________________________________________
Xfce/FreeBSD
URL: https://wiki.FreeBSD.org/Xfce
URL: http://people.freebsd.org/~olivierd/patches/midori-0.4.9_0.5.0.diff
Contact: FreeBSD Xfce Team <xfce< at >FreeBSD.org>
The Xfce FreeBSD Team has updated many ports, especially:
* tumbler: 0.1.27 (add new option, COVER)
* Parole: 0.5.0
* xfdesktop: 4.10.2
* Midori: 0.4.9 (full compatible with Vala 0.18), 0.5.0 is available
(see links)
* Orage: 4.8.4
* xfce4-terminal: 0.6.1 (renamed by upstream, previous name was
Terminal)
This last application contains drop-down functionality, new window
slides down from the top of the screen when key (we can define keyboard
shortcut) is pressed.
Open tasks:
1. Replace libxfce4gui (deprecated and not maintained by upstream) by
libxfce4ui in order to enhance support panel plugins for Xfce >=
4.10.
2. Work on Midori Gtk3 port.
3. Fix gtk-xfce-engine with Gtk+ >=3.6.
__________________________________________________________________
xorg on FreeBSD
URL: http://wiki.freebsd.org/Xorg
URL: http://people.freebsd.org/~zeising/xorg-7.7.diff
URL: http://trillian.chruetertee.ch/ports/browser/trunk
URL: http://trillian.chruetertee.ch/ports/browser/branches/xorg-7.7
Contact: FreeBSD X11 Team <x11< at >FreeBSD.org>
Contact: Niclas Zeising <zeising< at >FreeBSD.org>
Contact: Koop Mast <kwm< at >FreeBSD.org>
Most of the work during this period has been in updating, testing and
stabilizing the development repository. A number of xorg applications
and various other leaf ports has been committed as part of this effort.
After this a CFT was sent out asking for help in testing the remaining
bits in development, including updates to all major libraries and
xorg-server.
Currently, the CFT patch has been submitted for an exp-run to iron out
any final bugs. The plan is to merge it sometime after FreeBSD 8.4 is
released and the ports tree is reopened for commits.
Work is also on-going to port new versions of MESA and OpenGL, as well
as a new version of xorg-server, and perhaps in the future, Wayland.
These are considered more long-term goals and are not targeted for the
current update.
Open tasks:
1. Decide how to handle the new and old xorg distributions. In recent
xorg, a lot of legacy driver support has been dropped, therefore we
need to maintain two xorg distributions to not lose a lot of
hardware drivers. Currently, this is done by setting the flag
WITH_NEW_XORG in /etc/make.conf, but a more practical solution is
needed. This is especially important since the flag is not very
user-friendly, and since there currently will be no official
packages for the new distribution.
2. Continue to test and update xorg related ports. There are new
versions of xserver, as well as MESA and related OpenGL libraries
which needs to be ported and eventually integrated into the ports
tree.
3. Port Wayland. The future of graphical environments in open source
operating systems seems to be Wayland. This needs to be ported to
FreeBSD so that a wider audience can test it, and so that it
eventually can be integrated into the ports tree, perhaps as a
replacement for the current xorg.
4. Look into replacements for HAL. HAL is used for hot-plugging of
devices, but it has been long abandoned by Linux. A replacement,
perhaps build on top of devd would be nice to have. This work
should be coordinated with the FreeBSD GNOME and KDE teams.
__________________________________________________________________
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"</pre>Gabor Pali2013-05-12T17:54:05Build GENERIC with IPX support
http://comments.gmane.org/gmane.os.freebsd.stable/86378
<pre>Hi list,
I am using 9.1-RELEASE amd64 FreeBSD
I order to connect my FreeBSD box to NetWare servers, I am trying to
recompile the kernel.
To GENERIC config I've added following options:
options IPX
options NCP
options NWFS
unfortunately, during buildkernel process I got an error:
nwfs_subr.o: In function `ncp_lookup_volume':
/usr/src/sys/fs/nwfs/nwfs_subr.c:499: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:500: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:501: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:502: undefined reference to
`mb_put_uint16le'
/usr/src/sys/fs/nwfs/nwfs_subr.c:504: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:505: undefined reference to
`mb_put_uint32be'
/usr/src/sys/fs/nwfs/nwfs_subr.c:506: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:507: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:512: undefined reference to
`md_get_uint32le'
/usr/src/sys/fs/nwfs/nwfs_subr.c:513: undefined reference to
`md_get_uint32le'
/usr/src/sys/fs/nwfs/nwfs_subr.c:514: undefined reference to `md_get_uint8'
nwfs_subr.o: In function `ncp_get_namespaces':
/usr/src/sys/fs/nwfs/nwfs_subr.c:237: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:238: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:239: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:240: undefined reference to
`mb_put_uint16le'
/usr/src/sys/fs/nwfs/nwfs_subr.c:241: undefined reference to
`mb_put_uint32le'
/usr/src/sys/fs/nwfs/nwfs_subr.c:242: undefined reference to
`mb_put_uint32le'
/usr/src/sys/fs/nwfs/nwfs_subr.c:247: undefined reference to
`mb_put_uint16le'
/usr/src/sys/fs/nwfs/nwfs_subr.c:255: undefined reference to
`md_get_uint32le'
/usr/src/sys/fs/nwfs/nwfs_subr.c:256: undefined reference to `md_get_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:257: undefined reference to `md_get_uint8'
nwfs_subr.o: In function `ncp_setattr':
/usr/src/sys/fs/nwfs/nwfs_subr.c:393: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:394: undefined reference to `mb_put_mem'
/usr/src/sys/fs/nwfs/nwfs_subr.c:395: undefined reference to
`mb_put_uint32be'
/usr/src/sys/fs/nwfs/nwfs_subr.c:396: undefined reference to
`mb_put_uint16be'
nwfs_subr.o: In function `ncp_search_for_file_or_subdir':
/usr/src/sys/fs/nwfs/nwfs_subr.c:110: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:111: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:112: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:113: undefined reference to
`mb_put_uint16le'
/usr/src/sys/fs/nwfs/nwfs_subr.c:114: undefined reference to
`mb_put_uint32le'
/usr/src/sys/fs/nwfs/nwfs_subr.c:115: undefined reference to `mb_put_mem'
/usr/src/sys/fs/nwfs/nwfs_subr.c:116: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:117: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:118: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:123: undefined reference to `md_get_mem'
/usr/src/sys/fs/nwfs/nwfs_subr.c:124: undefined reference to `md_get_uint8'
nwfs_subr.o: In function `ncp_obtain_info':
/usr/src/sys/fs/nwfs/nwfs_subr.c:152: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:153: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:154: undefined reference to `mb_put_uint8'
/usr/src/sys/fs/nwfs/nwfs_subr.c:155: undefined reference to
`mb_put_uint16le'
/usr/src/sys/fs/nwfs/nwfs_subr.c:156: undefined reference to
`mb_put_uint32le'
ncp_mod.o: In function `sncp_request':
/usr/src/sys/netncp/ncp_mod.c:157: undefined reference to `mb_put_mem'
/usr/src/sys/netncp/ncp_mod.c:165: undefined reference to `md_get_mem'
ncp_mod.o: In function `ncp_conn_frag_rq':
/usr/src/sys/netncp/ncp_mod.c:450: undefined reference to `mb_put_mem'
/usr/src/sys/netncp/ncp_mod.c:465: undefined reference to `md_get_mem'
ncp_ncp.o: In function `ncp_negotiate_buffersize':
/usr/src/sys/netncp/ncp_ncp.c:164: undefined reference to `mb_put_uint16be'
/usr/src/sys/netncp/ncp_ncp.c:168: undefined reference to `md_get_uint16be'
ncp_ncp.o: In function `ncp_get_encryption_key':
/usr/src/sys/netncp/ncp_ncp.c:312: undefined reference to `md_get_mem'
ncp_ncp.o: In function `ncp_login_unencrypted':
/usr/src/sys/netncp/ncp_ncp.c:388: undefined reference to `mb_put_uint16be'
ncp_ncp.o: In function `ncp_login_encrypted':
/usr/src/sys/netncp/ncp_ncp.c:363: undefined reference to `mb_put_mem'
/usr/src/sys/netncp/ncp_ncp.c:364: undefined reference to `mb_put_uint16be'
ncp_ncp.o: In function `ncp_get_bindery_object_id':
/usr/src/sys/netncp/ncp_ncp.c:283: undefined reference to `mb_put_uint16be'
/usr/src/sys/netncp/ncp_ncp.c:289: undefined reference to `md_get_uint32be'
/usr/src/sys/netncp/ncp_ncp.c:290: undefined reference to `md_get_uint16be'
/usr/src/sys/netncp/ncp_ncp.c:291: undefined reference to `md_get_mem'
ncp_ncp.o: In function `ncp_negotiate_size_and_options':
/usr/src/sys/netncp/ncp_ncp.c:185: undefined reference to `mb_put_uint16be'
/usr/src/sys/netncp/ncp_ncp.c:186: undefined reference to `mb_put_uint8'
/usr/src/sys/netncp/ncp_ncp.c:191: undefined reference to `md_get_uint16be'
/usr/src/sys/netncp/ncp_ncp.c:193: undefined reference to `md_get_uint16be'
/usr/src/sys/netncp/ncp_ncp.c:194: undefined reference to `md_get_uint8'
ncp_ncp.o: In function `ncp_write':
/usr/src/sys/netncp/ncp_ncp.c:470: undefined reference to `mb_put_uint8'
/usr/src/sys/netncp/ncp_ncp.c:471: undefined reference to `mb_put_mem'
/usr/src/sys/netncp/ncp_ncp.c:472: undefined reference to `mb_put_uint32be'
/usr/src/sys/netncp/ncp_ncp.c:473: undefined reference to `mb_put_uint16be'
/usr/src/sys/netncp/ncp_ncp.c:474: undefined reference to `mb_put_uio'
ncp_ncp.o: In function `ncp_read':
/usr/src/sys/netncp/ncp_ncp.c:431: undefined reference to `md_get_uio'
/usr/src/sys/netncp/ncp_ncp.c:420: undefined reference to `mb_put_uint8'
/usr/src/sys/netncp/ncp_ncp.c:421: undefined reference to `mb_put_mem'
/usr/src/sys/netncp/ncp_ncp.c:422: undefined reference to `mb_put_uint32be'
/usr/src/sys/netncp/ncp_ncp.c:423: undefined reference to `mb_put_uint16be'
/usr/src/sys/netncp/ncp_ncp.c:428: undefined reference to `md_get_uint16be'
/usr/src/sys/netncp/ncp_ncp.c:430: undefined reference to `md_get_mem'
ncp_rq.o: In function `ncp_request_int':
/usr/src/sys/netncp/ncp_rq.c:281: undefined reference to `mb_fixhdr'
/usr/src/sys/netncp/ncp_rq.c:409: undefined reference to `md_initm'
/usr/src/sys/netncp/ncp_rq.c:420: undefined reference to `md_get_mem'
ncp_rq.o: In function `ncp_sign_packet':
/usr/src/sys/netncp/ncp_rq.c:239: undefined reference to `mb_put_mem'
ncp_rq.o: In function `ncp_rq_pathstring':
/usr/src/sys/netncp/ncp_rq.c:172: undefined reference to `mb_put_uint8'
ncp_rq.o: In function `ncp_rq_dbase_path':
/usr/src/sys/netncp/ncp_rq.c:199: undefined reference to `mb_put_uint8'
/usr/src/sys/netncp/ncp_rq.c:200: undefined reference to `mb_put_mem'
/usr/src/sys/netncp/ncp_rq.c:201: undefined reference to `mb_put_uint8'
/usr/src/sys/netncp/ncp_rq.c:217: undefined reference to `mb_put_uint8'
/usr/src/sys/netncp/ncp_rq.c:218: undefined reference to `mb_put_uint8'
/usr/src/sys/netncp/ncp_rq.c:213: undefined reference to `mb_put_uint8'
/usr/src/sys/netncp/ncp_rq.c:205: undefined reference to `mb_put_uint8'
ncp_rq.o:/usr/src/sys/netncp/ncp_rq.c:208: more undefined references to
`mb_put_uint8' follow
ncp_rq.o: In function `ncp_rq_dbase_path':
/usr/src/sys/netncp/ncp_rq.c:209: undefined reference to `mb_put_mem'
ncp_rq.o: In function `ncp_rq_pstring':
/usr/src/sys/netncp/ncp_rq.c:186: undefined reference to `mb_put_uint8'
ncp_rq.o: In function `ncp_rq_done':
/usr/src/sys/netncp/ncp_rq.c:138: undefined reference to `mb_done'
/usr/src/sys/netncp/ncp_rq.c:139: undefined reference to `md_done'
ncp_rq.o: In function `ncp_rq_init_any':
/usr/src/sys/netncp/ncp_rq.c:116: undefined reference to `mb_init'
/usr/src/sys/netncp/ncp_rq.c:125: undefined reference to `mb_reserve'
/usr/src/sys/netncp/ncp_rq.c:120: undefined reference to `mb_reserve'
ncp_rq.o: In function `ncp_rq_alloc_subfn':
/usr/src/sys/netncp/ncp_rq.c:92: undefined reference to `mb_reserve'
/usr/src/sys/netncp/ncp_rq.c:93: undefined reference to `mb_put_uint8'
ncp_rq.o: In function `ncp_rq_pathstring':
/usr/src/sys/netncp/ncp_rq.c:175: undefined reference to `mb_put_mem'
ncp_rq.o: In function `ncp_rq_pstring':
/usr/src/sys/netncp/ncp_rq.c:189: undefined reference to `mb_put_mem'
*** [kernel.debug] Error code 1
Stop in /tmp/obj/usr/src/sys/GENERICIPX.
*** [buildkernel] Error code 1
Stop in /usr/src.
*** [buildkernel] Error code 1
Stop in /usr/src.
641.92s user 284.90s system 102% cpu 15:03.37s total
marek< at >bsd-gen:/usr/src%
Does anyone still uses IPX and could help me compiling the kernel ?
Regards,
</pre>Marek Salwerowicz2013-05-11T23:14:18How abuot firewall_nat_rules?
http://comments.gmane.org/gmane.os.freebsd.stable/86376
<pre>Hi stable list,
Now ipfw_nat's rules must be write directly in firewall_nat_flags. This is
messy to describe many rules. firewall_nat_rules will be treat smartly.
To enable firewall_nat_rules,apply following patch to /etc/rc.firewall
--- /etc/rc.firewall.org2013-05-11 08:23:13.000000000 +0900
+++ /etc/rc.firewall2013-05-11 08:29:11.000000000 +0900
< at >< at > -162,6 +162,9 < at >< at >
case ${firewall_nat_enable} in
[Yy][Ee][Ss])
if [ -n "${firewall_nat_interface}" ]; then
+if [ -r "${firewall_nat_rules}" ]; then
+firewall_nat_flags="${firewall_nat_flags} `cat ${firewall_nat_rules}`"
+fi
if echo "${firewall_nat_interface}" | \
grep -q -E '^[0-9]+(\.[0-9]+){0,3}$'; then
firewall_nat_flags="ip ${firewall_nat_interface} ${firewall_nat_flags}"
and then put in /etc/rc.conf
firewall_enable="YES"
firewall_type="OPEN"
firewall_nat_enable="YES"
firewall_nat_interface="X.X.X.X"
firewall_nat_flags="deny_in reset same_ports unreg_only"
firewall_nat_rules="/etc/ipfw_nat.rules"
where X.X.X.X is the outgoing global address and firewall_nat_rules specfies
the file in which describe ipfw_nat's rules, actually ipfw arguments
following to "${fwcmd} nat 123 config log" for example
redirect_port tcp192.168.1.7:2401 2401
redirect_port tcp192.168.1.5:8080
redirect_port tcp192.168.1.1:2222069
redirect_port tcp192.168.1.2:2222053
redirect_port tcp192.168.1.3:2222025
redirect_port tcp192.168.1.4:2222080
redirect_port tcp192.168.1.5:2222021
redirect_port tcp192.168.1.6:2222067
redirect_port tcp192.168.1.7:2222401
redirect_port tcp192.168.1.8:2222081
redirect_port tcp192.168.1.32:910063189
redirect_port tcp192.168.1.252:910023089
redirect_port tcp192.168.1.254:2222
Regards
---
kiri< at >openedu.org
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"
</pre>KIRIYAMA Kazuhiko2013-05-11T00:30:15[releng_8 tinderbox] failure on powerpc/powerpc
http://comments.gmane.org/gmane.os.freebsd.stable/86375
<pre>TB --- 2013-05-10 23:38:23 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2013-05-10 23:38:23 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root< at >farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013-05-10 23:38:23 - starting RELENG_8 tinderbox run for powerpc/powerpc
TB --- 2013-05-10 23:38:23 - cleaning the object tree
TB --- 2013-05-10 23:38:23 - /usr/local/bin/svn stat /src
TB --- 2013-05-10 23:38:25 - At svn revision 250487
TB --- 2013-05-10 23:38:26 - building world
TB --- 2013-05-10 23:38:26 - CROSS_BUILD_TESTING=YES
TB --- 2013-05-10 23:38:26 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-05-10 23:38:26 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-05-10 23:38:26 - SRCCONF=/dev/null
TB --- 2013-05-10 23:38:26 - TARGET=powerpc
TB --- 2013-05-10 23:38:26 - TARGET_ARCH=powerpc
TB --- 2013-05-10 23:38:26 - TZ=UTC
TB --- 2013-05-10 23:38:26 - __MAKE_CONF=/dev/null
TB --- 2013-05-10 23:38:26 - cd /src
TB --- 2013-05-10 23:38:26 - /usr/bin/make -B buildworld
[...]
cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -c /src/usr.sbin/ndp/../../contrib/tcpdump/gmt2local.c
cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -o ndp ndp.o gmt2local.o
gzip -cn /src/usr.sbin/ndp/ndp.8 > ndp.8.gz
===> usr.sbin/newsyslog (all)
cc -O2 -pipe -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/newsyslog/newsyslog.c
cc1: warnings being treated as errors
/src/usr.sbin/newsyslog/newsyslog.c: In function 'delete_oldest_timelog':
/src/usr.sbin/newsyslog/newsyslog.c:1511: warning: unused variable 'valid'
*** [newsyslog.o] Error code 1
Stop in /src/usr.sbin/newsyslog.
*** [all] Error code 1
Stop in /src/usr.sbin.
*** [usr.sbin.all__D] Error code 1
Stop in /src.
*** [everything] Error code 1
Stop in /src.
*** [buildworld] Error code 1
Stop in /src.
TB --- 2013-05-11 00:21:02 - WARNING: /usr/bin/make returned exit code 1
TB --- 2013-05-11 00:21:02 - ERROR: failed to build world
TB --- 2013-05-11 00:21:02 - 2160.27 user 369.84 system 2559.17 real
http://tinderbox.freebsd.org/tinderbox-freebsd8-build-RELENG_8-powerpc-powerpc.full
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"
</pre>FreeBSD Tinderbox2013-05-11T00:21:02[releng_8 tinderbox] failure on sparc64/sparc64
http://comments.gmane.org/gmane.os.freebsd.stable/86374
<pre>TB --- 2013-05-10 23:38:53 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2013-05-10 23:38:53 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root< at >farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013-05-10 23:38:53 - starting RELENG_8 tinderbox run for sparc64/sparc64
TB --- 2013-05-10 23:38:53 - cleaning the object tree
TB --- 2013-05-10 23:38:53 - /usr/local/bin/svn stat /src
TB --- 2013-05-10 23:38:55 - At svn revision 250487
TB --- 2013-05-10 23:38:56 - building world
TB --- 2013-05-10 23:38:56 - CROSS_BUILD_TESTING=YES
TB --- 2013-05-10 23:38:56 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-05-10 23:38:56 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-05-10 23:38:56 - SRCCONF=/dev/null
TB --- 2013-05-10 23:38:56 - TARGET=sparc64
TB --- 2013-05-10 23:38:56 - TARGET_ARCH=sparc64
TB --- 2013-05-10 23:38:56 - TZ=UTC
TB --- 2013-05-10 23:38:56 - __MAKE_CONF=/dev/null
TB --- 2013-05-10 23:38:56 - cd /src
TB --- 2013-05-10 23:38:56 - /usr/bin/make -B buildworld
[...]
cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -c /src/usr.sbin/ndp/../../contrib/tcpdump/gmt2local.c
cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -fstack-protector -o ndp ndp.o gmt2local.o
gzip -cn /src/usr.sbin/ndp/ndp.8 > ndp.8.gz
===> usr.sbin/newsyslog (all)
cc -O2 -pipe -std=gnu99 -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/newsyslog/newsyslog.c
cc1: warnings being treated as errors
/src/usr.sbin/newsyslog/newsyslog.c: In function 'delete_oldest_timelog':
/src/usr.sbin/newsyslog/newsyslog.c:1511: warning: unused variable 'valid'
*** [newsyslog.o] Error code 1
Stop in /src/usr.sbin/newsyslog.
*** [all] Error code 1
Stop in /src/usr.sbin.
*** [usr.sbin.all__D] Error code 1
Stop in /src.
*** [everything] Error code 1
Stop in /src.
*** [buildworld] Error code 1
Stop in /src.
TB --- 2013-05-11 00:19:36 - WARNING: /usr/bin/make returned exit code 1
TB --- 2013-05-11 00:19:36 - ERROR: failed to build world
TB --- 2013-05-11 00:19:36 - 2036.98 user 363.34 system 2443.49 real
http://tinderbox.freebsd.org/tinderbox-freebsd8-build-RELENG_8-sparc64-sparc64.full
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"
</pre>FreeBSD Tinderbox2013-05-11T00:19:36[releng_8 tinderbox] failure on ia64/ia64
http://comments.gmane.org/gmane.os.freebsd.stable/86373
<pre>TB --- 2013-05-10 23:05:12 - tinderbox 2.10 running on freebsd-legacy2.sentex.ca
TB --- 2013-05-10 23:05:12 - FreeBSD freebsd-legacy2.sentex.ca 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root< at >farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
TB --- 2013-05-10 23:05:12 - starting RELENG_8 tinderbox run for ia64/ia64
TB --- 2013-05-10 23:05:12 - cleaning the object tree
TB --- 2013-05-10 23:05:12 - /usr/local/bin/svn stat /src
TB --- 2013-05-10 23:05:15 - At svn revision 250487
TB --- 2013-05-10 23:05:16 - building world
TB --- 2013-05-10 23:05:16 - CROSS_BUILD_TESTING=YES
TB --- 2013-05-10 23:05:16 - MAKEOBJDIRPREFIX=/obj
TB --- 2013-05-10 23:05:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin
TB --- 2013-05-10 23:05:16 - SRCCONF=/dev/null
TB --- 2013-05-10 23:05:16 - TARGET=ia64
TB --- 2013-05-10 23:05:16 - TARGET_ARCH=ia64
TB --- 2013-05-10 23:05:16 - TZ=UTC
TB --- 2013-05-10 23:05:16 - __MAKE_CONF=/dev/null
TB --- 2013-05-10 23:05:16 - cd /src
TB --- 2013-05-10 23:05:16 - /usr/bin/make -B buildworld
[...]
cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -c /src/usr.sbin/ndp/../../contrib/tcpdump/gmt2local.c
cc -O2 -pipe -I. -I/src/usr.sbin/ndp -I/src/usr.sbin/ndp/../../contrib/tcpdump -D_U_="" -std=gnu99 -o ndp ndp.o gmt2local.o
gzip -cn /src/usr.sbin/ndp/ndp.8 > ndp.8.gz
===> usr.sbin/newsyslog (all)
cc -O2 -pipe -std=gnu99 -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized -Wno-pointer-sign -c /src/usr.sbin/newsyslog/newsyslog.c
cc1: warnings being treated as errors
/src/usr.sbin/newsyslog/newsyslog.c: In function 'delete_oldest_timelog':
/src/usr.sbin/newsyslog/newsyslog.c:1511: warning: unused variable 'valid'
*** [newsyslog.o] Error code 1
Stop in /src/usr.sbin/newsyslog.
*** [all] Error code 1
Stop in /src/usr.sbin.
*** [usr.sbin.all__D] Error code 1
Stop in /src.
*** [everything] Error code 1
Stop in /src.
*** [buildworld] Error code 1
Stop in /src.
TB --- 2013-05-10 23:59:59 - WARNING: /usr/bin/make returned exit code 1
TB --- 2013-05-10 23:59:59 - ERROR: failed to build world
TB --- 2013-05-10 23:59:59 - 2852.12 user 412.70 system 3287.60 real
http://tinderbox.freebsd.org/tinderbox-freebsd8-build-RELENG_8-ia64-ia64.full
_______________________________________________
freebsd-stable< at >freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe< at >freebsd.org"
</pre>FreeBSD Tinderbox2013-05-10T23:59:59Search EngineSearch the mailing list at Gmanequery
http://search.gmane.org/?group=$group=gmane.os.freebsd.stable