v3.7 final works just fine as well as 3.7.6, which I am currently running.
v3.8-rc1 doesn't work, nor does anything since (I have checked the last 2 night's daily build)
I noticed sp5100_tco fails to load in 3.7, but does load on 3.8-rc1. I am not sure if it is related in any manner, it just caught my attention.
dmesg from v3.7:
[ 14.431032] sp5100_tco: SP5100 TCO WatchDog Timer Driver v0.01
[ 14.431096] sp5100_tco: mmio address 0xfec000f0 already in use
dmesg from v3.8-rc1:
[ 10.854230] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.03
[ 10.854294] sp5100_tco: PCI Revision ID: 0x3a
[ 10.854341] sp5100_tco: Using 0xfed45000 for watchdog MMIO address
[ 10.854349] sp5100_tco: Last reboot was triggered by watchdog.
[ 10.854388] sp5100_tco: initialized (0xffffc90000678000). heartbeat=60 sec (n
v3.7 final works just fine as well as 3.7.6, which I am currently running.
v3.8-rc1 doesn't work, nor does anything since (I have checked the last 2 night's daily build)
I noticed sp5100_tco fails to load in 3.7, but does load on 3.8-rc1. I am not sure if it is related in any manner, it just caught my attention.
dmesg from v3.7:
[ 14.431032] sp5100_tco: SP5100 TCO WatchDog Timer Driver v0.01
[ 14.431096] sp5100_tco: mmio address 0xfec000f0 already in use
dmesg from v3.8-rc1:
[ 10.854230] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver v0.03 8000). heartbeat=60 sec (n
[ 10.854294] sp5100_tco: PCI Revision ID: 0x3a
[ 10.854341] sp5100_tco: Using 0xfed45000 for watchdog MMIO address
[ 10.854349] sp5100_tco: Last reboot was triggered by watchdog.
[ 10.854388] sp5100_tco: initialized (0xffffc9000067