On Tuesday 03 August 2004 01:11, Norbert Preining wrote: > Then I tried lsusb, which hang, here is what sysrq-t says: > lsusb D C0158CDC 0 3942 3849 (NOTLB) > ... > Call Trace: > [<c0158cdc>] link_path_walk+0xa1f/0xd4e > [<c02d3f5f>] __down+0x8b/0x116 > [<c0118cf9>] default_wake_function+0x0/0xc > [<e08e0798>] usbdev_open+0x54/0xfa [usbcore] > [<c02d4144>] __down_failed+0x8/0xc > [<e08e26ba>] .text.lock.devio+0x5/0xff [usbcore] > [<c014ba8b>] filp_open+0x4c/0x4e > [<c014c62d>] vfs_read+0xa9/0xf5 > [<c014c846>] sys_read+0x38/0x59 > [<c0105e4f>] syscall_call+0x7/0xb
Not clear how to read that stack; if it's usbdev_open() that's making the trouble, lock_kernel() is blocked. But that doesn't quite make sense to me. Sorry! - Dave ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
