Date: Sat, 28 Sep 2013 17:19:27 -0300 From: "Nenhum_de_Nos" <matheus@eternamente.info> Cc: freebsd-embedded@freebsd.org Subject: Re: Dlink DIR-825 B1 trial Message-ID: <bcdc063b28832171db0b3eeea1dd0316.squirrel@arroway.org> In-Reply-To: <d8fa1ea48c26685f5393b9adbc63ca8f.squirrel@arroway.org> References: <b9e5a389e69c587c54ac71e70ae47cfd.squirrel@arroway.org> <CALCpEUEWWY9ycCYE9%2BFv4EBaUTBf-0oLVnGfcPfCkH3JYKKiXw@mail.gmail.com> <CAJ-VmokphPLP44Kz-7FHaEKwhYuuf0SR=dizK404pvFutFk4Ew@mail.gmail.com> <CALCpEUHtuRPFwOVUX_BEVA=0u6UPx5rpZcM95qEsSVRDWmjffQ@mail.gmail.com> <CAJ-VmomfO01-cu1QMxnm_r=_ZBdoPBin%2BaASOw-WM5vbUTXiPQ@mail.gmail.com> <CALCpEUGdEXaDctUR2akSjpU%2B=JhYvHUqwoyYTj2FyrEVMZGAbg@mail.gmail.com> <B1EB18C5-7DFA-44D1-A764-15F96F1BADF5@bsdimp.com> <CAJ-Vmo=uLwn7468cKGN024%2BtJD-tdVAHFLbwTeRUfpbLTeJbdQ@mail.gmail.com> <1596945574.20130920003652@serebryakov.spb.ru> <CAJ-Vmokz22qRfgCKuhqTtxT=0f-_Zn87os73g5aX4NG_Rvfsvw@mail.gmail.com> <CAJ-VmokjeUeuEoqbcHWfoYwQm8BuNaU6A27g-9JTeaV7X8kxEg@mail.gmail.com> <d5efbc68aa46b5352e4e9fcd9197d0c4.squirrel@arroway.org> <CALCpEUFAVefJgyiwQhHOES9KRyncKrSLK-sKCqBQegjuH4xMtQ@mail.gmail.com> <36f9d8bdb9ff1d961ecab6c413862716.squirrel@arroway.org> <d8fa1ea48c26685f5393b9adbc63ca8f.squirrel@arroway.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, September 28, 2013 17:17, Nenhum_de_Nos wrote: > > On Sat, September 28, 2013 16:03, Nenhum_de_Nos wrote: >> >> On Wed, September 25, 2013 11:52, hiren panchasara wrote: >>> On Sep 25, 2013 4:25 AM, "Nenhum_de_Nos" <matheus@eternamente.info> wrote: >>>> >>>> >>>> On Fri, September 20, 2013 13:46, Adrian Chadd wrote: >>>> > .. can you repeat this with i386? The amd64 crowd may just assume >>> there's >>>> > much, much more minimum RAM available. >>>> > >>>> > I have the 10-ALPHA1 i386 ISO image waiting for a test install on >>>> > virtualbox; it'll happen over the weekend. >>>> > >>>> > >>>> > -adrian >>>> >>>> Hi guys, >>>> >>>> back to testing. >>>> >>>> I changed the line Hiren said, and now I am compiling it again. Using the >>> same code of that time. >>>> Better to update do today head ? >>> Better to test with the same code where you were seeing reproducible >>> problem. So that you can verify if the change I suggested is fixing it. >> >> hiren and all others, >> >> it is a complex task to make it have ssh/sshd/scp ? >> >> I have all time to make my modifications, and copy all stuff by hand :( >> >> # pwd >> /etc/cfg >> # ls >> hostapd.wlan0.conf manifest >> hostapd.wlan1.conf rc.conf >> >> this is all I need so far. I found that in build/files mfsroot gets files for it. But is there a >> way to make it look for in a place for each device ? I will test both 1043ND and 825, so if one >> messes the other, problem :) >> >> it is build already, just saving cfg to test it. >> >> thanks, >> >> matheus > > same outcome: > > th1: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > wlan0: Ethernet address: 20:11:91:53:59:44 > wlan1: Ethernet address: 59:44:91:53:20:11 > ar5416StopDmaReceive: dma failed to stop in 10ms > AR_CR=0x00000024 > AR_DIAG_SW=0x42000020 > ar5416StopDmaReceive: dma failed to stop in 10ms > AR_CR=0x00000024 > AR_DIAG_SW=0x42000020 > ar5416StopDmaReceive: dma failed to stop in 10ms > AR_CR=0x00000024 > AR_DIAG_SW=0x42000020 > ar5416StopDmaReceive: dma failed to stop in 10ms > AR_CR=0x00000024 > AR_DIAG_SW=0x42000020 > ar5416StopDmaReceive: dma failed to stop in 10ms > AR_CR=0x00000024 > AR_DIAG_SW=0x42000020 > ar5416StopDmaReceive: dma failed to stop in 10ms > AR_CR=0x00000024 > AR_DIAG_SW=0x42000020 > ar5416StopDmaReceive: dma failed to stop in 10ms > AR_CR=0x00000024 > AR_DIAG_SW=0x42000020 > bridge0: Ethernet address: 5e:35:c9:37:f6:d1 > ar5416StopDmaReceive: dma failed to stop in 10ms > AR_CR=0x00000024 > AR_DIAG_SW=0x42000020 > wlan1: start 60 second CAC timer on channel 52 (5260 MHz) > # wlan1: CAC timer on channel 52 (5260 MHz) expired; no radar detected > wlan1: ieee80211_new_state_locked: pending CAC -> RUN transition lost > lock order reversal: (sleepable after non-sleepable) > 1st 0xc70a3014 ath1_com_lock (ath1_com_lock) @ > /root/work/freebsd/head/src/sys/modules/wlan/../../net80211/ieee80211_scan.c:686 > 2nd 0x8036dff8 user map (user map) @ /root/work/freebsd/head/src/sys/vm/vm_glue.c:168 > KDB: stack backtrace: > db_trace_thread+30 (?,?,?,?) ra c059989000000018 sp 0 sz 0 > db_trace_self+1c (?,?,?,?) ra c05998a800000018 sp 0 sz 0 > 8007ad18+34 (?,?,?,?) ra c05998c0000001a0 sp 0 sz 0 > kdb_backtrace+44 (?,?,?,?) ra c0599a6000000018 sp 0 sz 0 > 801704b8+34 (?,?,?,?) ra c0599a7800000020 sp 0 sz 0 > witness_checkorder+b0c (?,?,802f97d4,a8) ra c0599a9800000050 sp 0 sz 1 > _sx_slock+c0 (?,?,?,?) ra c0599ae800000030 sp 0 sz 0 > _vm_map_lock_read+40 (?,?,?,?) ra c0599b1800000018 sp 0 sz 0 > useracc+80 (?,?,?,?) ra c0599b3000000028 sp 0 sz 0 > 802a7dc4+dc (?,?,?,?) ra c0599b5800000040 sp 0 sz 0 > trap+e6c (?,?,?,?) ra c0599b98000000b8 sp 0 sz 0 > MipsKernGenException+134 (ffff,4,806089b0,0) ra c0599c50000000c8 sp 100000001 sz 1 > hostap_newstate+358 (?,?,?,?) ra c0599d1800000038 sp 0 sz 0 > ath_newstate+2c0 (?,?,?,?) ra c0599d5000000058 sp 0 sz 0 > ieee80211_newstate_cb+20c (?,?,?,?) ra c0599da800000040 sp 0 sz 0 > 801630c8+e8 (?,?,?,?) ra c0599de800000038 sp 0 sz 0 > taskqueue_thread_loop+8c (?,?,?,?) ra c0599e2000000038 sp 0 sz 0 > fork_exit+b0 (?,?,?,?) ra c0599e5800000028 sp 0 sz 0 > fork_trampoline+10 (?,?,?,?) ra c0599e8000000000 sp 0 sz 0 > pid 0 > Trap cause = 4 (address error (load or I-fetch) - kernel mode) > [ thread pid 0 tid 100043 ] > Stopped at hostap_newstate+0x358: lw v0,0(a0) > db> > > att, I get a lot of this: wlan1: stop CAC timer on channel 52 (5260 MHz) wlan1: start 60 second CAC timer on channel 52 (5260 MHz) wlan1: stop CAC timer on channel 52 (5260 MHz) wlan1: start 60 second CAC timer on channel 52 (5260 MHz) wlan1: stop CAC timer on channel 52 (5260 MHz) matheus > matheus > >>> Thanks for testing, >>> Hiren >>>> >>>> thanks, >>>> >>>> matheus >>>> >>>> -- >>>> We will call you Cygnus, >>>> The God of balance you shall be >>>> >>>> A: Because it messes up the order in which people normally read text. >>>> Q: Why is top-posting such a bad thing? >>>> >>>> http://en.wikipedia.org/wiki/Posting_style >>>> _______________________________________________ >>>> freebsd-embedded@freebsd.org mailing list >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-embedded >>>> To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org >>> " >>> >> >> >> -- >> We will call you Cygnus, >> The God of balance you shall be >> >> A: Because it messes up the order in which people normally read text. >> Q: Why is top-posting such a bad thing? >> >> http://en.wikipedia.org/wiki/Posting_style >> _______________________________________________ >> freebsd-embedded@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-embedded >> To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" >> > > > -- > We will call you Cygnus, > The God of balance you shall be > > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > > http://en.wikipedia.org/wiki/Posting_style > _______________________________________________ > freebsd-embedded@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-embedded > To unsubscribe, send any mail to "freebsd-embedded-unsubscribe@freebsd.org" > -- We will call you Cygnus, The God of balance you shall be A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? http://en.wikipedia.org/wiki/Posting_style
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bcdc063b28832171db0b3eeea1dd0316.squirrel>