gmane.os.freebsd.stable

Re: Apparent fxp regression in FreeBSD 8.4-RC3

Jeremy Chadwick — 2013-05-24T01:09:43

Mike, Yong-Hyeon asked you a very important question which you didn't
answer:

http://lists.freebsd.org/pipermail/freebsd-stable/2013-May/073458.html

If you assign a static IP address, does fxp0 behave properly?

I'm also re-adding Yong-Hyeon to the CC list here.

Re: Apparent fxp regression in FreeBSD 8.4-RC3

Michael L. Squires — 2013-05-24T00:18:33

I've just tested 8.4-RC3 using a different Supermicro 1U box with a fresh
installation of 8.4-RC3.  I had problems with the installation, wouldn't
boot until I used a Windows 98 FDISK to write a master boot record (no 
idea why; this system uses an Adaptec SATA 1.5 6-channel PCI-X board with two
drives in RAID 1).

Using the em0 interface there are no problems with DHCP; when I switch to 
the fxp0 interface the interface starts going up/down in the same manner as 
reported.

The problem appears associated with "world", not with the kernel (running
the 8.4 kernel with the 8.3 world does not have this problem).

This motherboard is an X5DPL-iGM with 2 Xeon 2.8GHz CPUs and 4 GB of RAM.
The other unit (an earlier board) has a Serverworks chipset with a single
Xeon CPU but also with a 100Mbit Intel Pro100 Ethernet port and a 1000Mbit
Intel Pro1000 Ethernet port.

This unit isn't doing anything useful, so testing isn't a problem.

Mike Squires
mikes< at >siralan.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"

Proposed MFC to hastctl: compact 'status' and introduce 'list' command

Dmitry Morozovsky — 2013-05-23T20:54:56

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!

Re: Swap Warning Message?

Jeremy Chadwick — 2013-05-23T19:48:58

Taken from my /boot/loader.conf:


# Set kern.maxswzone to 0 to squelch "total configured swap exceeds
# maximum recommended amount" warning, even with maxpages/2 fix.
# http://lists.freebsd.org/pipermail/freebsd-stable/2012-August/thread.html#69301
#
kern.maxswzone="0"


Give the small amount of memory on your system, I would suggest using
the above /boot/loader.conf setting, since your system is significantly 
likely to make use of lots of swap; decreasing swap space in your case
seems downright silly.

Re: Swap Warning Message?

Ronald Klop — 2013-05-23T13:27:24


Do you ever use that amount of swap?
Swap needs some memory for administration of which page goes where so it  
has a cost to increase swap too much.
If you are swapping 2 GB on 256 MB I don't think you have a very usable  
machine, but I don't know the details of what you are doing. Maybe your  
swap is on very fast SSD.

My advice would be to monitor your swap usage and reduce the amount of  
swap to a little more than you really use. Probably 1 or 2 times the  
amount of RAM.

Ronald.
_______________________________________________
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"

Swap Warning Message?

Michael Gass — 2013-05-23T12:55:20

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?

Re: OpenSSH in -STABLE

Dag-Erling Smørgrav — 2013-05-22T08:13:59

Use the port.

DES

Re: OpenSSH in -STABLE

Freddie Cash — 2013-05-22T03:28:54

Well, you showed an interest in testing a specific feature of 6.2, so a
recommendation to use the version in ports is perfectly valid. :)
 On 2013-05-21 8:03 PM, <usaopp< at >hushmail.com> wrote:

_______________________________________________
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"

Re: OpenSSH in -STABLE

Jeremy Chadwick — 2013-05-22T03:12:11

Typo on my part: this should have read May 17th, as is obvious from
svnweb.

Re: OpenSSH in -STABLE

Jeremy Chadwick — 2013-05-22T03:11:09

Try freebsd-security< at >freebsd.org, I am certain you will get an answer
there.

Fact: OpenSSH 6.2p1 was imported to head/CURRENT on March 22nd, and
6.2p2 was imported to head/CURRENT on May 22nd:

http://svnweb.freebsd.org/base/head/crypto/openssh/ChangeLog

OpenSSH is such an important/key piece of software that, much like
OpenSSL, it is one that does not warrant haste when it comes to getting
MFC'd.  If you want something more recent on non-CURRENT, you will
usually be told to run the version from ports.

Re: OpenSSH in -STABLE

2013-05-22T03:02:27

On Tue, 21 May 2013 22:20:08 -0400 "David Wolfskill" 
<david< at >catwhisker.org> wrote:

Thanks, but that wasn't what I asked about. I'm aware of the 
version in ports.

_______________________________________________
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"

em2: watchdog timeout -- resetting

Giorgio Emanuel — 2013-05-22T03:01:38

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"

Re: OpenSSH in -STABLE

David Wolfskill — 2013-05-22T02:19:58

Please refer to ports/security/openssh-portable; its Makefile says it's
6.2p2,1, last updated about 5 days ago.

Peace,
david

OpenSSH in -STABLE

2013-05-22T01:42:39

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"

Re: Command line not responding

Warren Block — 2013-05-21T15:24:34


