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(?)
Date: Wed, 15 Mar 2006 00:25:15 +0100 [thread overview]
Message-ID: <20060314232515.GA21782@elte.hu> (raw)
In-Reply-To: <20060314151812.2779ed4b.rdunlap@xenotime.net>
* 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
next prev parent reply other threads:[~2006-03-14 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-14 21:41 soft lockup in serial8250_console_write(?) Randy.Dunlap
2006-03-14 21:40 ` Ingo Molnar
2006-03-14 23:18 ` Randy.Dunlap
2006-03-14 23:25 ` Ingo Molnar [this message]
2006-03-14 23:45 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060314232515.GA21782@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rmk+serial@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox