Date: Tue, 28 Jan 2014 20:28:47 -0200 From: Pedro Flynn <pedro.flynn@gmail.com> To: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: FreeBSD 10.0: hostapd crash with Ralink 3070 Message-ID: <CAN48zxkcJu-nYWrqJmrpC2VQ_LO2RwV6c9r3sUdKA6uXpfjcVQ@mail.gmail.com> In-Reply-To: <CAJ-VmokDb3mUj7Xw6hQKvX5beCv_hXLmMm-nAfz_ZZ-EYq1gyQ@mail.gmail.com> References: <CAN48zxmMZHsjr55AAbFaeB591Ahd9S1-AkGksRiRtgNOJv6DYQ@mail.gmail.com> <CALCpEUHRsquBrE4o6WxfcLgi-O2BN1FtPa%2BrS2Cdk==0dUdPaA@mail.gmail.com> <CAN48zxkXiUFyGuysTSkEPiwdS9VvEZgeyvo1eTr_seFQ2yM-6A@mail.gmail.com> <CAN48zxn%2BeKDFCbFDHwBJOUfyqvjH3whttTH0whtTfgBQxFRrGA@mail.gmail.com> <CAJ-VmonPDSHOzuD8bqpjLC1FjYQqHrwz2-w8u5wCqUw-hspVfQ@mail.gmail.com> <CAN48zx=zhBYSnkm4Kszs4oe1MdGPrP01B_0eysyso7T5a_WWMA@mail.gmail.com> <CAN48zxmxL_h=9B32C1dC5uGAbV_ExEXQoumPS1Zwvwt2RAbPUQ@mail.gmail.com> <CAN48zx=QgdLpTUm3OK2V-TVUxxBpiGF4A1WzZbSL6thqB_C%2B%2Bg@mail.gmail.com> <CAJ-VmokDb3mUj7Xw6hQKvX5beCv_hXLmMm-nAfz_ZZ-EYq1gyQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Adrian. Yes. There is a core.txt.0 file. I uploaded it to the folder. Thanks! pflynn On Tue, Jan 28, 2014 at 8:23 PM, Adrian Chadd <adrian@freebsd.org> wrote: > Hi, > > Did it create a crash .txt file? If so, that's mostly enough to go on. > Can you just attach that to a post to the mailing list? > > > -a > > > On 28 January 2014 13:26, Pedro Flynn <pedro.flynn@gmail.com> wrote: > > Hi! > > > > I generated the crash dump and uploaded the image to a public folder on > > Google Drive. This is the link to the folder: > > > > > https://drive.google.com/folderview?id=0B0sVwxI7RI7oc3R2bjVQR0pXWG8&usp=sharing > > > > the image is xz compressed and the uncompressed size is 161 MB. I also > put > > the uname -a output in the file uname-a.output. This is the uname -a: > > > > FreeBSD wormhole2 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan > > 16 22:34:59 UTC 2014 root@snap.freebsd.org: > /usr/obj/usr/src/sys/GENERIC > > amd64 > > > > Hope this dump will have some information. I can build a kernel with > debug > > symbols if one think more information is better. > > > > Thanks, > > > > pflynn > > > > > > On Tue, Jan 28, 2014 at 2:21 PM, Pedro Flynn <pedro.flynn@gmail.com> > wrote: > > > >> Hi Adrian, > >> > >> This morning I installed 10.0-RELEASE on a second machine (I had to > >> rollback my router to 9.2) with the same hardware with dumpdev set to > YES > >> in rc.conf. I will generate the crashdump as soon as I get home. > >> > >> Thanks, > >> > >> pflynn > >> > >> > >> On Tue, Jan 28, 2014 at 2:11 PM, Adrian Chadd <adrian@freebsd.org> > wrote: > >> > >>> Do you get a crashdump that you can feed into kgdb upon reboot? If > >>> not, would you mind enabling crashdumps? > >>> > >>> > >>> > >>> -a > >>> > >>> > >>> On 28 January 2014 02:57, Pedro Flynn <pedro.flynn@gmail.com> wrote: > >>> > (sorry - this reply was sent only to Hiren. Here is it for the list) > >>> > > >>> > > >>> > Hi Hiren, > >>> > > >>> > this is what I get immediately after starting hostapd - via "service > >>> > hostapd onestart", since I need to do it manually as the system will > >>> reboot > >>> > in loop if I enable > >>> > hostapd in rc.conf): > >>> > > >>> > KDB: stack backtrace > >>> > #0 0xffffffff808e7dd0 at kbd_backtrace+0x60 > >>> > #1 0xffffffff808af8b5 at panic+0x115 > >>> > #2 0xffffffff80c8e692 at trap_fatal+0x3a2 > >>> > #3 0xffffffff80c8e969 at trap_pfault+0x2c9 > >>> > #4 0xffffffff80c8e0f6 at trap+0x5e6 > >>> > #5 0xffffffff80c75392 at calltrap+0x8 > >>> > #6 0xffffffff81a158bc at run_update_beacon+0x16c > >>> > #7 0xffffffff809b42bd at ieee80211_wme_update_params_locked+0x32d > >>> > #8 0xffffffff809b437a at ieee80211_wme_update_params+0x5a > >>> > #9 0xffffffff809bb3f43 at ieee80211_wme_init_params+0x2a3 > >>> > #10 0xffffffff809a9aec at ieee80211_sta_join1+0xdc > >>> > #11 0xffffffff8099047b at hostap_newstate+0x2eb > >>> > #12 0xffffffff81a1636a at run_newstate+0x83a > >>> > #13 0xffffffff809b2edf at ieee80211_newstate_cb+0x14f > >>> > #14 0xffffffff808f5b66 at taskqueue_run_locked+0xe6 > >>> > #15 0xffffffff808f63e8 at taskqueue_thread_loop+0xa8 > >>> > #16 0xffffffff8088198a at fork_exit+0x9a > >>> > #17 0xffffffff80c758ce at fork_trampoline+0xe > >>> > Uptime: 45 s > >>> > Automatic reboot in 15 seconds - press a key on the console to abort > >>> > --> Press a key on the console to reboot, > >>> > --> or switch off the station now. > >>> > > >>> > Thanks for any help or suggestion. > >>> > > >>> > pflynn > >>> > > >>> > > >>> > On Mon, Jan 27, 2014 at 8:43 PM, hiren panchasara < > >>> > hiren.panchasara@gmail.com> wrote: > >>> > > >>> >> On Mon, Jan 27, 2014 at 2:16 PM, Pedro Flynn <pedro.flynn@gmail.com > > > >>> >> wrote: > >>> >> > >>> >> > I can provide information as needed. > >>> >> > >>> >> Sharing lots of kernel debug messages that you are seeing might be a > >>> >> good start :-) > >>> >> > >>> >> cheers, > >>> >> Hiren > >>> >> > >>> > _______________________________________________ > >>> > freebsd-wireless@freebsd.org mailing list > >>> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > >>> > To unsubscribe, send any mail to " > >>> freebsd-wireless-unsubscribe@freebsd.org" > >>> > >> > >> > >> > > _______________________________________________ > > freebsd-wireless@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > > To unsubscribe, send any mail to " > freebsd-wireless-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN48zxkcJu-nYWrqJmrpC2VQ_LO2RwV6c9r3sUdKA6uXpfjcVQ>