Subject: wm0: wm_tx_offload: packet headers did not fit in first mbuf, packet dropped
To: None <current-users@netbsd.org>
From: Markus W Kilbinger <kilbi@rad.rwth-aachen.de>
List: current-users
Date: 11/30/2004 20:25:42
Hi!

Recent -current changes produce many

  wm0: wm_tx_offload: packet headers did not fit in first mbuf, packet dropped
  wm1: wm_tx_offload: packet headers did not fit in first mbuf, packet dropped

messages on one of our i386 machines (the only machine with wm* nics,
dmesg excerpt):

  wm0 at pci2 dev 10 function 0: Intel i82545EM 1000BASE-T Ethernet, rev. 1
  wm0: interrupting at ioapic0 pin 22 (irq 5)
  wm0: 32-bit 33MHz PCI bus
  wm0: 256 word (8 address bits) MicroWire EEPROM
  wm0: Ethernet address 00:07:e9:xx:xx:xx
  makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
  makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
  wm1 at pci2 dev 11 function 0: Intel i82545EM 1000BASE-T Ethernet, rev. 1
  wm1: interrupting at ioapic0 pin 23 (irq 9)
  wm1: 32-bit 33MHz PCI bus
  wm1: 256 word (8 address bits) MicroWire EEPROM
  wm1: Ethernet address 00:07:e9:yy:yy:yy
  makphy1 at wm1 phy 1: Marvell 88E1011 Gigabit PHY, rev. 3
  makphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto

Though the machines is still accessible from one side (for login e.
g.), it no longer routes network packets ...

A kernel compiled from Nov 13th -current sources does not show this
misbehavior.

Is this a known wm* issue? Did I miss some config changes?

Markus.