From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tony Lindgren Subject: Re: USB gadgets with configfs hang reboot Date: Tue, 26 Apr 2016 09:49:19 -0700 Message-ID: <20160426164918.GA5995@atomide.com> References: <571F9AD4.8010900@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <571F9AD4.8010900-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Ivaylo Dimitrov Cc: Alan Stern , Felipe Balbi , linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Greg Kroah-Hartman , Robert Baldyga , Andrzej Pietrasiewicz , Michal Nazarewicz List-Id: linux-omap@vger.kernel.org * Ivaylo Dimitrov [160426 09:46]: > > > On 26.04.2016 18:03, Alan Stern wrote: > >On Tue, 26 Apr 2016, Felipe Balbi wrote: > > > >>>Is there a reason why a process (pnatd in this particular case) doesn't > >>>get killed on reboot? > >> > >>there might be, and that's probably the bug we're trying to figure > >>out. But so far, no idea. > > > >One possible reason is that the process is in an uninterruptible wait > >inside the kernel, waiting for something that isn't going to happen. > > The process waits in poll(&fds, 1u, -1), where fds contains only the fd of > /dev/ttyGS2. Nothing suspicious I can see here. I think the easy way to reproduce this is to start getty or minicom on /dev/ttyG* and disconnect the USB cable. Regards, Tony -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html