Looking into it a little more now, uart_tasklet_action() in drivers/serial/serial_core.c looks suspicious. Meelis, can you add a BUG_ON(state->info->tty==NULL) in the middle of uart_tasklet_action() and see if it dies on that instead?
Yes, this BUG triggers
At least I'm looking in the right place, even if I don't know what I'm looking for.
Ok, one more thing to try. Still in serial_core.c, let's also add a BUG_ON(info->tty==NULL) in the middle of uart_write_wakeup(). I don't expect this bug to trigger. My current guess is that the tty is closed between scheduling and running the tasklet. How about adding a printk after each time where info->tty is set: near line 1224 in uart_close(), line 1320 in uart_hangup(), and line 1538 in uart_open(). If my guess is right, we will see a uart_close just before the BUG from the tasklet.
Bob
- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
