Bug#846792: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot

[Ben Hutchings]

Control: tag -1 - fixed-upstream
Control: tag -1 patch

Although the bugzilla.k.o report has been closed, this is not yet fixed
upstream.  However there is a tested patch which was sent to the linux-
acpi list: https://www.spinics.net/lists/linux-acpi/msg71496.html

Ben.

-- 
Ben Hutchings
Never put off till tomorrow what you can avoid all together.


signature.asc
Description: This is a digitally signed message part

Bug#846792: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot

[Jakobus Schürz]

Am 2016-12-30 um 23:30 schrieb Jakobus Schürz:
> Hi Salvatore!
> 
> Thanks for your reply!
> 
> 
 I know that is right now not a big help, but confirming if it is not a
 Debian specific change, would help, to make aware upstream.
>>>
>>>
>>> I build a vanilla-kernel from the kernel.org-sources (Don't know, if i
>>> made it correct). But I got a working Kernel 4.9 (without any
>>> patches???).The delay of 6 seconds persists after the EC: EC: in dmesg.
>>>
>>> Do i have to aply any patches?
>>>
>>> I build my Kernel with this recepie
>>> 
>>>
>>> Is this correct?
>>
>> Yes perfect. So we know that the issue is persisting with the vanilla
>> kernel without patches. Now the next step would be that you report
>> that to the bugzilla on kernel.org. Once you have the bugnumber, then
>> you can mark #846792 as forwarded to the upstream bug.
>>
>> Helps?
> 
> So i filed a bug in bugzilla on kernel.org
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=70891
> 
> But i don't know, how to mark a bugreport as forwarded... :(

Now i know, but i took the wrong bugnumber for kernel org.
The correct link is:

https://bugzilla.kernel.org/show_bug.cgi?id=191561

Regards

Jakob

Bug#846792: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot

[Jakobus Schürz]

Hi Salvatore!

Thanks for your reply!


>>> I know that is right now not a big help, but confirming if it is not a
>>> Debian specific change, would help, to make aware upstream.
>>
>>
>> I build a vanilla-kernel from the kernel.org-sources (Don't know, if i
>> made it correct). But I got a working Kernel 4.9 (without any
>> patches???).The delay of 6 seconds persists after the EC: EC: in dmesg.
>>
>> Do i have to aply any patches?
>>
>> I build my Kernel with this recepie
>> 
>>
>> Is this correct?
> 
> Yes perfect. So we know that the issue is persisting with the vanilla
> kernel without patches. Now the next step would be that you report
> that to the bugzilla on kernel.org. Once you have the bugnumber, then
> you can mark #846792 as forwarded to the upstream bug.
> 
> Helps?

So i filed a bug in bugzilla on kernel.org

https://bugzilla.kernel.org/show_bug.cgi?id=70891

But i don't know, how to mark a bugreport as forwarded... :(

Regards

Jakob

Bug#846792: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot

[Jakobus Schürz]

Hi Salvatore!

No problem. I know, christmas is the most busy time in the year... :)
Same here.

> Apologies for the delay in coming back to you. So I'm not having
> really an idea. I suggest the following in case it is feasible for
> you:
> 
> Try to reproduce the problem with "vanilla" kernel. This is to make
> sure the issue is not introduced by a Debian specific change, but
> using otherwise the same configuration.
> 
> The following contains some indication:
> https://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.2 ->
> https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-building
> 
> If this turns out to not be a issue specific to a Debian change, then
> could you please report the bug to the kernel bug database?
> 
> Once you have the bugnumber, mark this bug as forwarded.
> 
> I know that is right now not a big help, but confirming if it is not a
> Debian specific change, would help, to make aware upstream.


I build a vanilla-kernel from the kernel.org-sources (Don't know, if i
made it correct). But I got a working Kernel 4.9 (without any
patches???).The delay of 6 seconds persists after the EC: EC: in dmesg.

Do i have to aply any patches?

I build my Kernel with this recepie


Is this correct?

Regards Jakob

Bug#846792: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot

[Salvatore Bonaccorso]

Jakobus,

On Tue, Dec 06, 2016 at 10:14:45PM +0100, Jakobus Schürz wrote:
> Hi Salvatore
> 
> Thanks for your help.
> 
> Am 2016-12-04 um 06:42 schrieb Salvatore Bonaccorso:
> 
> > No that actually is enought, since the commit is is is in upstream
> > version 4.9-rc1 and thus already included in the most recent package
> > from experimental.
> > 
> > Thanks for testing that. So it looks might not be the same issue. Can
> > you report what you did to me directly to the bug to keep the triage
> > history?
> 
> 
> I've just installed the kernel 4.9.0-rc7-amd64 from experimental and
> rebooted... And the delay was again here.
> 
> Do you need some information about my hardware or BIOS (its HP-EFI or is
> it UEFI? :) )
> I posted the Version in my bugreport.

Apologies for the delay in coming back to you. So I'm not having
really an idea. I suggest the following in case it is feasible for
you:

