Nothing strikes me as odd with the requested output. The usb-related output was to do with looking for anything that might be enabled to generate wakeup events. With the grub output. I was looking for ACPI-related parameters. However, your log definitely reports unusual behaviour with
2014-11-17T18:36:35.660751+00:00 Orion-14 kernel: 1289.869829] Broke affinity for irq 16
2014-11-17T18:36:35.660754+00:00 Orion-14 kernel: 1289.869868] Broke affinity for irq 19
2014-11-17T18:36:35.660756+00:00 Orion-14 kernel: 1289.869882] Broke affinity for irq 22
2014-11-17T18:36:35.660758+00:00 Orion-14 kernel: 1289.869884] Broke affinity for irq 42
so a bug report might be needed to help chase this down.
I’ve just finished trying a few things… I’m guessing there’s maybe something about this hardware that 13.2 doesn’t like.
I have just replaced the two SSDs this machine normally runs on with a single HDD that already had a ‘virgin’ install of 13.1 on it.
Suspend/resume works as expected, as I had no problems with this on 13.1
I then did a complete fresh install of 13.2 to that HDD, formatting both root and home. After completion of the install suspend to RAM appears to work correctly in as much as it does not resume immediately ‘by itself’ … however, it won’t resume at all lol! I simply get a blank screen, the ‘Caps Lock’ and ‘Scroll Lock (?)’ LED on the keyboard are flashing. A hard reset is the only way out… (Why the behaviour would be different I have no idea.)