linux-kernel - Re: 2.6.37 says WARNING: at arch/x86/kernel/apic/apic.c:1287 setup_local

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <201101262121.41405.maciej.rutecki@gmail.com>
Date:	Wed, 26 Jan 2011 21:21:41 +0100
From:	Maciej Rutecki <maciej.rutecki@...il.com>
To:	Rob Landley <rlandley@...allels.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: 2.6.37 says WARNING: at arch/x86/kernel/apic/apic.c:1287 setup_local_APIC+0x18f/0x263()

I created a Bugzilla entry at 
https://bugzilla.kernel.org/show_bug.cgi?id=27642
for your bug report, please add your address to the CC list in there, thanks!
On wtorek, 18 stycznia 2011 o 14:11:36 Rob Landley wrote:
> Booting an x86-64 2.6.37 kernel under QEMU with the attached .config and
> this  qemu command line:
> 
>   qemu-system-x86_64 -nographic -no-reboot -kernel "zImage-x86_64" \
>     -hda "image-x86_64.sqf" -append \
>     "root=/dev/hda rw init=/sbin/init.sh panic=1 PATH=/bin:/sbin
> console=ttyS0 HOST=x86_64"
> 
> It said this during boot:
> 
> CPU: AMD QEMU Virtual CPU version 0.13.50 stepping 03
> Setting APIC routing to flat
> ------------[ cut here ]------------
> WARNING: at arch/x86/kernel/apic/apic.c:1287 setup_local_APIC+0x18f/0x263()
> Hardware name: Bochs
> Pid: 1, comm: swapper Not tainted 2.6.37 #1
> Call Trace:
>  [<ffffffff812dc36d>] ? setup_local_APIC+0x18f/0x263
>  [<ffffffff8101c86b>] ? warn_slowpath_common+0x73/0x88
>  [<ffffffff812dc36d>] ? setup_local_APIC+0x18f/0x263
>  [<ffffffff812c6155>] ? APIC_init_uniprocessor+0x99/0x109
>  [<ffffffff812bf886>] ? kernel_init+0x5e/0x122
>  [<ffffffff81002694>] ? kernel_thread_helper+0x4/0x10
>  [<ffffffff812bf828>] ? kernel_init+0x0/0x122
>  [<ffffffff81002690>] ? kernel_thread_helper+0x0/0x10
> ---[ end trace 4eaa2a86a8e2da22 ]---
> ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
> devtmpfs: initialized
> 
> And so on.  Seems to have booted fine, but I thought you'd like to know
> and I couldn't find a mention of this in the January lkml archive...
> 
> Rob

-- 
Maciej Rutecki
http://www.maciek.unixy.pl
--
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/