Yes, we tried with 3.14 and after less than 24hrs.
What could we do to fix the issue?
Thank you,
Matteo
Here's dmesg output:
[103200.145660] INFO: task XXXXXXXX:2341 blocked for more than 120 seconds.
[103200.145774] Not tainted 3.14.0-XXXXXXXX+ #3
[103200.145844] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
disables this message.
[103200.145950] XXXXXXXXX D de7a0000 0 2341 2263 0x00000000
[103200.146163] de79be5c 00200086 c17d8de0 de7a0000 de79be00 c17d8de0
00200246 c17d8e00
[103200.146357] de79be44 de7a0000 de79bfec de7a0000 c179b560 00200246
c17d8e00 de79be44
[103200.146661] de7a0000 0000007b c104eb7e c17d0000 00000000 ffffffcf
c154c2d5 de79be44
[103200.146853] Call Trace:
[103200.146948] [<c104eb7e>] ? preempt_count_sub+0xb/0xac
[103200.147103] [<c154c2d5>] ? _raw_spin_unlock_irqrestore+0x27/0x45
[103200.147200] [<c154c2df>] ? _raw_spin_unlock_irqrestore+0x31/0x45
[103200.147308] [<c1055899>] ? prepare_to_wait_event+0x60/0xb5
[103200.147432] [<c134af26>] ? usb_put_dev+0x14/0x16
[103200.147525] [<c1548be3>] schedule+0x22/0x54
[103200.147611] [<c1353ac1>] usb_kill_urb+0x51/0x80
[103200.147695] [<c10554a7>] ? bit_waitqueue+0x54/0x54
[103200.147809] [<dfff1408>] usb_serial_generic_close+0x63/0x72 [usbserial]
[103200.147921] [<dffef01f>] serial_port_shutdown+0x1f/0x21 [usbserial]
[103200.148096] [<c12c0307>] tty_port_shutdown+0x5b/0x7c
[103200.148188] [<c12c0a43>] tty_port_close+0x20/0x3d
[103200.148285] [<dffef595>] serial_close+0x23/0x25 [usbserial]
[103200.148377] [<c12b94c0>] tty_release+0xa4/0x52a
[103200.148492] [<c1116a63>] ? locks_remove_posix+0xe/0x94
[103200.148584] [<c105d432>] ? do_raw_spin_unlock+0x9/0x78
[103200.148674] [<c110c40f>] ? fsnotify+0xe/0x287
[103200.148753] [<c110c40f>] ? fsnotify+0xe/0x287
[103200.148848] [<c10d791e>] __fput+0x89/0x1ec
[103200.148933] [<c10d7ab5>] ____fput+0xd/0xf
[103200.149011] [<c1044225>] task_work_run+0x66/0x89
[103200.149161] [<c1001f2b>] do_notify_resume+0x5c/0x5e
[103200.149246] [<c154c759>] ? syscall_exit+0x8/0x1b
[103200.149330] [<c154c812>] work_notifysig+0x24/0x2a
[103200.149450] [<c1540000>] ? set_gssp_clnt+0xb3/0x125
[103200.163776] 2 locks held by XXXXXXXX/2341:
[103200.163856] #0: (&tty->legacy_mutex){......}, at: [<c154c580>]
tty_lock_nested+0x37/0x80
[103200.165368] #1: (&port->mutex){......}, at: [<c12c02ca>]
tty_port_shutdown+0x1e/0x7c
2014-04-11 16:09 GMT+02:00 Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx>:
> On Fri, Apr 11, 2014 at 12:19:55PM +0200, Matteo Fortini wrote:
>> We are experiencing stuck processes (D state) which are talking to an
>> FTD_SIO usb_serial adapter. The process sometimes has to close the
>> serial device when it detects an error or a timeout.
>
> Does this also happen with 3.14?
>
> thanks,
>
> greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
