From: Rolf Eike Beer <eike-kernel@sf-tec.de>
To: linux-kernel@vger.kernel.org
Cc: len.brown@intel.com, linux-acpi@vger.kernel.org
Subject: [BUG] Oops on boot (probably ACPI related)
Date: Wed, 27 Sep 2006 14:24:47 +0200 [thread overview]
Message-ID: <200609271424.47824.eike-kernel@sf-tec.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1877 bytes --]
I get this on my machine. SMP kernel, linus git from this morning. .config and
test available on request.
Eike
BUG: unable to handle kernel paging request at virtual address f0003504
printing eip:
c102d804
*pde = 00000000
Oops: 0000 [#1]
SMP
Modules linked in:
CPU: 0
EIP: 0060:[<c102d804>] Not tainted VLI
EFLAGS: 00010086 (2.6.18 #3)
EIP is at mark_lock+0x24/0x34c
eax: f00034ec ebx: c126a674 ecx: 00000001 edx: 00000001
esi: c126a140 edi: 00000000 ebp: c1380e88 esp: c1380e78
ds: 007b es: 007b ss: 0068
Process swapper (pid: 0, ti=c1380000 task=c126a140 task.ti=c1380000)
Stack: 00000001 f00034ec 00000018 0000ffff c1380ec4 c102e5ee c11ee67a 00000000
00000000 00000018 c126a140 c126a674 00000000 c126a674 00000000 00000001
00000046 00000018 0000ffff c1380ee4 c102f03a 00000000 00000002 00000001
Call Trace:
[<c102e5ee>] __lock_acquire+0x45e/0x967
[<c102f03a>] lock_acquire+0x4b/0x6d
[<c11f15ef>] _spin_lock_irqsave+0x22/0x32
[<c11ee67a>] __down_trylock+0x12/0x48
[<c11f0e76>] __down_failed_trylock+0xa/0x10
DWARF2 unwinder stuck at __down_failed_trylock+0xa/0x10
Leftover inexact backtrace:
[<c10e9362>] acpi_os_wait_semaphore+0x38/0xd7
[<c10ff1e6>] acpi_ut_acquire_mutex+0x39/0x77
[<c10f768e>] acpi_ns_get_node+0x42/0x84
[<c10f64e1>] acpi_ns_root_initialize+0x276/0x2ad
[<c10fdd23>] acpi_initialize_subsystem+0x38/0x5d
[<c1397f64>] acpi_early_init+0x4e/0x108
[<c1384747>] start_kernel+0x376/0x383
[<00000000>] 0x0
=======================
Code: 8d 65 f8 5b 5e 5d c3 55 89 e5 57 56 53 83 ec 04 89 c6 89 d3 89 cf c7 45
f0 01 00 00 00 d3 65 f0 8b 42 08 ba 01 00 00 00 8b 4d f0 <85> 48 18 0f 85 15
03 00 00 f0 fe 0d 9c f8 26 c1 79 0d f3 90 80
EIP: [<c102d804>] mark_lock+0x24/0x34c SS:ESP 0068:c1380e78
<0>Kernel panic - not syncing: Attempted to kill the idle task!
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-09-27 12:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-27 12:24 Rolf Eike Beer [this message]
2006-09-27 17:56 ` [BUG] Oops on boot (probably ACPI related) 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=200609271424.47824.eike-kernel@sf-tec.de \
--to=eike-kernel@sf-tec.de \
--cc=len.brown@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox