System      : OpenBSD 4.3
	Details     : OpenBSD 4.3-current (GENERIC) #832: Sun Apr 20 17:10:49 MDT 2008
			 deraadt@i386.openbsd.org:/usr/src/sys/arch/i386/compile/GENERIC

	Architecture: OpenBSD.i386
	iwi(4) stops functioning (loses network connection and stops passing
	trafic) if it is made part of a trunk(4) interface together with a
	bge(4) device (setup as the example in trunk(4) shows). The same
	behaviour also occurs when the iwi interface is *not* part of the
	trunk interface (which is somewhat surprising), consisting of only a
	bge(4) interface.

	rum(4) functions correctly under the same conditions with (more or
	less) the same configuration. Also, iwi works fine if setup without
	involving trunk.

	The archives contains evidence of others having the same problem:
	http://marc.info/?l=openbsd-misc&m=115777376323394&w=2
	(interestingly on a similar laptop: Dell Latitude D810 while mine is
	a Dell Latitude D800)

	Also see http://marc.info/?l=openbsd-misc&m=117158212922551&w=2
	which seems to be related.

	The following tests first shows that the environment and basic
	configuration works by using a rum device instead of iwi, then
	tries to setup a trunk interface with bge and iwi which fails.
	Then a similar test with an axe device instead of bge.

	The rest of the tests focus on provoking an error when iwi is
	not part of the trunk interface. A few different variants
	was made to show the behaviour with different conditions. While
	the behaviour of each test configuration is more or less
	consistent for each execution, the behaviour using different
	devices is not.
  
	Tests (performed against the same network):
	  1. bge0 and rum0 trunked - works fine (further testing not shown
	     here has been done as well)
	  2. bge0 and iwi0 trunked - iwi stops working with "fatal firmware
	     error". System freezes for ~15s while running ifconfig.
	  3. axe0 and iwi0 trunked - iwi is not 'active' in the trunk interface.

	Tests with only one interfa...
[ message continues ]