Date: Wed, 15 Mar 2006 00:25:15 +0100
From: Ingo Molnar <mingo@elte.hu>
To: "Randy.Dunlap" <rdunlap@xenotime.net>
Cc: rmk+serial@arm.linux.org.uk, linux-kernel@vger.kernel.org,
       Andrew Morton <akpm@osdl.org>
Subject: Re: soft lockup in serial8250_console_write(?)
Message-ID: <20060314232515.GA21782@elte.hu>
References: <20060314134110.3470fc63.rdunlap@xenotime.net> <20060314214049.GA29536@elte.hu> <20060314151812.2779ed4b.rdunlap@xenotime.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060314151812.2779ed4b.rdunlap@xenotime.net>
User-Agent: Mutt/1.4.2.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 763
Lines: 23


* Randy.Dunlap <rdunlap@xenotime.net> wrote:

> > > This function calls wait_for_xmitr() [inline], which in worst case can 
> > > spin for 1.010 seconds.  Could this be the cause of a soft lockup?
> > 
> > hm, it shouldnt cause that. Could you try the attached patch [which is 
> > the next-gen softlockup detector], do you get the message even with that 
> > one applied?
> 
> 5/5 good boots with your new patch.
> 5/5 soft lockups without it.
> 
> Is this scheduled for post-2.6.16 ?

yes, in theory. Andrew?

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/