Re: 8250serial driver causing DEADLOCK, suggestions needed

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Mar 27, 2013 at 07:33:47PM +0530, Ritesh Harjani wrote:
> 
> Hi guys
> 
> I am facing following deadlock on my ARM SMP machine and thought of mailing you
> guys for any valuable suggestions on this.
> 
> [Problem]
> 1. In serial8250_handle_irq function after acquiring a spin_lock, I want to
> print some debug info. This printk will call serial8250_console_write function.
> This function too tries to acquire the same spin_lock and spins on it if
> someone else already acquired it. Assume that this scenario happened on cpu0,
> that means this situation will create a deadlock (as cpu0 will busy spin for
> acquiring a lock which it had already acquired).

Then don't do that :)

Use the tracing infrastructure if you really want to do debug stuff from
within your console irq handler.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux PPP]     [Linux FS]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Linmodem]     [Device Mapper]     [Linux Kernel for ARM]

  Powered by Linux