linux-kernel - Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <864ff133-815c-0c7f-5e36-fdcc32d0261d@linux.intel.com>
Date:   Mon, 24 Jul 2017 18:41:47 +0300
From:   Martin Peres <martin.peres@...ux.intel.com>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     jeffy.chen@...k-chips.com,
        "Sarvela, Tomi P" <tomi.p.sarvela@...el.com>,
        linux-kernel@...r.kernel.org
Subject: Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

On 24/07/17 18:28, Thomas Gleixner wrote:
> On Mon, 24 Jul 2017, Martin Peres wrote:
>>
>> I am contacting you because your patch "bf22ff45b genirq: Avoid unnecessary
>> low level irq function calls" broke suspend/resume on an old Intel platform.
>>
>> This was not caught in linux-next and only got introduced in linux 4.13-rc1.
>>
>> Here is the current place where the bug has been reported[0] but I can move it
>> to bugzilla.kernel.org if you would want that.
> 
> Can we please handle this per mail?

Sure, if you prefer.

> 
>> Here are the kernel logs[1]. What information would you need?
> 
> Output of 'cat /proc/interrupts' and a description what kind of 'old' Intel
> platform that is.

Sorry, I should have repeated the name outside of just the subject of 
the email. It is an Intel Eagle Lake Core2Duo.

$ sudo cat /proc/interrupts
            CPU0       CPU1 
 

   0:        182          0   IO-APIC   2-edge      timer 
 

   1:          2          1   IO-APIC   1-edge      i8042 
 

   4:          6          4   IO-APIC   4-edge      serial 
 

   5:          0          0   IO-APIC   5-edge      ehci_hcd:usb1, 
uhci_hcd:usb5, uhci_hcd:usb8 

   8:          1          0   IO-APIC   8-edge      rtc0 
 

   9:          0          0   IO-APIC   9-fasteoi   acpi 
 

  10:          0          0   IO-APIC  10-edge      ehci_hcd:usb2, 
uhci_hcd:usb3, uhci_hcd:usb6 

  11:          0          0   IO-APIC  11-edge      uhci_hcd:usb4, 
uhci_hcd:usb7 

  12:          3          2   IO-APIC  12-edge      i8042 
 

  24:      63345          0  HPET-MSI   2-edge      hpet2 
 

  25:          0      70778  HPET-MSI   3-edge      hpet3 
 

  28:          0          0   PCI-MSI 458752-edge      PCIe PME 
 

  29:          0          0   PCI-MSI 466944-edge      PCIe PME 
 

  30:       5349      10818   PCI-MSI 512000-edge 
ahci[0000:00:1f.2] 

  31:        810      10234   PCI-MSI 409600-edge      enp0s25 
 

  32:          9          9   PCI-MSI 49152-edge      mei_me 
 

  33:        233        223   PCI-MSI 442368-edge 
snd_hda_intel:card0 

  34:          1          0   PCI-MSI 32768-edge      i915 
 

NMI:         38         33   Non-maskable interrupts 
 

LOC:        710        438   Local timer interrupts 
 

SPU:          0          0   Spurious interrupts 
 

PMI:         38         33   Performance monitoring interrupts 
 

IWI:          0          0   IRQ work interrupts 
 

RTR:          0          0   APIC ICR read retries 
 

RES:       2629       2425   Rescheduling interrupts 
 

CAL:        618        722   Function call interrupts 
 

TLB:        321        309   TLB shootdowns 
 

TRM:          0          0   Thermal event interrupts 
 

THR:          0          0   Threshold APIC interrupts 
 

MCE:          0          0   Machine check exceptions 
 

MCP:          7          7   Machine check polls 
 

ERR:          0 
 

MIS:          0 
 

PIN:          0          0   Posted-interrupt notification event 
 

PIW:          0          0   Posted-interrupt wakeup event

Cheers,
Martin