Another thing that I found during the THP patch testing but that seems to be independent. Rebooting since at least 3.12 (up to yesterdays git with fixes) gives this but it still reboots. 3.10 and 3.11 maybe do not have the problem (at least from sulogin - I can not boot up full system because udev requires devtmpfs now). Maybe this is somehow related to my U5/Blade 100 RED state exceptions on reboot? [....] Deactivating swap...done. [....] Unmounting local filesystems...done. [ 250.124651] EXT4-fs (sda2): re-mounted. Opts: (null) [info] Will now restart. [ 252.547832] sd 1:0:0:0: [sda] Synchronizing SCSI cache [ 252.617964] reboot: Restarting system ********************************************** PSTATE=0000000000000015 TBA=00000000f0000000 DCU Control=0000000000000000 AFSR=0000000000000000 AFAR=0000000002004000 PIL=000000000000000f I-SFSR=0000000000ec10ba D-SFSR=0000000000000000 D-SFAR=00000000f7f4578c TL=0005 TT=0064 TPC=00000000f0004c80 TNPC=00000000f0004c84 TL=0004 TT=0064 TPC=00000000f0004c80 TNPC=00000000f0004c84 TL=0003 TT=0064 TPC=00000000f0004c80 TNPC=00000000f0004c84 TL=0002 TT=0064 TPC=00000000f0000d00 TNPC=00000000f0000d04 TL=0001 TT=0068 TPC=00000000f00092f8 TNPC=00000000f00092fc ********************************************** It is usually the same, only D-SFAR varies slightly between the kernels: ********************************************** PSTATE=0000000000000015 TBA=00000000f0000000 DCU Control=0000000000000000 AFSR=0000000000000000 AFAR=0000000002004000 PIL=000000000000000f I-SFSR=0000000000ec10ba D-SFSR=0000000000000000 D-SFAR=00000000f7fc178c TL=0005 TT=0064 TPC=00000000f0004c80 TNPC=00000000f0004c84 TL=0004 TT=0064 TPC=00000000f0004c80 TNPC=00000000f0004c84 TL=0003 TT=0064 TPC=00000000f0004c80 TNPC=00000000f0004c84 TL=0002 TT=0064 TPC=00000000f0000d00 TNPC=00000000f0000d04 TL=0001 TT=0068 TPC=00000000f00092f8 TNPC=00000000f00092fc ********************************************** -- 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