ppc kernel mailing list?
Where should I send reports about problems compiling/running linux-2.4-bk
rsync'ed from penguinppc.org? linuxppc-dev@lists.linuxppc.org?
I've got a Daystar Digital Genesis MP, with four PPC604 CPUs. I'm
currently running 2.4.3-pre2 from the bk tree. I've had it lock up under
high load (4*distributed.net client running), with crap like
_spin_lock(c0151484) CPU#0 NIP c002c358 holder: cpu 0 pc C002CD30
... c0151484 #1 NIP c002ce1c holder: cpu 0 pc C002CD30
... c014f740 #2 NIP c0080130 holder: cpu 0 pc C0043E8C
... c014f740 #3 NIP c9855800 holder: cpu 0 pc C0043E8C
show up in no apparent order, one every ~10 seconds. sysrq shows that
kupdate is running. (If this isn't a known problem, I wrote down more stuff
about this, and I've got a System.map.
The last couple times I've tried to build a new kernel, booting hung after
the initial text from bootx, before where it usually says "psurge_init" (or
something). It hangs before any mention of psurge. This was with the BK
tree, at version 2.4.3-pre4, and pre-8. (The last BK in the bk-changelog in
that tree was changeset@1.85.1.36, IIRC.)
The kernel I rsync'ed today (most recent change: ChangeSet@1.98) doesn't
compile with the .config I created with make menuconfig. It dies while
linking vmlinux:
arch/ppc/kernel/kernel.o: In function chrp_find_bridges':
arch/ppc/kernel/kernel.o(.text.init+0x754c): undefined reference to
process_bridge_ranges'
arch/ppc/kernel/kernel.o(.text.init+0x754c): relocation truncated to fit:
R_PPC_REL24 process_bridge_ranges
make: *** [vmlinux] Error 1
I'll try again with a different config and see if it'll compile.
--
#define X(x,y) x##y
Peter Cordes ; e-mail: X(peter@llama.nslug. , ns.ca)
"The gods confound the man who first found out how to distinguish the hours!
Confound him, too, who in this place set up a sundial, to cut and hack
my day so wretchedly into small pieces!" -- Plautus, 200 BCE
Reply to: