Changes between Initial Version and Version 1 of Ticket #7252
- Timestamp:
- Feb 22, 2011, 5:31:13 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #7252 – Description
initial v1 1 1 Plug an USB adapter supported by either usb_asix, usb_ecm or usb_pegasus, with not wire connected. 2 2 3 The net_server detect it and starts toconfigure it via DHCP.4 Remove it before it fails.3 The net_server detect it and as the device report (wrongly) a link, it starts to auto-configure it via DHCP. 4 Remove the device before DHCP attempts ends. 5 5 6 You willget this KDL:6 I get this KDL: 7 7 8 8 {{{ … … 24 24 9 816b8f38 (+ 64) 81017c86 </boot/system/add-ons/kernel/network/stack> device_removed(net_device*: 0x85b6d9a8) + 0x0036 25 25 10 816b8f78 (+ 96) 81017e0e </boot/system/add-ons/kernel/network/stack> device_reader_thread(void*: 0x8638b968) + 0x010e 26 11 816b8fd8 (+ 32) 800 065d0b <kernel_x86> _create_kernel_thread_kentry() + 0x001526 11 816b8fd8 (+ 32) 80065d0b <kernel_x86> _create_kernel_thread_kentry() + 0x0015 27 27 12 816b8ff8 (+2123657224) 800069578 <kernel_x86> thread_kthread_exit() + 0x0000 28 28 }}} … … 33 33 34 34 One also can wonder why the pegasus device report a link when there is none yet... 35 36 Anyway, device_removed() should not leads to a KDL.