I hadn’t realized that URL was serial console, I guess I was fooled by the formatting (normally it’s just a .txt file). That particular method of posting the file does not allow me to use copy and paste so it is hard to quote.
One thing I noticed is this (not necessarily an issue, but something to keep in mind): The kernel reports it was built using gcc 5.4.0 20160609. The original kernel is built with gcc 4.8.5. So the kernel was re-built, and sometimes compiler matters (probably not an issue for this, but it could be). More important might be to know what config changes were made.
Right before things diverge and where it still seems normal is when it probes i2c and SATA. After this yours has a huge amount of output which is missing (normally serial console would get this, I’d only expect to see it missing on a regular console). The first thing which fails to show up would be this (this is from my own log):
[ 2.813963] [OV5693]: probing v4l2 sensor.
[ 3.005169] ata1: SATA link down (SStatus 0 SControl 300)
[ 3.597277] <b>gspca_main: v2.14.0 registered</b>
[ 3.597321] <b>usbcore: registered new interface driver gspca_zc3xx</b>
It looks like the missing “gspca_main” is V4L (possibly linked through USB). Everything before this is ok. This is line 790 in my log. The next line where things show up again in my own logs as matching yours is line 1344. You’re missing approximately 475 lines of boot log which starts around V4L/USB. Things start logging correctly again at:
[ 19.552467] Parent Clock set for DC plld2
This line about the clock is startup of the display. The first failure which wouldn’t be an issue if further up in the log does turn out to be an issue when it is here instead…this is what should have occurred:
[ 20.660379] tegradc 15210000.nvdisplay: unblank
…this is what happened (again, this is ok at earlier locations, it doesn’t seem to be ok here…I’m quoting from your earlier post which seemed ok, but which is wrong where it actually occurs again…the time stamp should be around 19 seconds in, not 3.1 seconds):
[ 3.170595] tegradc 15210000.nvdisplay: vrr_setup failed
Although the vrr_setup failed message seems normal at about 2.6 seconds in…the 3.1 seconds in fooled me because you are missing 700+ lines of logging which should have taken about 16 seconds longer to reach.
Because the initial missing logs are from V4L (possibly associated with USB), what kind of changes have you made to add USB devices and video devices (especially USB Video devices)?