Bisected: RED State Exception in 4.5 on E420R

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

 



> Just got power & cooling back to my computer lab (and I'm back to 
> reporting bugs). I have a bqacklog of things to test but on E420R I got 
> a halt during early bootup:

> [    0.000000] Kernel: Using 5 locked TLB entries for main kernel image.
> [    0.000000] Remapping the kernel... done.
> 
> RED State Exception

Bisected:

commit 1a40b95374f680625318ab61d81958e949e0afe3
Author: Mike Frysinger <vapier@xxxxxxxxxx>
Date:   Mon Jan 18 06:32:30 2016 -0500

    sparc: Fix system call tracing register handling.
    
    A system call trace trigger on entry allows the tracing
    process to inspect and potentially change the traced
    process's registers.
    
    Account for that by reloading the %g1 (syscall number)
    and %i0-%i5 (syscall argument) values.  We need to be
    careful to revalidate the range of %g1, and reload the
    system call table entry it corresponds to into %l7.
    
    Reported-by: Mike Frysinger <vapier@xxxxxxxxxx>
    Signed-off-by: David S. Miller <davem@xxxxxxxxxxxxx>
    Tested-by: Mike Frysinger <vapier@xxxxxxxxxx>

:040000 040000 3fa8c484537ffff82dd469dba7a0f2b770cf8505 5a9834a3f5ed8bae7f788bdeb9bee15279618b5c M      arch

Actually this commit juts makes the system hang here, not RED state 
exception. a couple of last bisect targets were like that so if needed, 
I can also bisect where the hang transformed into RED State Exception.

-- 
Meelis Roos (mroos@xxxxxxxx)
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Development]     [DCCP]     [Linux ARM Development]     [Linux]     [Photo]     [Yosemite Help]     [Linux ARM Kernel]     [Linux SCSI]     [Linux x86_64]     [Linux Hams]

  Powered by Linux