It is almost always a mistake to set CFLAGS in make.conf.  Not only does 
it not improve performance, it frequently causes problems.  It will 
sometimes decrease performance for ports that can safely use custom 
CFLAGS themselves, because it prevents them from using those custom 
flags.

In other words, custom CFLAGS provide few or zero improvements, and have 
a significant risk of causing problems.
_______________________________________________
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"

Re: still mbuf leak in 9.0 / 9.1?

dennis berger — 2013-05-21T12:40:38

Hi Jeremy,
thanks for your detailed explanation.


-dennis

Am 18.05.2013 um 17:35 schrieb Jeremy Chadwick:


Dipl.-Inform. (FH)
Dennis Berger

email:   db< at >bsdsystems.de
mobile: +491791231509
fon: +494054001817

_______________________________________________
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"

Re: Unexpected reboot/crash on 8.2-RELEASE.

Steven Hartland — 2013-05-19T10:51:57

Under 8.2 once MFI sees a timeout it will timeout forever.

I committed major updates to MFI in r247367 & r247369 which deal with
many error condition problems that cause panics. So if your seeing issues
with MFI I'd suggest you upgrade to stable/8.

    Regards
    Steve

----- Original Message ----- 
From: <kpneal< at >pobox.com>
To: <freebsd-stable< at >freebsd.org>
Sent: Sunday, May 19, 2013 2:45 AM
Subject: Unexpected reboot/crash on 8.2-RELEASE.




================================================
This e.mail is private and confidential between Multiplay (UK) Ltd. and the person or entity to whom it is addressed. In the event of misdirection, the recipient is prohibited from using, copying, printing or otherwise disseminating it or any information contained in it. 

In the event of misdirection, illegible or incomplete transmission please telephone +44 845 868 1337
or return the E.mail to postmaster< at >multiplay.co.uk.

_______________________________________________
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"

Re: Is there a library issue between 9.0 and 9.1 -ThreadRuneLocale ?

Xin Li — 2013-05-19T06:06:58

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 5/18/13 11:49 AM, Michael Gass wrote:

You will have to move up to 9.1, running binaries compiled for newer
FreeBSD versions is not supported.

You don't have to start over though, running binaries compiled for
older FreeBSD versions is supported.

Cheers,

-----BEGIN PGP SIGNATURE-----

iQEcBAEBCAAGBQJRmGwCAAoJEG80Jeu8UPuzO+cH/R4ru4Br7zq0kMvIs7G3IJEZ
uKYUG1gmDrEFcHD67huPTGcS9YX56U5eb3EXuMiT/913WGgVVrcjxU/ui96Y3hEs
zJy5BIha9MEYzqv52fqWQtyCusJFcW+0aMHQrd9gDaCJuTmfpQ0ArcZ0yWoPu3UV
cubW0vHODkGBUx2MGPURqMLxow8FAFnUvCinymWhHTfPwnh7WwocqA5cR6/H40hg
RbOJoCDxvw2f/s9eeAKW1ebjpxQ1JfvEPNvq9Ss+pZvZk23aCUxEPfT6Mdlm27EY
VZJFNY2yTXCT+ZTMO00ytOjjd51hKo7C2/FJ41dtHICN4VQFbZD1pTnoDR1kCYs=
=uUhB
-----END PGP SIGNATURE-----
_______________________________________________
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"

Re: Unexpected reboot/crash on 8.2-RELEASE.

2013-05-19T05:05:24

Ah. This is probably the missing piece of info I needed. It sound like
what I thought was evidence pointing away from a power outage really isn't.

Given this I guess I can assume that this was a simple power outage.

Thanks for the help!
 

Yep. I meant "had been" or "has previously been".
 

Probably, but I threw it in there anyway. A machine is stable for 400+
days, has mfi issues, and a few days later unexpectedly gets restarted.
Coincidence? It sounds like it now, but I didn't know in my first post
on this to the list.

Re: Unexpected reboot/crash on 8.2-RELEASE.

2013-05-19T04:46:57

It was showing 472 days before it was rebooted. Sorry I used the wrong
tense in my statement above.
 

Here's the status at this very second:

12:42AM  up 10:34, 3 users, load averages: 0.00, 0.03, 0.00

That looks an awful lot like the machine was restarted for some reason.
What I don't know is why.



You usually mention people not giving enough information. I'm trying to
provide anything I can think of that might for whatever reason be involved.

Re: Unexpected reboot/crash on 8.2-RELEASE.

Mark Johnston — 2013-05-19T02:36:37

The LSI controllers I've used will keep internal event logs which are
persistent across power cycles (so long as the BBU isn't dead,
presumably). It looks like mfi(4) has been set up to dump the entire
event log during boot. Log entries created after the last reboot are
displayed with a timestamp of "boot + Ns".


That's a bit confusing... did you mean "had been"? This is the exact
uptime that's in status.txt below.


This is probably unrelated? As an aside, it'd be nice if mfi(4) dumped
info about the dcmd/io cmd at least once if it times out. At the moment,
it only does that if MFI_DEBUG is enabled... does anyone have an
objection to changing this from a compile-time option to a sysctl?

Thanks,
-Mark

_______________________________________________
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"