linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Joe Perches <joe@perches.com>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Petr Mladek <pmladek@suse.cz>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Subject: Re: linux.git: printk() problem
Date: Mon, 24 Oct 2016 23:23:31 +0900	[thread overview]
Message-ID: <20161024142331.GA415@swordfish> (raw)
In-Reply-To: <20161024140845.GA626@swordfish>

> On (10/23/16 12:46), Linus Torvalds wrote:
> > +static void deferred_cont_flush(void)
> > +{
> > +	static DEFINE_TIMER(timer, flush_timer, 0, 0);
> > +
> > +	if (!cont.len)
> >  		return;
> > +	mod_timer(&timer, jiffies + HZ/10);
> >  }
> 
> [..]
> 
> > @@ -2360,6 +2285,8 @@ void console_unlock(void)
> >  		return;
> >  	}
> >  
> > +	deferred_cont_flush();
> > +
> 

[    0.000000] BUG: spinlock bad magic on CPU#0, swapper/0
[    0.000000]  lock: __init_begin+0x1cebc0/0x1da000, .magic: 00000000, .owner: swapper/0, .owner_cpu: 0
[    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 4.9.0-rc1-next-20161024-dbg-dirty #150
[    0.000000]  ffffffff81803c18 ffffffff81221216 ffffffff8180a540 ffffffff81ac7bc0
[    0.000000]  ffffffff81803c38 ffffffff81081414 ffffffff81ac7bc0 0000000000000046
[    0.000000]  ffffffff81803c58 ffffffff81081444 ffffffff81ac7bc0 ffffffff81737e85
[    0.000000] Call Trace:
[    0.000000]  [<ffffffff81221216>] dump_stack+0x4f/0x65
[    0.000000]  [<ffffffff81081414>] spin_dump+0x8a/0x8f
[    0.000000]  [<ffffffff81081444>] spin_bug+0x2b/0x2d
[    0.000000]  [<ffffffff81081604>] do_raw_spin_unlock+0x22/0x81
[    0.000000]  [<ffffffff814b145a>] _raw_spin_unlock_irqrestore+0x2c/0x4e
[    0.000000]  [<ffffffff81097974>] mod_timer+0x266/0x2a0
[    0.000000]  [<ffffffff81084f14>] deferred_cont_flush+0x2a/0x2c
[    0.000000]  [<ffffffff81086092>] console_unlock+0x28/0x45c
[    0.000000]  [<ffffffff8108686c>] ? vprintk_emit+0x3a6/0x3c5
[    0.000000]  [<ffffffff81086875>] vprintk_emit+0x3af/0x3c5
[    0.000000]  [<ffffffff810869f7>] vprintk_default+0x1d/0x1f
[    0.000000]  [<ffffffff810ecb95>] printk+0x48/0x50
[    0.000000]  [<ffffffff810869f7>] ? vprintk_default+0x1d/0x1f
[    0.000000]  [<ffffffff81adb082>] e820_print_map+0x4a/0x70
[    0.000000]  [<ffffffff81000000>] ? 0xffffffff81000000
[    0.000000]  [<ffffffff81adbbc4>] setup_memory_map+0x37/0x3a
[    0.000000]  [<ffffffff81ad9264>] setup_arch+0x16d/0x890
[    0.000000]  [<ffffffff81ad3b9c>] start_kernel+0x59/0x40c
[    0.000000]  [<ffffffff81ad328e>] x86_64_start_reservations+0x2a/0x2c
[    0.000000]  [<ffffffff81ad340a>] x86_64_start_kernel+0x17a/0x18d
[    0.000000]  [<ffffffff810001a5>] start_cpu+0x5/0x14
[    0.000000]  [<ffffffff810001a5>] ? start_cpu+0x5/0x14
[    0.000000] usable

	-ss

  reply	other threads:[~2016-10-24 14:24 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 13:30 linux.git: printk() problem Tetsuo Handa
2016-10-12 14:35 ` Michal Hocko
2016-10-12 16:08   ` Joe Perches
2016-10-13  6:26     ` Michal Hocko
2016-10-13  9:29       ` Joe Perches
2016-10-13 10:04         ` Michal Hocko
2016-10-13 10:20           ` Joe Perches
2016-10-13 11:06             ` Michal Hocko
2016-10-12 15:47 ` Linus Torvalds
2016-10-12 16:16   ` Joe Perches
2016-10-12 16:54     ` Linus Torvalds
2016-10-12 18:50       ` [PATCH] acpi_os_vprintf: Use printk_get_level() to avoid unnecessary KERN_CONT Joe Perches
2016-10-13 21:59         ` Rafael J. Wysocki
2016-10-23  9:22   ` linux.git: printk() problem Geert Uytterhoeven
2016-10-23 18:11     ` Linus Torvalds
2016-10-23 19:06       ` Joe Perches
2016-10-23 19:32         ` Linus Torvalds
2016-10-23 19:46           ` Linus Torvalds
2016-10-24 11:15             ` Geert Uytterhoeven
2016-10-24 14:08             ` Sergey Senozhatsky
2016-10-24 14:23               ` Sergey Senozhatsky [this message]
2016-10-24 17:54               ` Linus Torvalds
2016-10-24 17:55                 ` Linus Torvalds
2016-10-25  1:55                   ` Sergey Senozhatsky
2016-10-25  2:06                     ` Linus Torvalds
2016-10-25  2:22                       ` Linus Torvalds
2016-10-25  4:06                         ` Sergey Senozhatsky
2016-10-25  4:13                           ` Joe Perches
2016-10-25  4:15                           ` Linus Torvalds
2016-10-25  4:44                             ` Sergey Senozhatsky
2016-10-25 14:44                         ` Petr Mladek
2016-11-09 15:47                         ` Petr Mladek
2016-10-25  2:24                     ` Sergey Senozhatsky
2016-10-23 20:33           ` Joe Perches
2016-10-23 21:13             ` Linus Torvalds
2016-10-25 14:42       ` Steven Rostedt

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=20161024142331.GA415@swordfish \
    --to=sergey.senozhatsky@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=pmladek@suse.cz \
    --cc=sergey.senozhatsky.work@gmail.com \
    --cc=torvalds@linux-foundation.org \
    /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;
as well as URLs for NNTP newsgroup(s).