Re: Call for bge(4) testers
Hi! There were lots of reports that stock bge(4) does not work on Dell Rx20/HP DL 360 G8. I tested it with 9.1-RC1 amd64 on a HP DL 360 G8. Without the patch, bge0 did not work (timeouts etc). With the patch, bge0 does work: bge0: Broadcom unknown BCM5719, ASIC rev. 0x5719001 mem 0xf6bf-0xf6bf,0xf6be-0xf6be,0xf6bd-0xf6bd irq 32 at device 0.0 on pci3 bge0: APE FW version: NCSI v1.0.88.0 bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E miibus0: MII bus on bge0 brgphy0: BCM5719C 1000BASE-T media interface PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Ethernet address: ac:16:2d:77:22:88 pci0:3:0:1: failed to read VPD data. box. I'm especially interested in whether there is any ASF/IPMI regression on BCM570x/571x. Any ipmi-specific tests I should make ? -- p...@opsec.eu+49 171 3101372 8 years to go ! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for bge(4) testers
Hi! box. I'm especially interested in whether there is any ASF/IPMI regression on BCM570x/571x. Any ipmi-specific tests I should make ? This comes with kldload ipmi: ipmi0: IPMI System Interface port 0xca2-0xca3 on acpi0 ipmi0: KCS mode found at io 0xca2 on acpi ipmi0: KCS error: ff ipmi0: IPMI device rev. 1, firmware rev. 1.10, version 2.0 ipmi0: Number of channels 1 ipmi0: Attached watchdog ipmi1: IPMI System Interface on isa0 device_attach: ipmi1 attach returned 16 ppc0: cannot reserve I/O port range -- p...@opsec.eu+49 171 3101372 8 years to go ! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for bge(4) testers
Hi! There were lots of reports that stock bge(4) does not work on Dell Rx20/HP DL 360 G8. I tested it with 9.1-RC1 amd64 on a HP DL 360 G8. Without the patch, bge0 did not work (timeouts etc). With the patch, bge0 does work: bge0: Broadcom unknown BCM5719, ASIC rev. 0x5719001 mem 0xf6bf-0xf6bf,0xf6be-0xf6be,0xf6bd-0xf6bd irq 32 at device 0.0 on pci3 bge0: APE FW version: NCSI v1.0.88.0 bge0: CHIP ID 0x05719001; ASIC REV 0x5719; CHIP REV 0x57190; PCI-E miibus0: MII bus on bge0 brgphy0: BCM5719C 1000BASE-T media interface PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow bge0: Ethernet address: ac:16:2d:77:22:88 pci0:3:0:1: failed to read VPD data. box. I'm especially interested in whether there is any ASF/IPMI regression on BCM570x/571x. Any ipmi-specific tests I should make ? -- p...@opsec.eu+49 171 3101372 8 years to go ! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for bge(4) testers
Hi. On 15.09.2012 03:27, YongHyeon PYUN wrote: I'm especially interested in whether there is any ASF/IPMI regression on BCM570x/571x. There's a reopened bug concerning 8.x releases version of the bge(4) driver not working with IPMI ( http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/122252 http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/122252 ). I can also say that enabling ASF on RELENG_8 still leads to locking and hangups. Does this CFT mean that this situation may be improved with the new bge(4) version, on 9.x ? Eugene. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for bge(4) testers
Hi, here is the dmesg output. bge0: HP NC107i PCIe Gigabit Server Adapter, ASIC rev. 0x5784100 mem 0xfe9f-0xfe9f irq 18 at device 0.0 on pci4 bge0: CHIP ID 0x05784100; ASIC REV 0x5784; CHIP REV 0x57841; PCI-E miibus0: MII bus on bge0 brgphy0: BCM5784 10/100/1000baseT PHY PHY 1 on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto, auto-flow FreeBSD 9.0 RELEASE. Regards. Qian watchdog timeouts can be triggered by various issues so it's hard to guess the root cause of the issue. Would you show me the dmesg output(bge(4)/brgphy(4) output only)? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for bge(4) testers
On Monday, September 17, 2012 6:46:31 am Kurt Jaeger wrote: Hi! box. I'm especially interested in whether there is any ASF/IPMI regression on BCM570x/571x. Any ipmi-specific tests I should make ? This comes with kldload ipmi: ipmi0: IPMI System Interface port 0xca2-0xca3 on acpi0 ipmi0: KCS mode found at io 0xca2 on acpi ipmi0: KCS error: ff ipmi0: IPMI device rev. 1, firmware rev. 1.10, version 2.0 ipmi0: Number of channels 1 ipmi0: Attached watchdog ipmi1: IPMI System Interface on isa0 device_attach: ipmi1 attach returned 16 ppc0: cannot reserve I/O port range That shows you have a working BMC (just ignore the ipmi1 warning). I think to test you will want to use ipmitool from a remote machine to access the BMC over the network. (Some BMC's have web UI's as well that support remote KVM, etc. That would be a better test than just using ipmitool.) -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: mfi driver performance
On Thursday, September 13, 2012 4:48:20 pm matt wrote: On 09/13/12 13:13, Garrett Cooper wrote: On Thu, Sep 13, 2012 at 12:54 PM, matt sendtom...@gmail.com wrote: On 09/10/12 19:31, Garrett Cooper wrote: ... It seems hw.mfi.max_cmds is read only. The performance is pretty close to expected with no nvram or bbu on this card and commodity disks from 1.5 years ago, as far as I'm concerned. I'd love better write performance, but it's probably being held back by the single platter in the mirror when it is writing far from its edge. Try loader.conf: $ grep -r hw.mfi.max_cmds /sys/dev/mfi/ /sys/dev/mfi/mfi.c:TUNABLE_INT(hw.mfi.max_cmds, mfi_max_cmds); Cheers, -Garrett $ cat /usr/src/sys/dev/mfi/*.c | fgrep 'max_cmds' static intmfi_max_cmds = 128; TUNABLE_INT(hw.mfi.max_cmds, mfi_max_cmds); SYSCTL_INT(_hw_mfi, OID_AUTO, max_cmds, CTLFLAG_RD, mfi_max_cmds, ncmds = MIN(mfi_max_cmds, sc-mfi_max_fw_cmds); Definitely a loader tunable, thanks. I'll try increasing and decreasing the value and running bonnie again...Still not sure whether I'm getting 3gb/s and 6gb/s negotiation with my drives. MPS correctly reported da devices with 600mb/s and 300mb/s transfers where appropriate. mfiutil doesn't seem to know, and mfip devices appear as 150mb/s. No transfer speed message when mfisyspd devices attach. Mess with mfi_max_cmds at your own risk. The limit was added to work around broken mfi(4) firmware revisions that would lock up when the entire command queue (256) was used. Just a suggestion to be cautious. It is probably safe to use more than 128, but I would be wary of using all of the slots on your adapter. (A verbose boost will show you the number of command slots your firmware supports.) -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Call for bge(4) testers
On Mon, Sep 17, 2012 at 5:27 AM, John Baldwin j...@freebsd.org wrote: On Monday, September 17, 2012 6:46:31 am Kurt Jaeger wrote: Hi! box. I'm especially interested in whether there is any ASF/IPMI regression on BCM570x/571x. Any ipmi-specific tests I should make ? This comes with kldload ipmi: ipmi0: IPMI System Interface port 0xca2-0xca3 on acpi0 ipmi0: KCS mode found at io 0xca2 on acpi ipmi0: KCS error: ff ipmi0: IPMI device rev. 1, firmware rev. 1.10, version 2.0 ipmi0: Number of channels 1 ipmi0: Attached watchdog ipmi1: IPMI System Interface on isa0 device_attach: ipmi1 attach returned 16 ppc0: cannot reserve I/O port range That shows you have a working BMC (just ignore the ipmi1 warning). I think to test you will want to use ipmitool from a remote machine to access the BMC over the network. (Some BMC's have web UI's as well that support remote KVM, etc. That would be a better test than just using ipmitool.) Also, just to see what the behavior is like, try rebooting the box while connected via remote KVM/SOL and if you have the gear to do so, try being connected via serial in parallel. Broadcoms have had issues in the past (personal experience) with ipmi on older versions of FreeBSD (well, ok.. bce, not bge) because of the song and dance done when initializing the BMC/NIC at boot where if you're connected via ipmitool/the remote KVM software while booting, it might kick you out (which is ok depending on the phase of the moon), but not let you back in (this is a problem if this didn't occur before). A similar issue with the NIC song and dance exists with Supermicros and the shared em(4)/igb(4) port and on pre-8.x there were bugs that prevent you from accessing the BMC after boot (but that was another driver interaction probably on the system). Thanks! -Garrett PS I'll give the patch a shot on my Lenovo workstation running 9-STABLE when I get a chance. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
