[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#683202: marked as done (Some Bug in Linux kernel)

Your message dated Sun, 29 May 2016 21:24:52 +0100
with message-id f6e6dc02-753e-4788-a751-156905cabc45@decadent.org.uk
and subject line Closing bugs assigned to linux-2.6 package
has caused the Debian Bug report #683202,
regarding Some Bug in Linux kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
683202: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683202
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.32-5-686
Version: 2.6.32-45

When I used wvdial and pppd to make connection,
Sometimes ppp0 interface goes down,
any my system get hangged.

I am sending kern.log.

I am using Tata Photon USB modem.
 $ lsusb
Bus 004 Device 003: ID 12d1:140b Huawei Technologies Co., Ltd. EC1260 Wireless Data Modem HSD USB Card

After usb_modswitch from 12d1:1505 

I am using : Debian 6.0.5
Jul 29 23:11:47 debian kernel: [10528.575876] usb 4-1: USB disconnect, address 3
Jul 29 23:14:25 debian kernel: [10686.035383] INFO: task khubd:149 blocked for more than 120 seconds.
Jul 29 23:14:25 debian kernel: [10686.035554] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 29 23:14:25 debian kernel: [10686.035643] khubd         D 00000000     0   149      2 0x00000000
Jul 29 23:14:25 debian kernel: [10686.035678]  daa40440 00000046 bb11df37 00000000 00000282 c141d100 c141d100 c14186ac
Jul 29 23:14:25 debian kernel: [10686.035712]  daa405fc c1c08100 00000000 00000282 fffffff0 e48469e0 da935000 e3124d00
Jul 29 23:14:25 debian kernel: [10686.035742]  fffffffe daa405fc 002703ed 00000000 e3124d00 fffffff0 daa93e40 e46d052c
Jul 29 23:14:25 debian kernel: [10686.035777] Call Trace:
Jul 29 23:14:25 debian kernel: [10686.036229]  [<e46c1efb>] ? usb_kill_urb+0x84/0xa0 [usbcore]
Jul 29 23:14:25 debian kernel: [10686.036341]  [<c104432e>] ? autoremove_wake_function+0x0/0x2d
Jul 29 23:14:25 debian kernel: [10686.036391]  [<e46c0e34>] ? usb_hcd_flush_endpoint+0xbc/0xce [usbcore]
Jul 29 23:14:25 debian kernel: [10686.036441]  [<e46c26a2>] ? usb_disable_endpoint+0x40/0x56 [usbcore]
Jul 29 23:14:25 debian kernel: [10686.036485]  [<e46c2797>] ? usb_disable_interface+0x25/0x32 [usbcore]
Jul 29 23:14:25 debian kernel: [10686.036533]  [<e46c4c2b>] ? usb_unbind_interface+0x3a/0xb4 [usbcore]
Jul 29 23:14:25 debian kernel: [10686.036607]  [<c11b3a80>] ? __device_release_driver+0x74/0xb7
Jul 29 23:14:25 debian kernel: [10686.036628]  [<c11b3b4f>] ? device_release_driver+0x15/0x1e
Jul 29 23:14:25 debian kernel: [10686.036648]  [<c11b333b>] ? bus_remove_device+0x6e/0x87
Jul 29 23:14:25 debian kernel: [10686.036668]  [<c11b1fd8>] ? device_del+0xfa/0x152
Jul 29 23:14:25 debian kernel: [10686.036715]  [<e46c26ea>] ? usb_disable_device+0x32/0xba [usbcore]
Jul 29 23:14:25 debian kernel: [10686.036757]  [<e46bea9e>] ? usb_disconnect+0x70/0xf8 [usbcore]
Jul 29 23:14:25 debian kernel: [10686.036800]  [<e46bf832>] ? hub_thread+0x521/0xe53 [usbcore]
Jul 29 23:14:25 debian kernel: [10686.036826]  [<c104432e>] ? autoremove_wake_function+0x0/0x2d
Jul 29 23:14:25 debian kernel: [10686.036867]  [<e46bf311>] ? hub_thread+0x0/0xe53 [usbcore]
Jul 29 23:14:25 debian kernel: [10686.036886]  [<c10440fc>] ? kthread+0x61/0x66
Jul 29 23:14:25 debian kernel: [10686.036902]  [<c104409b>] ? kthread+0x0/0x66
Jul 29 23:14:25 debian kernel: [10686.036969]  [<c1003d47>] ? kernel_thread_helper+0x7/0x10
Jul 29 23:14:25 debian kernel: [10686.037081] INFO: task wvdial:1188 blocked for more than 120 seconds.
Jul 29 23:14:25 debian kernel: [10686.037136] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 29 23:14:25 debian kernel: [10686.037220] wvdial        D 0026d6f1     0  1188   1094 0x00000004
Jul 29 23:14:25 debian kernel: [10686.037241]  dab46640 00000082 e23a9c7c 0026d6f1 00000296 c141d100 c141d100 c14186ac
Jul 29 23:14:25 debian kernel: [10686.037270]  dab467fc c1c08100 00000000 00000296 00000000 e48469e0 da935000 e3165400
Jul 29 23:14:25 debian kernel: [10686.037298]  fffffffe dab467fc 0026d7eb 00000000 e3165400 00000000 e23a9ccc e46d052c
Jul 29 23:14:25 debian kernel: [10686.037327] Call Trace:
Jul 29 23:14:25 debian kernel: [10686.037384]  [<e46c1efb>] ? usb_kill_urb+0x84/0xa0 [usbcore]
Jul 29 23:14:25 debian kernel: [10686.037405]  [<c104432e>] ? autoremove_wake_function+0x0/0x2d
Jul 29 23:14:25 debian kernel: [10686.037456]  [<e46c2f1c>] ? usb_start_wait_urb+0x62/0x92 [usbcore]
Jul 29 23:14:25 debian kernel: [10686.037500]  [<e46c235e>] ? usb_init_urb+0x1a/0x26 [usbcore]
Jul 29 23:14:25 debian kernel: [10686.037546]  [<e46c3157>] ? usb_control_msg+0xf7/0x111 [usbcore]
Jul 29 23:14:25 debian kernel: [10686.037570]  [<e506d306>] ? option_send_setup+0x7a/0x84 [option]
Jul 29 23:14:25 debian kernel: [10686.037604]  [<e5054e29>] ? usb_wwan_set_termios+0x44/0x49 [usb_wwan]
Jul 29 23:14:25 debian kernel: [10686.037623]  [<e5054de5>] ? usb_wwan_set_termios+0x0/0x49 [usb_wwan]
Jul 29 23:14:25 debian kernel: [10686.037678]  [<e5031740>] ? serial_set_termios+0x5f/0x72 [usbserial]
Jul 29 23:14:25 debian kernel: [10686.037722]  [<c1193ad5>] ? set_termios+0x320/0x3a3
Jul 29 23:14:25 debian kernel: [10686.037744]  [<c1193d85>] ? tty_mode_ioctl+0x188/0x45c
Jul 29 23:14:25 debian kernel: [10686.037836]  [<c1025291>] ? check_preempt_wakeup+0x32/0x202
Jul 29 23:14:25 debian kernel: [10686.037885]  [<c113c4f3>] ? copy_from_user+0x27/0x10e
Jul 29 23:14:25 debian kernel: [10686.037955]  [<c10beec4>] ? set_fd_set+0x18/0x2d
Jul 29 23:14:25 debian kernel: [10686.037986]  [<e50a8b55>] ? ppp_asynctty_ioctl+0x13b/0x165 [ppp_async]
Jul 29 23:14:25 debian kernel: [10686.038006]  [<e50a8a1a>] ? ppp_asynctty_ioctl+0x0/0x165 [ppp_async]
Jul 29 23:14:25 debian kernel: [10686.038026]  [<c11904e9>] ? tty_ioctl+0x870/0x8b1
Jul 29 23:14:25 debian kernel: [10686.038043]  [<c118fb29>] ? tty_wakeup+0x43/0x47
Jul 29 23:14:25 debian kernel: [10686.038077]  [<c1195b90>] ? pty_write+0x39/0x3f
Jul 29 23:14:25 debian kernel: [10686.038095]  [<c118fc79>] ? tty_ioctl+0x0/0x8b1
Jul 29 23:14:25 debian kernel: [10686.038117]  [<c10be1b0>] ? vfs_ioctl+0x1c/0x5f
Jul 29 23:14:25 debian kernel: [10686.038135]  [<c10be744>] ? do_vfs_ioctl+0x4aa/0x4e5
Jul 29 23:14:25 debian kernel: [10686.038152]  [<c118f6a0>] ? tty_write_unlock+0x27/0x2a
Jul 29 23:14:25 debian kernel: [10686.038168]  [<c118f9e0>] ? tty_write+0x1af/0x1c0
Jul 29 23:14:25 debian kernel: [10686.038188]  [<e50a8006>] ? ppp_asynctty_write+0x0/0x6 [ppp_async]
Jul 29 23:14:25 debian kernel: [10686.038205]  [<c118f831>] ? tty_write+0x0/0x1c0
Jul 29 23:14:25 debian kernel: [10686.038260]  [<c10b4134>] ? vfs_write+0x7e/0xd6
Jul 29 23:14:25 debian kernel: [10686.038281]  [<c10be7c0>] ? sys_ioctl+0x41/0x58
Jul 29 23:14:25 debian kernel: [10686.038303]  [<c10030fb>] ? sysenter_do_call+0x12/0x28

--- End Message ---
--- Begin Message --- 
Version: 3.4.1-1~experimental.1+rm

Debian 6.0 Long Term Support has ended, and the 'linux-2.6' source
package will no longer be updated.  This bug was reassigned to the
'linux' source package earlier today, but I am now closing it on the
assumption that it does not affect the kernel versions in newer Debian
releases.

If you can still reproduce this bug in a newer release, please reopen
the bug report and reassign it to 'src:linux' and the affected version
of the package.  You can find the package version for the running
kernel by running:

    uname -v

or the versions of all installed kernel packages by running:

    dpkg -l 'linux-image-[34]*' | grep ^.i

and looking at the third column.

I apologise that we weren't able to provide a specific resolution for
this bug.

Ben.

-- 
Ben Hutchings - Debian developer, member of Linux kernel and LTS teams

--- End Message ---
Reply to: