stephane duverger wrote: > Greg KH <greg@xxxxxxxxx> wrote: > > > Could you port it to 2.6.35-rc3 and resend it with a signed-off-by > > line so that we can apply it to the tree if it all works out properly? > > Here is the patch for 2.6.35-rc3. > > The most recent kernel i've been able to test on my board is > 2.6.35-rc1. > > I noticed the following warning in the kernel logs: > > [ 338.090820] ------------[ cut here ]------------ > [ 338.095489] WARNING: at kernel/mutex.c:214 __mutex_lock_slowpath+0x64/0x218() > [ 338.102661] Modules linked in: g_dbgp [last unloaded: g_dbgp] > [ 338.108520] [<c0038268>] (unwind_backtrace+0x0/0xec) from [<c0057558>] (warn_slowpath_common+0x4c/0x7c) > [ 338.117980] [<c0057558>] (warn_slowpath_common+0x4c/0x7c) from [<c00575a4>] (warn_slowpath_null+0x1c/0x24) > [ 338.127716] [<c00575a4>] (warn_slowpath_null+0x1c/0x24) from [<c03b537c>] (__mutex_lock_slowpath+0x64/0x218) > [ 338.137603] [<c03b537c>] (__mutex_lock_slowpath+0x64/0x218) from [<c03b553c>] (mutex_lock+0xc/0x1c) > [ 338.146759] [<c03b553c>] (mutex_lock+0xc/0x1c) from [<c020eb14>] (echo_set_canon_col+0x18/0x40) > [ 338.155517] [<c020eb14>] (echo_set_canon_col+0x18/0x40) from [<c0210e3c>] (n_tty_receive_buf+0xbb8/0x1058) > [ 338.165222] [<c0210e3c>] (n_tty_receive_buf+0xbb8/0x1058) from [<c0213458>] (flush_to_ldisc+0xd4/0x170) > [ 338.174743] [<c0213458>] (flush_to_ldisc+0xd4/0x170) from [<bf0073d8>] (gs_rx_push+0x118/0x1c4 [g_dbgp]) > [ 338.184326] [<bf0073d8>] (gs_rx_push+0x118/0x1c4 [g_dbgp]) from [<c005bd80>] (tasklet_action+0x74/0xb8) > [ 338.193817] [<c005bd80>] (tasklet_action+0x74/0xb8) from [<c005c3cc>] (__do_softirq+0x78/0x100) > [ 338.202606] [<c005c3cc>] (__do_softirq+0x78/0x100) from [<c005c494>] (irq_exit+0x40/0x94) > [ 338.210876] [<c005c494>] (irq_exit+0x40/0x94) from [<c0033078>] (asm_do_IRQ+0x78/0x98) > [ 338.218872] [<c0033078>] (asm_do_IRQ+0x78/0x98) from [<c0033ab4>] (__irq_svc+0x34/0x80) > [ 338.226928] Exception stack(0xc04f7f30 to 0xc04f7f78) > [ 338.232025] 7f20: 15e2d62c 40000013 40000013 c0506c88 > [ 338.240264] 7f40: 15e2d62c 00000152 c0506c88 0000132f 00001324 c0505ff8 c0555ea0 c0555fe0 > [ 338.248535] 7f60: c04fbfe8 c04f7f78 c003da48 c0076550 60000013 ffffffff > [ 338.255218] [<c0033ab4>] (__irq_svc+0x34/0x80) from [<c0076550>] (tick_nohz_stop_sched_tick+0x384/0x3d0) > [ 338.264801] [<c0076550>] (tick_nohz_stop_sched_tick+0x384/0x3d0) from [<c0034e4c>] (cpu_idle+0x20/0x84) > [ 338.274291] [<c0034e4c>] (cpu_idle+0x20/0x84) from [<c0008b0c>] (start_kernel+0x254/0x2b8) > [ 338.282623] [<c0008b0c>] (start_kernel+0x254/0x2b8) from [<80008034>] (0x80008034) > [ 338.290252] ---[ end trace c425a969cdc97fc2 ]--- > > My module does not make use of any mutex. It happens only once (first > time g_dbgp module is used). It seems to be related with gserial_xxxx() > code which is called by my module when it receives the DEBUG feature. I > don't have time and skills to look into gserial code. > This patch should probably fix this warning you see: <http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/usb.current/usb-g_serial-don-t-set-low_latency-flag.patch> - Anand -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html