RE: x86/non-x86: percpu, node ids, apic ids x86.git fixup
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: "Ingo Molnar" <mingo@xxxxxxx>
- Subject: RE: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- From: "Luck, Tony" <tony.luck@xxxxxxxxx>
- Date: Tue, 5 Feb 2008 11:05:03 -0800
- Cc: "Mike Travis" <travis@xxxxxxx>, "Geert Uytterhoeven" <Geert.Uytterhoeven@xxxxxxxxxxx>, "Linus Torvalds" <torvalds@xxxxxxxxxxxxxxxxxxxx>, "Thomas Gleixner" <tglx@xxxxxxxxxxxxx>, "Linux Kernel Development" <linux-kernel@xxxxxxxxxxxxxxx>, "Linux/PPC Development" <linuxppc-dev@xxxxxxxxxx>, <linux-ia64@xxxxxxxxxxxxxxx>, <sparclinux@xxxxxxxxxxxxxxx>
- In-reply-to: <1FE6DD409037234FAB833C420AA843EC78C75A@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- List-id: <linux-ia64.vger.kernel.org>
- References: <20080130180623.GA24881@xxxxxxx> <1FE6DD409037234FAB833C420AA843EC757DEA@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <47A0CD4B.5040706@xxxxxxx> <1FE6DD409037234FAB833C420AA843EC757F12@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080130194616.GA19426@xxxxxxx> <1FE6DD409037234FAB833C420AA843EC757F7C@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080130200221.GA28073@xxxxxxx> <1FE6DD409037234FAB833C420AA843EC757FC2@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080130205915.GA4562@xxxxxxx> <1FE6DD409037234FAB833C420AA843EC78C219@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20080131090642.GA5688@xxxxxxx> <1FE6DD409037234FAB833C420AA843EC78C75A@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Thread-index: Achj6MJxBSJCZx/gQf+KkNIfkM+UVgATq2qQAPx+iIA=
- Thread-topic: x86/non-x86: percpu, node ids, apic ids x86.git fixup
> Applied that patch and UP kernel built ok, and then crashed in the
> same place with the memset() to a user-looking address from kmem_cache_alloc()
>
> So the percpu changes are innocent ... something else since 2.6.24 is
> to blame. Only 5749 commits :-) I'll start bisecting.
The bisection narrowed in on an innocent patch in ipv4 space. Meanwhile
the rush of patches continues. When I retested yesterday when Linus
HEAD was 8af03e782... the CONFIG_SMP=n kernel worked perfectly. So
maybe it was fixed? Or maybe the bug depends on the relative
location of various bits of code/data and as the kernel grows and
shrinks with incoming changes the problem comes and goes :-(
-Tony
-
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
- References:
- Re: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- RE: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- Re: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- RE: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- Re: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- RE: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- Re: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- RE: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- Re: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- RE: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- Re: x86/non-x86: percpu, node ids, apic ids x86.git fixup
- RE: x86/non-x86: percpu, node ids, apic ids x86.git fixup
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]