Re: [3.5-rc6+] mei: irq: request_threaded_irq is missing the IRQF_ONESHOT flag
On Fri, Jul 13, 2012 at 12:29 PM, Sedat Dilek wrote: > On Fri, Jul 13, 2012 at 12:15 PM, Winkler, Tomas > wrote: >> >> >>> -Original Message- >>> From: Sedat Dilek [mailto:sedat.di...@gmail.com] >>> Sent: Friday, July 13, 2012 12:48 PM >>> To: Winkler, Tomas >>> Cc: Thomas Gleixner; LKML; Greg Kroah-Hartman; Roland Dreier >>> Subject: [3.5-rc6+] mei: irq: request_threaded_irq is missing the >>> IRQF_ONESHOT flag >>> >>> Hi, >>> >>> while dealing with [1], I saw this mei-related infos in dmesg when doing a >>> suspend + resume (see [1] for more logs): >> >> The fix is included in this post pull request >> http://marc.info/?l=linux-kernel=134201523903406=2 >> > > [ CC Rafael @ linux-pm ML ] > > Hmm, I have this commit in my local GIT buil-tree already: > > $ git log --oneline | grep "mei: pci_resume: set IRQF_ONESHOT for msi > request_threaded_irq" > 16a50b1 mei: pci_resume: set IRQF_ONESHOT for msi request_threaded_irq > > Dunno, if it's a PM related problem? As I see this: > > [17047.460520] PM: Device :00:16.0 failed to resume async: error -22 > > BTW, what is "wd:" and what means if it "failed"? > > [ 23.646041] mei :00:16.0: irq 47 for MSI/MSI-X > [ 23.650677] mei :00:16.0: wd: failed to find the client > > - Sedat - > > [1] > http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=16a50b1270455a6d41f9f6d8f99a72cf9d76824a > >> Thanks >> Tomas >> >> Grr, looking into the wrong logs, I did a S/R with the *new* kernel including Thomas mei-fix! It's really fixed. Sorry for the noise - more coffee for me & all who like it. - Sedat - [ 9905.393328] wlan0: deauthenticating from 00:04:0e:e4:00:3d by local choice (reason=3) [ 9905.407744] cfg80211: All devices are disconnected, going to restore regulatory settings [ 9905.407749] cfg80211: Restoring regulatory settings [ 9905.407754] cfg80211: Calling CRDA to update world regulatory domain [ 9905.519897] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain [ 9905.519900] cfg80211: World regulatory domain updated: [ 9905.519901] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 9905.519903] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 9905.519904] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 9905.519905] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 9905.519906] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 9905.519907] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 9907.437715] PM: Syncing filesystems ... done. [ 9907.451380] PM: Preparing system for mem sleep [ 9907.969359] Freezing user space processes ... (elapsed 0.01 seconds) done. [ 9907.985344] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [ 9908.001427] PM: Entering mem sleep [ 9908.001515] Suspending console(s) (use no_console_suspend to debug) [ 9908.001761] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [ 9908.001941] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 9908.004563] sd 1:0:0:0: [sdb] Stopping disk [ 9908.014078] sd 0:0:0:0: [sda] Stopping disk [ 9908.608945] PM: suspend of devices complete after 607.766 msecs [ 9908.608946] PM: suspend devices took 0.608 seconds [ 9908.609072] PM: late suspend of devices complete after 0.124 msecs [ 9908.624982] r8169 :02:00.0: wake-up capability enabled by ACPI [ 9908.704875] PM: noirq suspend of devices complete after 95.865 msecs [ 9908.705107] ACPI: Preparing to enter system sleep state S3 [ 9908.728945] PM: Saving platform NVS memory [ 9908.733684] Disabling non-boot CPUs ... [ 9908.836694] CPU 1 is now offline [ 9908.940625] CPU 2 is now offline [ 9909.044544] CPU 3 is now offline [ 9909.044919] Extended CMOS year: 2000 [ 9909.046163] ACPI: Low-level resume complete [ 9909.046210] PM: Restoring platform NVS memory [ 9909.047453] Extended CMOS year: 2000 [ 9909.047498] Enabling non-boot CPUs ... [ 9909.047590] Booting Node 0 Processor 1 APIC 0x1 [ 9909.058697] Disabled fast string operations [ 9909.061320] CPU1 is up [ 9909.061441] Booting Node 0 Processor 2 APIC 0x2 [ 9909.072476] Disabled fast string operations [ 9909.075115] CPU2 is up [ 9909.075216] Booting Node 0 Processor 3 APIC 0x3 [ 9909.086250] Disabled fast string operations [ 9909.088917] CPU3 is up [ 9909.093772] ACPI: Waking up from system sleep state S3 [ 9909.141341] PM: noirq resume of devices complete after 2.199 msecs [ 9909.141450] PM: early resume of devices complete after 0.064 msecs [ 9909.141482] i915 :00:02.0: setting latency timer to 64 [ 9909.141569] mei :00:16.0: irq 47 for MSI/MSI-X [ 9909.141633] ehci_hcd :00:1a.0: setting latency timer to 64 [ 9909.141677] ehci_hcd :00:1d.0: setting latency timer to 64 [ 9909.141679] ahci :00:1f.2: setting latency timer to 64 [ 9909.141699] snd_hda_intel :00:1b.0: irq 50 for MSI/MSI-X [ 9909.141755] r8169
Re: [3.5-rc6+] mei: irq: request_threaded_irq is missing the IRQF_ONESHOT flag
On Fri, Jul 13, 2012 at 12:15 PM, Winkler, Tomas wrote: > > >> -Original Message- >> From: Sedat Dilek [mailto:sedat.di...@gmail.com] >> Sent: Friday, July 13, 2012 12:48 PM >> To: Winkler, Tomas >> Cc: Thomas Gleixner; LKML; Greg Kroah-Hartman; Roland Dreier >> Subject: [3.5-rc6+] mei: irq: request_threaded_irq is missing the >> IRQF_ONESHOT flag >> >> Hi, >> >> while dealing with [1], I saw this mei-related infos in dmesg when doing a >> suspend + resume (see [1] for more logs): > > The fix is included in this post pull request > http://marc.info/?l=linux-kernel=134201523903406=2 > [ CC Rafael @ linux-pm ML ] Hmm, I have this commit in my local GIT buil-tree already: $ git log --oneline | grep "mei: pci_resume: set IRQF_ONESHOT for msi request_threaded_irq" 16a50b1 mei: pci_resume: set IRQF_ONESHOT for msi request_threaded_irq Dunno, if it's a PM related problem? As I see this: [17047.460520] PM: Device :00:16.0 failed to resume async: error -22 BTW, what is "wd:" and what means if it "failed"? [ 23.646041] mei :00:16.0: irq 47 for MSI/MSI-X [ 23.650677] mei :00:16.0: wd: failed to find the client - Sedat - [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=16a50b1270455a6d41f9f6d8f99a72cf9d76824a > Thanks > Tomas > > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [3.5-rc6+] mei: irq: request_threaded_irq is missing the IRQF_ONESHOT flag
> -Original Message- > From: Sedat Dilek [mailto:sedat.di...@gmail.com] > Sent: Friday, July 13, 2012 12:48 PM > To: Winkler, Tomas > Cc: Thomas Gleixner; LKML; Greg Kroah-Hartman; Roland Dreier > Subject: [3.5-rc6+] mei: irq: request_threaded_irq is missing the > IRQF_ONESHOT flag > > Hi, > > while dealing with [1], I saw this mei-related infos in dmesg when doing a > suspend + resume (see [1] for more logs): The fix is included in this post pull request http://marc.info/?l=linux-kernel=134201523903406=2 Thanks Tomas
Re: [3.5-rc6+] mei: irq: request_threaded_irq is missing the IRQF_ONESHOT flag
On Fri, Jul 13, 2012 at 11:47 AM, Sedat Dilek wrote: > Hi, > > while dealing with [1], I saw this mei-related infos in dmesg when > doing a suspend + resume (see [1] for more logs): > > [17046.348467] [] mei_pci_suspend+0x78/0xd0 [mei] > [17047.460315] mei :00:16.0: irq 47 for MSI/MSI-X > [17047.460512] mei :00:16.0: request_threaded_irq failed: irq = 47. > > I am not sure whom to address with the issue - so I just asked on > #linux-rt and Thomas responded: > > [ 13-Jul-2012: German local-time (UTC+2) ] > ... > [11:03:40] request_threaded_irq is missing the IRQF_ONESHOT flag > ... > [11:24:18] anyone can fix it by sending a patch which adds the flag :) > > Futhermore, I found those commits, so I added folks from there to this BR: > > 16a50b1 mei: pci_resume: set IRQF_ONESHOT for msi request_threaded_irq > aa189ec misc: mei: set IRQF_ONESHOT for msi request_threaded_irq > > If you need more infos and/or logs, please let me know. > > Feel free to add: > > Reported-by: Sedat Dilek > > Kind Regards, > - Sedat (dileks on IRC) - > > [1] http://marc.info/?l=linux-kernel=134216822724119=2 Here some more infos: $ lspci -nnvv | egrep 'mei|00:16' 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) Kernel driver in use: mei $ dmesg | egrep 'mei|00:16' [0.242776] pci :00:16.0: [8086:1c3a] type 00 class 0x078000 [0.242802] pci :00:16.0: reg 10: [mem 0xf0705000-0xf070500f 64bit] [0.242884] pci :00:16.0: PME# supported from D0 D3hot D3cold [ 23.645968] mei :00:16.0: setting latency timer to 64 [ 23.646041] mei :00:16.0: irq 47 for MSI/MSI-X [ 23.650677] mei :00:16.0: wd: failed to find the client [ 1386.959871] mei :00:16.0: irq 47 for MSI/MSI-X [ 1386.960810] mei :00:16.0: wd: failed to find the client [ 1435.138062] mei :00:16.0: irq 47 for MSI/MSI-X [ 1435.139033] mei :00:16.0: wd: failed to find the client >From the above mentionned dmesg log: $ dmesg | egrep 'mei|00:16|IRQF_ONESHOT' CALL-TRACE_3.5.0-rc6-1-iniza-generic_PM-related_HW-hidden.txt [17046.348410] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek rfcomm bnep parport_pc ppdev joydev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm coretemp kvm_intel snd_page_alloc kvm arc4 snd_seq_midi snd_seq_midi_event iwlwifi i915 snd_rawmidi uvcvideo snd_seq ghash_clmulni_intel snd_seq_device videobuf2_vmalloc aesni_intel snd_timer videobuf2_memops aes_x86_64 drm_kms_helper videobuf2_core cryptd mac80211 drm snd videodev psmouse samsung_laptop i2c_algo_bit btusb hid_generic soundcore microcode serio_raw cfg80211 lp mei bluetooth video mac_hid lpc_ich parport usbhid hid r8169 [17046.348467] [] mei_pci_suspend+0x78/0xd0 [mei] [17047.460315] mei :00:16.0: irq 47 for MSI/MSI-X [17047.460512] mei :00:16.0: request_threaded_irq failed: irq = 47. [17047.460520] PM: Device :00:16.0 failed to resume async: error -22 I am sorry if this is a different issue as already reported. Greetings, - Sedat - -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [3.5-rc6+] mei: irq: request_threaded_irq is missing the IRQF_ONESHOT flag
On Fri, Jul 13, 2012 at 11:47 AM, Sedat Dilek sedat.di...@gmail.com wrote: Hi, while dealing with [1], I saw this mei-related infos in dmesg when doing a suspend + resume (see [1] for more logs): [17046.348467] [a00554d8] mei_pci_suspend+0x78/0xd0 [mei] [17047.460315] mei :00:16.0: irq 47 for MSI/MSI-X [17047.460512] mei :00:16.0: request_threaded_irq failed: irq = 47. I am not sure whom to address with the issue - so I just asked on #linux-rt and Thomas responded: [ 13-Jul-2012: German local-time (UTC+2) ] ... [11:03:40] tglx request_threaded_irq is missing the IRQF_ONESHOT flag ... [11:24:18] tglx anyone can fix it by sending a patch which adds the flag :) Futhermore, I found those commits, so I added folks from there to this BR: 16a50b1 mei: pci_resume: set IRQF_ONESHOT for msi request_threaded_irq aa189ec misc: mei: set IRQF_ONESHOT for msi request_threaded_irq If you need more infos and/or logs, please let me know. Feel free to add: Reported-by: Sedat Dilek sedat.di...@gmail.com Kind Regards, - Sedat (dileks on IRC) - [1] http://marc.info/?l=linux-kernelm=134216822724119w=2 Here some more infos: $ lspci -nnvv | egrep 'mei|00:16' 00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04) Kernel driver in use: mei $ dmesg | egrep 'mei|00:16' [0.242776] pci :00:16.0: [8086:1c3a] type 00 class 0x078000 [0.242802] pci :00:16.0: reg 10: [mem 0xf0705000-0xf070500f 64bit] [0.242884] pci :00:16.0: PME# supported from D0 D3hot D3cold [ 23.645968] mei :00:16.0: setting latency timer to 64 [ 23.646041] mei :00:16.0: irq 47 for MSI/MSI-X [ 23.650677] mei :00:16.0: wd: failed to find the client [ 1386.959871] mei :00:16.0: irq 47 for MSI/MSI-X [ 1386.960810] mei :00:16.0: wd: failed to find the client [ 1435.138062] mei :00:16.0: irq 47 for MSI/MSI-X [ 1435.139033] mei :00:16.0: wd: failed to find the client From the above mentionned dmesg log: $ dmesg | egrep 'mei|00:16|IRQF_ONESHOT' CALL-TRACE_3.5.0-rc6-1-iniza-generic_PM-related_HW-hidden.txt [17046.348410] Modules linked in: snd_hda_codec_hdmi snd_hda_codec_realtek rfcomm bnep parport_pc ppdev joydev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm coretemp kvm_intel snd_page_alloc kvm arc4 snd_seq_midi snd_seq_midi_event iwlwifi i915 snd_rawmidi uvcvideo snd_seq ghash_clmulni_intel snd_seq_device videobuf2_vmalloc aesni_intel snd_timer videobuf2_memops aes_x86_64 drm_kms_helper videobuf2_core cryptd mac80211 drm snd videodev psmouse samsung_laptop i2c_algo_bit btusb hid_generic soundcore microcode serio_raw cfg80211 lp mei bluetooth video mac_hid lpc_ich parport usbhid hid r8169 [17046.348467] [a00554d8] mei_pci_suspend+0x78/0xd0 [mei] [17047.460315] mei :00:16.0: irq 47 for MSI/MSI-X [17047.460512] mei :00:16.0: request_threaded_irq failed: irq = 47. [17047.460520] PM: Device :00:16.0 failed to resume async: error -22 I am sorry if this is a different issue as already reported. Greetings, - Sedat - -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: [3.5-rc6+] mei: irq: request_threaded_irq is missing the IRQF_ONESHOT flag
-Original Message- From: Sedat Dilek [mailto:sedat.di...@gmail.com] Sent: Friday, July 13, 2012 12:48 PM To: Winkler, Tomas Cc: Thomas Gleixner; LKML; Greg Kroah-Hartman; Roland Dreier Subject: [3.5-rc6+] mei: irq: request_threaded_irq is missing the IRQF_ONESHOT flag Hi, while dealing with [1], I saw this mei-related infos in dmesg when doing a suspend + resume (see [1] for more logs): The fix is included in this post pull request http://marc.info/?l=linux-kernelm=134201523903406w=2 Thanks Tomas
Re: [3.5-rc6+] mei: irq: request_threaded_irq is missing the IRQF_ONESHOT flag
On Fri, Jul 13, 2012 at 12:15 PM, Winkler, Tomas tomas.wink...@intel.com wrote: -Original Message- From: Sedat Dilek [mailto:sedat.di...@gmail.com] Sent: Friday, July 13, 2012 12:48 PM To: Winkler, Tomas Cc: Thomas Gleixner; LKML; Greg Kroah-Hartman; Roland Dreier Subject: [3.5-rc6+] mei: irq: request_threaded_irq is missing the IRQF_ONESHOT flag Hi, while dealing with [1], I saw this mei-related infos in dmesg when doing a suspend + resume (see [1] for more logs): The fix is included in this post pull request http://marc.info/?l=linux-kernelm=134201523903406w=2 [ CC Rafael @ linux-pm ML ] Hmm, I have this commit in my local GIT buil-tree already: $ git log --oneline | grep mei: pci_resume: set IRQF_ONESHOT for msi request_threaded_irq 16a50b1 mei: pci_resume: set IRQF_ONESHOT for msi request_threaded_irq Dunno, if it's a PM related problem? As I see this: [17047.460520] PM: Device :00:16.0 failed to resume async: error -22 BTW, what is wd: and what means if it failed? [ 23.646041] mei :00:16.0: irq 47 for MSI/MSI-X [ 23.650677] mei :00:16.0: wd: failed to find the client - Sedat - [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=16a50b1270455a6d41f9f6d8f99a72cf9d76824a Thanks Tomas -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [3.5-rc6+] mei: irq: request_threaded_irq is missing the IRQF_ONESHOT flag
On Fri, Jul 13, 2012 at 12:29 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Fri, Jul 13, 2012 at 12:15 PM, Winkler, Tomas tomas.wink...@intel.com wrote: -Original Message- From: Sedat Dilek [mailto:sedat.di...@gmail.com] Sent: Friday, July 13, 2012 12:48 PM To: Winkler, Tomas Cc: Thomas Gleixner; LKML; Greg Kroah-Hartman; Roland Dreier Subject: [3.5-rc6+] mei: irq: request_threaded_irq is missing the IRQF_ONESHOT flag Hi, while dealing with [1], I saw this mei-related infos in dmesg when doing a suspend + resume (see [1] for more logs): The fix is included in this post pull request http://marc.info/?l=linux-kernelm=134201523903406w=2 [ CC Rafael @ linux-pm ML ] Hmm, I have this commit in my local GIT buil-tree already: $ git log --oneline | grep mei: pci_resume: set IRQF_ONESHOT for msi request_threaded_irq 16a50b1 mei: pci_resume: set IRQF_ONESHOT for msi request_threaded_irq Dunno, if it's a PM related problem? As I see this: [17047.460520] PM: Device :00:16.0 failed to resume async: error -22 BTW, what is wd: and what means if it failed? [ 23.646041] mei :00:16.0: irq 47 for MSI/MSI-X [ 23.650677] mei :00:16.0: wd: failed to find the client - Sedat - [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commitdiff;h=16a50b1270455a6d41f9f6d8f99a72cf9d76824a Thanks Tomas Grr, looking into the wrong logs, I did a S/R with the *new* kernel including Thomas mei-fix! It's really fixed. Sorry for the noise - more coffee for me all who like it. - Sedat - [ 9905.393328] wlan0: deauthenticating from 00:04:0e:e4:00:3d by local choice (reason=3) [ 9905.407744] cfg80211: All devices are disconnected, going to restore regulatory settings [ 9905.407749] cfg80211: Restoring regulatory settings [ 9905.407754] cfg80211: Calling CRDA to update world regulatory domain [ 9905.519897] cfg80211: Ignoring regulatory request Set by core since the driver uses its own custom regulatory domain [ 9905.519900] cfg80211: World regulatory domain updated: [ 9905.519901] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 9905.519903] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 9905.519904] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 9905.519905] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 9905.519906] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 9905.519907] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 9907.437715] PM: Syncing filesystems ... done. [ 9907.451380] PM: Preparing system for mem sleep [ 9907.969359] Freezing user space processes ... (elapsed 0.01 seconds) done. [ 9907.985344] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [ 9908.001427] PM: Entering mem sleep [ 9908.001515] Suspending console(s) (use no_console_suspend to debug) [ 9908.001761] sd 1:0:0:0: [sdb] Synchronizing SCSI cache [ 9908.001941] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 9908.004563] sd 1:0:0:0: [sdb] Stopping disk [ 9908.014078] sd 0:0:0:0: [sda] Stopping disk [ 9908.608945] PM: suspend of devices complete after 607.766 msecs [ 9908.608946] PM: suspend devices took 0.608 seconds [ 9908.609072] PM: late suspend of devices complete after 0.124 msecs [ 9908.624982] r8169 :02:00.0: wake-up capability enabled by ACPI [ 9908.704875] PM: noirq suspend of devices complete after 95.865 msecs [ 9908.705107] ACPI: Preparing to enter system sleep state S3 [ 9908.728945] PM: Saving platform NVS memory [ 9908.733684] Disabling non-boot CPUs ... [ 9908.836694] CPU 1 is now offline [ 9908.940625] CPU 2 is now offline [ 9909.044544] CPU 3 is now offline [ 9909.044919] Extended CMOS year: 2000 [ 9909.046163] ACPI: Low-level resume complete [ 9909.046210] PM: Restoring platform NVS memory [ 9909.047453] Extended CMOS year: 2000 [ 9909.047498] Enabling non-boot CPUs ... [ 9909.047590] Booting Node 0 Processor 1 APIC 0x1 [ 9909.058697] Disabled fast string operations [ 9909.061320] CPU1 is up [ 9909.061441] Booting Node 0 Processor 2 APIC 0x2 [ 9909.072476] Disabled fast string operations [ 9909.075115] CPU2 is up [ 9909.075216] Booting Node 0 Processor 3 APIC 0x3 [ 9909.086250] Disabled fast string operations [ 9909.088917] CPU3 is up [ 9909.093772] ACPI: Waking up from system sleep state S3 [ 9909.141341] PM: noirq resume of devices complete after 2.199 msecs [ 9909.141450] PM: early resume of devices complete after 0.064 msecs [ 9909.141482] i915 :00:02.0: setting latency timer to 64 [ 9909.141569] mei :00:16.0: irq 47 for MSI/MSI-X [ 9909.141633] ehci_hcd :00:1a.0: setting latency timer to 64 [ 9909.141677] ehci_hcd :00:1d.0: setting latency timer to 64 [ 9909.141679] ahci :00:1f.2: setting latency timer to 64 [ 9909.141699] snd_hda_intel :00:1b.0: irq 50 for MSI/MSI-X [ 9909.141755] r8169 :02:00.0: wake-up capability disabled by ACPI
