On 05/08/18 10:23, Harry Schmalzbauer wrote: > Bezüglich Kevin Bowling's Nachricht vom 08.05.2018 11:52 (localtime): > … >>> But if the simple iflib/hw-support test with kawela+hartwell helps I'm >>> happy to do. >> >> At this point it would be helpful, we think e1000 is nearing pretty >> good shape and I need to become familiar with any outstanding bugs. > > I started with hartwell: > em1: attach_pre capping queues at 2 > > Current cap: 0x460b > em1: using 1024 tx descriptors and 1024 rx descriptors > em1: msix_init qsets capped at 2 > em1: pxm cpus: 2 queue msgs: 4 admincnt: 1 > em1: using 2 rx queues 2 tx queues > em1: Using MSIX interrupts with 3 vectors > em1: allocated for 2 tx_queues > em1: allocated for 2 rx_queues > em1: Ethernet address: 00:1b:21:3e:90:52 > em1: netmap queues/slots: TX 2/1024, RX 2/1024 > dev.em.1.iflib.driver_version: 7.6.1-k > dev.em.1.queue_rx_1.rx_irq: 0 > dev.em.1.queue_rx_1.rxd_tail: 607 > dev.em.1.queue_rx_1.rxd_head: 21 > dev.em.1.queue_rx_0.rx_irq: 0 > dev.em.1.queue_rx_0.rxd_tail: 410 > dev.em.1.queue_rx_0.rxd_head: 412 > dev.em.1.queue_tx_1.tx_irq: 0 > dev.em.1.queue_tx_1.txd_tail: 8 > dev.em.1.queue_tx_1.txd_head: 8 > dev.em.1.queue_tx_0.tx_irq: 0 > dev.em.1.queue_tx_0.txd_tail: 428 > dev.em.1.queue_tx_0.txd_head: 428 > > Looks good so far, no problems with simple line speed (NFS4) copies. > > According to the i217 (Clarkville) Datasheet, it also supports 2 queues: > Table 63. Intel® Ethernet Controller I217 Capability PHY Address 01, > Page 776,Register 19 > But it probably was never supported, at least I haven't ever checked > pre-iflib. > Here's the clakville: > em0: attach_pre capping queues at 1 > em0: using 1024 tx descriptors and 1024 rx descriptors > em0: msix_init qsets capped at > em0: PCIY_MSIX capability not found; or rid 0 == 0. > em0: Using an MSI interrupt > em0: allocated for 1 tx_queues > em0: allocated for 1 rx_queues > em0: Ethernet address: 54:be:f7:0b:d7:4e > em0: netmap queues/slots: TX 1/1024, RX 1/1024 > > Since it's not not effort here, I also tried LACP, which panicked. > vmcore available, but what debugger to use these days? kgdb seems to be > replaced... > > -harry > _____________
/usr/libexec/kgdb should be the old kgdb that you are used to. Most of us have switched to using devel/gdb from ports. sean
signature.asc
Description: OpenPGP digital signature