From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paulius Zaleckas Subject: Re: [RFC] Patch to option HSO driver to the kernel Date: Wed, 16 Apr 2008 16:11:57 +0300 Message-ID: <4805FB1D.4070304@teltonika.lt> References: <20080414213238.GB28833@kroah.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Return-path: In-Reply-To: <20080414213238.GB28833-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org> Sender: linux-usb-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: netdev.vger.kernel.org With the latest patch I always get BUG when closing my serial terminal application. I have two different modems (GTM378 and GTM380) plugged at USB hub. Here is the dump: BUG: sleeping function called from invalid context at drivers/usb/core/urb.c:542 in_atomic():1, irqs_disabled():0 Pid: 30031, comm: gtkterm Not tainted 2.6.24.4-64.fc8 #1 Call Trace: [] usb_kill_urb+0x1a/0xf1 [] mutex_lock+0x1e/0x2f [] fasync_helper+0x4a/0xcd [] :hso:hso_stop_serial_device+0x85/0x99 [] :hso:hso_serial_close+0xea/0x110 [] release_dev+0x212/0x618 [] free_pages_and_swap_cache+0x73/0x8f [] tty_release+0x11/0x1a [] __fput+0xc2/0x18f [] filp_close+0x5d/0x65 [] sys_close+0x8d/0xca [] tracesys+0xd5/0xda BUG: scheduling while atomic: gtkterm/30031/0x10000100 Pid: 30031, comm: gtkterm Not tainted 2.6.24.4-64.fc8 #1 Call Trace: [] schedule+0x91/0x706 [] __cond_resched+0x2d/0x55 [] cond_resched+0x2e/0x39 [] usb_kill_urb+0x1f/0xf1 [] mutex_lock+0x1e/0x2f [] fasync_helper+0x4a/0xcd [] :hso:hso_stop_serial_device+0x85/0x99 [] :hso:hso_serial_close+0xea/0x110 [] release_dev+0x212/0x618 [] free_pages_and_swap_cache+0x73/0x8f [] tty_release+0x11/0x1a [] __fput+0xc2/0x18f [] filp_close+0x5d/0x65 [] sys_close+0x8d/0xca [] tracesys+0xd5/0xda -- 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