On 6/29/05, Mike Silbersack <silby_at_silby.com> wrote: > > I'm still seeing these printfs. Much like Pascal, my "value" is fairly > > consistent. It does seem to change based on access point... I've tested > > this on three different access points-- 2 open, and 1 with WPA-PSK. When I > > connect to the open access points, I get "val=102c0de". When connecting to > > the WPA-PSK access point, I get "val=2cc0de". This value is consistent > > across kernel rebuilds and connect sessions. > > > > My hardware is a Thinkpad 380XD w/ Belkin F5D7010 (ral) pc card nic. > > > > Let me know if I can provide more information. > > Actually, that is a real bug. :) > > Damien just committed a fix in revision 1.4 of if_ral.c. Please cvsup and > see if that stops the warnings. Just thought i would give a heads up .. with the latest mbuf and if_ral patches i no longer see the mbuf-related-printfs. It was nice to see though how the messages were traced to the wireless code as i am indeed using an if_ral network interface using WPA_PSK (Linksys WMP54G). -- Pascal HofsteeReceived on Thu Jun 30 2005 - 21:00:12 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:37 UTC