Skip to contentSkip to conversation

Dying of First sti()

DISCUSSION Kent Borg 1 participant 2 messages Oct 22, 2001 – Oct 25, 2001

lore
Share & tools
lore

Kent Borg

author
#0 lore raw

I have been trying to move work from an old Linux PPC kernel to a current (rsync-ed from source.mvista.com::linuxppc_2_4_devel) kernel tree. I have a 405GP on a custom board.

In this effort I am getting some output on the serial port, I make it in init/main.c to the point where sti() is about to be called. But I never get back from the sti() call.

Early in the boot I turned off all interrupt sources. Using RISC Watch I can (laboriously) trace through timer_interrupt(), and I am not caught in an infinite loop in there, it does return.

I am thinking our limited boot ROM isn't setting up everything the kernel expects.

Ideas?

Thanks,

-kb

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

author
#1 lore raw
Quoted 2 lines · Kent Borg

I make it in init/main.c to the point where sti() is about to be called. But I never get back from the sti() call.

I found my problem. We had put the wrong value in bi_intfreq (and bi_busfreq). We were off by a mere factor of a million. It meant that the PIT was rolling over nearly instantly. Oops. Works *much* better with a sensible value in there.

-kb

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/