> > 8025f004 <cleanup_src_unaligned>:
> > 8025f004: 10c00017 beqz a2,8025f064 <done>
> > 8025f008: 30d80003 andi t8,a2,0x3
> > 8025f00c: 13060009 beq t8,a2,8025f034 <copy_bytes>
> > 8025f010: 88a80000 lwl t0,0(a1)
> > The instruction at 8025f00c is the offending instruction, however, the
> Don't you mean 8025f010?
> > epc == 8025f00c, ra == 8011c3c8
> > epc : 8025f00c Not tainted
> > Status: 3000fc03
> > Cause : 90000008
> > I am using the last version of the 2.4.18 Linux/MIPS kernel. It looks
> > like there was a possible fix for this in 'arch/mips/kernel/unaligned.c'
> > by Ralf, but it did not seem to work. Any thoughts on this?
> This looks like the unaligned access in a branch delay slot problem I
> experienced a while ago, where the CPU doesn't set the BD flag if the branch
> not taken. Can you please try the patch I posted?
In this particular case, it would appear that it's not the delay slot problem.
According to the Cause value above, BD is set, and EPC has been rolled
back to point at the branch. That all looks consistent to me.
Note that the lwl will not take an unaligned exception, and the Cause code
value indicates a TLB miss. I don't have the full context of the problem,
but is 0xA (i.e., virtual page zero) actually a valid address? If not,
that's the cause of the problem.
By the way, having the oops message put out the BadVAddr and PRId CP0 registers
would be very helpful.
Michael Uhler, VP, Systems, Architecture, and Software Products
MIPS Technologies, Inc. Email: firstname.lastname@example.org Pager: email@example.com
1225 Charleston Road Voice: (650)567-5025 FAX: (650)567-5225
Mountain View, CA 94043 Mobile: (650)868-6870 Admin: (650)567-5085