[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <46939045.5070508@sw.ru>
Date: Tue, 10 Jul 2007 17:57:25 +0400
From: Pavel Emelianov <xemul@...ru>
To: Ashok Raj <ashok.raj@...el.com>, Shaohua Li <shaohua.li@...el.com>,
Anil S Keshavamurthy <anil.s.keshavamurthy@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
CC: Andrew Morton <akpm@...l.org>
Subject: OOPS at dmar_table_init (2.6.22-rc6-mm1 kernel)
Hi.
While working with Andrew's kernel I faced an OOPS on x86_64
machine. Unfortunately kernel logs are not appearing in serial
console by the time oops happens, but I have some info on the
screen:
OOPs is at dmar_table_init() here:
ffffffff80532873 <dmar_table_init>:
ffffffff80532873: 41 55 push %r13
ffffffff80532875: 41 54 push %r12
ffffffff80532877: 55 push %rbp
ffffffff80532878: 53 push %rbx
ffffffff80532879: 51 push %rcx
ffffffff8053287a: 4c 8b 2d 07 21 01 00 mov 73991(%rip),%r13 # ffffffff80544988 <dmar_tbl>
ffffffff80532881: 41 0f b6 45 24 movzbl 0x24(%r13),%eax <<<<<<<<<<< OOPS, %r13 = NULL
ffffffff80532886: 84 c0 test %al,%al
ffffffff80532888: 75 11 jne ffffffff8053289b <dmar_table_init+0x28>
ffffffff8053288a: 48 c7 c7 b0 3d 45 80 mov $0xffffffff80453db0,%rdi
ffffffff80532891: e8 c2 4a cf ff callq ffffffff80227358 <printk>
ffffffff80532896: e9 f2 01 00 00 jmpq ffffffff80532a8d <dmar_table_init+0x21a>
Looks like dmar_tbl is NULL.
BUG is 100% reproducible. Is there any other info that can be useful?
Thanks,
Pavel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists