Re: OpenWrt shutdown ModemManager/libglib crash
> > 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 etc on a small system, > and it may not even connect at all. > > Also it seems like the problem is not repeatable if I reboot immediately > after the first connect after boot, so there might be some condition > that has to happen first. > > I will put a non-stripped/debug MM/glib binary on the system, and see if > I can get more info. > Thanks for that. I don't like crashes like this, so any info about what happened or how to repro it is very welcome. -- Aleksander
Re: OpenWrt shutdown ModemManager/libglib crash
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 messes with all the connection timings etc on a small system, and it may not even connect at all. Also it seems like the problem is not repeatable if I reboot immediately after the first connect after boot, so there might be some condition that has to happen first. I will put a non-stripped/debug MM/glib binary on the system, and see if I can get more info.
Re: OpenWrt shutdown ModemManager/libglib crash
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 1.18.x? > > As I mention, it's happened as long as I can recall, so probably 2 years or > so. > I can't be more precise than that. It's just something I never got quite > around to mentioning given other more pressing issues. > 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. -- Aleksander
Re: OpenWrt shutdown ModemManager/libglib crash
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. Did this not happen with 1.18.x? As I mention, it's happened as long as I can recall, so probably 2 years or so. I can't be more precise than that. It's just something I never got quite around to mentioning given other more pressing issues.
Re: OpenWrt shutdown ModemManager/libglib crash
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_page_fault(): sending SIGSEGV to ModemManager for invalid > read > access from > [ 550.472911] epc = 77c4717d in libglib-2.0.so.0.7000.4[77c1+df000] > [ 550.485799] ra = 5566f85f in ModemManager[5563+183000] > [ 553.460649] reboot: Restarting system > > 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 1.18.x? -- Aleksander
OpenWrt shutdown ModemManager/libglib crash
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 [ 550.472911] epc = 77c4717d in libglib-2.0.so.0.7000.4[77c1+df000] [ 550.485799] ra = 5566f85f in ModemManager[5563+183000] [ 553.460649] reboot: Restarting system 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. Open to ideas on debugging here.
Re: Openwrt with modemmanager
On 10/20/18 8:18 PM, Russ Westrem wrote: > I've compiled and had working modemmanager with lede. Now when trying to > use it with openwrt it never establishes a connection. Does something > need to be done to use it with openwrt? > Given that I've never used it with Lede and only used it with OpenWRT, I would say nothing special is needed :) There aren't many things that could fail: check the hotplug scripts to see if all ports are reported, check whether MM detects the modem, and check whether netifd accepts the network config associated to the specific modem sysfs path. -- Aleksander https://aleksander.es ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
Openwrt with modemmanager
I've compiled and had working modemmanager with lede. Now when trying to use it with openwrt it never establishes a connection. Does something need to be done to use it with openwrt? ___ ModemManager-devel mailing list ModemManager-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
