Renee Danson wrote:
> ...
> Regarding the problem Matthew reported (link down following the error
> report from ieee80211_crypto_enmic), it sounds like Quaker had some
> possibilities to investigate.  In particular, there's the CR that he
> mentioned, 6698754, which is still open.
>   
Yes, I think it's a similar problem of CR6698754, and actually, the 
failure of ieee80211_crypto_enmic() is
caused by the packet error of iwk driver.

Matthew, could you please use attached dtrace script to get more 
information for me, then I can help
to dig into it.

Thanks,

--
Quaker

> There were also several bugs fixed in the iwk driver in nevada build
> 87; Matthew was running build 90, but your tests were against builds
> 81 and 86, and would not have included those fixes.  
>
> I also have a question for Matthew:
>
>   
>>> Kaiwai Gardiner wrote:
>>>       
>>>> On Tue, 2008-05-27 at 10:07 +0800, Fu, Zhonghui wrote:
>>>>         
>>>>> Kaiwai Gardiner,
>>>>>
>>>>> Have you used other wireless cards in addition to 4965? Is there the
>>>>> same phenomena as 4965 on them?
>>>>> Could you please give out your operation steps in detail?
>>>>>           
>>>> No, unfortunately not. I only have this one laptop. I do have a
>>>> athereos one in my bedroom in a desktop and it doesn't display the
>>>> same rate of dropping out - and dladm states that the reception is
>>>> poor. Soomething is going wrong when a poor signal is maintaining a
>>>> conneciton whilst this laptop classes the signal as excellent - the
>>>> reception keeps falling out of the sky.
>>>>         
>
> I'm a little confused about the signal levels.  Which device reports the
> poor signal strength: the atheros or the iwk?
>
> Thanks,
> renee
> _______________________________________________
> laptop-discuss mailing list
> laptop-discuss at opensolaris.org
>   

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ieee80211_newstate.d
URL: 
<http://mail.opensolaris.org/pipermail/laptop-discuss/attachments/20080529/3bb946c8/attachment.ksh>

Reply via email to