Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1253690

Re: [PATCH] x86/spinlocks: Avoid a deadlock when someone unlock a zapped ticked spinlock

Show all headers | View raw

On Thu, Oct 22, 2015 at 11:39:38AM +0200, Petr Mladek wrote:
> Maybe, we could add support to use early console in case of Oops and
> panic. But we should not do this by default. It would help, especially
> when the problem is reproducible and we get stacked with the normal
> console.

What I typically do is route everything to 8250 early console and rip
out everything printk buffer nonsense.

That gets you a fairly reliable console, no locking, only vscnprintf()
and OUTB banging.

No printk() wanting to do wakeups and other such nonsense that doesn't
work.

I appreciate that might not be for everybody, but it also shouldn't be
this hard to get something reliable.
--
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/

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[PATCH] x86/spinlocks: Avoid a deadlock when someone unlock a zapped ticked spinlock Petr Mladek <pmladek@suse.com> - 2015-10-21 11:20 +0200
  Re: [PATCH] x86/spinlocks: Avoid a deadlock when someone unlock a  zapped ticked spinlock Peter Zijlstra <peterz@infradead.org> - 2015-10-21 13:20 +0200
    Re: [PATCH] x86/spinlocks: Avoid a deadlock when someone unlock a  zapped ticked spinlock Petr Mladek <pmladek@suse.com> - 2015-10-22 11:40 +0200
      Re: [PATCH] x86/spinlocks: Avoid a deadlock when someone unlock a  zapped ticked spinlock Peter Zijlstra <peterz@infradead.org> - 2015-10-22 12:20 +0200

csiph-web