(In reply to Zhang Rui from comment #22)
> (In reply to Manuel Krause from comment #16)
> > There are generally only two different re-occurring scenarios for
> > "grep . /sys/class/thermal/thermal_zone*/cdev*/device/path", so that I 
> > want to abbreviate them in the following:
> > 
> > Scenario-1:
> > # grep . /sys/class/thermal/thermal_zone*/cdev*/device/path
> > /sys/class/thermal/thermal_zone1/cdev0/device/path:\_PR_.CPU1
> > /sys/class/thermal/thermal_zone1/cdev1/device/path:\_PR_.CPU0
> > /sys/class/thermal/thermal_zone1/cdev2/device/path:\_TZ_.FAN0
> > /sys/class/thermal/thermal_zone1/cdev3/device/path:\_TZ_.FAN1
> > /sys/class/thermal/thermal_zone1/cdev4/device/path:\_TZ_.FAN2
> > /sys/class/thermal/thermal_zone1/cdev5/device/path:\_TZ_.FAN3
> > /sys/class/thermal/thermal_zone1/cdev6/device/path:\_TZ_.FAN4
> > /sys/class/thermal/thermal_zone2/cdev0/device/path:\_PR_.CPU1
> > /sys/class/thermal/thermal_zone2/cdev1/device/path:\_PR_.CPU0
> > /sys/class/thermal/thermal_zone3/cdev0/device/path:\_PR_.CPU1
> > /sys/class/thermal/thermal_zone3/cdev1/device/path:\_PR_.CPU0
> > 
> > Scenario-2:
> > # grep . /sys/class/thermal/thermal_zone*/cdev*/device/path
> > /sys/class/thermal/thermal_zone1/cdev0/device/path:\_TZ_.FAN4
> > /sys/class/thermal/thermal_zone1/cdev1/device/path:\_TZ_.FAN3
> > /sys/class/thermal/thermal_zone1/cdev2/device/path:\_TZ_.FAN2
> > /sys/class/thermal/thermal_zone1/cdev3/device/path:\_TZ_.FAN1
> > /sys/class/thermal/thermal_zone1/cdev4/device/path:\_TZ_.FAN0
> > /sys/class/thermal/thermal_zone1/cdev5/device/path:\_PR_.CPU1
> > /sys/class/thermal/thermal_zone1/cdev6/device/path:\_PR_.CPU0
> > /sys/class/thermal/thermal_zone2/cdev0/device/path:\_PR_.CPU1
> > /sys/class/thermal/thermal_zone2/cdev1/device/path:\_PR_.CPU0
> > /sys/class/thermal/thermal_zone3/cdev0/device/path:\_PR_.CPU1
> > /sys/class/thermal/thermal_zone3/cdev1/device/path:\_PR_.CPU0
> > 
> > Already, during bisecting this issue, I've found out, that these scenarios
> > have something to do with rebooting: So, I've rebooted the new bisected
> > kernel
> > twice in the second roundup.
> > But I haven't expected the following disorder:
> > 
> > This is a row of results from last night, rebooting different kernels, one
> > after the other, and capturing some relevant data.
> > 
> > 
> > # uname -r
> > 3.12.16
> > # grep . /sys/class/thermal/thermal_zone*/cdev*/device/path
> > Scenario-2
> > 
> > # uname -r
> > 3.13.8
> > # grep . /sys/class/thermal/thermal_zone*/cdev*/device/path
> > Scenario-2
> > 
> > # uname -r
> > 3.13.8
> > # grep . /sys/class/thermal/thermal_zone*/cdev*/device/path
> > Scenario-1
> > 
> > # uname -r
> > 3.12.13
> > # grep . /sys/class/thermal/thermal_zone*/cdev*/device/path
> > Scenario-2
> > 
> > # uname -r
> > 3.12.13
> > # grep . /sys/class/thermal/thermal_zone*/cdev*/device/path
> > Scenario-1
> > 
> > # uname -r
> > 3.12.13
> > # grep . /sys/class/thermal/thermal_zone*/cdev*/device/path
> > Scenario-2
> > 
> I suppose these 3.12.13 kernel are the exactly the same kernel without any
> rebuilding, right?

Yes, of course, without rebuilding. Only re-/booting previously built kernels, to show you the obvious differences after rebooting.

> could you please change your config file and always build in the ACPI
> thermal and fan driver and see if this problem still exists?

I've done so for a 3.12.13 kernel and a 3.13.11.

We'd get a new Scenario-3:
# grep . /sys/class/thermal/thermal_zone*/cdev*/device/path
/sys/class/thermal/thermal_zone1/cdev0/device/path:\_PR_.CPU1
/sys/class/thermal/thermal_zone1/cdev1/device/path:\_PR_.CPU0
/sys/class/thermal/thermal_zone1/cdev2/device/path:\_TZ_.FAN4
/sys/class/thermal/thermal_zone1/cdev3/device/path:\_TZ_.FAN3
/sys/class/thermal/thermal_zone1/cdev4/device/path:\_TZ_.FAN2
/sys/class/thermal/thermal_zone1/cdev5/device/path:\_TZ_.FAN1
/sys/class/thermal/thermal_zone1/cdev6/device/path:\_TZ_.FAN0
/sys/class/thermal/thermal_zone2/cdev0/device/path:\_PR_.CPU1
/sys/class/thermal/thermal_zone2/cdev1/device/path:\_PR_.CPU0
/sys/class/thermal/thermal_zone3/cdev0/device/path:\_PR_.CPU1
/sys/class/thermal/thermal_zone3/cdev1/device/path:\_PR_.CPU0

As new comparison:
fan, thermal, processor as MODULES; sequentially rebooted same kernel:
3.12.17 - 1. boot: Scenario-1
3.12.17 - 2. boot: Scenario-1
3.12.17 - 3. boot: Scenario-2
3.12.17 - 4. boot: Scenario-2
3.12.17 - 5. boot: Scenario-2
3.12.17 - 6. boot: Scenario-1

fan, thermal, processor as BUILT IN:
3.12.13 - 6 sequential reboots: all Scenario-3

fan, thermal, processor as BUILT IN:
3.13.11 - 6 sequential reboots: all Scenario-3

After that config change 3.12 still works fine / 3.13 still FAILS:

In my opinion, this has nothing to do with the original fan / trip point problem. But fine, if you can fix this little bug, too, in addition. ;-)

Best regards, Manuel Krause