Date: Sat, 18 Jun 2016 21:11:21 -0700 From: Maxim Sobolev <sobomax@sippysoft.com> To: Jim Thompson <jim@netgate.com>, Luiz Otavio O Souza <loos.br@gmail.com> Cc: Svatopluk Kraus <onwahe@gmail.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: BBB (cpsw(4)) seems to be broken in the latest 11-current Message-ID: <CAH7qZfvAh-dSRYM7G1BkpgMZc3zkeSDakj7LOO=s2JF%2BUy=eUw@mail.gmail.com> In-Reply-To: <CAH7qZfvRB4y=GP9yjCAjjBy2h3pHTifdm0t%2BTTVFONQNPe9=8w@mail.gmail.com> References: <CAH7qZfsMiUSCTG827ysO89o9nH9WAKu4w%2BiZPZ-UKKVa6T2pcA@mail.gmail.com> <CAFHCsPWUFDiM%2BQh6EkNKPdbm0BrqtgStdzig4WyFmj8L31qN%2Bg@mail.gmail.com> <CAH7qZftdjhrp_m440BPHeArSnV-QQmghm4UyMJ3qro75NMGPQA@mail.gmail.com> <83A18C0E-FA89-4009-A8D5-3185FB27A688@netgate.com> <CAH7qZfvRB4y=GP9yjCAjjBy2h3pHTifdm0t%2BTTVFONQNPe9=8w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Jim, some update from here. Running r283287 of the driver, I still see the same "watchdog timeout" messages, but they do not lead to the interface lockout. The traffic resumes momentarily. Which is probably why I never paid much attention to those warnings before. Therefore, I suspect that the new MAC code does not deal with watchdog-triggered interface reset as good as the old code. Does it give you any ideas about what could be wrong there by any chance? 03:54:50 CPSW watchdog cpsw0: watchdog timeout cpsw0: Unable to cleanly shutdown transmitter 03:58:03 CPSW watchdog cpsw0: watchdog timeout cpsw0: Unable to cleanly shutdown transmitter On Sat, Jun 18, 2016 at 2:09 PM, Maxim Sobolev <sobomax@freebsd.org> wrote: > Jim, > > Yes, I've seen those. There were just handful of revision into the driver > between my old good kernel and now, most of them are from you guys: > > r299477 | gonzo | 2016-05-11 11:20:02 -0700 (=D1=81=D1=80, 11 =D0=BC=D0= =B0=D0=B9 2016) | 16 lines > r298352 | pfg | 2016-04-20 08:45:55 -0700 (=D1=81=D1=80, 20 =D0=B0=D0=BF= =D1=80 2016) | 6 lines > r297132 | loos | 2016-03-20 20:16:56 -0700 (=D0=B2=D1=81, 20 =D0=BC=D0=B0= =D1=80 2016) | 5 lines > r297043 | loos | 2016-03-18 13:24:31 -0700 (=D0=BF=D1=82, 18 =D0=BC=D0=B0= =D1=80 2016) | 4 lines > r297042 | loos | 2016-03-18 13:09:54 -0700 (=D0=BF=D1=82, 18 =D0=BC=D0=B0= =D1=80 2016) | 4 lines > r297041 | loos | 2016-03-18 13:04:34 -0700 (=D0=BF=D1=82, 18 =D0=BC=D0=B0= =D1=80 2016) | 4 lines > r296993 | loos | 2016-03-17 12:35:08 -0700 (=D1=87=D1=82, 17 =D0=BC=D0=B0= =D1=80 2016) | 24 lines > r296980 | loos | 2016-03-16 23:23:48 -0700 (=D1=81=D1=80, 16 =D0=BC=D0=B0= =D1=80 2016) | 6 lines > r283287 | andrew | 2015-05-22 07:25:23 -0700 (=D0=BF=D1=82, 22 =D0=BC=D0= =B0=D0=B9 2015) | 4 lines > (last known good one) > > I've reverted the driver to the state all way down to r283287, while > keeping the rest of the kernel intact and soon will see if it works bette= r. > If that works fine, I'll try to bi-sect it to a single troublesome revisi= on. > > -Max > > On Sat, Jun 18, 2016 at 12:26 PM, Jim Thompson <jim@netgate.com> wrote: > >> There are recent changes to enable the switch and two port MAC mode. >> >> These were lightly tested on BBB prior to being committed. >> >> -- Jim >> >> > On Jun 18, 2016, at 11:49 AM, Maxim Sobolev <sobomax@freebsd.org> >> wrote: >> > >> > Well, I am not sure either as I don't have any issue restarting it >> > afterwards. >> > >> > Yes, it seems to be happening fairly reliably here. :( Happened for me >> > again, I left it running overnight. I am 99% positive it was not the >> case >> > before kernel upgrade.. >> > >> > 07:11:52 CPSW watchdog cpswss0: watchdog timeout >> > cpswss0: Unable to cleanly shutdown transmitter >> > >> > >> >> On Sat, Jun 18, 2016 at 1:09 AM, Svatopluk Kraus <onwahe@gmail.com> >> wrote: >> >> >> >> On Sat, Jun 18, 2016 at 8:50 AM, Maxim Sobolev <sobomax@freebsd.org> >> >> wrote: >> >>> Updated my BBB to the latest -current, immediately got this while >> trying >> >> to >> >>> make world over ssh console: >> >>> >> >>> 06:02:17 CPSW watchdog cpswss0: watchdog timeout >> >>> cpswss0: Unable to cleanly shutdown transmitter >> >> >> >> My BBB stucks in cpsw0 during boot rarely, and even soft reset (reset >> >> button) does not help. Only hard reset (power-off) helps. I have neve= r >> >> had time to discover where a problem is. I'm not even sure if this is >> >> related to your problem as I did not remember exact dmesg in my case. >> >> >> >> Svata >> >> >> >> >> >>> >> >>> Interface seems to be locked after that, no traffic comes in or out. >> >>> >> >>> This is: >> >>> >> >>> FreeBSD 11.0-ALPHA3 #1 ba7edef(tps65217x)-dirty: Fri Jun 17 16:22:07 >> PDT >> >>> 2016, svn revision 301898 >> >>> >> >>> The previous version that was rock-solid was: >> >>> >> >>> FreeBSD 11.0-CURRENT #0 9d390ee(tps65217x)-dirty: Mon Jul 6 19:31:3= 0 >> PDT >> >>> 2015, svn revision 284878 >> >>> >> >>> I've been running buildworlds for literally days on that board, >> because >> >>> it's how long it takes to build on that hardware. :) >> >>> >> >>> I'll run it again and see if the issue re-appears. >> >>> >> >>> If anyone seen this or if it's known issue please let me know. >> >>> >> >>> Thanks! >> >>> >> >>> -Max >> >>> _______________________________________________ >> >>> freebsd-arm@freebsd.org mailing list >> >>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> >>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.or= g >> " >> > _______________________________________________ >> > freebsd-arm@freebsd.org mailing list >> > https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> >> > --=20 Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts Tel (Canada): +1-778-783-0474 Tel (Toll-Free): +1-855-747-7779 Fax: +1-866-857-6942 Web: http://www.sippysoft.com MSN: sales@sippysoft.com Skype: SippySoft
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAH7qZfvAh-dSRYM7G1BkpgMZc3zkeSDakj7LOO=s2JF%2BUy=eUw>