Re: CPU0: local APIC error 0x40 CPU1: local APIC error 0x40
I just got the error just now. I'm keeping the machine booted for a little longer in case someone wants to ask any questions. If I simple reboot the machine, it will just hang forever and eventually need to power cycle it. Mar 9 04:58:51 jpr1 kernel: j...@jpr1.prdhost.com:/usr/obj/usr/src/sys/JPR1 amd64 Mar 9 04:58:51 jpr1 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0 Mar 9 04:58:51 jpr1 kernel: CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ (3214.84-MHz K8-class CPU) Mar 9 04:58:51 jpr1 kernel: Origin = "AuthenticAMD" Id = 0x40f33 Family = f Model = 43 Stepping = 3 Mar 9 04:58:51 jpr1 kernel: Features=0x178bfbff Mar 9 04:58:51 jpr1 kernel: Features2=0x2001 Mar 9 04:58:51 jpr1 kernel: AMD Features=0xea500800 Mar 9 04:58:51 jpr1 kernel: AMD Features2=0x1f Mar 9 04:58:51 jpr1 kernel: real memory = 8589934592 (8192 MB) Mar 9 04:58:51 jpr1 kernel: avail memory = 8228098048 (7846 MB) Mar 9 04:58:51 jpr1 kernel: ACPI APIC Table: Mar 9 04:58:51 jpr1 kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs Mar 9 04:58:51 jpr1 kernel: FreeBSD/SMP: 1 package(s) x 2 core(s) Mar 9 04:58:51 jpr1 kernel: cpu0 (BSP): APIC ID: 0 Mar 9 04:58:51 jpr1 kernel: cpu1 (AP): APIC ID: 1 Mar 9 04:58:51 jpr1 kernel: ioapic0: Changing APIC ID to 4 Mar 9 04:58:51 jpr1 kernel: ioapic0 irqs 0-23 on motherboard Mar 9 04:58:51 jpr1 kernel: kbd1 at kbdmux0 Mar 9 04:58:51 jpr1 kernel: acpi0: on motherboard Mar 9 04:58:51 jpr1 kernel: acpi0: [ITHREAD] Mar 9 04:58:51 jpr1 kernel: acpi0: Power Button (fixed) Mar 9 04:58:51 jpr1 kernel: acpi0: reservation of 0, a (3) failed Mar 9 04:58:51 jpr1 kernel: acpi0: reservation of 10, cedf (3) failed Mar 9 04:58:51 jpr1 kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 Mar 9 04:58:51 jpr1 kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0 Mar 9 04:58:51 jpr1 kernel: cpu0: on acpi0 Mar 9 04:58:51 jpr1 kernel: cpu1: on acpi0 Mar 9 04:58:51 jpr1 kernel: acpi_button0: on acpi0 Mar 9 04:58:51 jpr1 kernel: pcib0: port 0xcf8-0xcff on acpi0 Mar 9 04:58:51 jpr1 kernel: pci0: on pcib0 Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.0 (no driver attached) Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.1 (no driver attached) Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.2 (no driver attached) Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.3 (no driver attached) Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.4 (no driver attached) Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.5 (no driver attached) Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.6 (no driver attached) Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.7 (no driver attached) Mar 9 04:58:51 jpr1 kernel: vgapci0: mem 0xfc00-0xfcff,0xd000-0xdfff,0xfb00-0xfbff irq 16 at device 5.0 on pci0 Mar 9 04:58:51 jpr1 kernel: pci0: at device 9.0 (no driver attached) Mar 9 04:58:51 jpr1 kernel: isab0: at device 10.0 on pci0 Mar 9 04:58:51 jpr1 kernel: isa0: on isab0 Mar 9 04:58:51 jpr1 kernel: nfsmb0: port 0x4c00-0x4c3f,0x4c40-0x4c7f at device 10.1 on pci0 Mar 9 04:58:51 jpr1 kernel: smbus0: on nfsmb0 Mar 9 04:58:51 jpr1 kernel: smb0: on smbus0 Mar 9 04:58:51 jpr1 kernel: nfsmb1: on nfsmb0 Mar 9 04:58:51 jpr1 kernel: smbus1: on nfsmb1 Mar 9 04:58:51 jpr1 kernel: smb1: on smbus1 Mar 9 04:58:51 jpr1 kernel: pci0: at device 10.2 (no driver attached) Mar 9 04:58:51 jpr1 kernel: ohci0: mem 0xfe02f000-0xfe02 at device 11.0 on pci0 Mar 9 04:58:51 jpr1 kernel: ohci0: [ITHREAD] Mar 9 04:58:51 jpr1 kernel: usbus0: on ohci0 Mar 9 04:58:51 jpr1 kernel: ehci0: mem 0xfe02e000-0xfe02e0ff at device 11.1 on pci0 Mar 9 04:58:51 jpr1 kernel: ehci0: [ITHREAD] Mar 9 04:58:51 jpr1 kernel: usbus1: EHCI version 1.0 Mar 9 04:58:51 jpr1 kernel: usbus1: on ehci0 Mar 9 04:58:51 jpr1 kernel: atapci0: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfd00-0xfd0f at device 13.0 on pci0 Mar 9 04:58:51 jpr1 kernel: ata0: on atapci0 Mar 9 04:58:51 jpr1 kernel: ata0: [ITHREAD] Mar 9 04:58:51 jpr1 kernel: ata1: on atapci0 Mar 9 04:58:51 jpr1 kernel: ata1: [ITHREAD] Mar 9 04:58:51 jpr1 kernel: atapci1: port 0x9f0-0x9f7,0xbf0-0xbf3,0x970-0x977,0xb70-0xb73,0xf800-0xf80f mem 0xfe02d000-0xfe02dfff irq 20 at device 14.0 on pci0 Mar 9 04:58:51 jpr1 kernel: atapci1: [ITHREAD] Mar 9 04:58:51 jpr1 kernel: ata2: on atapci1 Mar 9 04:58:51 jpr1 kernel: ata2: [ITHREAD] Mar 9 04:58:51 jpr1 kernel: ata3: on atapci1 Mar 9 04:58:51 jpr1 kernel: ata3: [ITHREAD] Mar 9 04:58:51 jpr1 kernel: atapci2: port 0x9e0-0x9e7,0xbe0-0xbe3,0x960-0x967,0xb60-0xb63,0xf300-0xf30f mem 0xfe02c000-0xfe02cfff irq 21 at device 15.0 on pci0 Mar 9 04:58:51 jpr1 kernel: atapci2: [ITHREAD] Mar 9 04:58:51 jpr1 kernel: ata4: on atapci2 Mar 9 04:58:51 jpr1 kernel: ata4: [ITHREAD] Mar 9 04:58:51 jpr1 kernel: ata5: on atapci2 Mar 9 04:58:51 jpr1 kernel: ata5: [ITHREAD] Mar 9 04:58:51 jpr1 kernel: pcib1: at device 16.0 on pci0 Mar 9 04:58:51 jp
Re: CPU0: local APIC error 0x40 CPU1: local APIC error 0x40
Here's what happened when i did a ctrl+alt+del on the console. Mar 10 03:10:23 jpr1 rc.shutdown: 30 second watchdog timeout expired. Shutdown terminated. Mar 10 03:10:23 jpr1 init: /bin/sh on /etc/rc.shutdown terminated abnormally, going to single user mode Mar 10 03:10:23 jpr1 syslogd: exiting on signal 15 Mar 10 03:13:26 jpr1 syslogd: kernel boot file is /boot/kernel/kernel Mar 10 03:13:26 jpr1 kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done Mar 10 03:13:26 jpr1 kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...timed out Mar 10 03:13:26 jpr1 kernel: Waiting (max 60 seconds) for system process `syncer' to stop... Mar 10 03:13:26 jpr1 kernel: Syncing disks, vnodes remaining...0 timed out Mar 10 03:13:26 jpr1 kernel: All buffers synced. On Thu, Mar 10, 2011 at 1:50 AM, Jack L. wrote: > I just got the error just now. I'm keeping the machine booted for a > little longer in case someone wants to ask any questions. If I simple > reboot the machine, it will just hang forever and eventually need to > power cycle it. > > Mar 9 04:58:51 jpr1 kernel: > j...@jpr1.prdhost.com:/usr/obj/usr/src/sys/JPR1 amd64 > Mar 9 04:58:51 jpr1 kernel: Timecounter "i8254" frequency 1193182 Hz quality > 0 > Mar 9 04:58:51 jpr1 kernel: CPU: AMD Athlon(tm) 64 X2 Dual Core > Processor 6400+ (3214.84-MHz K8-class CPU) > Mar 9 04:58:51 jpr1 kernel: Origin = "AuthenticAMD" Id = 0x40f33 > Family = f Model = 43 Stepping = 3 > Mar 9 04:58:51 jpr1 kernel: > Features=0x178bfbff > Mar 9 04:58:51 jpr1 kernel: Features2=0x2001 > Mar 9 04:58:51 jpr1 kernel: AMD > Features=0xea500800 > Mar 9 04:58:51 jpr1 kernel: AMD Features2=0x1f > Mar 9 04:58:51 jpr1 kernel: real memory = 8589934592 (8192 MB) > Mar 9 04:58:51 jpr1 kernel: avail memory = 8228098048 (7846 MB) > Mar 9 04:58:51 jpr1 kernel: ACPI APIC Table: > Mar 9 04:58:51 jpr1 kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 > CPUs > Mar 9 04:58:51 jpr1 kernel: FreeBSD/SMP: 1 package(s) x 2 core(s) > Mar 9 04:58:51 jpr1 kernel: cpu0 (BSP): APIC ID: 0 > Mar 9 04:58:51 jpr1 kernel: cpu1 (AP): APIC ID: 1 > Mar 9 04:58:51 jpr1 kernel: ioapic0: Changing APIC ID to 4 > Mar 9 04:58:51 jpr1 kernel: ioapic0 irqs 0-23 on motherboard > Mar 9 04:58:51 jpr1 kernel: kbd1 at kbdmux0 > Mar 9 04:58:51 jpr1 kernel: acpi0: on motherboard > Mar 9 04:58:51 jpr1 kernel: acpi0: [ITHREAD] > Mar 9 04:58:51 jpr1 kernel: acpi0: Power Button (fixed) > Mar 9 04:58:51 jpr1 kernel: acpi0: reservation of 0, a (3) failed > Mar 9 04:58:51 jpr1 kernel: acpi0: reservation of 10, cedf (3) failed > Mar 9 04:58:51 jpr1 kernel: Timecounter "ACPI-fast" frequency 3579545 > Hz quality 1000 > Mar 9 04:58:51 jpr1 kernel: acpi_timer0: <24-bit timer at > 3.579545MHz> port 0x4008-0x400b on acpi0 > Mar 9 04:58:51 jpr1 kernel: cpu0: on acpi0 > Mar 9 04:58:51 jpr1 kernel: cpu1: on acpi0 > Mar 9 04:58:51 jpr1 kernel: acpi_button0: on acpi0 > Mar 9 04:58:51 jpr1 kernel: pcib0: port > 0xcf8-0xcff on acpi0 > Mar 9 04:58:51 jpr1 kernel: pci0: on pcib0 > Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.0 (no > driver attached) > Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.1 (no > driver attached) > Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.2 (no > driver attached) > Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.3 (no > driver attached) > Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.4 (no > driver attached) > Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.5 (no > driver attached) > Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.6 (no > driver attached) > Mar 9 04:58:51 jpr1 kernel: pci0: at device 0.7 (no > driver attached) > Mar 9 04:58:51 jpr1 kernel: vgapci0: mem > 0xfc00-0xfcff,0xd000-0xdfff,0xfb00-0xfbff irq > 16 at device 5.0 on pci0 > Mar 9 04:58:51 jpr1 kernel: pci0: at device 9.0 (no > driver attached) > Mar 9 04:58:51 jpr1 kernel: isab0: at device 10.0 on pci0 > Mar 9 04:58:51 jpr1 kernel: isa0: on isab0 > Mar 9 04:58:51 jpr1 kernel: nfsmb0: Controller> port 0x4c00-0x4c3f,0x4c40-0x4c7f at device 10.1 on pci0 > Mar 9 04:58:51 jpr1 kernel: smbus0: on nfsmb0 > Mar 9 04:58:51 jpr1 kernel: smb0: on smbus0 > Mar 9 04:58:51 jpr1 kernel: nfsmb1: Controller> on nfsmb0 > Mar 9 04:58:51 jpr1 kernel: smbus1: on nfsmb1 > Mar 9 04:58:51 jpr1 kernel: smb1: on smbus1 > Mar 9 04:58:51 jpr1 kernel: pci0: at device 10.2 (no > driver attached) > Mar 9 04:58:51 jpr1 kernel: ohci0: > mem 0xfe02f000-0xfe02 at device 11.0 on pci0 > Mar 9 04:58:51 jpr1 kernel: ohci0: [ITHREAD] > Mar 9 04:58:51 jpr1 kernel: usbus0: on ohci0 > Mar 9 04:58:51 jpr1 kernel: ehci0: controller> mem 0xfe02e000-0xfe02e0ff at device 11.1 on pci0 > Mar 9 04:58:51 jpr1 kernel: ehci0: [ITHREAD] > Mar 9 04:58:51 jpr1 kernel: usbus1: EHCI version 1.0 > Mar 9 04:58:51 jpr1 kernel: usbus1: controller> on ehci0 > Mar 9 04:58:51 jpr1 kernel: atapci0: controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xfd00-0
Re: happy hacker lite 2 keyboard
Quite late return to the subject. I finally ordered one for myself and have a question regarding it's usage with 64 bit system. All newer HH keuboards are usb ones. Manufacturer doesn't confirm connection to ps/2 port with usb to ps/2 adapter. Is there any reason not to do that on amd64? Best regards Zoran ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: happy hacker lite 2 keyboard
On Thu, 10 Mar 2011 10:15:27 -0600, Zoran Kolic wrote: Quite late return to the subject. I finally ordered one for myself and have a question regarding it's usage with 64 bit system. All newer HH keuboards are usb ones. Manufacturer doesn't confirm connection to ps/2 port with usb to ps/2 adapter. Is there any reason not to do that on amd64? Hrm, strange that a nice keyboard like that comes as USB only. My Adesso comes natively as PS/2 but has a PS/2 to USB converter that works flawlessly. The idea is that PS/2 is better for keyboards because it allows you to simultaneously press more keys at once than USB can handle. Anyway, I've had really bad luck with off the shelf adapters. You are probably OK with just running it as USB. Regards, Mark ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
gmirror start bug?
Dear Pawel, it seems thet gmirror is entering the endless loop if one inserted disk with previously configured mirror part in syncronyzing state: root@moose:/media/sata# gmirror list m0g Geom name: m0g State: STARTING Components: 2 Balance: split Slice: 4096 Flags: NONE GenID: 0 SyncID: 0 ID: 2992987948 Consumers: 1. Name: ad22g Mediasize: 272441875968 (254G) Sectorsize: 512 Mode: r1w1e1 State: NEW Priority: 0 Flags: SYNCHRONIZING GenID: 0 SyncID: 2 ID: 3619189671 root@moose:/media/sata# gmirror stop m0g ; gmirror clear ad22g Can't clear metadata on ad22g: Operation not permitted. gmirror: Not fully done. from kernel log: Mar 10 21:04:31 moose kernel: GEOM_MIRROR: Force device m0g start due to timeout. Mar 10 21:04:31 moose kernel: GEOM_MIRROR: Device m0g destroyed. Mar 10 21:04:35 moose kernel: GEOM_MIRROR: Force device m0g start due to timeout. Mar 10 21:04:35 moose kernel: GEOM_MIRROR: Device m0g destroyed. Mar 10 21:04:39 moose kernel: GEOM_MIRROR: Force device m0g start due to timeout. Mar 10 21:04:39 moose kernel: GEOM_MIRROR: Device m0g destroyed. ... In my case, a workaround was: detach broken disk, configure mirror with the same name (I did it over md), then gmirror clear ad22g -- but I suppose this situation should be somehow detected and loop broken. Thanks! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.ru *** ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: em0 hangs without any messages like "Watchdog timeout" only down/up reset it.
On Thu, 2011-02-24 at 03:03 -0800, Pete French wrote: > I havent investigated far enough yet to see if this is the same problem, but > I am also seeing hangs on em0 when under heavy load. This is 8-STABLE from > the 17 at around 3pm. > > em0@pci0:0:25:0:class=0x02 card=0x281e103c chip=0x10bd8086 > rev=0x02 hdr=0x00 > vendor = 'Intel Corporation' > device = 'Intel 82566DM Gigabit Ethernet Adapter (82566DM)' > class = network > subclass = ethernet > > What I am doing here is using ggated/ggatec to provide drives to another > machine which is adding them into a ZFS pool. This locks up the ethernet > in about 20 minutes. Going to concole on the machine all looks fine, > but it is not possible to ping anything through the em0 interface. > > I have no special tunings for em0, though I do have expanded buffer > space to improve the ggated performance > > kern.ipc.maxsockbuf=1048576 > net.inet.tcp.sendspace=131072 > net.inet.tcp.recvspace=131072 > > Machine is amd64 with 6 gig of RAM. > > -pete. > _ If you ifconfig down/up the interface does it come back to life? Sean ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: happy hacker lite 2 keyboard
On 03/10/2011 09:31, Mark Felder wrote: Hrm, strange that a nice keyboard like that comes as USB only. It's not _that_ strange. PS/2 doesn't allow for safe hot-plugging, USB does. And very few typists are going to exceed the keyrate of USB. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
kldload if_carp fails on 8.2 when kernel built without SCTP option -- link_elf_obj: symbol sha1_loop undefined
Hello! I have amd64 FreeBSD-8.2 box and found that kldload'ing if_carp fails with "link_elf_obj: symbol sha1_loop undefined" message. When using a kernel with SCTP option the problem goes away. Is it intentional? Is carp really needs SCTP? Also if I run ld manually the module loads fine: cd /usr/src/sys/modules/if_carp && make && ld -d -warn-common -r -d -o if_carp.ko ip_carp.o /usr/obj/usr/src/sys/XGATE/modules/usr/src/sys/modules/crypto/sha1.o && make load. Unfortunately I am not familiar with with kernel build process and need advice how to make happy if_carp module and my kernel. -- Mikhail ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: happy hacker lite 2 keyboard
"Mark Felder" writes: - On Thu, 10 Mar 2011 10:15:27 -0600, Zoran Kolic wrote: - > All newer HH keuboards are usb ones. Manufacturer doesn't - > confirm connection to ps/2 port with usb to ps/2 adapter. - > Is there any reason not to do that on amd64? - - - Hrm, strange that a nice keyboard like that comes as USB only. The orginal Happy Hacker was PS2. I have two of those, as well as two of the USB HH2's.. I don't know if the original Happy Hacker keyboard is still available, it hasn't been an issue for me. :D -- Eric Schnoebelene...@cirr.com http://www.cirr.com "Cutting the space budget really restores my faith in humanity. It eliminates dreams, goals, and ideals and lets us get straight to the business of hate, debauchery, and self-annihilation." -- Johnny Hart ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
LSI SAS2008 performance with mps(4) driver
I'm running a build of the mps(4) driver on FreeBSD 8.2 with an LSI SAS2008 bus adapter. The code I'm using was current as of the last commit on 2011-02-25, and is built for amd64. I can't seem to get any better performance than about 250MB/s writes through the controller. I'm testing with a zpool of six 250MB magnetic SATA disks, doing a couple of concurrent sequential writes with dd: dd bs=128k if=/dev/zero of=/datadisk/zero1 & dd bs=128k if=/dev/zero of=/datadisk/zero2 & This is in comparison to an older LSI C1068E controller using the mpt driver with an identical 6-disk zpool. Such a configuration can easily sustain 500MB/s writes. A devlist from camcontrol reports: scbus0 on mps0 bus 0: at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1,da1) at scbus0 target 2 lun 0 (pass2,da2) at scbus0 target 3 lun 0 (pass3,da3) at scbus0 target 4 lun 0 (pass4,da4) at scbus0 target 5 lun 0 (pass5,da5) at scbus0 target 6 lun 0 (pass6,da6) at scbus0 target 7 lun 0 (pass7,da7) scbus-1 on xpt0 bus 0: <> at scbus-1 target -1 lun -1 (xpt0) I realize that this driver is fairly new; if there is any information that would be helpful in finding the bottleneck, I would be happy to provide it. Thanks! - .Dustin___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: em0 hangs without any messages like "Watchdog timeout" only down/up reset it.
> If you ifconfig down/up the interface does it come back to life? Nope - has no effect. See another separate post of mine about how I added another em card, and that works fine. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
if_bridge and IPv6
Hi, I have a bridge interface with em0 and tap0/tap1 on it to run a layer 2 VPN. I find that em0 gets an IPv6 link local address but bridge0 does not (via net.inet6.ip6.auto_linklocal). I did some googling and it seems that this is a deliberate policy decision, and unfortunately you can't change it on a per interface basis :) It would be nice if I could suppress automatic link local for em0 and enable it on bridge0 rather than having to delete & add them manually. Also, does anyone have a code snippet handy for generating link local addresses? My google-fu was unable to find a description.. Thanks :) -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: LSI SAS2008 performance with mps(4) driver
Hello Dustin, I've been testing this SAS2008 LSI chip (on a LSI 9211-8i) for the last month or so and I can say that it makes a pretty good HBA but there are indeed a few caveats you might need to be aware of. In support of that - tonight I finished a FreeBSD 8.2-STABLE machine with 2 x 24 disk chassis (each with a 3Gbit expander) = 48 x 2TB SATA RE4-GP disks in 6 x 8disk raidz2 and I am able to squeeze out 900MB/s write and 1200 MB/s read in a sequential (single dd) manner. The limit here is the backplane speed. So back to your problem: 1) What kind of backplane are you using: please specify the exact model. Is it a SAS expander or direct attached? 3Gbit/s or 6Gbit/s? 2) What kind of disk controller exactly are you using? More importantly what kind of firmware does it have? Those two are very important. In my case it turned out that if I was connecting SAS2008 chips to pretty much every kind of SuperMicro SAS expander backplanes (tried against 826EL26, 836E1, 846E1) I was getting around 200-300MB/s read/write speeds (FreeBSD and Linux). Direct attached backplanes (826A) worked fine. At the end it turned out that it was some sort of a problem with the LSI firmware (version 8.00 in my case) and I was given to try version 9.00 (soon to be released) which completely solved the problem. Contact LSI support (very high quality) if you want to try this firmware. I can't seem to get any better performance than about 250MB/s writes through > the controller. I'm testing with a zpool of six 250MB magnetic SATA disks, > doing a couple of concurrent sequential writes with dd: > > dd bs=128k if=/dev/zero of=/datadisk/zero1 & > dd bs=128k if=/dev/zero of=/datadisk/zero2 & > > 3) What kind of zpool raid level do you have those disks organized in? 4) Running two parallel dd's on the same pool will actually turn the game into no-so-sequential type and more of a random access. Please try the following and paste results here: 4.1) dd if=/dev/zero of=/datadisk/zero1 bs=1M count=5 (only one dd and use a file size larger than your memory) 4.2) Destroy the zpool (if you have no useful data on it of course) and try dd against each and every disk individually. So something like: dd if=/dev/zero of=/dev/da0 bs=1M count=5 dd if=/dev/da0 of=/dev/null bs=1M count=5 monitor throughput with gstat -f da0 or I can send you a simple C program that I wrote which resembles dd but prints stats every second. On a related note I also experienced very slow read speeds (200MB/s) with the above mentioned configuration and after enabling prefetch (I used to set it to disabled as per Jeremy Chadwick's advise) everything went back to normal - so keep it in mind. Cheers, Rumen Telbizov -- Rumen Telbizov http://telbizov.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: if_bridge and IPv6
"Daniel O'Connor" writes: > Hi, I have a bridge interface with em0 and tap0/tap1 on it to run a > layer 2 VPN. > > I find that em0 gets an IPv6 link local address but bridge0 does not > (via net.inet6.ip6.auto_linklocal). I did some googling and it seems > that this is a deliberate policy decision, and unfortunately you can't > change it on a per interface basis :) > > It would be nice if I could suppress automatic link local for em0 and > enable it on bridge0 rather than having to delete & add them manually. > > Also, does anyone have a code snippet handy for generating link local > addresses? My google-fu was unable to find a description.. You should be able to do something like the following: ifconfig bridge0 inet6 fe80:: eui64 add That assumes that it has a MAC address already assigned. I can't help if it doesn't have one yet. -- Carl Johnsonca...@peak.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: if_bridge and IPv6
Hi,
> On Thu, 10 Mar 2011 21:19:00 -0800
> Carl Johnson said:
carlj> You should be able to do something like the following:
carlj> ifconfig bridge0 inet6 fe80:: eui64 add
carlj> That assumes that it has a MAC address already assigned. I can't help
carlj> if it doesn't have one yet.
Unfortunately, eui64 option doesn't support link-local address.
You need to specify link-local address, explicitly.
Here is a patch to support it.
Sincerely,
Index: sbin/ifconfig/af_inet6.c
diff -u -p sbin/ifconfig/af_inet6.c.orig sbin/ifconfig/af_inet6.c
--- sbin/ifconfig/af_inet6.c.orig 2009-11-21 20:28:57.783110487 +0900
+++ sbin/ifconfig/af_inet6.c 2009-11-23 21:00:02.212252557 +0900
@@ -36,6 +36,9 @@ static const char rcsid[] =
#include
#include
#include
+#include
+#include
+#include
#include
#include
@@ -130,6 +133,56 @@ setip6vltime(const char *seconds, int du
setip6lifetime("vltime", seconds, s, afp);
}
+static struct sockaddr_dl *
+getsdl(struct ifaddrs *ifap, char *ifname)
+{
+ struct ifaddrs *ifa;
+ struct sockaddr_dl *sdl = NULL;
+
+ for (ifa = ifap; ifa; ifa = ifa->ifa_next) {
+ if (ifname != NULL && strcmp(ifa->ifa_name, ifname) != 0)
+ continue;
+ if (ifa->ifa_addr == NULL)
+ continue;
+ if (ifa->ifa_addr->sa_family != AF_LINK)
+ continue;
+ sdl = (struct sockaddr_dl *)ifa->ifa_addr;
+ if (sdl == NULL)
+ continue;
+ if (sdl->sdl_type != IFT_ETHER ||
+ sdl->sdl_alen != ETHER_ADDR_LEN) {
+ sdl = NULL;
+ continue;
+ }
+ break;
+ }
+ return (sdl);
+}
+
+static void
+link2eui64(struct ifaddrs *ifap, struct in6_addr *in6)
+{
+ struct sockaddr_dl *sdl;
+ char *cp;
+
+ sdl = getsdl(ifap, name);
+ if (sdl == NULL) {
+ sdl = getsdl(ifap, NULL);
+ if (sdl == NULL)
+ errx(EXIT_FAILURE, "cannot find interface information");
+ }
+ cp = (char *)(sdl->sdl_data + sdl->sdl_nlen);
+ in6->s6_addr[8] = cp[0];
+ in6->s6_addr[8] ^= 0x02; /* reverse the u/l bit*/
+ in6->s6_addr[9] = cp[1];
+ in6->s6_addr[10] = cp[2];
+ in6->s6_addr[11] = 0xff;
+ in6->s6_addr[12] = 0xfe;
+ in6->s6_addr[13] = cp[3];
+ in6->s6_addr[14] = cp[4];
+ in6->s6_addr[15] = cp[5];
+}
+
static void
setip6eui64(const char *cmd, int dummy __unused, int s,
const struct afswtch *afp)
@@ -156,10 +209,13 @@ setip6eui64(const char *cmd, int dummy _
}
}
}
- if (!lladdr)
- errx(EXIT_FAILURE, "could not determine link local address");
-
- memcpy(&in6->s6_addr[8], &lladdr->s6_addr[8], 8);
+ if (!lladdr) {
+ if (!IN6_IS_ADDR_LINKLOCAL(in6))
+ errx(EXIT_FAILURE,
+ "could not determine link local address");
+ link2eui64(ifap, in6);
+ } else
+ memcpy(&in6->s6_addr[8], &lladdr->s6_addr[8], 8);
freeifaddrs(ifap);
}
--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
u...@mahoroba.org ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: statd/lockd startup failure
>> On 02/18/2011 10:08, Rick Macklem wrote: >> > The attached patches changes the behaviour so that it tries to >> > get an unused port for each of the 4 cases. >> >> can you send me the patches? >> thanks, >> danny > They're attached. If you get to test them, please let me know > how it goes. > > rick Hi Rick, the good side of living on different time zones :-) I got impatient, so I came up with a different fix. The rational is that IMHO, there is no need for all listeners to be on the same port: rnd> rpcinfo protonew |grep mountd 151udp6 ::.3.141 mountd superuser 153udp6 ::.3.141 mountd superuser 151tcp6 ::.3.141 mountd superuser 153tcp6 ::.3.141 mountd superuser 151udp 0.0.0.0.3.141 mountd superuser 153udp 0.0.0.0.3.141 mountd superuser 151tcp 0.0.0.0.3.92 mountd superuser <--- 153tcp 0.0.0.0.3.92 mountd superuser <--- rnd> rpcinfo -t protonew mountd program 15 version 1 ready and waiting rpcinfo: RPC: Program/version mismatch; low version = 1, high version = 3 program 15 version 2 is not available program 15 version 3 ready and waiting the patches are in: ftp://ftp.cs.huji.ac.il/users/danny/freebsd/patches/address_already_in_use/ cheers, danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