Try to reproduce the problem with "vanilla" kernel. This is to make
sure the issue is not introduced by a Debian specific change, but
using otherwise the same configuration.

The following contains some indication:
https://kernel-handbook.alioth.debian.org/ch-bugs.html#s9.2 ->
https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-building

If this turns out to not be a issue specific to a Debian change, then
could you please report the bug to the kernel bug database?

Once you have the bugnumber, mark this bug as forwarded.

I know that is right now not a big help, but confirming if it is not a
Debian specific change, would help, to make aware upstream.

Regards,
Salvatore

Bug#846792: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot

[Jakobus Schürz]

Hi Salvatore

Thanks for your help.

Am 2016-12-04 um 06:42 schrieb Salvatore Bonaccorso:

> No that actually is enought, since the commit is is is in upstream
> version 4.9-rc1 and thus already included in the most recent package
> from experimental.
> 
> Thanks for testing that. So it looks might not be the same issue. Can
> you report what you did to me directly to the bug to keep the triage
> history?


I've just installed the kernel 4.9.0-rc7-amd64 from experimental and
rebooted... And the delay was again here.

Do you need some information about my hardware or BIOS (its HP-EFI or is
it UEFI? :) )
I posted the Version in my bugreport.

Regards

Jakob

Bug#846792: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot

[Jakobus Schürz]

Hi Salvatore!

Thanks for the info. I read about, but didnt think on the experimental
repo... :)

Now i installed this kernel and rebooted:

# uname -a
Linux aldebaran 4.9.0-rc7-amd64 #1 SMP Debian 4.9~rc7-1~exp1

(2016-12-03) x86_64 GNU/Linux

# systemd-analyze
Startup finished in 8.733s (firmware) + 18.800s (loader) + 12.723s
(kernel) + 6.350s (userspace) = 46.607s

and dmesg shows the following... the 6 second-gap still exists here.

[0.403864] ACPI: Added _OSI(Module Device)
[0.403865] ACPI: Added _OSI(Processor Device)
[0.403866] ACPI: Added _OSI(3.0 _SCP Extensions)
[0.403867] ACPI: Added _OSI(Processor Aggregator Device)
[0.414682] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[0.421810] ACPI: Dynamic OEM Table Load:
[0.421820] ACPI: SSDT 0x8BF509FA5000 0003F3 (v01 PmRef  Cpu0Cst
3001 INTL 20130927)
[0.422283] ACPI: Dynamic OEM Table Load:
[0.422292] ACPI: SSDT 0x8BF50982E800 0005DB (v01 PmRef  ApIst
3000 INTL 20130927)
[0.422831] ACPI: Dynamic OEM Table Load:
[0.422837] ACPI: SSDT 0x8BF509FC8000 000119 (v01 PmRef  ApCst
3000 INTL 20130927)
[0.424079] ACPI : EC: EC started
[6.346985] ACPI: \_SB_.PCI0.LPCB.EC0_: Used as first EC
[6.346987] ACPI: \_SB_.PCI0.LPCB.EC0_: GPE=0x6, EC_CMD/EC_SC=0x66,
EC_DATA=0x62
[6.346989] ACPI: \_SB_.PCI0.LPCB.EC0_: Used as boot DSDT EC to
handle transactions
[6.346990] ACPI: Interpreter enabled
[6.347029] ACPI: (supports S0 S3 S4 S5)
[6.347030] ACPI: Using IOAPIC for interrupt routing


Do you need more informations about my system? Which one?


Regards,

Jakob

Bug#846792: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot

[Jakobus Schürz]

Hi again!

Am 2016-12-03 um 17:15 schrieb Salvatore Bonaccorso:

> Is this resolved if you install the kernel from experimental?
> (Currently 4.9~rc7-1~exp1). Does the commit applied in 4.9-rc1
> (2a5708409e4e05446eb1a89ecb48641d6fd5d5a9) resolves the issue for you?
> You can do this by following the instructions at
> https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2 

I studied your answer again. Did i get it right, i have to path the
kernel 4.9-rc7 myself with this commit, or is it enough to install the
kernel from experimental?

If i have to patch it myself, I need some help. Have no experiences with
kernel-patching.

Regards

Jakob

Bug#846792: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot

[Salvatore Bonaccorso]

HI Jakobus,

On Sat, Dec 03, 2016 at 01:37:06PM +0100, Jakobus Schürz wrote:
> Package: src:linux
> Version: 4.8.7-1
> Severity: normal
> 
> Dear Maintainer,
> 
> My Laptop is a HP-Probook 450 G2. 
> Loading the Kernel takes about 19 seconds
> 
> # systemd-analyze 
> Startup finished in 9.025s (firmware) + 7.440s (loader) + 19.061s (kernel) + 
> 6.802s (userspace) = 42.330s
> 
> Here you can see in dmesg-output two delay-gaps with about 6 Seconds. Each on 
> starting acpi embedded-controller.

