> > If you could have it debugged a bit more, e.g. with gdb in order to
> > get a backtrace, that would be great. Not sure how easy that is in
> > your target device though.
> >
>
> I tried briefly, but the problem is that gdb slows everything down, and
> this messes with all the connection timings
On 11/8/22 15:12, Aleksander Morgado wrote:
Hey
If you could have it debugged a bit more, e.g. with gdb in order to
get a backtrace, that would be great. Not sure how easy that is in
your target device though.
I tried briefly, but the problem is that gdb slows everything down, and
this mes
Hey
> >> This is obviously an awkward point to debug anything, and it's perhaps not
> >> super important at this point, but it's pretty repeatable and has happened
> >> as long as I can remember.
> >>
> >> This is with MM 1.20.0, glib 2.70.4 and libqmi 1.32.0.
> >>
> >
> > Did this not happen with
On 11/7/22 10:22, Aleksander Morgado wrote:
Hey Peter!
This is obviously an awkward point to debug anything, and it's perhaps not
super important at this point, but it's pretty repeatable and has happened
as long as I can remember.
This is with MM 1.20.0, glib 2.70.4 and libqmi 1.32.0.
Di
Hey Peter!
On Fri, Nov 4, 2022 at 3:49 PM Peter Naulls wrote:
>
>
> When rebooting in OpenWrt:
>
> [ 548.410590] mtk_soc_eth 1e10.ethernet eth0: Link is Down
> [ 548.425055] device eth0 left promiscuous mode
> [ 548.434058] br-lan: port 1(eth0) entered disabled state
> [ 550.455000] do_pa
When rebooting in OpenWrt:
[ 548.410590] mtk_soc_eth 1e10.ethernet eth0: Link is Down
[ 548.425055] device eth0 left promiscuous mode
[ 548.434058] br-lan: port 1(eth0) entered disabled state
[ 550.455000] do_page_fault(): sending SIGSEGV to ModemManager for invalid read
access from 00
