works for me

works for me and is in prouction on most machines except the 5 core-servers which will follow tomorrow

Works for me on multiple machines

karma: +1

Relevant output from my E531:

[ 2418.216600] PM: Syncing filesystems ... done.
[ 2418.711550] PM: Preparing system for sleep (mem)
[ 2418.712437] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 2418.715259] OOM killer disabled.
[ 2418.715261] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2418.716757] PM: Suspending system (mem)
[ 2418.716790] Suspending console(s) (use no_console_suspend to debug)
[ 2418.742342] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[ 2418.742345] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[ 2418.742347] rmi4_physical rmi4-00: Failed to suspend functions: -6
[ 2418.742350] rmi4_smbus 8-002c: Failed to suspend device: -6
[ 2418.742358] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
[ 2418.742360] PM: Device 8-002c failed to suspend: error -6
[ 2418.742363] PM: Some devices failed to suspend, or early wake event detected
[ 2418.748592] PM: resume of devices complete after 6.223 msecs
[ 2418.748916] PM: resume devices took 0.006 seconds
[ 2418.748983] PM: Finishing wakeup.
[ 2418.748984] OOM killer enabled.
[ 2418.748987] Restarting tasks ... done.
[ 2418.751321] PM: Syncing filesystems ... 
[ 2418.764380] rmi4_f03 rmi4-00.fn03: rmi_f03_pt_write: Failed to write to F03 TX register (-6).
[ 2418.948815] done.
[ 2418.948826] PM: Preparing system for sleep (freeze)
[ 2418.949090] Freezing user space processes ... (elapsed 0.002 seconds) done.
[ 2418.951905] OOM killer disabled.
[ 2418.951907] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 2418.953392] PM: Suspending system (freeze)
[ 2418.953394] Suspending console(s) (use no_console_suspend to debug)
[ 2418.978304] rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -6.
[ 2418.978307] rmi4_f01 rmi4-00.fn01: Suspend failed with code -6.
[ 2418.978310] rmi4_physical rmi4-00: Failed to suspend functions: -6
[ 2418.978312] rmi4_smbus 8-002c: Failed to suspend device: -6
[ 2418.978321] dpm_run_callback(): rmi_smb_suspend+0x0/0x50 [rmi_smbus] returns -6
[ 2418.978323] PM: Device 8-002c failed to suspend: error -6
[ 2418.978325] PM: Some devices failed to suspend, or early wake event detected
[ 2418.984840] PM: resume of devices complete after 6.509 msecs
[ 2418.985195] PM: resume devices took 0.007 seconds
[ 2418.985241] PM: Finishing wakeup.
[ 2418.985242] OOM killer enabled.
[ 2418.985244] Restarting tasks ... done.

Suspend issue filed as #1480602.

Also, I'm seeing issues similar to #1462381 in a virtualized environment, but less severe. I can boot, but then QXL starts hitting other errors. Not -1 on its own, but a bug.

Works, x86_64, GNOME (CPU: Core2 Quad Q8400, RAM: 8 GiB, GPU: RV635).

• Works on Dell Latitude 3350.

• Passed kernel regression tests.

Seems to work, and passed kernel regression test twice (twice kernel regression test suite froze)

I'm using kernel-4.12.3-1 without any problem and I'm going update to 4.12.6 from koji

Sergio, do you mean 4.12.5 or really 4.12.3?

4.12.3 from https://copr.fedorainfracloud.org/coprs/jforbes/kernel-stabilization/builds/

@sergiomb WHY the fuck do you comment 4.12.5 with some random expirience of a random 4.12.3 build? do the world and yourself a favor and type "dnf install fedora-easy-karma"

@hreindl Maybe that kind of language doesn't help.

@Sergio, I am sure you are aware that it doesn't help to provide feedback and karma on a kernel that you neither installed nor tested. That defeats the purpose of feedback and manipulates the stabilization process. I am sure the community would appreciate your understanding.

I'm providing karma for kernel 4.12 in general , now I'm using 4.12.6-200.fc25.x86_64 and is also ok . This bodhi have autopush disable, so I'm just giving my ok , to change from kernel 4.11 to kernel 4.12 in F25 , I hope not offence anybody.

YOU MUST NOT "providing karma for kernel 4.12 in general" - the karma is for EXACTLY A SPECIFIC BUILD and nothing else and in doubt what you are doing is not helful but harmful if you provide positive karma for a kernel build you never tested, has a terrible regression which eats users data and there are too much people like you leading make it into stable updates

the same for negative karma when a bug or regression affecting you is already fixed and because of your and others doing it that wrong karma it don't make it to stable

and since 4.11 is EOL, 4.12.7 already released and 4.12.6 as well as 4.12.7 are fixing security relevants chnage from 4.11 to 4.12 is happening anyways