linux-kernel - Re: latest -git: WARNING: at arch/x86/kernel/ipi.c:123 send_IPI_mask

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <19f34abd0808241045r37eb8661h3cc688b6f0513777@mail.gmail.com>
Date:	Sun, 24 Aug 2008 19:45:48 +0200
From:	"Vegard Nossum" <vegard.nossum@...il.com>
To:	"H. Peter Anvin" <hpa@...nel.org>
Cc:	"Dave Jones" <davej@...hat.com>,
	"Andi Kleen" <andi@...stfloor.org>,
	"the arch/x86 maintainers" <x86@...nel.org>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Rusty Russell" <rusty@...tcorp.com.au>
Subject: Re: latest -git: WARNING: at arch/x86/kernel/ipi.c:123 send_IPI_mask_bitmask+0xc3/0xe0()

On Sun, Aug 24, 2008 at 7:22 PM, Vegard Nossum <vegard.nossum@...il.com> wrote:
>>> Kernel fails to detect cpu1 at all.
> I'm sorry, I _just_ reverted your patch and tested the bare kernel...
> but it still only detects cpu0 :-(
>
> Apart from that, it's also incredibly slow and I get some
> "end_request: I/O error, dev fd0, sector 0" messages. Start-up (init 3
> on a F7) takes closer to 10 minutes. Will now take a closer look at my
> config.
>
> Oh. I _just_ noticed a completely different change -- I added acpi=off
> to my boot line *blush*

Removing acpi=off helps with the CPU detection problem. The kernel is
still really slow, though. From /proc/cpuinfo:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 15
model           : 6
model name      : Intel(R) Pentium(R) 4 CPU 3.00GHz
stepping        : 5
cpu MHz         : 375.000
cache size      : 2048 KB

Why is MHz on 375!? I tried cpufreq-selector, but nothing changed. Maybe

calling  acpi_cpufreq_init+0x0/0x90
initcall acpi_cpufreq_init+0x0/0x90 returned -19 after 0 msecs

There's also this:

SMP: Allowing 2 CPUs, 0 hotplug CPUs

(but CPU hotplug still work, is the line above about something
different, like physical hotplug?)

Apart from that, with your patch applied, hotplug seems to work OK (no
warnings).

Okay, now I used cpufreq-selector to change to "ondemand" governor,
and MHz goes back to 3000. Weird. Why would "performance" governor put
my machine to a constant 375?

Thanks,


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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/