From: Markus Dahms <mad@automagically.de>
To: linux-acpi@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] Oops on boot (probably ACPI related)
Date: Wed, 27 Sep 2006 19:56:13 +0200 [thread overview]
Message-ID: <pan.2006.09.27.17.56.13.80913@automagically.de> (raw)
In-Reply-To: 200609271424.47824.eike-kernel@sf-tec.de
Am Wed, 27 Sep 2006 14:24:47 +0200 schrieb Rolf Eike Beer:
> I get this on my machine. SMP kernel, linus git from this morning. .config
> and test available on request.
I encountered a similar bug, but a lot earlier. It seems to be a locking
problem, as it is lockdep which does the BUG() for me.
It's also an SMP machine in my case, acpi_os_wait_semaphore() is in the
call chain, too. No textual output (no serial connection attached, too
early for netconsole), but a screenshot:
http://automagically.de/images/linux-2.6.18+-acpi-lockup.jpg (154kB)
2.6.18 works for me, newer git versions explode.
Maybe it's an SMP-related problem, but it does BUG() before initialization
of the second CPU.
Markus
WARNING: multiple messages have this Message-ID (diff)
From: Markus Dahms <mad@automagically.de>
To: linux-kernel@vger.kernel.org
Cc: linux-acpi@vger.kernel.org
Subject: Re: [BUG] Oops on boot (probably ACPI related)
Date: Wed, 27 Sep 2006 19:56:13 +0200 [thread overview]
Message-ID: <pan.2006.09.27.17.56.13.80913@automagically.de> (raw)
In-Reply-To: 200609271424.47824.eike-kernel@sf-tec.de
Am Wed, 27 Sep 2006 14:24:47 +0200 schrieb Rolf Eike Beer:
> I get this on my machine. SMP kernel, linus git from this morning. .config
> and test available on request.
I encountered a similar bug, but a lot earlier. It seems to be a locking
problem, as it is lockdep which does the BUG() for me.
It's also an SMP machine in my case, acpi_os_wait_semaphore() is in the
call chain, too. No textual output (no serial connection attached, too
early for netconsole), but a screenshot:
http://automagically.de/images/linux-2.6.18+-acpi-lockup.jpg (154kB)
2.6.18 works for me, newer git versions explode.
Maybe it's an SMP-related problem, but it does BUG() before initialization
of the second CPU.
Markus
next prev parent reply other threads:[~2006-09-27 18:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 12:24 [BUG] Oops on boot (probably ACPI related) Rolf Eike Beer
2006-09-27 17:56 ` Markus Dahms [this message]
2006-09-27 17:56 ` Markus Dahms
2006-09-27 18:40 ` Kyle McMartin
2006-09-27 19:38 ` Andi Kleen
2006-09-27 20:21 ` Linus Torvalds
2006-09-27 20:35 ` Linus Torvalds
2006-09-27 20:50 ` Andi Kleen
2006-09-27 21:38 ` Linus Torvalds
2006-09-28 7:49 ` Andi Kleen
2006-09-27 20:58 ` Kyle McMartin
2006-09-27 22:32 ` Andrew Morton
2006-09-27 19:38 ` Andi Kleen
2006-09-28 7:04 ` Rolf Eike Beer
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=pan.2006.09.27.17.56.13.80913@automagically.de \
--to=mad@automagically.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.