Ignacio Marambio Cat?n wrote: > looks a lot like > http://defect.opensolaris.org/bz/show_bug.cgi?id=3786 > but my dmesg is different > I think it's same, and you can add your comments on it.
-- Quaker > On Mon, Dec 22, 2008 at 1:10 AM, Quaker Fang <Quaker.Fang at sun.com> wrote: > >> Hi Ignacio, >> >> Ignacio Marambio Cat?n wrote: >> >>> sort of, yes, this problem happens usually when transfering data >>> (300mb files) from a cifs share either by using the native cifs >>> solaris client or whatever gnome uses. >>> Big http transfers like downloading a cd image from a web page also >>> trigger the problem >>> >>> >> Hmm, this should be a known issue of wpi driver. >> >> -- >> Quaker >> >>> On Mon, Dec 22, 2008 at 12:49 AM, Quaker Fang <Quaker.Fang at sun.com> >>> wrote: >>> >>> >>>> Hi Ignacio, >>>> >>>> Felix wrote: >>>> >>>> >>>>> Ignacio Marambio Cat?n wrote: >>>>> >>>>> >>>>> >>>>>> I'm using wpi to connect to a an AP using wpa and the connection to >>>>>> the AP resets often. Some of those times the connection does not get >>>>>> back at all. >>>>>> each of those times I get something like this in dmesg >>>>>> >>>>>> Dec 21 23:16:28 saturn genunix: [ID 358043 kern.warning] WARNING: >>>>>> ieee80211_crypto_enmic failed. >>>>>> >>>>>> >>>>>> >>>>> Hi, >>>>> >>>>> From your dmesg, we can see that your problem is caused by >>>>> 'ieee80211_crypto_enmic failed'. That happened during encapsulating an >>>>> outbound data frame. The script you used is the normal process when >>>>> >>>>> >>>> ieee80211_crypto_enmic() failure was caused by fatal error in wpi driver >>>> (dead packets). >>>> I am wondering do you use wifi on a heavy data transfer? >>>> >>>> -- >>>> Quaker >>>> >>>> >>>>> re-connecting to an AP. I doubt that your wpi interface does not really >>>>> connect to the AP in wpa mode. So, can your wpi interface get IP after >>>>> connecting to an AP? And could you have a try in none encryption mode? >>>>> Thanks. >>>>> >>>>> ------ >>>>> Thanks, >>>>> Felix >>>>> >>>>> >>>>>> Dec 21 23:16:28 saturn mac: [ID 486395 kern.info] NOTICE: wpi0 link >>>>>> down >>>>>> Dec 21 23:16:28 saturn in.routed[381]: [ID 238047 daemon.warning] >>>>>> interface wpi0 to 192.168.1.134 turned off >>>>>> Dec 21 23:16:31 saturn mac: [ID 744254 kern.info] NOTICE: wpi0 link up >>>>>> >>>>>> this is the result of uname -a >>>>>> nacho at saturn:~$ uname -a >>>>>> SunOS saturn 5.11 snv_101b i86pc i386 i86pc >>>>>> >>>>>> and finally, i found a d script used to diagnose these errors called >>>>>> ieee80211_newstate.d >>>>>> i renamed it to wifi,d and ran it, this is what it returned: >>>>>> nacho at saturn:~$ pfexec ./wifi.d >>>>>> ieee80211_newstate(0 <- 4) >>>>>> >>>>>> wpi`wpi_newstate+0x297 >>>>>> wpi`wpi_intr+0x17d >>>>>> unix`av_dispatch_autovect+0x7c >>>>>> unix`dispatch_hardint+0x33 >>>>>> unix`switch_sp_and_call+0x13 >>>>>> ieee80211_newstate(0 <- 0) >>>>>> >>>>>> wpi`wpi_newstate+0x297 >>>>>> wpi`wpi_thread+0xbc >>>>>> unix`thread_start+0x8 >>>>>> ieee80211_newstate(0 <- 0) >>>>>> >>>>>> wpi`wpi_newstate+0x297 >>>>>> net80211`wl_set_mlme+0x12b >>>>>> net80211`ieee80211_setprop+0x8c >>>>>> wpi`wpi_m_setprop+0x26 >>>>>> mac`mac_set_prop+0x42 >>>>>> dld`drv_ioc_prop_common+0x1f0 >>>>>> dld`drv_ioc_setprop+0x24 >>>>>> dld`drv_ioctl+0x128 >>>>>> genunix`cdev_ioctl+0x45 >>>>>> specfs`spec_ioctl+0x83 >>>>>> genunix`fop_ioctl+0x7b >>>>>> genunix`ioctl+0x18e >>>>>> unix`_sys_sysenter_post_swapgs+0x14b >>>>>> ieee80211_newstate(0 <- 1) >>>>>> >>>>>> wpi`wpi_newstate+0x297 >>>>>> net80211`ieee80211_end_scan+0x1fe >>>>>> wpi`wpi_notif_softintr+0xe7 >>>>>> unix`av_dispatch_softvect+0x5f >>>>>> unix`dispatch_softint+0x34 >>>>>> unix`switch_sp_and_call+0x13 >>>>>> ieee80211_newstate(2 <- 0) >>>>>> >>>>>> wpi`wpi_newstate+0x297 >>>>>> net80211`ieee80211_sta_join+0x116 >>>>>> net80211`wl_set_mlme+0xaa >>>>>> net80211`ieee80211_setprop+0x8c >>>>>> wpi`wpi_m_setprop+0x26 >>>>>> mac`mac_set_prop+0x42 >>>>>> dld`drv_ioc_prop_common+0x1f0 >>>>>> dld`drv_ioc_setprop+0x24 >>>>>> dld`drv_ioctl+0x128 >>>>>> genunix`cdev_ioctl+0x45 >>>>>> specfs`spec_ioctl+0x83 >>>>>> genunix`fop_ioctl+0x7b >>>>>> genunix`ioctl+0x18e >>>>>> unix`_sys_sysenter_post_swapgs+0x14b >>>>>> ieee80211_newstate(3 <- 2) >>>>>> >>>>>> wpi`wpi_newstate+0x297 >>>>>> net80211`ieee80211_auth_open+0xd0 >>>>>> net80211`ieee80211_recv_mgmt+0x7af >>>>>> net80211`ieee80211_input+0x37c >>>>>> wpi`wpi_rx_intr+0xc7 >>>>>> wpi`wpi_notif_softintr+0xa6 >>>>>> unix`av_dispatch_softvect+0x5f >>>>>> unix`dispatch_softint+0x34 >>>>>> unix`switch_sp_and_call+0x13 >>>>>> ieee80211_newstate(4 <- 3) >>>>>> >>>>>> wpi`wpi_newstate+0x297 >>>>>> net80211`ieee80211_recv_mgmt+0x2fe >>>>>> net80211`ieee80211_input+0x37c >>>>>> wpi`wpi_rx_intr+0xc7 >>>>>> wpi`wpi_notif_softintr+0xa6 >>>>>> unix`av_dispatch_softvect+0x5f >>>>>> unix`dispatch_softint+0x34 >>>>>> unix`switch_sp_and_call+0x13 >>>>>> >>>>>> The connection is a lot more stable in windows XP, what might the >>>>>> problem >>>>>> be? >>>>>> _______________________________________________ >>>>>> laptop-discuss mailing list >>>>>> laptop-discuss at opensolaris.org >>>>>> >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> laptop-discuss mailing list >>>>> laptop-discuss at opensolaris.org >>>>> >>>>> >>>>> >>>> >>
