I generated the crash dump and uploaded the image to a public folder on
Google Drive. This is the link to the folder:
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 r...@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC
Hope this dump will have some information. I can build a kernel with debug
symbols if one think more information is better.
On Tue, Jan 28, 2014 at 2:21 PM, Pedro Flynn <pedro.fl...@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.
> On Tue, Jan 28, 2014 at 2:11 PM, Adrian Chadd <adr...@freebsd.org> wrote:
>> Do you get a crashdump that you can feed into kgdb upon reboot? If
>> not, would you mind enabling crashdumps?
>> On 28 January 2014 02:57, Pedro Flynn <pedro.fl...@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
>> > 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.panchas...@gmail.com> wrote:
>> >> On Mon, Jan 27, 2014 at 2:16 PM, Pedro Flynn <pedro.fl...@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
>> > _______________________________________________
>> > email@example.com mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
>> > To unsubscribe, send any mail to "
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"