Re: My WLI-UC-GNM up crash
Before using the computer USB power supply, the implementation of usbdump, the kernel Panic Some log: http://pastebin.com/wPURnAg5 http://img.vim-cn.com/5f/576bc22abaadb1014dae4c4e73b07f48579e8e.bmp addr2line information: http://pastebin.com/sE5C7bqi 1A is used after the power supply Enter no response, TTL did not show additional information -- Regards. By: XiaoQI Ge; PGP:8B09D5F7 WWW: https://www.7axu.com/ 2013/8/1 Rui Paulo : > On 31 Jul 2013, at 01:28, XiaoQI Ge wrote: > >> Last night, I use the latest FreeBSD source (r253827) and >> crochet-freebsd compile img >> My WLI-UC-GNM will be disconnected after a period of operation >> >> run0: device timeout >> run0: at uhub0, port 1, addr 2 (disconnected) > > If you are using the USB cable to power the BBB, then that's your problem. > You need a 5V 1A+ power adapter to be able to use USB WiFi cards with the > BeagleBone. > > -- > Rui Paulo > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
On 31 Jul 2013, at 01:28, XiaoQI Ge wrote: > Last night, I use the latest FreeBSD source (r253827) and > crochet-freebsd compile img > My WLI-UC-GNM will be disconnected after a period of operation > > run0: device timeout > run0: at uhub0, port 1, addr 2 (disconnected) If you are using the USB cable to power the BBB, then that's your problem. You need a 5V 1A+ power adapter to be able to use USB WiFi cards with the BeagleBone. -- Rui Paulo ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
RE: My WLI-UC-GNM up crash
Hi, Typically this means the USB firmware died, or some command needs to be re-transmitted. See: usbdump -i usbusX -s 65536 What is really going on. --HPS -Original message- > From:Adrian Chadd mailto:adr...@freebsd.org> > > Sent: Wednesday 31st July 2013 20:03 > To: Ian Lepore mailto:i...@freebsd.org> > > Cc: freebsd-arm mailto:freebsd-...@freebsd.org> >; > freebsd-wireless@freebsd.org <mailto:freebsd-wireless@freebsd.org> ; Hans > Petter Selasky <mailto:hans.petter.sela...@bitfrost.no> > > Subject: Re: My WLI-UC-GNM up crash > > No idea about the device disconnect, sorry. is it a power draw problem? > > > -adrian > > On 31 July 2013 06:41, Ian Lepore mailto:i...@freebsd.org> > > wrote: > > On Wed, 2013-07-31 at 16:28 +0800, XiaoQI Ge wrote: > >> Last night, I use the latest FreeBSD source (r253827) and > >> crochet-freebsd compile img > >> My WLI-UC-GNM will be disconnected after a period of operation > >> > >> run0: device timeout > >> run0: at uhub0, port 1, addr 2 (disconnected) > >> > >> Another log prompted > >> ti_mmchs0: Error: current cmd NULL, already done? > >> > >> My BB-Black broken? > > > > The ti_mmchs0 error is not new. My old BBW has done that for months. > > I'm not sure it's totally harmless, but it's not related to the run0 > > timeouts. > > > > -- Ian > > > > ___ > > freebsd-...@freebsd.org <mailto:freebsd-...@freebsd.org> mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > <http://lists.freebsd.org/mailman/listinfo/freebsd-arm> > > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org > > <mailto:freebsd-arm-unsubscr...@freebsd.org> " > ___ > freebsd-...@freebsd.org <mailto:freebsd-...@freebsd.org> mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > <http://lists.freebsd.org/mailman/listinfo/freebsd-arm> > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org > <mailto:freebsd-arm-unsubscr...@freebsd.org> " > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
No idea about the device disconnect, sorry. is it a power draw problem? -adrian On 31 July 2013 06:41, Ian Lepore wrote: > On Wed, 2013-07-31 at 16:28 +0800, XiaoQI Ge wrote: >> Last night, I use the latest FreeBSD source (r253827) and >> crochet-freebsd compile img >> My WLI-UC-GNM will be disconnected after a period of operation >> >> run0: device timeout >> run0: at uhub0, port 1, addr 2 (disconnected) >> >> Another log prompted >> ti_mmchs0: Error: current cmd NULL, already done? >> >> My BB-Black broken? > > The ti_mmchs0 error is not new. My old BBW has done that for months. > I'm not sure it's totally harmless, but it's not related to the run0 > timeouts. > > -- Ian > > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
On Wed, 2013-07-31 at 16:28 +0800, XiaoQI Ge wrote: > Last night, I use the latest FreeBSD source (r253827) and > crochet-freebsd compile img > My WLI-UC-GNM will be disconnected after a period of operation > > run0: device timeout > run0: at uhub0, port 1, addr 2 (disconnected) > > Another log prompted > ti_mmchs0: Error: current cmd NULL, already done? > > My BB-Black broken? The ti_mmchs0 error is not new. My old BBW has done that for months. I'm not sure it's totally harmless, but it's not related to the run0 timeouts. -- Ian ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
Last night, I use the latest FreeBSD source (r253827) and
crochet-freebsd compile img
My WLI-UC-GNM will be disconnected after a period of operation
run0: device timeout
run0: at uhub0, port 1, addr 2 (disconnected)
Another log prompted
ti_mmchs0: Error: current cmd NULL, already done?
My BB-Black broken?
--
Regards.
By: XiaoQI Ge; PGP:8B09D5F7
WWW: https://www.7axu.com/
2013/7/30 Ian Lepore :
> On Mon, 2013-07-29 at 14:15 -0700, John-Mark Gurney wrote:
>> Hans Petter Selasky wrote this message on Mon, Jul 29, 2013 at 19:58 +0200:
>> > The aligned will make sure that the structure gets padded properly to the
>> > size specified. Only on ARM/MIPS etc, structures get automatically aligned
>> > according to the element in the structure requiring the greatest
>> > alignment. I've test-compiled the USB WLAN drivers, and the aligned makes
>> > a difference. The problem is that the radiotap header skews some following
>> > elements, so that they are no longer aligned. The radiotap header itself
>> > is packed, and this is not a problem.
>>
>> Ouch, has anyone looked at the code that caused this?
>>
>> in ieee80211_radiotap.c, it looks like the original fault was in either
>> set_channel, or set_xchannel, and both do (the equivalent of):
>> struct {
>> uint16_tfreq;
>> uint16_tflags;
>> } *rc = p;
>>
>> rc->freq = htole16(c->ic_freq);
>> rc->flags = htole16(c->ic_flags);
>>
>
> If there's any chance the pointer isn't aligned in code like this, then
> htole16() is the wrong function, it should be using le16enc() such as
>
> le16enc(&rc->freq, c->ic_freq);
> le16enc(&rc->flags, c->ic_flags);
>
> With any luck, an x86 compiler can optimize the inline code for the
> endian enc/dec functions to take advantage of the platform's ability to
> do unaligned accesses. But that's a side issue to code correctness --
> portable code has to get these things right even when it's inefficient.
>
> -- Ian
>
>> And then there is complicated code that calculates offsets, etc, in
>> radiotap_offset.. What we probably really need is to mark the above
>> as __packed or equiv so that we don't assume that the passed in pointer
>> is aligned...
>>
>> The whole management of this radiochan and radiotap_offset is pretty
>> nasty... If marking the structures __packed works, it's probably
>> because two bugs are offsetting, and magicly making things align
>> again...
>>
>> > -Original message-
>> > > From:Warner Losh mailto:i...@bsdimp.com> >
>> > > Sent: Monday 29th July 2013 17:04
>> > > To: Adrian Chadd mailto:adr...@freebsd.org> >
>> > > Cc: Hans Petter Selasky > > > <mailto:hans.petter.sela...@bitfrost.no> >; freebsd-arm
>> > > mailto:freebsd-...@freebsd.org> >;
>> > > freebsd-wireless@freebsd.org <mailto:freebsd-wireless@freebsd.org>
>> > > Subject: Re: My WLI-UC-GNM up crash
>> > >
>> > > Aren't structures already aligned to 4 bytes when placed inside other
>> > > structures (unless marked __packed)?
>> > >
>> > > Warner
>> > >
>> > > On Jul 28, 2013, at 11:50 AM, Adrian Chadd wrote:
>> > >
>> > > > As long as that results in the radiotap structures being 4 or 8 byte
>> > > > padded when it's embedded in the softc - then yes, indeed.
>> > > >
>> > > > Xiao, can you try?
>> > > >
>> > > >
>> > > > -adrian
>> > > >
>> > > > On 28 July 2013 03:35, Hans Petter Selasky > > > > <mailto:h...@bitfrost.no> > wrote:
>> > > >> Hi,
>> > > >>
>> > > >> Can you try the attached patch?
>> > > >>
>> > > >> --HPS
>> > > > ___
>> > > > freebsd-...@freebsd.org <mailto:freebsd-...@freebsd.org> mailing list
>> > > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> > > > <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>
>> > > > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org
>> > > > <mailto:freebsd-arm-unsubscr...@freebsd.org> "
>> > >
>> > >
>> >
>> > ___
>> > freebsd-...@freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"
>>
>
>
> ___
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
On Mon, 2013-07-29 at 14:15 -0700, John-Mark Gurney wrote:
> Hans Petter Selasky wrote this message on Mon, Jul 29, 2013 at 19:58 +0200:
> > The aligned will make sure that the structure gets padded properly to the
> > size specified. Only on ARM/MIPS etc, structures get automatically aligned
> > according to the element in the structure requiring the greatest alignment.
> > I've test-compiled the USB WLAN drivers, and the aligned makes a
> > difference. The problem is that the radiotap header skews some following
> > elements, so that they are no longer aligned. The radiotap header itself is
> > packed, and this is not a problem.
>
> Ouch, has anyone looked at the code that caused this?
>
> in ieee80211_radiotap.c, it looks like the original fault was in either
> set_channel, or set_xchannel, and both do (the equivalent of):
> struct {
> uint16_tfreq;
> uint16_tflags;
> } *rc = p;
>
> rc->freq = htole16(c->ic_freq);
> rc->flags = htole16(c->ic_flags);
>
If there's any chance the pointer isn't aligned in code like this, then
htole16() is the wrong function, it should be using le16enc() such as
le16enc(&rc->freq, c->ic_freq);
le16enc(&rc->flags, c->ic_flags);
With any luck, an x86 compiler can optimize the inline code for the
endian enc/dec functions to take advantage of the platform's ability to
do unaligned accesses. But that's a side issue to code correctness --
portable code has to get these things right even when it's inefficient.
-- Ian
> And then there is complicated code that calculates offsets, etc, in
> radiotap_offset.. What we probably really need is to mark the above
> as __packed or equiv so that we don't assume that the passed in pointer
> is aligned...
>
> The whole management of this radiochan and radiotap_offset is pretty
> nasty... If marking the structures __packed works, it's probably
> because two bugs are offsetting, and magicly making things align
> again...
>
> > -Original message-
> > > From:Warner Losh mailto:i...@bsdimp.com> >
> > > Sent: Monday 29th July 2013 17:04
> > > To: Adrian Chadd mailto:adr...@freebsd.org> >
> > > Cc: Hans Petter Selasky > > <mailto:hans.petter.sela...@bitfrost.no> >; freebsd-arm
> > > mailto:freebsd-...@freebsd.org> >;
> > > freebsd-wireless@freebsd.org <mailto:freebsd-wireless@freebsd.org>
> > > Subject: Re: My WLI-UC-GNM up crash
> > >
> > > Aren't structures already aligned to 4 bytes when placed inside other
> > > structures (unless marked __packed)?
> > >
> > > Warner
> > >
> > > On Jul 28, 2013, at 11:50 AM, Adrian Chadd wrote:
> > >
> > > > As long as that results in the radiotap structures being 4 or 8 byte
> > > > padded when it's embedded in the softc - then yes, indeed.
> > > >
> > > > Xiao, can you try?
> > > >
> > > >
> > > > -adrian
> > > >
> > > > On 28 July 2013 03:35, Hans Petter Selasky > > > <mailto:h...@bitfrost.no> > wrote:
> > > >> Hi,
> > > >>
> > > >> Can you try the attached patch?
> > > >>
> > > >> --HPS
> > > > ___
> > > > freebsd-...@freebsd.org <mailto:freebsd-...@freebsd.org> mailing list
> > > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > > > <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>
> > > > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org
> > > > <mailto:freebsd-arm-unsubscr...@freebsd.org> "
> > >
> > >
> >
> > ___
> > freebsd-...@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"
>
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
Hans Petter Selasky wrote this message on Mon, Jul 29, 2013 at 19:58 +0200:
> The aligned will make sure that the structure gets padded properly to the
> size specified. Only on ARM/MIPS etc, structures get automatically aligned
> according to the element in the structure requiring the greatest alignment.
> I've test-compiled the USB WLAN drivers, and the aligned makes a difference.
> The problem is that the radiotap header skews some following elements, so
> that they are no longer aligned. The radiotap header itself is packed, and
> this is not a problem.
Ouch, has anyone looked at the code that caused this?
in ieee80211_radiotap.c, it looks like the original fault was in either
set_channel, or set_xchannel, and both do (the equivalent of):
struct {
uint16_tfreq;
uint16_tflags;
} *rc = p;
rc->freq = htole16(c->ic_freq);
rc->flags = htole16(c->ic_flags);
And then there is complicated code that calculates offsets, etc, in
radiotap_offset.. What we probably really need is to mark the above
as __packed or equiv so that we don't assume that the passed in pointer
is aligned...
The whole management of this radiochan and radiotap_offset is pretty
nasty... If marking the structures __packed works, it's probably
because two bugs are offsetting, and magicly making things align
again...
> -Original message-
> > From:Warner Losh mailto:i...@bsdimp.com> >
> > Sent: Monday 29th July 2013 17:04
> > To: Adrian Chadd mailto:adr...@freebsd.org> >
> > Cc: Hans Petter Selasky > <mailto:hans.petter.sela...@bitfrost.no> >; freebsd-arm
> > mailto:freebsd-...@freebsd.org> >;
> > freebsd-wireless@freebsd.org <mailto:freebsd-wireless@freebsd.org>
> > Subject: Re: My WLI-UC-GNM up crash
> >
> > Aren't structures already aligned to 4 bytes when placed inside other
> > structures (unless marked __packed)?
> >
> > Warner
> >
> > On Jul 28, 2013, at 11:50 AM, Adrian Chadd wrote:
> >
> > > As long as that results in the radiotap structures being 4 or 8 byte
> > > padded when it's embedded in the softc - then yes, indeed.
> > >
> > > Xiao, can you try?
> > >
> > >
> > > -adrian
> > >
> > > On 28 July 2013 03:35, Hans Petter Selasky > > <mailto:h...@bitfrost.no> > wrote:
> > >> Hi,
> > >>
> > >> Can you try the attached patch?
> > >>
> > >> --HPS
> > > ___
> > > freebsd-...@freebsd.org <mailto:freebsd-...@freebsd.org> mailing list
> > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> > > <http://lists.freebsd.org/mailman/listinfo/freebsd-arm>
> > > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org
> > > <mailto:freebsd-arm-unsubscr...@freebsd.org> "
> >
> >
>
> ___
> freebsd-...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
> To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
On Mon, Jul 29, 2013 at 12:34:00PM -0600, Warner Losh wrote: > > On Jul 29, 2013, at 11:58 AM, Hans Petter Selasky wrote: > > > The aligned will make sure that the structure gets padded properly to the > > size specified. Only on ARM/MIPS etc, structures get automatically aligned > > according to the element in the structure requiring the greatest alignment. > > I'd turn this around and say only on x86 do structures not get aligned this > way. On any riscy architecture, unaligned accesses are expensive, which is > why the ABI there mandates this. > The alignment of the structure to the largest alignment of the member is required by the ABIs on i386 and amd64 as well. pgp8C63eUZqgf.pgp Description: PGP signature
Re: My WLI-UC-GNM up crash
On Jul 29, 2013, at 11:58 AM, Hans Petter Selasky wrote: > The aligned will make sure that the structure gets padded properly to the > size specified. Only on ARM/MIPS etc, structures get automatically aligned > according to the element in the structure requiring the greatest alignment. I'd turn this around and say only on x86 do structures not get aligned this way. On any riscy architecture, unaligned accesses are expensive, which is why the ABI there mandates this. > I've test-compiled the USB WLAN drivers, and the aligned makes a difference. > The problem is that the radiotap header skews some following elements, so > that they are no longer aligned. The radiotap header itself is packed, and > this is not a problem. This suggests a bigger problem. How is the radiotap header being popualted? Is it by DMA or programmatically? If by DMA then we have cache line sharing, which is bad. If by program, why is it packed to start with? Warner > --HPS > > > -Original message- > > From:Warner Losh > > Sent: Monday 29th July 2013 17:04 > > To: Adrian Chadd > > Cc: Hans Petter Selasky ; freebsd-arm > > ; freebsd-wireless@freebsd.org > > Subject: Re: My WLI-UC-GNM up crash > > > > Aren't structures already aligned to 4 bytes when placed inside other > > structures (unless marked __packed)? > > > > Warner > > > > On Jul 28, 2013, at 11:50 AM, Adrian Chadd wrote: > > > > > As long as that results in the radiotap structures being 4 or 8 byte > > > padded when it's embedded in the softc - then yes, indeed. > > > > > > Xiao, can you try? > > > > > > > > > -adrian > > > > > > On 28 July 2013 03:35, Hans Petter Selasky wrote: > > >> Hi, > > >> > > >> Can you try the attached patch? > > >> > > >> --HPS > > > ___ > > > freebsd-...@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org" > > > > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
RE: My WLI-UC-GNM up crash
Hi, The aligned will make sure that the structure gets padded properly to the size specified. Only on ARM/MIPS etc, structures get automatically aligned according to the element in the structure requiring the greatest alignment. I've test-compiled the USB WLAN drivers, and the aligned makes a difference. The problem is that the radiotap header skews some following elements, so that they are no longer aligned. The radiotap header itself is packed, and this is not a problem. --HPS -Original message- > From:Warner Losh mailto:i...@bsdimp.com> > > Sent: Monday 29th July 2013 17:04 > To: Adrian Chadd mailto:adr...@freebsd.org> > > Cc: Hans Petter Selasky <mailto:hans.petter.sela...@bitfrost.no> >; freebsd-arm > mailto:freebsd-...@freebsd.org> >; > freebsd-wireless@freebsd.org <mailto:freebsd-wireless@freebsd.org> > Subject: Re: My WLI-UC-GNM up crash > > Aren't structures already aligned to 4 bytes when placed inside other > structures (unless marked __packed)? > > Warner > > On Jul 28, 2013, at 11:50 AM, Adrian Chadd wrote: > > > As long as that results in the radiotap structures being 4 or 8 byte > > padded when it's embedded in the softc - then yes, indeed. > > > > Xiao, can you try? > > > > > > -adrian > > > > On 28 July 2013 03:35, Hans Petter Selasky > <mailto:h...@bitfrost.no> > wrote: > >> Hi, > >> > >> Can you try the attached patch? > >> > >> --HPS > > ___ > > freebsd-...@freebsd.org <mailto:freebsd-...@freebsd.org> mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > <http://lists.freebsd.org/mailman/listinfo/freebsd-arm> > > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org > > <mailto:freebsd-arm-unsubscr...@freebsd.org> " > > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
Aren't structures already aligned to 4 bytes when placed inside other structures (unless marked __packed)? Warner On Jul 28, 2013, at 11:50 AM, Adrian Chadd wrote: > As long as that results in the radiotap structures being 4 or 8 byte > padded when it's embedded in the softc - then yes, indeed. > > Xiao, can you try? > > > -adrian > > On 28 July 2013 03:35, Hans Petter Selasky wrote: >> Hi, >> >> Can you try the attached patch? >> >> --HPS > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
The __aligned(8) likely isn't going to do anything. It says that you are guaranteeing to the compiler that you'll only ever allocate / cast pointers to this data type on a 8-byte boundary. __packed might help, but likely won't because that's for on-wire things and anything thing that wasn't already not marked packed that should be would already be broken, but broken giving bad data, not broken segfaulting. __aligned(1) is what you want. But that has other performance problems... Warner On Jul 28, 2013, at 4:35 AM, Hans Petter Selasky wrote: > Hi, > > Can you try the attached patch? > > --HPS > ___ > freebsd-...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org" ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
Patch radiotap.diff ifconfig wlan0 normal execution through wifi wpa also be connected to the But often disconnected: Edit /etc/motd to change this login announcement. root@FreeBSD:~ # uptime 11:13PM up 33 secs, 1 user, load averages: 1.34, 0.37, 0.13 root@FreeBSD:~ # date Thu Jul 25 23:13:43 UTC 2013 root@FreeBSD:~ # ifconfig wlan create wlandev run0 wlan0: Ethernet address: 10:6f:3f:2b:fd:7d wlan0 ugen0.2: at usbus0 run0: <1.0> on usbus0 run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 10:6f:3f:2b:fd:7d run0: firmware RT2870 ver. 0.236 loaded root@FreeBSD:~ # date Thu Jul 25 23:15:38 UTC 2013 root@FreeBSD:~ # uname -a FreeBSD FreeBSD.7axu.com 10.0-CURRENT FreeBSD 10.0-CURRENT #1 r253662M: Mon Jul 29 16:39:29 CST 2013 r...@freebsd.7axu.com:/usr/obj/arm.armv6/usr/src/sys/CUBIEBOARD1G arm root@FreeBSD:~ # ugen0.2: at usbus0 (disconnected) run0: at uhub1, port 1, addr 2 (disconnected) root@FreeBSD:~ # ugen0.2: at usbus0 run0: <1.0> on usbus0 run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 10:6f:3f:2b:fd:7d ifconfig run0: firmware RT2870 ver. 0.236 loaded run0 down root@FreeBSD:~ # run0: firmware RT2870 ver. 0.236 loaded root@FreeBSD:~ # -- Regards. By: XiaoQI Ge; PGP:8B09D5F7 WWW: https://www.7axu.com/ 2013/7/29 Adrian Chadd : > As long as that results in the radiotap structures being 4 or 8 byte > padded when it's embedded in the softc - then yes, indeed. > > Xiao, can you try? > > > -adrian > > On 28 July 2013 03:35, Hans Petter Selasky wrote: >> Hi, >> >> Can you try the attached patch? >> >> --HPS ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
As long as that results in the radiotap structures being 4 or 8 byte padded when it's embedded in the softc - then yes, indeed. Xiao, can you try? -adrian On 28 July 2013 03:35, Hans Petter Selasky wrote: > Hi, > > Can you try the attached patch? > > --HPS ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
Hi, Can you try the attached patch? --HPS === sys/dev/usb/wlan/if_rumvar.h == --- sys/dev/usb/wlan/if_rumvar.h (revision 253548) +++ sys/dev/usb/wlan/if_rumvar.h (local) @@ -29,7 +29,7 @@ int8_t wr_antsignal; int8_t wr_antnoise; uint8_t wr_antenna; -}; +} __packed __aligned(8); #define RT2573_RX_RADIOTAP_PRESENT \ ((1 << IEEE80211_RADIOTAP_FLAGS) |\ @@ -47,7 +47,7 @@ uint16_t wt_chan_freq; uint16_t wt_chan_flags; uint8_t wt_antenna; -}; +} __packed __aligned(8); #define RT2573_TX_RADIOTAP_PRESENT \ ((1 << IEEE80211_RADIOTAP_FLAGS) |\ === sys/dev/usb/wlan/if_runvar.h == --- sys/dev/usb/wlan/if_runvar.h (revision 253548) +++ sys/dev/usb/wlan/if_runvar.h (local) @@ -58,7 +58,7 @@ int8_t wr_dbm_antsignal; uint8_t wr_antenna; uint8_t wr_antsignal; -} __packed; +} __packed __aligned(8); #define RUN_RX_RADIOTAP_PRESENT\ (1 << IEEE80211_RADIOTAP_FLAGS | \ @@ -75,7 +75,7 @@ uint16_t wt_chan_freq; uint16_t wt_chan_flags; uint8_t wt_hwqueue; -} __packed; +} __packed __aligned(8); #define IEEE80211_RADIOTAP_HWQUEUE 15 === sys/dev/usb/wlan/if_uathvar.h == --- sys/dev/usb/wlan/if_uathvar.h (revision 253548) +++ sys/dev/usb/wlan/if_uathvar.h (local) @@ -52,7 +52,7 @@ int8_t wr_antsignal; int8_t wr_antnoise; u_int8_t wr_antenna; -} __packed; +} __packed __aligned(8); #define UATH_RX_RADIOTAP_PRESENT ( \ (1 << IEEE80211_RADIOTAP_TSFT) | \ @@ -69,7 +69,7 @@ uint8_t wt_flags; uint16_t wt_chan_freq; uint16_t wt_chan_flags; -} __packed; +} __packed __aligned(8); #define UATH_TX_RADIOTAP_PRESENT \ ((1 << IEEE80211_RADIOTAP_FLAGS) |\ === sys/dev/usb/wlan/if_upgtvar.h == --- sys/dev/usb/wlan/if_upgtvar.h (revision 253548) +++ sys/dev/usb/wlan/if_upgtvar.h (local) @@ -380,7 +380,7 @@ uint16_t wr_chan_freq; uint16_t wr_chan_flags; int8_t wr_antsignal; -} __packed; +} __packed __aligned(8); #define UPGT_RX_RADIOTAP_PRESENT \ ((1 << IEEE80211_RADIOTAP_FLAGS) |\ @@ -394,7 +394,7 @@ uint8_t wt_rate; uint16_t wt_chan_freq; uint16_t wt_chan_flags; -} __packed; +} __packed __aligned(8); #define UPGT_TX_RADIOTAP_PRESENT \ ((1 << IEEE80211_RADIOTAP_FLAGS) |\ === sys/dev/usb/wlan/if_uralvar.h == --- sys/dev/usb/wlan/if_uralvar.h (revision 253548) +++ sys/dev/usb/wlan/if_uralvar.h (local) @@ -34,7 +34,7 @@ int8_t wr_antsignal; int8_t wr_antnoise; uint8_t wr_antenna; -}; +} __packed __aligned(8); #define RAL_RX_RADIOTAP_PRESENT \ ((1 << IEEE80211_RADIOTAP_FLAGS) |\ @@ -51,7 +51,7 @@ uint16_t wt_chan_freq; uint16_t wt_chan_flags; uint8_t wt_antenna; -}; +} __packed __aligned(8); #define RAL_TX_RADIOTAP_PRESENT \ ((1 << IEEE80211_RADIOTAP_FLAGS) |\ === sys/dev/usb/wlan/if_urtwnreg.h == --- sys/dev/usb/wlan/if_urtwnreg.h (revision 253548) +++ sys/dev/usb/wlan/if_urtwnreg.h (local) @@ -1030,7 +1030,7 @@ uint16_t wr_chan_freq; uint16_t wr_chan_flags; uint8_t wr_dbm_antsignal; -} __packed; +} __packed __aligned(8); #define URTWN_RX_RADIOTAP_PRESENT \ (1 << IEEE80211_RADIOTAP_FLAGS | \ @@ -1043,7 +1043,7 @@ uint8_t wt_flags; uint16_t wt_chan_freq; uint16_t wt_chan_flags; -} __packed; +} __packed __aligned(8); #define URTWN_TX_RADIOTAP_PRESENT \ (1 << IEEE80211_RADIOTAP_FLAGS | \ === sys/dev/usb/wlan/if_urtwvar.h == --- sys/dev/usb/wlan/if_urtwvar.h (revision 253548) +++ sys/dev/usb/wlan/if_urtwvar.h (local) @@ -63,7 +63,7 @@ uint16_t wr_chan_freq; uint16_t wr_chan_flags; int8_t wr_dbm_antsignal; -} __packed; +} __packed __aligned(8); #define URTW_RX_RADIOTAP_PRESENT \ ((1 << IEEE80211_RADIOTAP_FLAGS) |\ @@ -75,7 +75,7 @@ uint8_t wt_flags; uint16_t wt_chan_freq; uint16_t wt_chan_flags; -} __packed; +} __packed __aligned(8); #define URTW_TX_RADIOTAP_PRESENT \ ((1 << IEEE80211_RADIOTAP_FLAGS) |\ === sys/dev/usb/wlan/if_zydreg.h == --- sys/dev/usb/wlan/if_zydreg.h (revision 253548) +++ sys/dev/usb/wlan/if_zydreg.h (local) @@ -1185,7 +1185,7 @@ uint16_t wr_chan_flags; int8_t wr_antsignal; int8_t wr_antnoise; -} __packed; +} __packed __aligned(8); #define ZYD_RX_RADIOTAP_PRESENT \ ((1 << IEEE80211_RADIOTAP_FLAGS) |\ @@ -1200,7 +1200,7 @@ uint8_t wt_rate; uint16_t wt_chan_freq; uint16_t wt_chan_flags; -} __packed; +} __packed __aligned(8); #define ZYD_TX_RADIOTAP_PRESENT \ ((1 << IEEE80211_RADIOTAP_FLAGS) |\ ___
RE: My WLI-UC-GNM up crash
This patch? commit bae4e38c197f464c4bffe7037d5d491e462105b0 Author: sam Date: Thu Apr 1 00:38:45 2004 + radiotap updates: o force little-endian byte order for header o pad header to 32-bit boundary to guard against applications that assume packet data alignment --HPS -Original message- > From:Adrian Chadd mailto:adr...@freebsd.org> > > Sent: Sunday 28th July 2013 6:29 > To: XiaoQI Ge mailto:g...@7axu.com> > > Cc: freebsd-arm mailto:freebsd-...@freebsd.org> >; > freebsd-wireless@freebsd.org <mailto:freebsd-wireless@freebsd.org> > Subject: Re: My WLI-UC-GNM up crash > > Not sure, I haven't dug into it. It shouldn't be hard to fix though. > > I think someone just screwed up in defining the structures in the USB > drivers and didn't specify alignment. ath(4) got it right because Sam > ran it on MIPS/ARM boards. > > > > -adrian > > On 27 July 2013 20:34, XiaoQI Ge mailto:g...@7axu.com> > > wrote: > > That should be how to solve it? > > -- > > Regards. > > By: XiaoQI Ge; PGP:8B09D5F7 > > WWW: https://www.7axu.com/ > > > > > > > > 2013/7/27 Adrian Chadd mailto:adr...@freebsd.org> >: > >> This is known; there's some alignment issue with the radiotap TX/RX > >> structures in some of these USB devices. > >> > >> > >> > >> -adrain > >> > >> On 25 July 2013 20:23, XiaoQI Ge mailto:g...@7axu.com> > > >> wrote: > >>> 我更新到最新的源码（r253662），这次错误信息变成了0xde9f4d34 > >>> > >>> [root@FreeBSD.ttyu0 <mailto:root@FreeBSD.ttyu0> ] ˜ # Fatal kernel mode > >>> data abort: 'Alignment Fault 1' > >>> trapframe: 0xde9f4d34 > >>> FSR=0801, FAR=c284afbb, spsr=0013 > >>> r0 =c284c000, r1 =c284afbb, r2 =c284c210, r3 =096c > >>> r4 =c284c024, r5 =c05f07c5, r6 =0014, r7 =c2844800 > >>> r8 =c05f07c5, r9 =c284c000, r10=35cb, r11=de9f4e10 > >>> r12=002e, ssp=de9f4d80, slr=, pc =c046d20c > >>> > >>> [ thread pid 0 tid 100053 ] > >>> Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1] > >>> db> > >>> --- > >>> Kernel wlan related options > >>> device wlan# 802.11 support > >>> options IEEE80211_DEBUG # enable debug msgs > >>> options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's > >>> options IEEE80211_SUPPORT_MESH # enable 802.11s draft support > >>> device wlan_wep# 802.11 WEP support > >>> device wlan_ccmp # 802.11 CCMP support > >>> device wlan_tkip # 802.11 TKIP support > >>> device wlan_amrr # AMRR transmit rate control algorithm > >>> device firmware# firmware assist module > >>> device run #Ralink Technology USB IEEE 802.11a/g/n > >>> wireless network device > >>> device runfw#Firmware Module for Ralink driver > >>> > >>> --- > >>> The compiler command > >>> make TARGET_ARCH=armv6 TARGET_CPUTYPE=armv6 KERNCONF=BBB WITH_FDT=yes > >>> buildkernel > >>> -- > >>> Regards. > >>> By: XiaoQI Ge; PGP:8B09D5F7 > >>> WWW: https://www.7axu.com/ > >>> > >>> > >>> > >>> 2013/7/24 XiaoQI Ge mailto:g...@7axu.com> >: > >>>> How do I debug it? Can provide useful information > >>>> > >>>> login: root > >>>> Jul 24 18:27:31 FreeBSD login: ROOT LOGIN (root) ON ttyu0 > >>>> FreeBSD 10.0-CURRENT (BBB) #4 r253585M: Wed Jul 24 17:07:53 CST 2013 > >>>> [root@FreeBSD.ttyu0 <mailto:root@FreeBSD.ttyu0> ] ˜ # ifconfig wlan > >>>> create wlandev run0 > >>>> wlan0: Ethernet address: 10:6f:3f:2b:fd:6d > >>>> wlan0 > >>>> [root@FreeBSD.ttyu0 <mailto:root@FreeBSD.ttyu0> ] ˜ # ifconfig wlan0 up > >>>> run0: firmware RT2870 ver. 0.236 loaded > >>>> Fatal kernel mode data abort: 'Alignment Fault 1' > >>>> trapframe: 0xde9e4d5c > >>>> FSR=0801, FAR=c282ffbb, spsr=0013 > >>>> r0 =c2831000, r1 =c282ffbb, r2 =c2831210, r3 =096c > >>>> r4 =c2831024, r5 =c2831000, r6 =c05d9362, r7 =c2829800 > >>>> r8 =0014, r9 =c08144d8, r10=80001cce, r11=de9e4e10 > >>&g
Re: My WLI-UC-GNM up crash
Not sure, I haven't dug into it. It shouldn't be hard to fix though.
I think someone just screwed up in defining the structures in the USB
drivers and didn't specify alignment. ath(4) got it right because Sam
ran it on MIPS/ARM boards.
-adrian
On 27 July 2013 20:34, XiaoQI Ge wrote:
> That should be how to solve it?
> --
> Regards.
> By: XiaoQI Ge; PGP:8B09D5F7
> WWW: https://www.7axu.com/
>
>
>
> 2013/7/27 Adrian Chadd :
>> This is known; there's some alignment issue with the radiotap TX/RX
>> structures in some of these USB devices.
>>
>>
>>
>> -adrain
>>
>> On 25 July 2013 20:23, XiaoQI Ge wrote:
>>> 我更新到最新的源码（r253662），这次错误信息变成了0xde9f4d34
>>>
>>> [root@FreeBSD.ttyu0] ~ # Fatal kernel mode data abort: 'Alignment Fault 1'
>>> trapframe: 0xde9f4d34
>>> FSR=0801, FAR=c284afbb, spsr=0013
>>> r0 =c284c000, r1 =c284afbb, r2 =c284c210, r3 =096c
>>> r4 =c284c024, r5 =c05f07c5, r6 =0014, r7 =c2844800
>>> r8 =c05f07c5, r9 =c284c000, r10=35cb, r11=de9f4e10
>>> r12=002e, ssp=de9f4d80, slr=, pc =c046d20c
>>>
>>> [ thread pid 0 tid 100053 ]
>>> Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1]
>>> db>
>>> ---
>>> Kernel wlan related options
>>> device wlan# 802.11 support
>>> options IEEE80211_DEBUG # enable debug msgs
>>> options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's
>>> options IEEE80211_SUPPORT_MESH # enable 802.11s draft support
>>> device wlan_wep# 802.11 WEP support
>>> device wlan_ccmp # 802.11 CCMP support
>>> device wlan_tkip # 802.11 TKIP support
>>> device wlan_amrr # AMRR transmit rate control algorithm
>>> device firmware# firmware assist module
>>> device run #Ralink Technology USB IEEE 802.11a/g/n
>>> wireless network device
>>> device runfw#Firmware Module for Ralink driver
>>>
>>> ---
>>> The compiler command
>>> make TARGET_ARCH=armv6 TARGET_CPUTYPE=armv6 KERNCONF=BBB WITH_FDT=yes
>>> buildkernel
>>> --
>>> Regards.
>>> By: XiaoQI Ge; PGP:8B09D5F7
>>> WWW: https://www.7axu.com/
>>>
>>>
>>>
>>> 2013/7/24 XiaoQI Ge :
How do I debug it? Can provide useful information
login: root
Jul 24 18:27:31 FreeBSD login: ROOT LOGIN (root) ON ttyu0
FreeBSD 10.0-CURRENT (BBB) #4 r253585M: Wed Jul 24 17:07:53 CST 2013
[root@FreeBSD.ttyu0] ~ # ifconfig wlan create wlandev run0
wlan0: Ethernet address: 10:6f:3f:2b:fd:6d
wlan0
[root@FreeBSD.ttyu0] ~ # ifconfig wlan0 up
run0: firmware RT2870 ver. 0.236 loaded
Fatal kernel mode data abort: 'Alignment Fault 1'
trapframe: 0xde9e4d5c
FSR=0801, FAR=c282ffbb, spsr=0013
r0 =c2831000, r1 =c282ffbb, r2 =c2831210, r3 =096c
r4 =c2831024, r5 =c2831000, r6 =c05d9362, r7 =c2829800
r8 =0014, r9 =c08144d8, r10=80001cce, r11=de9e4e10
r12=002e, ssp=de9e4da8, slr=, pc =c045c510
[ thread pid 0 tid 100053 ]
Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1]
db>
These two places modified:
2522 }
2523
2524 ant = run_maxrssi_chain(sc, rxwi);
2525 rssi = rxwi->rssi[ant];
2526 nf = run_rssi2dbm(sc, rssi, ant);
2527
2528 m->m_pkthdr.rcvif = ifp;
2529 m->m_pkthdr.len = m->m_len = len;
2530 /*
2531 if (ni != NULL) {
2532 (void)ieee80211_input(ni, m, rssi, nf);
2533 ieee80211_free_node(ni);
2534 } else {
2535 (void)ieee80211_input_all(ic, m, rssi, nf);
2536 }
2537 */
2538 /*
2539 * DAAN: fill-in tap header BEFORE calling ieee80211_input*() so
the
2540 * user will see the actual data that belongs to THIS packet..
2541 */
2542 if (__predict_false(ieee80211_radiotap_active(ic))) {
2543 struct run_rx_radiotap_header *tap = &sc->sc_rxtap;
2544
2545 tap->wr_flags = 0;
2546 tap->wr_chan_freq = htole16(ic->ic_curchan->ic_freq);
2547 tap->wr_chan_flags = htole16(ic->ic_curchan->ic_flags);
2548 tap->wr_antsignal = rssi;
2549 tap->wr_antenna = ant;
2550 tap->wr_dbm_antsignal = run_rssi2dbm(sc, rssi, ant);
2551 tap->wr_rate = 2; /* in case it can't be found below */
2552 phy = le16toh(rxwi->phy);
2553 switch (phy & RT2860_PHY_MODE) {
2554 case RT2860_PHY_CCK:
2555 switch ((phy & RT2860_PHY_MCS) & ~RT2860_PHY_SHPRE) {
2556 case 0: tap->wr_rate = 2; break;
2557 case 1: tap->wr_rate = 4; break;
2558 case 2: tap->wr_rate = 11; break;
2559 case 3: tap->wr_rate = 22; break;
2560 }
2561 if (phy & RT2860_PHY_SHPRE)
2562 tap->wr_flags |= IEEE80211_RAD
Re: My WLI-UC-GNM up crash
That should be how to solve it?
--
Regards.
By: XiaoQI Ge; PGP:8B09D5F7
WWW: https://www.7axu.com/
2013/7/27 Adrian Chadd :
> This is known; there's some alignment issue with the radiotap TX/RX
> structures in some of these USB devices.
>
>
>
> -adrain
>
> On 25 July 2013 20:23, XiaoQI Ge wrote:
>> 我更新到最新的源码（r253662），这次错误信息变成了0xde9f4d34
>>
>> [root@FreeBSD.ttyu0] ~ # Fatal kernel mode data abort: 'Alignment Fault 1'
>> trapframe: 0xde9f4d34
>> FSR=0801, FAR=c284afbb, spsr=0013
>> r0 =c284c000, r1 =c284afbb, r2 =c284c210, r3 =096c
>> r4 =c284c024, r5 =c05f07c5, r6 =0014, r7 =c2844800
>> r8 =c05f07c5, r9 =c284c000, r10=35cb, r11=de9f4e10
>> r12=002e, ssp=de9f4d80, slr=, pc =c046d20c
>>
>> [ thread pid 0 tid 100053 ]
>> Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1]
>> db>
>> ---
>> Kernel wlan related options
>> device wlan# 802.11 support
>> options IEEE80211_DEBUG # enable debug msgs
>> options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's
>> options IEEE80211_SUPPORT_MESH # enable 802.11s draft support
>> device wlan_wep# 802.11 WEP support
>> device wlan_ccmp # 802.11 CCMP support
>> device wlan_tkip # 802.11 TKIP support
>> device wlan_amrr # AMRR transmit rate control algorithm
>> device firmware# firmware assist module
>> device run #Ralink Technology USB IEEE 802.11a/g/n
>> wireless network device
>> device runfw#Firmware Module for Ralink driver
>>
>> ---
>> The compiler command
>> make TARGET_ARCH=armv6 TARGET_CPUTYPE=armv6 KERNCONF=BBB WITH_FDT=yes
>> buildkernel
>> --
>> Regards.
>> By: XiaoQI Ge; PGP:8B09D5F7
>> WWW: https://www.7axu.com/
>>
>>
>>
>> 2013/7/24 XiaoQI Ge :
>>> How do I debug it? Can provide useful information
>>>
>>> login: root
>>> Jul 24 18:27:31 FreeBSD login: ROOT LOGIN (root) ON ttyu0
>>> FreeBSD 10.0-CURRENT (BBB) #4 r253585M: Wed Jul 24 17:07:53 CST 2013
>>> [root@FreeBSD.ttyu0] ~ # ifconfig wlan create wlandev run0
>>> wlan0: Ethernet address: 10:6f:3f:2b:fd:6d
>>> wlan0
>>> [root@FreeBSD.ttyu0] ~ # ifconfig wlan0 up
>>> run0: firmware RT2870 ver. 0.236 loaded
>>> Fatal kernel mode data abort: 'Alignment Fault 1'
>>> trapframe: 0xde9e4d5c
>>> FSR=0801, FAR=c282ffbb, spsr=0013
>>> r0 =c2831000, r1 =c282ffbb, r2 =c2831210, r3 =096c
>>> r4 =c2831024, r5 =c2831000, r6 =c05d9362, r7 =c2829800
>>> r8 =0014, r9 =c08144d8, r10=80001cce, r11=de9e4e10
>>> r12=002e, ssp=de9e4da8, slr=, pc =c045c510
>>>
>>> [ thread pid 0 tid 100053 ]
>>> Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1]
>>> db>
>>>
>>>
>>> These two places modified:
>>> 2522 }
>>> 2523
>>> 2524 ant = run_maxrssi_chain(sc, rxwi);
>>> 2525 rssi = rxwi->rssi[ant];
>>> 2526 nf = run_rssi2dbm(sc, rssi, ant);
>>> 2527
>>> 2528 m->m_pkthdr.rcvif = ifp;
>>> 2529 m->m_pkthdr.len = m->m_len = len;
>>> 2530 /*
>>> 2531 if (ni != NULL) {
>>> 2532 (void)ieee80211_input(ni, m, rssi, nf);
>>> 2533 ieee80211_free_node(ni);
>>> 2534 } else {
>>> 2535 (void)ieee80211_input_all(ic, m, rssi, nf);
>>> 2536 }
>>> 2537 */
>>> 2538 /*
>>> 2539 * DAAN: fill-in tap header BEFORE calling ieee80211_input*() so
>>> the
>>> 2540 * user will see the actual data that belongs to THIS packet..
>>> 2541 */
>>> 2542 if (__predict_false(ieee80211_radiotap_active(ic))) {
>>> 2543 struct run_rx_radiotap_header *tap = &sc->sc_rxtap;
>>> 2544
>>> 2545 tap->wr_flags = 0;
>>> 2546 tap->wr_chan_freq = htole16(ic->ic_curchan->ic_freq);
>>> 2547 tap->wr_chan_flags = htole16(ic->ic_curchan->ic_flags);
>>> 2548 tap->wr_antsignal = rssi;
>>> 2549 tap->wr_antenna = ant;
>>> 2550 tap->wr_dbm_antsignal = run_rssi2dbm(sc, rssi, ant);
>>> 2551 tap->wr_rate = 2; /* in case it can't be found below */
>>> 2552 phy = le16toh(rxwi->phy);
>>> 2553 switch (phy & RT2860_PHY_MODE) {
>>> 2554 case RT2860_PHY_CCK:
>>> 2555 switch ((phy & RT2860_PHY_MCS) & ~RT2860_PHY_SHPRE) {
>>> 2556 case 0: tap->wr_rate = 2; break;
>>> 2557 case 1: tap->wr_rate = 4; break;
>>> 2558 case 2: tap->wr_rate = 11; break;
>>> 2559 case 3: tap->wr_rate = 22; break;
>>> 2560 }
>>> 2561 if (phy & RT2860_PHY_SHPRE)
>>> 2562 tap->wr_flags |= IEEE80211_RADIOTAP_F_SHORTPRE;
>>> 2563 break;
>>> 2564 case RT2860_PHY_OFDM:
>>> 2565 switch (phy & RT2860_PHY_MCS) {
>>> 2566 case 0: tap->wr_rate = 12; break;
>>> 2567 case 1: tap->wr_rate = 18; break;
>>> 2568 case 2: tap->wr_rate = 24; break;
>>> 2569 case 3: tap->wr_rate = 36; break;
>>> 2570 case 4: tap->wr_rate = 48; break;
>
Re: My WLI-UC-GNM up crash
This is known; there's some alignment issue with the radiotap TX/RX
structures in some of these USB devices.
-adrain
On 25 July 2013 20:23, XiaoQI Ge wrote:
> 我更新到最新的源码（r253662），这次错误信息变成了0xde9f4d34
>
> [root@FreeBSD.ttyu0] ~ # Fatal kernel mode data abort: 'Alignment Fault 1'
> trapframe: 0xde9f4d34
> FSR=0801, FAR=c284afbb, spsr=0013
> r0 =c284c000, r1 =c284afbb, r2 =c284c210, r3 =096c
> r4 =c284c024, r5 =c05f07c5, r6 =0014, r7 =c2844800
> r8 =c05f07c5, r9 =c284c000, r10=35cb, r11=de9f4e10
> r12=002e, ssp=de9f4d80, slr=, pc =c046d20c
>
> [ thread pid 0 tid 100053 ]
> Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1]
> db>
> ---
> Kernel wlan related options
> device wlan# 802.11 support
> options IEEE80211_DEBUG # enable debug msgs
> options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's
> options IEEE80211_SUPPORT_MESH # enable 802.11s draft support
> device wlan_wep# 802.11 WEP support
> device wlan_ccmp # 802.11 CCMP support
> device wlan_tkip # 802.11 TKIP support
> device wlan_amrr # AMRR transmit rate control algorithm
> device firmware# firmware assist module
> device run #Ralink Technology USB IEEE 802.11a/g/n
> wireless network device
> device runfw#Firmware Module for Ralink driver
>
> ---
> The compiler command
> make TARGET_ARCH=armv6 TARGET_CPUTYPE=armv6 KERNCONF=BBB WITH_FDT=yes
> buildkernel
> --
> Regards.
> By: XiaoQI Ge; PGP:8B09D5F7
> WWW: https://www.7axu.com/
>
>
>
> 2013/7/24 XiaoQI Ge :
>> How do I debug it? Can provide useful information
>>
>> login: root
>> Jul 24 18:27:31 FreeBSD login: ROOT LOGIN (root) ON ttyu0
>> FreeBSD 10.0-CURRENT (BBB) #4 r253585M: Wed Jul 24 17:07:53 CST 2013
>> [root@FreeBSD.ttyu0] ~ # ifconfig wlan create wlandev run0
>> wlan0: Ethernet address: 10:6f:3f:2b:fd:6d
>> wlan0
>> [root@FreeBSD.ttyu0] ~ # ifconfig wlan0 up
>> run0: firmware RT2870 ver. 0.236 loaded
>> Fatal kernel mode data abort: 'Alignment Fault 1'
>> trapframe: 0xde9e4d5c
>> FSR=0801, FAR=c282ffbb, spsr=0013
>> r0 =c2831000, r1 =c282ffbb, r2 =c2831210, r3 =096c
>> r4 =c2831024, r5 =c2831000, r6 =c05d9362, r7 =c2829800
>> r8 =0014, r9 =c08144d8, r10=80001cce, r11=de9e4e10
>> r12=002e, ssp=de9e4da8, slr=, pc =c045c510
>>
>> [ thread pid 0 tid 100053 ]
>> Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1]
>> db>
>>
>>
>> These two places modified:
>> 2522 }
>> 2523
>> 2524 ant = run_maxrssi_chain(sc, rxwi);
>> 2525 rssi = rxwi->rssi[ant];
>> 2526 nf = run_rssi2dbm(sc, rssi, ant);
>> 2527
>> 2528 m->m_pkthdr.rcvif = ifp;
>> 2529 m->m_pkthdr.len = m->m_len = len;
>> 2530 /*
>> 2531 if (ni != NULL) {
>> 2532 (void)ieee80211_input(ni, m, rssi, nf);
>> 2533 ieee80211_free_node(ni);
>> 2534 } else {
>> 2535 (void)ieee80211_input_all(ic, m, rssi, nf);
>> 2536 }
>> 2537 */
>> 2538 /*
>> 2539 * DAAN: fill-in tap header BEFORE calling ieee80211_input*() so the
>> 2540 * user will see the actual data that belongs to THIS packet..
>> 2541 */
>> 2542 if (__predict_false(ieee80211_radiotap_active(ic))) {
>> 2543 struct run_rx_radiotap_header *tap = &sc->sc_rxtap;
>> 2544
>> 2545 tap->wr_flags = 0;
>> 2546 tap->wr_chan_freq = htole16(ic->ic_curchan->ic_freq);
>> 2547 tap->wr_chan_flags = htole16(ic->ic_curchan->ic_flags);
>> 2548 tap->wr_antsignal = rssi;
>> 2549 tap->wr_antenna = ant;
>> 2550 tap->wr_dbm_antsignal = run_rssi2dbm(sc, rssi, ant);
>> 2551 tap->wr_rate = 2; /* in case it can't be found below */
>> 2552 phy = le16toh(rxwi->phy);
>> 2553 switch (phy & RT2860_PHY_MODE) {
>> 2554 case RT2860_PHY_CCK:
>> 2555 switch ((phy & RT2860_PHY_MCS) & ~RT2860_PHY_SHPRE) {
>> 2556 case 0: tap->wr_rate = 2; break;
>> 2557 case 1: tap->wr_rate = 4; break;
>> 2558 case 2: tap->wr_rate = 11; break;
>> 2559 case 3: tap->wr_rate = 22; break;
>> 2560 }
>> 2561 if (phy & RT2860_PHY_SHPRE)
>> 2562 tap->wr_flags |= IEEE80211_RADIOTAP_F_SHORTPRE;
>> 2563 break;
>> 2564 case RT2860_PHY_OFDM:
>> 2565 switch (phy & RT2860_PHY_MCS) {
>> 2566 case 0: tap->wr_rate = 12; break;
>> 2567 case 1: tap->wr_rate = 18; break;
>> 2568 case 2: tap->wr_rate = 24; break;
>> 2569 case 3: tap->wr_rate = 36; break;
>> 2570 case 4: tap->wr_rate = 48; break;
>> 2571 case 5: tap->wr_rate = 72; break;
>> 2572 case 6: tap->wr_rate = 96; break;
>> 2573 case 7: tap->wr_rate = 108; break;
>> 2574 }
>> 2575 break;
>> 2576 }
>> 2577 }
>> 2578
>> 2
Re: My WLI-UC-GNM up crash
我更新到最新的源码（r253662），这次错误信息变成了0xde9f4d34
[root@FreeBSD.ttyu0] ~ # Fatal kernel mode data abort: 'Alignment Fault 1'
trapframe: 0xde9f4d34
FSR=0801, FAR=c284afbb, spsr=0013
r0 =c284c000, r1 =c284afbb, r2 =c284c210, r3 =096c
r4 =c284c024, r5 =c05f07c5, r6 =0014, r7 =c2844800
r8 =c05f07c5, r9 =c284c000, r10=35cb, r11=de9f4e10
r12=002e, ssp=de9f4d80, slr=, pc =c046d20c
[ thread pid 0 tid 100053 ]
Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1]
db>
---
Kernel wlan related options
device wlan# 802.11 support
options IEEE80211_DEBUG # enable debug msgs
options IEEE80211_AMPDU_AGE # age frames in AMPDU reorder q's
options IEEE80211_SUPPORT_MESH # enable 802.11s draft support
device wlan_wep# 802.11 WEP support
device wlan_ccmp # 802.11 CCMP support
device wlan_tkip # 802.11 TKIP support
device wlan_amrr # AMRR transmit rate control algorithm
device firmware# firmware assist module
device run #Ralink Technology USB IEEE 802.11a/g/n
wireless network device
device runfw#Firmware Module for Ralink driver
---
The compiler command
make TARGET_ARCH=armv6 TARGET_CPUTYPE=armv6 KERNCONF=BBB WITH_FDT=yes
buildkernel
--
Regards.
By: XiaoQI Ge; PGP:8B09D5F7
WWW: https://www.7axu.com/
2013/7/24 XiaoQI Ge :
> How do I debug it? Can provide useful information
>
> login: root
> Jul 24 18:27:31 FreeBSD login: ROOT LOGIN (root) ON ttyu0
> FreeBSD 10.0-CURRENT (BBB) #4 r253585M: Wed Jul 24 17:07:53 CST 2013
> [root@FreeBSD.ttyu0] ~ # ifconfig wlan create wlandev run0
> wlan0: Ethernet address: 10:6f:3f:2b:fd:6d
> wlan0
> [root@FreeBSD.ttyu0] ~ # ifconfig wlan0 up
> run0: firmware RT2870 ver. 0.236 loaded
> Fatal kernel mode data abort: 'Alignment Fault 1'
> trapframe: 0xde9e4d5c
> FSR=0801, FAR=c282ffbb, spsr=0013
> r0 =c2831000, r1 =c282ffbb, r2 =c2831210, r3 =096c
> r4 =c2831024, r5 =c2831000, r6 =c05d9362, r7 =c2829800
> r8 =0014, r9 =c08144d8, r10=80001cce, r11=de9e4e10
> r12=002e, ssp=de9e4da8, slr=, pc =c045c510
>
> [ thread pid 0 tid 100053 ]
> Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1]
> db>
>
>
> These two places modified:
> 2522 }
> 2523
> 2524 ant = run_maxrssi_chain(sc, rxwi);
> 2525 rssi = rxwi->rssi[ant];
> 2526 nf = run_rssi2dbm(sc, rssi, ant);
> 2527
> 2528 m->m_pkthdr.rcvif = ifp;
> 2529 m->m_pkthdr.len = m->m_len = len;
> 2530 /*
> 2531 if (ni != NULL) {
> 2532 (void)ieee80211_input(ni, m, rssi, nf);
> 2533 ieee80211_free_node(ni);
> 2534 } else {
> 2535 (void)ieee80211_input_all(ic, m, rssi, nf);
> 2536 }
> 2537 */
> 2538 /*
> 2539 * DAAN: fill-in tap header BEFORE calling ieee80211_input*() so the
> 2540 * user will see the actual data that belongs to THIS packet..
> 2541 */
> 2542 if (__predict_false(ieee80211_radiotap_active(ic))) {
> 2543 struct run_rx_radiotap_header *tap = &sc->sc_rxtap;
> 2544
> 2545 tap->wr_flags = 0;
> 2546 tap->wr_chan_freq = htole16(ic->ic_curchan->ic_freq);
> 2547 tap->wr_chan_flags = htole16(ic->ic_curchan->ic_flags);
> 2548 tap->wr_antsignal = rssi;
> 2549 tap->wr_antenna = ant;
> 2550 tap->wr_dbm_antsignal = run_rssi2dbm(sc, rssi, ant);
> 2551 tap->wr_rate = 2; /* in case it can't be found below */
> 2552 phy = le16toh(rxwi->phy);
> 2553 switch (phy & RT2860_PHY_MODE) {
> 2554 case RT2860_PHY_CCK:
> 2555 switch ((phy & RT2860_PHY_MCS) & ~RT2860_PHY_SHPRE) {
> 2556 case 0: tap->wr_rate = 2; break;
> 2557 case 1: tap->wr_rate = 4; break;
> 2558 case 2: tap->wr_rate = 11; break;
> 2559 case 3: tap->wr_rate = 22; break;
> 2560 }
> 2561 if (phy & RT2860_PHY_SHPRE)
> 2562 tap->wr_flags |= IEEE80211_RADIOTAP_F_SHORTPRE;
> 2563 break;
> 2564 case RT2860_PHY_OFDM:
> 2565 switch (phy & RT2860_PHY_MCS) {
> 2566 case 0: tap->wr_rate = 12; break;
> 2567 case 1: tap->wr_rate = 18; break;
> 2568 case 2: tap->wr_rate = 24; break;
> 2569 case 3: tap->wr_rate = 36; break;
> 2570 case 4: tap->wr_rate = 48; break;
> 2571 case 5: tap->wr_rate = 72; break;
> 2572 case 6: tap->wr_rate = 96; break;
> 2573 case 7: tap->wr_rate = 108; break;
> 2574 }
> 2575 break;
> 2576 }
> 2577 }
> 2578
> 2579 if (ni != NULL) {
> 2580 (void)ieee80211_input(ni, m, rssi, nf);
> 2581 ieee80211_free_node(ni);
> 2582 } else {
> 2583 (void)ieee80211_input_all(ic, m, rssi, nf);
> 2584 }
> 2585
> 2586 }
> 2587
> 2588 static void
>
>
> Index: sys/vm/vm_map.c
>
Re: My WLI-UC-GNM up crash
How do I debug it? Can provide useful information
login: root
Jul 24 18:27:31 FreeBSD login: ROOT LOGIN (root) ON ttyu0
FreeBSD 10.0-CURRENT (BBB) #4 r253585M: Wed Jul 24 17:07:53 CST 2013
[root@FreeBSD.ttyu0] ~ # ifconfig wlan create wlandev run0
wlan0: Ethernet address: 10:6f:3f:2b:fd:6d
wlan0
[root@FreeBSD.ttyu0] ~ # ifconfig wlan0 up
run0: firmware RT2870 ver. 0.236 loaded
Fatal kernel mode data abort: 'Alignment Fault 1'
trapframe: 0xde9e4d5c
FSR=0801, FAR=c282ffbb, spsr=0013
r0 =c2831000, r1 =c282ffbb, r2 =c2831210, r3 =096c
r4 =c2831024, r5 =c2831000, r6 =c05d9362, r7 =c2829800
r8 =0014, r9 =c08144d8, r10=80001cce, r11=de9e4e10
r12=002e, ssp=de9e4da8, slr=, pc =c045c510
[ thread pid 0 tid 100053 ]
Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1]
db>
These two places modified:
2522 }
2523
2524 ant = run_maxrssi_chain(sc, rxwi);
2525 rssi = rxwi->rssi[ant];
2526 nf = run_rssi2dbm(sc, rssi, ant);
2527
2528 m->m_pkthdr.rcvif = ifp;
2529 m->m_pkthdr.len = m->m_len = len;
2530 /*
2531 if (ni != NULL) {
2532 (void)ieee80211_input(ni, m, rssi, nf);
2533 ieee80211_free_node(ni);
2534 } else {
2535 (void)ieee80211_input_all(ic, m, rssi, nf);
2536 }
2537 */
2538 /*
2539 * DAAN: fill-in tap header BEFORE calling ieee80211_input*() so the
2540 * user will see the actual data that belongs to THIS packet..
2541 */
2542 if (__predict_false(ieee80211_radiotap_active(ic))) {
2543 struct run_rx_radiotap_header *tap = &sc->sc_rxtap;
2544
2545 tap->wr_flags = 0;
2546 tap->wr_chan_freq = htole16(ic->ic_curchan->ic_freq);
2547 tap->wr_chan_flags = htole16(ic->ic_curchan->ic_flags);
2548 tap->wr_antsignal = rssi;
2549 tap->wr_antenna = ant;
2550 tap->wr_dbm_antsignal = run_rssi2dbm(sc, rssi, ant);
2551 tap->wr_rate = 2; /* in case it can't be found below */
2552 phy = le16toh(rxwi->phy);
2553 switch (phy & RT2860_PHY_MODE) {
2554 case RT2860_PHY_CCK:
2555 switch ((phy & RT2860_PHY_MCS) & ~RT2860_PHY_SHPRE) {
2556 case 0: tap->wr_rate = 2; break;
2557 case 1: tap->wr_rate = 4; break;
2558 case 2: tap->wr_rate = 11; break;
2559 case 3: tap->wr_rate = 22; break;
2560 }
2561 if (phy & RT2860_PHY_SHPRE)
2562 tap->wr_flags |= IEEE80211_RADIOTAP_F_SHORTPRE;
2563 break;
2564 case RT2860_PHY_OFDM:
2565 switch (phy & RT2860_PHY_MCS) {
2566 case 0: tap->wr_rate = 12; break;
2567 case 1: tap->wr_rate = 18; break;
2568 case 2: tap->wr_rate = 24; break;
2569 case 3: tap->wr_rate = 36; break;
2570 case 4: tap->wr_rate = 48; break;
2571 case 5: tap->wr_rate = 72; break;
2572 case 6: tap->wr_rate = 96; break;
2573 case 7: tap->wr_rate = 108; break;
2574 }
2575 break;
2576 }
2577 }
2578
2579 if (ni != NULL) {
2580 (void)ieee80211_input(ni, m, rssi, nf);
2581 ieee80211_free_node(ni);
2582 } else {
2583 (void)ieee80211_input_all(ic, m, rssi, nf);
2584 }
2585
2586 }
2587
2588 static void
Index: sys/vm/vm_map.c
===
--- sys/vm/vm_map.c (revision 253514)
+++ sys/vm/vm_map.c (working copy)
@@ -239,8 +239,7 @@
vm_map_t map;
map = (vm_map_t)mem;
- map->nentries = 0;
- map->size = 0;
+ memset(map, 0, sizeof(*map));
mtx_init(&map->system_mtx, "vm map (system)", NULL, MTX_DEF |
MTX_DUPOK);
sx_init(&map->lock, "vm map (user)");
return (0);
--
Regards.
By: XiaoQI Ge; PGP:8B09D5F7
WWW: https://www.7axu.com/
2013/7/24 XiaoQI Ge :
> I manually make up, is compiling the kernel
> --
> Regards.
> By: XiaoQI Ge; PGP:8B09D5F7
> WWW: https://www.7axu.com/
>
>
>
> 2013/7/24 XiaoQI Ge :
>> patch < /root/if_run_2013_01_19_radiotap_fix_only.diff appears to be invalid
>>
>> ] /usr/src/sys/dev/usb/wlan # patch <
>> /root/if_run_2013_01_19_radiotap_fix_only.diff
>> Hmm... Looks like a unified diff to me...
>> The text leading up to this was:
>> --
>> |--- if_run.c.fix1_vnet 2013-06-14 10:12:49.786774072 +0200
>> |+++ if_run.c.fix2_vnet_plus_radiotap 2013-06-14 10:15:34.890774314 +0200
>> --
>> File to patch:
>>
>>
>> 2013/7/23 Daan Vreeken :
>>> cd /usr/src/sys/dev/usb/wlan
>>
>>
>>
>> --
>> Regards.
>> By: XiaoQI Ge; PGP:8B09D5F7
>> WWW: https://www.7axu.com/
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
I manually make up, is compiling the kernel -- Regards. By: XiaoQI Ge; PGP:8B09D5F7 WWW: https://www.7axu.com/ 2013/7/24 XiaoQI Ge : > patch < /root/if_run_2013_01_19_radiotap_fix_only.diff appears to be invalid > > ] /usr/src/sys/dev/usb/wlan # patch < > /root/if_run_2013_01_19_radiotap_fix_only.diff > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -- > |--- if_run.c.fix1_vnet 2013-06-14 10:12:49.786774072 +0200 > |+++ if_run.c.fix2_vnet_plus_radiotap 2013-06-14 10:15:34.890774314 +0200 > -- > File to patch: > > > 2013/7/23 Daan Vreeken : >> cd /usr/src/sys/dev/usb/wlan > > > > -- > Regards. > By: XiaoQI Ge; PGP:8B09D5F7 > WWW: https://www.7axu.com/ ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
patch < /root/if_run_2013_01_19_radiotap_fix_only.diff appears to be invalid ] /usr/src/sys/dev/usb/wlan # patch < /root/if_run_2013_01_19_radiotap_fix_only.diff Hmm... Looks like a unified diff to me... The text leading up to this was: -- |--- if_run.c.fix1_vnet 2013-06-14 10:12:49.786774072 +0200 |+++ if_run.c.fix2_vnet_plus_radiotap 2013-06-14 10:15:34.890774314 +0200 -- File to patch: 2013/7/23 Daan Vreeken : > cd /usr/src/sys/dev/usb/wlan -- Regards. By: XiaoQI Ge; PGP:8B09D5F7 WWW: https://www.7axu.com/ ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
Hi XiaoQI Ge, On Tuesday 23 July 2013 11:59:14 XiaoQI Ge wrote: > This patch I do not know how to use > > > Please see the patches I posted here : > > http://www.freebsd.org/cgi/query-pr.cgi?pr=arm%2F179532&cat= > > > > I think they may solve your problem. Download the following file : http://www.vitsch.nl/pub-diffs/if_run_2013_01_19_radiotap_fix_only.diff Then (assuming your sources are installed in /usr/src ), do the following : cd /usr/src/sys/dev/usb/wlan patch < /path/to/location/of/if_run_2013_01_19_radiotap_fix_only.diff Then recompile your kernel and try to boot it. Regards, -- Ing. Daan Vreeken Vitsch Electronics http://Vitsch.nl/ http://VitschVPN.nl/ tel: +31-(0)40-7113051 KvK nr: 17174380 -- Machines en netwerken op afstand beheren? Vitsch VPN oplossing! Kijk voor meer informatie op: http://www.VitschVPN.nl/ ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
This patch I do not know how to use Please see the patches I posted here : http://www.freebsd.org/cgi/query-pr.cgi?pr=arm%2F179532&cat= I think they may solve your problem. -- Regards. By: XiaoQI Ge; PGP:8B09D5F7 WWW: https://www.7axu.com/ 2013/7/15 Daan Vreeken : > Hi XiaoQI Ge, > > On Monday 15 July 2013 06:12:38 XiaoQI Ge wrote: >> My WLI-UC-GNM ifconfig up when collapsed, >> I do not know how to solve >> >> >> root@FreeBSD:~ # ifconfig wlan create wlandev run0 >> wlan0: Ethernet address: 10:6f:3f:2b:fd:6d >> wlan0 >> root@FreeBSD:~ # ifconfig >> lo0: flags=8049 metric 0 mtu 16384 >> options=63 >> inet6 ::1 prefixlen 128 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 >> inet 127.0.0.1 netmask 0xff00 >> nd6 options=21 >> run0: flags=8802 metric 0 mtu 2290 >> ether 10:6f:3f:2b:fd:6d >> nd6 options=29 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> wlan0: flags=8802 metric 0 mtu 1500 >> ether 10:6f:3f:2b:fd:6d >> nd6 options=29 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> ssid "" channel 1 (2412 MHz 11b) >> country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60 >> wme bintval 0 >> root@FreeBSD:~ # dhclient wlan0 >> wlan0: no link .. giving up >> root@FreeBSD:~ # pciconf -lv >> pciconf: /dev/pci: No such file or directory >> root@FreeBSD:~ # ifconfig wlan0 up scan >> run0: firmware RT2870 ver. 0.236 loaded >> root@FreeBSD:~ # Fatal kernel mode data abort: 'Alignment Fault 1' >> trapframe: 0xde177d68 >> FSR=0801, FAR=c24b3faf, spsr=0013 >> r0 =c24b7000, r1 =c24b3faf, r2 =c24b720c, r3 =096c >> r4 =80003eaf, r5 =c249c800, r6 =c24b7024, r7 =c0760898 >> r8 =c24b7000, r9 =0014, r10=c055851d, r11=de177e18 >> r12=002e, ssp=de177db4, slr=, pc =c04072d4 >> >> [ thread pid 0 tid 100038 ] >> Stopped at ieee80211_radiotap_chan_change+0x94:strhr3, [r1] >> db> bt >> Tracing pid 0 tid 100038 td 0xc232a620 >> _end() at 0xde177a90 >> scp=0xde177a90 rlv=0xc04f5e48 (db_trace_thread+0x34) >> rsp=0xde177a74 rfp=0xc05b8750 >> Bad frame pointer: 0xc05b8750 >> db> > > Please see the patches I posted here : > http://www.freebsd.org/cgi/query-pr.cgi?pr=arm%2F179532&cat= > > I think they may solve your problem. > > > Regards, > -- > Ing. Daan Vreeken > Vitsch Electronics > http://Vitsch.nl/ > http://VitschVPN.nl/ > tel: +31-(0)40-7113051 > KvK nr: 17174380 > -- > Machines en netwerken op afstand beheren? Vitsch VPN oplossing! > Kijk voor meer informatie op: http://www.VitschVPN.nl/ ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
I tried to fight this patch root@FreeBSD:~ # ifconfig wlan0 up run0: firmware RT2870 ver. 0.236 loaded root@FreeBSD:~ # Fatal kernel mode data abort: 'Alignment Fault 1' trapframe: 0xde9e4d5c FSR=0801, FAR=c282ffbb, spsr=0013 r0 =c2831000, r1 =c282ffbb, r2 =c2831210, r3 =096c r4 =c2831024, r5 =c2831000, r6 =c05d9362, r7 =c2829800 r8 =0014, r9 =c08144d8, r10=80006d5d, r11=de9e4e10 r12=002e, ssp=de9e4da8, slr=, pc =c045c524 [ thread pid 0 tid 100053 ] Stopped at ieee80211_radiotap_chan_change+0x90:strhr3, [r1] db> And crashes FreeBSD 10.0-CURRENT (BBB) #2 r253557M: Tue Jul 23 21:26:40 CST 2013 (Beagleboard Black) -- Regards. By: XiaoQI Ge; PGP:8B09D5F7 WWW: https://www.7axu.com/ 2013/7/15 Hans Petter Selasky : > Hi, > > Can you try the attached patch? > > --HPS ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
I'll try this patch -- Regards. By: XiaoQI Ge; PGP:8B09D5F7 WWW: https://www.7axu.com/ 2013/7/15 Daan Vreeken : > Hi XiaoQI Ge, > > On Monday 15 July 2013 06:12:38 XiaoQI Ge wrote: >> My WLI-UC-GNM ifconfig up when collapsed, >> I do not know how to solve >> >> >> root@FreeBSD:~ # ifconfig wlan create wlandev run0 >> wlan0: Ethernet address: 10:6f:3f:2b:fd:6d >> wlan0 >> root@FreeBSD:~ # ifconfig >> lo0: flags=8049 metric 0 mtu 16384 >> options=63 >> inet6 ::1 prefixlen 128 >> inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 >> inet 127.0.0.1 netmask 0xff00 >> nd6 options=21 >> run0: flags=8802 metric 0 mtu 2290 >> ether 10:6f:3f:2b:fd:6d >> nd6 options=29 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> wlan0: flags=8802 metric 0 mtu 1500 >> ether 10:6f:3f:2b:fd:6d >> nd6 options=29 >> media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) >> status: no carrier >> ssid "" channel 1 (2412 MHz 11b) >> country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60 >> wme bintval 0 >> root@FreeBSD:~ # dhclient wlan0 >> wlan0: no link .. giving up >> root@FreeBSD:~ # pciconf -lv >> pciconf: /dev/pci: No such file or directory >> root@FreeBSD:~ # ifconfig wlan0 up scan >> run0: firmware RT2870 ver. 0.236 loaded >> root@FreeBSD:~ # Fatal kernel mode data abort: 'Alignment Fault 1' >> trapframe: 0xde177d68 >> FSR=0801, FAR=c24b3faf, spsr=0013 >> r0 =c24b7000, r1 =c24b3faf, r2 =c24b720c, r3 =096c >> r4 =80003eaf, r5 =c249c800, r6 =c24b7024, r7 =c0760898 >> r8 =c24b7000, r9 =0014, r10=c055851d, r11=de177e18 >> r12=002e, ssp=de177db4, slr=, pc =c04072d4 >> >> [ thread pid 0 tid 100038 ] >> Stopped at ieee80211_radiotap_chan_change+0x94:strhr3, [r1] >> db> bt >> Tracing pid 0 tid 100038 td 0xc232a620 >> _end() at 0xde177a90 >> scp=0xde177a90 rlv=0xc04f5e48 (db_trace_thread+0x34) >> rsp=0xde177a74 rfp=0xc05b8750 >> Bad frame pointer: 0xc05b8750 >> db> > > Please see the patches I posted here : > http://www.freebsd.org/cgi/query-pr.cgi?pr=arm%2F179532&cat= > > I think they may solve your problem. > > > Regards, > -- > Ing. Daan Vreeken > Vitsch Electronics > http://Vitsch.nl/ > http://VitschVPN.nl/ > tel: +31-(0)40-7113051 > KvK nr: 17174380 > -- > Machines en netwerken op afstand beheren? Vitsch VPN oplossing! > Kijk voor meer informatie op: http://www.VitschVPN.nl/ ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
Hi XiaoQI Ge, On Monday 15 July 2013 06:12:38 XiaoQI Ge wrote: > My WLI-UC-GNM ifconfig up when collapsed, > I do not know how to solve > > > root@FreeBSD:~ # ifconfig wlan create wlandev run0 > wlan0: Ethernet address: 10:6f:3f:2b:fd:6d > wlan0 > root@FreeBSD:~ # ifconfig > lo0: flags=8049 metric 0 mtu 16384 > options=63 > inet6 ::1 prefixlen 128 > inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 > inet 127.0.0.1 netmask 0xff00 > nd6 options=21 > run0: flags=8802 metric 0 mtu 2290 > ether 10:6f:3f:2b:fd:6d > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > wlan0: flags=8802 metric 0 mtu 1500 > ether 10:6f:3f:2b:fd:6d > nd6 options=29 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 1 (2412 MHz 11b) > country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60 > wme bintval 0 > root@FreeBSD:~ # dhclient wlan0 > wlan0: no link .. giving up > root@FreeBSD:~ # pciconf -lv > pciconf: /dev/pci: No such file or directory > root@FreeBSD:~ # ifconfig wlan0 up scan > run0: firmware RT2870 ver. 0.236 loaded > root@FreeBSD:~ # Fatal kernel mode data abort: 'Alignment Fault 1' > trapframe: 0xde177d68 > FSR=0801, FAR=c24b3faf, spsr=0013 > r0 =c24b7000, r1 =c24b3faf, r2 =c24b720c, r3 =096c > r4 =80003eaf, r5 =c249c800, r6 =c24b7024, r7 =c0760898 > r8 =c24b7000, r9 =0014, r10=c055851d, r11=de177e18 > r12=002e, ssp=de177db4, slr=, pc =c04072d4 > > [ thread pid 0 tid 100038 ] > Stopped at ieee80211_radiotap_chan_change+0x94:strhr3, [r1] > db> bt > Tracing pid 0 tid 100038 td 0xc232a620 > _end() at 0xde177a90 > scp=0xde177a90 rlv=0xc04f5e48 (db_trace_thread+0x34) > rsp=0xde177a74 rfp=0xc05b8750 > Bad frame pointer: 0xc05b8750 > db> Please see the patches I posted here : http://www.freebsd.org/cgi/query-pr.cgi?pr=arm%2F179532&cat= I think they may solve your problem. Regards, -- Ing. Daan Vreeken Vitsch Electronics http://Vitsch.nl/ http://VitschVPN.nl/ tel: +31-(0)40-7113051 KvK nr: 17174380 -- Machines en netwerken op afstand beheren? Vitsch VPN oplossing! Kijk voor meer informatie op: http://www.VitschVPN.nl/ ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
Re: My WLI-UC-GNM up crash
Tomorrow I'll try Is the clang compiler content in make.conf WITH_LIBCPLUSPLUS=yes NO_WERROR= WERROR= Using what command to compile the make TARGET_ARCH=arm WITH_FDT=yes MALLOC_PRODUCTION=yes kernel-toolchain make TARGET_ARCH=arm TARGET_CPUTYPE=armv6 KERNCONF=CB1G WITH_FDT=yes MALLOC_PRODUCTION=yes buildkernel -- Regards. By: XiaoQI Ge; PGP:8B09D5F7 WWW: https://www.7axu.com/ 2013/7/15 Hans Petter Selasky > ** > > Can you tell us which compiler you used to build your image? > > --HPS > > ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
RE: My WLI-UC-GNM up crash
Can you tell us which compiler you used to build your image? --HPS ___ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
RE: My WLI-UC-GNM up crash
Hi,
Can you try the attached patch?
--HPS
diff --git a/sys/net80211/ieee80211_radiotap.h b/sys/net80211/ieee80211_radiotap.h
index b8a8b51..c199d48 100644
--- a/sys/net80211/ieee80211_radiotap.h
+++ b/sys/net80211/ieee80211_radiotap.h
@@ -78,7 +78,7 @@ struct ieee80211_radiotap_header {
* Additional extensions are made
* by setting bit 31.
*/
-} __packed;
+} __packed __aligned(4);
/*
* Name Data type Units
___
freebsd-wireless@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-wireless
To unsubscribe, send any mail to "freebsd-wireless-unsubscr...@freebsd.org"