Is this resolved if you install the kernel from experimental?
(Currently 4.9~rc7-1~exp1). Does the commit applied in 4.9-rc1
(2a5708409e4e05446eb1a89ecb48641d6fd5d5a9) resolves the issue for you?
You can do this by following the instructions at
https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s4.2.2 

Regards,
Salvatore

Bug#846792: linux-image-4.8.0-1-amd64: ACPI : EC: EC started delay on boot

[Jakobus Schürz]

Package: src:linux
Version: 4.8.7-1
Severity: normal

Dear Maintainer,

My Laptop is a HP-Probook 450 G2. 
Loading the Kernel takes about 19 seconds

# systemd-analyze 
Startup finished in 9.025s (firmware) + 7.440s (loader) + 19.061s (kernel) + 
6.802s (userspace) = 42.330s

Here you can see in dmesg-output two delay-gaps with about 6 Seconds. Each on 
starting acpi embedded-controller.

[0.396350] ACPI: Added _OSI(Module Device)
[0.396351] ACPI: Added _OSI(Processor Device)
[0.396352] ACPI: Added _OSI(3.0 _SCP Extensions)
[0.396353] ACPI: Added _OSI(Processor Aggregator Device)
[0.406992] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[0.413937] ACPI: Dynamic OEM Table Load:
[0.413947] ACPI: SSDT 0xFFF92789FD4C00 0003F3 (v01 PmRef  Cpu0Cst  3001 
INTL 20130927)
[0.414931] ACPI: Dynamic OEM Table Load:
[0.414940] ACPI: SSDT 0xFFF9278983F000 0005DB (v01 PmRef  ApIst
3000 INTL 20130927)
[0.416011] ACPI: Dynamic OEM Table Load:
[0.416017] ACPI: SSDT 0xFFF92789860A00 000119 (v01 PmRef  ApCst3000 
INTL 20130927)
[0.417750] ACPI : EC: EC started
[6.680046] ACPI: Interpreter enabled
[6.680085] ACPI: (supports S0 S3 S4 S5)
[6.680087] ACPI: Using IOAPIC for interrupt routing


[6.837352] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 10 11 12 14 15) 
*0, disabled.
[6.837412] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 10 11 12 14 15) 
*0, disabled.
[6.837469] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 10 11 12 14 15) 
*0, disabled.
[6.837525] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 10 11 12 14 15) 
*0, disabled.
[6.837581] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 10 11 12 14 15) 
*0, disabled.
[6.837637] ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 10 11 12 14 15) 
*0, disabled.
[6.837692] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 10 11 12 14 15) 
*0, disabled.
[6.837748] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 10 11 12 14 15) 
*0, disabled.
[6.838206] ACPI: Enabled 5 GPEs in block 00 to 7F
[6.838362] ACPI : EC: EC stopped
[6.838410] ACPI : EC: GPE = 0x6, I/O: command/status = 0x66, data = 0x62
[6.838411] ACPI : EC: EC started
[   12.899931] vgaarb: setting as boot device: PCI::00:02.0
[   12.899933] vgaarb: device added: 
PCI::00:02.0,decodes=io+mem,owns=io+mem,locks=none


There is another thing about this EC:

# ls /proc/acpi
button  wakeup

no embedded-controller in /proc

If you need information about my BIOS:

# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
31 structures occupying 1547 bytes.
Table at 0xA7D3F000.

Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Hewlett-Packard
Version: M74 Ver. 01.41
Release Date: 05/19/2016
Address: 0xF
Runtime Size: 64 kB
ROM Size: 6144 kB
Characteristics:
PCI is supported
PC Card (PCMCIA) is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
EDD is supported
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
Smart battery is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
UEFI is supported
BIOS Revision: 1.41
Firmware Revision: 103.37


Maybe this is the same bug - and solution in 4.9...
Look at https://bugzilla.kernel.org/show_bug.cgi?id=153511

Regards

Jakob


-- Package-specific info:
** Version:
Linux version 4.8.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 5.4.1 
20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 (2016-11-13)

** Command line:
\vmlinuz-4.8.0-1-amd64 root=UUID=03d34c21-a150-4e91-8470-a6346d04287a ro 
noalpic acpi=0 i915.i915_enable_rc6=1 rootflags=subvol=@debian-testing 
apparmor=1 security=apparmor quiet splash initrd=\initrd.img-4.8.0-1-amd64

** Tainted: UOE (12352)
 * Userspace-defined naughtiness.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

** Kernel log:
[   21.396409] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   21.414163] systemd-journald[247]: Received request to flush runtime journal 
from PID 1
[   21.437513] pstore: using zlib compression
[   21.461204] iwlwifi :09:00.0 wlo1: renamed from wlan0
[   21.512628] ahci :00:1f.2: port does not support device sleep
[   21.597410] Bluetooth: Core ver 2.21
[   21.597426] NET: Registered protocol family 31
[   21.597427] Bluetooth: HCI device and connection manager initialized
[