From: Ingo Molnar <mingo@elte.hu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
Dmitry Torokhov <dtor@insightbb.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.27-git-a447c093244] BUG: spinlock bad magic on CPU#0, setserial/3527
Date: Tue, 14 Oct 2008 08:55:41 +0200 [thread overview]
Message-ID: <20081014065541.GA11047@elte.hu> (raw)
In-Reply-To: <20081013235013.17e3106b@lxorguk.ukuu.org.uk>
* Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Tue, 14 Oct 2008 00:05:39 +0200
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> > Hi,
> >
> > The Linus' tree from today on Asus L5D:
> >
> > BUG: spinlock bad magic on CPU#0, setserial/3527
> > lock: ffffffff80dae020, .magic: 00000000, .owner: <none>/-1, .owner_cpu: 0
> > Pid: 3527, comm: setserial Not tainted 2.6.27-git #57
>
> Yep looking at that at the moment. Its a fallout from dropping the
> NR_IRQ removal changes from the serial tree just before merging I
> think. Was done to make life simpler for Ingo's code push but appears
> to have slightly backfired.
i too have triggered it:
[ 31.099528] BUG: spinlock bad magic on CPU#1, agetty/2608
[ 31.101013] lock: ffffffff8182b020, .magic: 00000000, .owner: agetty/2608, .owner_cpu: 1
[ 31.101013] Pid: 2608, comm: agetty Not tainted 2.6.27-tip-03409-g064a754-dirty #42476
[ 31.101013] Call Trace:
[ 31.101013] [<ffffffff8041ee15>] spin_bug+0xa2/0xaa
[ 31.101013] [<ffffffff8041ee3e>] _raw_spin_unlock+0x21/0x8a
[ 31.101013] [<ffffffff8089aac5>] _spin_unlock_irq+0x2b/0x36
[ 31.101013] [<ffffffff804a9a7b>] serial8250_startup+0x3f2/0x5a3
[ 31.101013] [<ffffffff804a5b00>] uart_startup+0xa0/0x14b
[ 31.101013] [<ffffffff804a6a5a>] uart_open+0x1a8/0x3f7
[ 31.101013] [<ffffffff8089aafb>] ? _spin_unlock+0x2b/0x2f
[ 31.101013] [<ffffffff8047ec6a>] tty_open+0x2db/0x41c
[ 31.101013] [<ffffffff802ac383>] chrdev_open+0x130/0x151
[ 31.101013] [<ffffffff8089aafb>] ? _spin_unlock+0x2b/0x2f
[ 31.101013] [<ffffffff802ac253>] ? chrdev_open+0x0/0x151
[ 31.101013] [<ffffffff802a7e38>] __dentry_open+0x178/0x274
[ 31.101013] [<ffffffff802a7f67>] nameidata_to_filp+0x33/0x44
[ 31.101013] [<ffffffff802b43df>] do_filp_open+0x3be/0x753
[ 31.101013] [<ffffffff802beb11>] ? alloc_fd+0x101/0x110
[ 31.101013] [<ffffffff8027d9c9>] ? trace_hardirqs_off+0x1e/0x20
[ 31.101013] [<ffffffff8089aafb>] ? _spin_unlock+0x2b/0x2f
[ 31.101013] [<ffffffff802beb11>] ? alloc_fd+0x101/0x110
[ 31.101013] [<ffffffff802a7bce>] do_sys_open+0x58/0xdf
[ 31.101013] [<ffffffff802a7c88>] sys_open+0x20/0x22
[ 31.101013] [<ffffffff8020c1cb>] system_call_fastpath+0x16/0x1b
[ 31.405014] eth1: no IPv6 routers present
[ 32.947611] ACPI: PCI Interrupt Link [APC3] enabled at IRQ 18
can test any patch for you if it's not easy to reproduce there.
Ingo
next prev parent reply other threads:[~2008-10-14 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 22:05 [2.6.27-git-a447c093244] BUG: spinlock bad magic on CPU#0, setserial/3527 Rafael J. Wysocki
2008-10-13 22:50 ` Alan Cox
2008-10-14 6:55 ` Ingo Molnar [this message]
2008-10-14 10:22 ` [PATCH] serial: fix serial port lock init Ingo Molnar
2008-10-14 11:40 ` Kamalesh Babulal
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=20081014065541.GA11047@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dtor@insightbb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--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