Am Sonntag, 6. März 2005 11:20 schrieb Dmitry Nezhevenko:
> kernel: hub 2-0:1.0: port 1, status 0100, change 0003, 12 Mb/s
> kernel: usb 2-1: USB disconnect, address 3
> kernel: usb 2-1: usb_disable_device nuking all URBs
> kernel: ohci_hcd 0000:00:02.1: shutdown urb cf46f0e0 pipe c0410380 ep2in-bulk
> kernel: ohci_hcd 0000:00:02.1: shutdown urb cf46f060 pipe 40448380 ep9in-intr
> kernel: usb 2-1: unregistering interface 2-1:1.0
> kernel: usb 2-1:1.0: hotplug
> pppd[3989]: Modem hangup
> kernel: usb 2-1: unregistering interface 2-1:1.1
> kernel: usb 2-1:1.1: hotplug
> kernel: usb 2-1: unregistering device
> kernel: usb 2-1: hotplug
> pppd[3989]: Script /etc/ppp/ip-down started (pid 4385)
> pppd[3989]: Connection terminated.
> pppd[3989]: Connect time 27.0 minutes.
> pppd[3989]: Sent 6058 bytes, received 7696 bytes.
> kernel: Unable to handle kernel NULL pointer dereference at virtual address
> 00000000
> kernel: printing eip:
> kernel: c0201e8a
> kernel: *pde = 00000000
> kernel: Oops: 0000 [#1]
> kernel: Modules linked in: ppp_async crc_ccitt ppp_generic slhc cdc_acm
> ipt_multiport ipt_state ip_nat_irc ip_nat_ftp ip_conntrack_irc
> ip_conntrack_ftp iptable_mangle iptable_nat ip_conntrack iptable_filter
> ip_tables af_packet snd_intel8x0 snd_ac97_codec snd_pcm snd_page_alloc
> ehci_hcd ohci_hcd usbcore nvidia
> kernel: CPU: 0
> kernel: EIP: 0060:[<c0201e8a>] Tainted: P VLI
> kernel: EFLAGS: 00010246 (2.6.11)
> kernel: EIP is at get_kobj_path_length+0x1a/0x40
> kernel: eax: 00000000 ebx: 00000000 ecx: ffffffff edx: c9a02e98
> kernel: esi: 00000001 edi: 00000000 ebp: ffffffff esp: cbe7cda0
> kernel: ds: 007b es: 007b ss: 0068
> kernel: Process pppd (pid: 3989, threadinfo=cbe7c000 task=c13870a0)
> kernel: Stack: c03dbda0 c9a02e74 cf46f4f8 c9a02e98 c0201f1f c9a02e98 cecbb468
> c02023f0
> kernel: cf5b7c88 c03dbda0 c9a02e74 cf46f4f8 cf46f2ec c02693aa c9a02e98
> 000000d0
> kernel: c03dbda0 cf46f4e0 cf5b7c29 c03dbd88 c0205a77 cf5b7c29 00000000
> 00000000
> kernel: Call Trace:
> kernel: [<c0201f1f>] kobject_get_path+0x1f/0x80
> kernel: [<c02023f0>] kobject_release+0x0/0x10
> kernel: [<c02693aa>] class_hotplug+0x9a/0x1a0
> kernel: [<c0205a77>] vsprintf+0x27/0x30
> kernel: [<c0202c5e>] kobject_hotplug+0x1ce/0x2c0
> kernel: [<c02022cb>] kobject_del+0x1b/0x40
> kernel: [<c02697d0>] class_device_del+0x90/0xc0
> kernel: [<c0269813>] class_device_unregister+0x13/0x30
> kernel: [<d0c974fb>] acm_tty_close+0xcb/0x110 [cdc_acm]
> kernel: [<c0245531>] release_dev+0x6e1/0x700
> kernel: [<c016581e>] destroy_inode+0x4e/0x50
> kernel: [<c0162f4b>] fcntl_setlk+0x11b/0x2d0
> kernel: [<d1040282>] ppp_ccp_closed+0x62/0xd0 [ppp_generic]
> kernel: [<c02c1340>] skb_queue_purge+0x10/0x40
> kernel: [<c015f0d8>] do_ioctl+0x58/0x80
> kernel: [<c02459ef>] tty_release+0xf/0x20
> kernel: [<c014efda>] __fput+0xea/0x100
> kernel: [<c014d809>] filp_close+0x59/0x90
> kernel: [<c014d890>] sys_close+0x50/0x60
> kernel: [<c0103003>] syscall_call+0x7/0xb
> kernel: Code: 74 e4 89 34 24 e8 97 0b f8 ff eb da 90 8d 74 26 00 55 bd ff ff
> ff ff 57 56 be 01 00 00 00 53 31 db 8b 54 24 14 8b 3a 89 e9 89 d8 <f2> ae f7
> d1 49 8b 52 24 8d 74 31 01 85 d2 75 ea 5b 89 f0 5e 5f
> kernel: <7>hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status
> 0x100
> Mar 6 12:10:23 deb kernel: ohci_hcd 0000:00:02.1: suspend root hub
> =========
>
> Sorry for so long mail. Is it bug?
Yes, it is a bug. It seems to happen when you shutdown the connection,
rather than during disconnect handling. This is a previously unknown
behavior. However it seems related to kobjects rather than acm.
Regards
Oliver
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
