[Prism54-devel] [Bug 51] Erratic behaviour after working properly

[bugzilla-daemon@mcgrof.com]

http://prism54.org/cgi-bin/bugzilla/show_bug.cgi?id=51





------- Additional Comments From Jens.Maurer@gmx.net  2004-01-29 23:30 -------
This looks strange.  For example, the card reports
Jan 29 15:05:59 plankje kernel: eth1: Out of memory, cannot handle oid 0xe0070015 

This is not a known OID, but it fits this
   DOT11_OID_DOT1XENABLE           = 0x150007E0,
considering that the byte swapping might be wrong.
This OID is set during reset.  Now, the question is why the
byteswapping is suddenly wrong after a reset.  I did remove
the endianess check in the mgmt receive function, because my
card always sends big endian mgmt frame headers. Potentially,
that needs the full choice again, when the card starts acting
funny.  I've restored the "little endian mgmt frame header"
functionality in the CVS.

I'm not sure why it crashed after the error (more precisely, during "ifconfig
down"), it should just ignore the frame.  Hm... Probably we should really
implement the "disable DMA / frame receive before reset" precautions.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.