firmware update

[dailijin]

Hi All,


Thanks all of you to help me investigate this issue. I have forwarded this issue to Sierra engineer, hope they can solve this issue.


Thanks again.





--

Best Regards,
Dai,Lijin



在 2015-12-23 19:58:42，"David McCullough" <david.mccullough at accelerated.com> 写道：
>
>Bjørn Mork wrote the following:
>> dailijin  <dailijin126 at 126.com> writes:
>> 
>> > tvupack tvu # cat /boot/config-3.8.0-23-generic  | grep PREEMPT 
>> > # CONFIG_PREEMPT_RCU is not set
>> > CONFIG_PREEMPT_NOTIFIERS=y
>> > # CONFIG_PREEMPT_NONE is not set
>> > CONFIG_PREEMPT_VOLUNTARY=y
>> > # CONFIG_PREEMPT is not set
>> 
>> That's normal and fine.
>> 
>> 
>> >>> Dec 23 03:45:09 tvupack kernel: INFO: task slqssdk:1555 blocked for more than 120 seconds.
>> >>> Dec 23 03:45:09 tvupack kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>> >>> Dec 23 03:45:09 tvupack kernel: slqssdk         D 0000000000000000     0  1555   1390 0x00000000
>> >>> Dec 23 03:45:09 tvupack kernel:  ffff8801065ab958 0000000000000086 ffff8801065ab978 ffff8801190eb1a0
>> >>> Dec 23 03:45:09 tvupack kernel:  ffff8801065abfd8 ffff8801065abfd8 ffff8801065abfd8 0000000000013f40
>> >>> Dec 23 03:45:09 tvupack kernel:  ffff880119b50000 ffff8801067d9740 ffff8801067d9740 ffff88010fe05968
>> >>> Dec 23 03:45:09 tvupack kernel: Call Trace:
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffff816e0669>] schedule+0x29/0x70
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffff816e091e>] schedule_preempt_disabled+0xe/0x10
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffff816df597>] __mutex_lock_slowpath+0xd7/0x150
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffff8151084e>] ? usb_alloc_urb+0x1e/0x50
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffff816df1aa>] mutex_lock+0x2a/0x50
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffffa029e10c>] Gobi_dtr_rts+0x6c/0x130 [GobiSerial]
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffffa03b2725>] ? usb_serial_generic_submit_read_urb+0x25/0x30 [usbserial]
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffffa03b058f>] serial_dtr_rts+0x7f/0x90 [usbserial]
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffff81429044>] tty_port_block_til_ready+0x174/0x320
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffff8107fc10>] ? add_wait_queue+0x60/0x60
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffffa03b04f2>] ? serial_activate+0x82/0xa0 [usbserial]
>> >>> Dec 23 03:45:09 tvupack kernel:  [<ffffffff814293eb>] tty_port_open+0xbb/0xe0
>> 
>> 
>> There is obviously something going wrong here.  Any chance you can
>> recreate this problem on a (semi-)recent kernel?
>> 
>> The serial_dtr_rts function was renamed to serial_port_dtr_rts in v3.10,
>> so you are obviously using something older than that.  There have been
>> quite a few cleanups and code refactoring in this area since then. So I
>> don't think there is any point wasting time on debugging this on such an
>> old kernel.
>
>I am running 4.1.
>
>Cheers,
>Davidm
>
>-- 
>David McCullough,  david.mccullough at accelerated.com,   Ph: 0410 560 763
>_______________________________________________
>libqmi-devel mailing list
>libqmi-devel at lists.freedesktop.org
>http://lists.freedesktop.org/mailman/listinfo/libqmi-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20151224/06d1069f/attachment.html>