From: Diego Calleja <diegocg@gmail.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.25-$SHA1: WARNING: at arch/x86/kernel/genapic_64.c:86 read_apic_id+0x78/0x80()
Date: Sat, 19 Apr 2008 23:25:43 +0200 [thread overview]
Message-ID: <20080419232543.6f0dc3ab.diegocg@gmail.com> (raw)
In-Reply-To: <20080418223945.GA4801@martell.zuzino.mipt.ru>
El Sat, 19 Apr 2008 02:39:45 +0400, Alexey Dobriyan <adobriyan@gmail.com> escribió:
> ------------[ cut here ]------------
> WARNING: at arch/x86/kernel/genapic_64.c:86 read_apic_id+0x78/0x80()
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.25-2cca775baecbfede2fec20c99add709232311fe7 #3
>
> Call Trace:
> [<ffffffff8023150f>] warn_on_slowpath+0x5f/0x80
> [<ffffffff80299e9e>] ? open_namei+0x4e/0x6b0
> [<ffffffff804594e5>] ? _spin_unlock_irqrestore+0x65/0x80
> [<ffffffff80254105>] ? trace_hardirqs_on+0xd5/0x160
> [<ffffffff804594c2>] ? _spin_unlock_irqrestore+0x42/0x80
> [<ffffffff8021ed28>] read_apic_id+0x78/0x80
> [<ffffffff805e7332>] verify_local_APIC+0xb2/0x1a0
> [<ffffffff805e6193>] native_smp_prepare_cpus+0x1a3/0x390
> [<ffffffff805e0713>] kernel_init+0x53/0x340
> [<ffffffff80459536>] ? _spin_unlock_irq+0x36/0x60
> [<ffffffff80458a92>] ? trace_hardirqs_on_thunk+0x35/0x3a
> [<ffffffff80254105>] ? trace_hardirqs_on+0xd5/0x160
> [<ffffffff8020c4b8>] child_rip+0xa/0x12
> [<ffffffff8020bba3>] ? restore_args+0x0/0x30
> [<ffffffff805e06c0>] ? kernel_init+0x0/0x340
> [<ffffffff8020c4ae>] ? child_rip+0x0/0x12
I'm getting exactly the same backtrace (it's also a Intel Core 2 machine)
next prev parent reply other threads:[~2008-04-19 21:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 22:39 Alexey Dobriyan
2008-04-19 21:25 ` Diego Calleja [this message]
2008-04-19 21:34 ` Dan Noe
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=20080419232543.6f0dc3ab.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=adobriyan@gmail.com \
--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
all inboxes | Powered by JetHome®