lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <20180413002415.GC5700@atomide.com> Date: Thu, 12 Apr 2018 17:24:15 -0700 From: Tony Lindgren <tony@...mide.com> To: Pavel Machek <pavel@....cz> Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>, linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org, Alan Cox <alan@...yncelyn.cymru>, Dan Williams <dcbw@...hat.com>, Jiri Prchal <jiri.prchal@...ignal.cz>, Jiri Slaby <jslaby@...e.cz>, Marcel Partap <mpartap@....net>, Merlijn Wajer <merlijn@...zup.org>, Michael Nazzareno Trimarchi <michael@...rulasolutions.com>, Michael Scott <michael.scott@...aro.org>, Peter Hurley <peter@...leysoftware.com>, Russ Gorby <russ.gorby@...el.com>, Sascha Hauer <s.hauer@...gutronix.de>, Sebastian Reichel <sre@...nel.org> Subject: Re: [PATCH 1/2] tty: n_gsm: Fix long delays with control frame timeouts in ADM mode * Pavel Machek <pavel@....cz> [180412 21:25]: > sudo insmod /tmp/n_gsm.ko debug=0xff > > user@...uan:/my/droid4-ngsm$ sudo ./droid4-ngsm > Starting ngsm.. > Testing ngsm.. > Could not open /dev/gsmtty1: Level 2 halted > Trying to start ngsm again: Level 2 halted > Starting ngsm.. > Testing ngsm.. > Could not open /dev/gsmtty1: Level 2 halted > Trying to start ngsm again: Level 2 halted > Starting ngsm.. > ^CCould not set conf: Interrupted system call > Could not start ngsm: Interrupted system call > > [ 3378.381134] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host > [ 3408.460937] cpcap-usb-phy cpcap-usb-phy.0: connected to USB host > [ 3413.633239] Q> 0) R: UIH(F) > [ 3413.639190] C3 > [ 3413.642761] gsm_data_kick: 00000000: 7e 01 ef c3 aa 7e > ~....~ > [ 3413.653564] gsmld_output: 00000000: 7e 01 ef c3 aa 7e OK so no response from the modem. After few of the above packets, you should then also see something coming back: gsm_data_kick: 00000000: 7e 01 ef c3 aa 7e gsmld_output: 00000000: 7e 01 ef c3 aa 7e gsmld_output: 00000000: f9 03 3f 01 1c f9 --> 0) C: SABM(P) gsmld_output: 00000000: f9 03 3f 01 1c f9 --> 0) C: SABM(P) gsmld_receive: 00000000: f9 03 1f 01 36 f9 <-- 0) C: DM(P) gsmld_output: 00000000: f9 03 3f 01 1c f9 --> 0) C: SABM(P) gsmld_receive: 00000000: f9 03 1f 01 36 f9 <-- 0) C: DM(P) DLCI 0 opening in ADM mode. Do you have phy-mapphone-mdm6600 loaded? That is still needed to configure all the boot mode pins for the modem so it is usable.. The UART will then work also without ohci-platform, just the USB PHY is disabled without ohci-platform. I have these in my .config: CONFIG_SERIAL_8250_OMAP=y CONFIG_SERIAL_8250_OMAP_TTYO_FIXUP=y CONFIG_PHY_MAPPHONE_MDM6600=m CONFIG_N_GSM=m And then the two patches from $subject thread. I just tried it with today's mainline kernel and it's still working for me. Maybe you're missing some related patch though if usingv4.16? 984c7706ff18 ("ARM: dts: omap4-droid4: Configure uart1 pins") e5b9fd7bdeb5 ("ARM: dts: omap4-droid4: Configure MDM6600 USB PHY") fdd192037fce ("ARM: dts: omap4-droid4: Fix USB PHY port naming") bca809d8183c ("ARM: omap2plus_defconfig: Enable MDM6600 USB PHY") 077e1cde78c3 ("ARM: omap2plus_defconfig: Enable 8250_OMAP" So maybe you're still using CONFIG_SERIAL_OMAP=y instead of CONFIG_SERIAL_8250_OMAP=y? Regards, Tony
Powered by blists - more mailing lists