Port-sparc64 archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: port/sparc64 known working on Netra X1?




On May 8, 2010, at 15:03, Chris Ross wrote:
I'm about to trace into psycho_set_intr() to see if I can learn anything else, but does this indicate to anyone why this would be failing now (after 4.99.72, in netbsd 5.1_RC1 and 5.99.29), or any other suggestions to try.

Okay. So, in looking at the diffs from netbsd-4 to netbsd-5 sparc64/dev/psycho.c, I see that the API to intr_establish changed. But, I was surprised to find that intr_establish() (within psycho_set_intr()) returns successfully on this last call that never returns.

The *last* line of psycho_set_intr() does not complete. What could/ would make this hang?

        *(ih->ih_map) |= INTMAP_V|(CPU_UPAID << INTMAP_TID_SHIFT);

I littered printf()'s through psycho_set_intr(), and the set of calls from psycho_attach() yield ('**' in psycho_attach, '@@' in psycho_set_intr()):

** osc == 0x0
** installing intr for psycho_ue
@@ malloc'ing 72 bytes
@@ got 0x2789480
@@ calling intr_establish()
@@ back from intr_establish(), ih_map is 0xe0023070
@@ returning from psycho_set_intr
** done; installing intr for psycho_cw
@@ malloc'ing 72 bytes
@@ got 0x2789400
@@ calling intr_establish()
@@ back from intr_establish(), ih_map is 0xe0023078
@@ returning from psycho_set_intr
** done; installing intr for psycho_bus_a
@@ malloc'ing 72 bytes
@@ got 0x2789380
@@ calling intr_establish()
@@ back from intr_establish(), ih_map is 0xe0023080
@@ returning from psycho_set_intr
** done; installing intr for psycho_powerfail
@@ malloc'ing 72 bytes
@@ got 0x2789300
@@ calling intr_establish()
@@ back from intr_establish(), ih_map is 0xe0023028


At which point it hangs. The last '@@' printf is after the call to intr_establish in psycho_set_intr, and the "returning from" printf that never fires on that last pass is after the line of code pasted above, and immediately before the close brace (and return).

I think I'm out of ideas, right here. Anyone else have any notion what's gotten messed up?

                                         - Chris



Home | Main Index | Thread Index | Old Index