Yes, all on raspberry
Stefan, I can setup VM and test amd64. Current or 6.1-stable?
To ensure I didn't a mess follow the diff:
diff -u ieee80211_proto-orig.c /usr/src/sys/net80211/ieee80211_proto.c
--- ieee80211_proto-orig.c Thu Aug 3 13:38:26 2017
+++ /usr/src/sys/net80211/ieee80211_proto.c Thu Aug 3 13:10:45 2017
@@ -1023,10 +1023,6 @@
case IEEE80211_S_INIT:
case IEEE80211_S_SCAN:
case IEEE80211_S_ASSOC:
- panic("invalid transition %s -> %s",
- ieee80211_state_name[ostate],
- ieee80211_state_name[nstate]);
- break;
case IEEE80211_S_AUTH:
IEEE80211_SEND_MGMT(ic, ni,
IEEE80211_FC0_SUBTYPE_ASSOC_REQ, 0);
Thank you
2017-08-03 15:04 GMT-03:00 Stefan Sperling <[email protected]>:
> On Thu, Aug 03, 2017 at 01:39:27PM -0300, R0me0 *** wrote:
> > Hi, applied the patch by hands as suggested:
> >
> >
> > urtwn0: no link ......... got link
>
> Since the link is up It is already in RUN state at this point.
>
> > DHCPDISCOVER on urtwn0 - interval 1
> > DHCPDISCOVER on urtwn0 - interval 1
> > panic: invalid transition AUTH -> RUN
>
> So this makes absolutely no sense at all without more context.
>
> Is this still on the raspberry pi?
> Can you reproduce this same bug on an amd64 machine?
>
> > Stopped at panic+0x158: TID PID UID PRFLAGS
> > PFLAGS C
> > PU COMMAND
> > *489298 5181 0 0x14000 0x200 0 usbtask
> > db_enter() at panic+0x154
> > panic() at rtwn_newstate+0x6c4
> > rtwn_newstate() at urtwn_task+0x5c
> > urtwn_task() at usb_task_thread+0xe8
> > usb_task_thread() at proc_trampoline+0xc
> > https://www.openbsd.org/ddb.html describes the minimum info required in
> bug
> > reports. Insufficient info makes it difficult to find and fix bugs.
> > ddb> show panic
> > invalid transition AUTH -> RUN
> > ddb> trace
> > db_enter() at panic+0x154
> > panic() at rtwn_newstate+0x6c4
> > rtwn_newstate() at urtwn_task+0x5c
> > urtwn_task() at usb_task_thread+0xe8
> > usb_task_thread() at proc_trampoline+0xc
> >
> >
> >
> > @Stefan thanks!
> >
> > :-)
> >
> >
> > 2017-08-01 18:39 GMT-03:00 Stefan Sperling <[email protected]>:
> >
> > > On Tue, Aug 01, 2017 at 06:54:00AM -0300, R0me0 *** wrote:
> > > > Hello, Stefan! How you doing!? Hope very well!;
> > > >
> > > > I have installed the latest snapshot and the issue persists. Also, I
> > > took a
> > > > look at diff you provided ( I am not a programmer sorry any mistake
> ) and
> > > > seems is already committed.
> > >
> > > AFAIK this diff is not committed yet.
> > >
>
