3.19-rc1 errors when opening LID

DISCUSSION Pali Rohár 4 participants 11 messages Dec 24, 2014 – Apr 6, 2015

Subsystems (3)

ACPI PCI ACPI component architecture (acpica)

lore

Share & tools

lore

Pali Rohár

author

2014-12-24 18:51 UTC #0 lore raw

Hello!

With new 3.19-rc1 kernel every time when I open LID on my laptop, kernel prints these error lines to dmesg:

[25566.368133] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.
[25566.368134] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[25566.368192] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.
[25566.368232] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.<4>[25568.446011] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] 
has bogus alignment
[25568.447018] pci_bus 0000:02: Allocating resources
[25568.447055] pci_bus 0000:03: Allocating resources
[25568.447135] pci_bus 0000:04: Allocating resources
[25568.447168] pci_bus 0000:05: Allocating resources
[25568.447195] pci_bus 0000:06: Allocating resources
[25568.447228] pci_bus 0000:0e: Allocating resources
[25568.447323] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.447557] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.447735] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.447847] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.448399] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.448438] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.448566] acpi MSFT1111:00: Cannot transition to power state D3cold for parent in (unknown)
[25568.448572] acpi INT33C2:00: Cannot transition to non-D0 state from D3
[25568.448577] acpi MSFT0002:00: Cannot transition to power state D3cold for parent in (unknown)
[25568.448581] acpi ELAN1010:00: Cannot transition to power state D3cold for parent in (unknown)
[25568.448587] acpi INT33C3:00: Cannot transition to non-D0 state from D3
[25568.448590] acpi INT33C0:00: Cannot transition to non-D0 state from D3
[25568.448594] acpi INT33C1:00: Cannot transition to non-D0 state from D3
[25568.448598] acpi INT33C4:00: Cannot transition to non-D0 state from D3
[25568.448602] acpi INT33C5:00: Cannot transition to non-D0 state from D3
[25568.448623] acpi device:41: Cannot transition to power state D3cold for parent in (unknown)
[25568.448627] acpi INT33C6:00: Cannot transition to non-D0 state from D3
[25568.448890] pci_bus 0000:01: Allocating resources
[25568.448905] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.449064] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.449472] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment

With older kernel (3.13) I do not see these errors, so it is regression. Can you look at it? If it is needed, I can provide other logs, ACPI/DSTD dumps, etc.

Signature · 2 lines

Pali Rohár
[email protected]

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

nick

2014-12-25 04:28 UTC #1 lore raw

Pali,
Do you known how to run git bisect as this is probably the best way to continue. Otherwise, I can teach you how it's not hard if your willing to learn :). Cheers Nick

Quoted 37 lines · Pali Rohár

Hello!

With new 3.19-rc1 kernel every time when I open LID on my laptop, kernel prints these error lines to dmesg:

[25566.368133] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.
[25566.368134] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt
[25566.368192] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.
[25566.368232] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.<4>[25568.446011] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] 
has bogus alignment
[25568.447018] pci_bus 0000:02: Allocating resources
[25568.447055] pci_bus 0000:03: Allocating resources
[25568.447135] pci_bus 0000:04: Allocating resources
[25568.447168] pci_bus 0000:05: Allocating resources
[25568.447195] pci_bus 0000:06: Allocating resources
[25568.447228] pci_bus 0000:0e: Allocating resources
[25568.447323] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.447557] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.447735] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.447847] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.448399] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.448438] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.448566] acpi MSFT1111:00: Cannot transition to power state D3cold for parent in (unknown)
[25568.448572] acpi INT33C2:00: Cannot transition to non-D0 state from D3
[25568.448577] acpi MSFT0002:00: Cannot transition to power state D3cold for parent in (unknown)
[25568.448581] acpi ELAN1010:00: Cannot transition to power state D3cold for parent in (unknown)
[25568.448587] acpi INT33C3:00: Cannot transition to non-D0 state from D3
[25568.448590] acpi INT33C0:00: Cannot transition to non-D0 state from D3
[25568.448594] acpi INT33C1:00: Cannot transition to non-D0 state from D3
[25568.448598] acpi INT33C4:00: Cannot transition to non-D0 state from D3
[25568.448602] acpi INT33C5:00: Cannot transition to non-D0 state from D3
[25568.448623] acpi device:41: Cannot transition to power state D3cold for parent in (unknown)
[25568.448627] acpi INT33C6:00: Cannot transition to non-D0 state from D3
[25568.448890] pci_bus 0000:01: Allocating resources
[25568.448905] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.449064] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.449472] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment

Quoted 9 lines

With older kernel (3.13) I do not see these errors, so it is regression. Can you look at it? If it is needed, I can provide other logs, ACPI/DSTD dumps, etc.
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

I know how to use git... first I wanted to report errors because maybe it could be known problem or somebody else can come with quick patch even without bisetcing (like for other problems which I reported).

Anyway those acpi devices which are mentioned in log do not exist in 3.13 kernel (I do not see them in /sys/devices)

Any idea why 3.19 kernel create new acpi devices which 3.13 kernel did not?

Quoted 73 lines · On Thursday 25 December 2014 05:28:27 nick wrote:

Pali,
Do you known how to run git bisect as this is probably the best way to continue. Otherwise, I can teach you how it's not hard if your willing to learn :). Cheers Nick
Quoted 67 lines · Pali Rohár
Hello!
With new 3.19-rc1 kernel every time when I open LID on my laptop, kernel prints these error lines to dmesg:
[25566.368133] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]]
*ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem. [25566.368134] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt [25566.368192] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem. [25566.368232] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.<4>[25568.446011] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.447018] pci_bus 0000:02: Allocating resources
[25568.447055] pci_bus 0000:03: Allocating resources
[25568.447135] pci_bus 0000:04: Allocating resources
[25568.447168] pci_bus 0000:05: Allocating resources
[25568.447195] pci_bus 0000:06: Allocating resources
[25568.447228] pci_bus 0000:0e: Allocating resources
[25568.447323] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bogus alignment [25568.447557] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.447735] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.447847] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.448399] i915 0000:00:02.0: BAR 6:
[??? 0x00000000 flags 0x2] has bogus alignment
[25568.448438] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bogus alignment [25568.448566] acpi MSFT1111:00: Cannot transition to power state D3cold for parent in (unknown) [25568.448572] acpi INT33C2:00: Cannot transition to non-D0 state from D3 [25568.448577] acpi MSFT0002:00: Cannot transition to power state D3cold for parent in (unknown) [25568.448581] acpi ELAN1010:00: Cannot transition to power state D3cold for parent in (unknown)
[25568.448587] acpi INT33C3:00: Cannot transition to non-D0
state from D3 [25568.448590] acpi INT33C0:00: Cannot
transition to non-D0 state from D3 [25568.448594] acpi
INT33C1:00: Cannot transition to non-D0 state from D3
[25568.448598] acpi INT33C4:00: Cannot transition to non-D0
state from D3 [25568.448602] acpi INT33C5:00: Cannot transition to non-D0 state from D3 [25568.448623] acpi device:41: Cannot transition to power state D3cold for parent in (unknown) [25568.448627] acpi INT33C6:00: Cannot transition to non-D0 state from D3 [25568.448890] pci_bus 0000:01: Allocating resources [25568.448905] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.449064] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.449472] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
With older kernel (3.13) I do not see these errors, so it is regression. Can you look at it? If it is needed, I can provide other logs, ACPI/DSTD dumps, etc.
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Signature · 2 lines

Pali Rohár
[email protected]

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

nick

2014-12-25 16:59 UTC #3 lore raw

Pali,
This was probably to either add better power management or enable some new features related to acpi. Can you send me the files they created in kernel 3.19 r1 as I can probably trace it back to the bad commit. Regards Nick

Quoted 5 lines · Pali Rohár

I know how to use git... first I wanted to report errors because maybe it could be known problem or somebody else can come with quick patch even without bisetcing (like for other problems which I reported).

Quoted 81 lines

Anyway those acpi devices which are mentioned in log do not exist in 3.13 kernel (I do not see them in /sys/devices)
Any idea why 3.19 kernel create new acpi devices which 3.13 kernel did not?
Quoted 73 lines · On Thursday 25 December 2014 05:28:27 nick wrote:
Pali,
Do you known how to run git bisect as this is probably the best way to continue. Otherwise, I can teach you how it's not hard if your willing to learn :). Cheers Nick
Quoted 67 lines · Pali Rohár
Hello!
With new 3.19-rc1 kernel every time when I open LID on my laptop, kernel prints these error lines to dmesg:
[25566.368133] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]]
*ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem. [25566.368134] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed register before interrupt [25566.368192] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem. [25566.368232] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.<4>[25568.446011] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.447018] pci_bus 0000:02: Allocating resources
[25568.447055] pci_bus 0000:03: Allocating resources
[25568.447135] pci_bus 0000:04: Allocating resources
[25568.447168] pci_bus 0000:05: Allocating resources
[25568.447195] pci_bus 0000:06: Allocating resources
[25568.447228] pci_bus 0000:0e: Allocating resources
[25568.447323] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bogus alignment [25568.447557] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.447735] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.447847] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.448399] i915 0000:00:02.0: BAR 6:
[??? 0x00000000 flags 0x2] has bogus alignment
[25568.448438] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bogus alignment [25568.448566] acpi MSFT1111:00: Cannot transition to power state D3cold for parent in (unknown) [25568.448572] acpi INT33C2:00: Cannot transition to non-D0 state from D3 [25568.448577] acpi MSFT0002:00: Cannot transition to power state D3cold for parent in (unknown) [25568.448581] acpi ELAN1010:00: Cannot transition to power state D3cold for parent in (unknown)
[25568.448587] acpi INT33C3:00: Cannot transition to non-D0
state from D3 [25568.448590] acpi INT33C0:00: Cannot
transition to non-D0 state from D3 [25568.448594] acpi
INT33C1:00: Cannot transition to non-D0 state from D3
[25568.448598] acpi INT33C4:00: Cannot transition to non-D0
state from D3 [25568.448602] acpi INT33C5:00: Cannot transition to non-D0 state from D3 [25568.448623] acpi device:41: Cannot transition to power state D3cold for parent in (unknown) [25568.448627] acpi INT33C6:00: Cannot transition to non-D0 state from D3 [25568.448890] pci_bus 0000:01: Allocating resources [25568.448905] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.449064] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.449472] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
With older kernel (3.13) I do not see these errors, so it is regression. Can you look at it? If it is needed, I can provide other logs, ACPI/DSTD dumps, etc.
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Pali Rohár

author

2014-12-27 08:19 UTC #4 lore raw

Hello,

in attachment is output of ls -l /sys/bus/acpi/devices from both 3.13 and 3.19 kernels.

Anyway Gabriele Mazzotta wrote me that new acpi devices could be created after commit faae404ebdc6bba (ACPICA: Add "Windows 2013" string to _OSI support).

Maybe this another output could help you:

$ cat /sys/bus/acpi/devices/INT33C5\:00/status
0
$ cat /sys/bus/acpi/devices/INT33C5\:00/power_state
(unknown)

Device INT33C5 is in that dmesg log:
acpi INT33C5:00: Cannot transition to non-D0 state from D3

And status 0 in sysnode could indicate that acpi device is not present right?

Quoted 93 lines · On Thursday 25 December 2014 17:59:36 nick wrote:

Pali,
This was probably to either add better power management or enable some new features related to acpi. Can you send me the files they created in kernel 3.19 r1 as I can probably trace it back to the bad commit. Regards Nick
Quoted 86 lines · Pali Rohár
I know how to use git... first I wanted to report errors because maybe it could be known problem or somebody else can come with quick patch even without bisetcing (like for other problems which I reported).
Anyway those acpi devices which are mentioned in log do not exist in 3.13 kernel (I do not see them in /sys/devices)
Any idea why 3.19 kernel create new acpi devices which 3.13 kernel did not?
Quoted 74 lines · On Thursday 25 December 2014 05:28:27 nick wrote:
Pali,
Do you known how to run git bisect as this is probably the best way to continue. Otherwise, I can teach you how it's not hard if your willing to learn :). Cheers Nick
Quoted 68 lines · Pali Rohár
Hello!
With new 3.19-rc1 kernel every time when I open LID on my laptop, kernel prints these error lines to dmesg:
[25566.368133] [drm:hsw_unclaimed_reg_detect.isra.6
[i915]] *ERROR* Unclaimed register detected. Please use
the i915.mmio_debug=1 to debug this problem.
[25566.368134] [drm:intel_uncore_check_errors [i915]]
*ERROR* Unclaimed register before interrupt
[25566.368192]
[drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem. [25566.368232] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.<4>[25568.446011] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.447018] pci_bus 0000:02: Allocating resources
[25568.447055] pci_bus 0000:03: Allocating resources
[25568.447135] pci_bus 0000:04: Allocating resources
[25568.447168] pci_bus 0000:05: Allocating resources
[25568.447195] pci_bus 0000:06: Allocating resources
[25568.447228] pci_bus 0000:0e: Allocating resources
[25568.447323] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bogus alignment [25568.447557] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.447735] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.447847] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.448399] i915 0000:00:02.0: BAR 6:
[??? 0x00000000 flags 0x2] has bogus alignment
[25568.448438] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bogus alignment [25568.448566] acpi MSFT1111:00: Cannot transition to power state D3cold for parent in (unknown) [25568.448572] acpi INT33C2:00: Cannot transition to non-D0 state from D3 [25568.448577] acpi MSFT0002:00: Cannot transition to power state D3cold for parent in (unknown) [25568.448581] acpi ELAN1010:00:
Cannot transition to power state D3cold for parent in (unknown) [25568.448587] acpi INT33C3:00: Cannot transition to non-D0 state from D3 [25568.448590] acpi INT33C0:00: Cannot transition to non-D0 state from D3
[25568.448594] acpi INT33C1:00: Cannot transition to
non-D0 state from D3 [25568.448598] acpi INT33C4:00:
Cannot transition to non-D0 state from D3 [25568.448602] acpi INT33C5:00: Cannot transition to non-D0 state from D3 [25568.448623] acpi device:41: Cannot transition to power state D3cold for parent in (unknown) [25568.448627] acpi INT33C6:00: Cannot transition to non-D0 state from D3 [25568.448890] pci_bus 0000:01: Allocating resources
[25568.448905] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bogus alignment [25568.449064] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.449472] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
With older kernel (3.13) I do not see these errors, so it is regression. Can you look at it? If it is needed, I can provide other logs, ACPI/DSTD dumps, etc.
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Signature · 2 lines

Pali Rohár
[email protected]

celkom 0
drwxr-xr-x 2 root root 0 dec 25 14:04 ./
drwxr-xr-x 4 root root 0 dec 25 14:04 ../
lrwxrwxrwx 1 root root 0 dec 25 14:04 ACPI0003:00 -> ../../../devices/LNXSYSTM:00/device:00/ACPI0003:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 DELLABCE:00 -> ../../../devices/LNXSYSTM:00/device:00/DELLABCE:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:0a -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:0b -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0a/device:0b/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:0c -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0c/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:0d -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0c/device:0d/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:0e -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0e/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:0f -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:0f/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:00 -> ../../../devices/LNXSYSTM:00/device:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:01 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:02 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:03 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:02/device:03/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:04 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:04/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:05 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:04/device:05/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:06 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:06/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:07 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:06/device:07/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:08 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:08/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:09 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:08/device:09/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:1a -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/device:12/device:1a/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:1b -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:1b/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:1c -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:1b/device:1c/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:1d -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:1b/device:1c/device:1d/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:1e -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:1b/device:1c/device:1d/device:1e/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:1f -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:1b/device:1c/device:1d/device:1f/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:10 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:11 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:12 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/device:12/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:13 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/device:12/device:13/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:14 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/device:12/device:14/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:15 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/device:12/device:15/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:16 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/device:12/device:16/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:17 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/device:12/device:17/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:18 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/device:12/device:18/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:19 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/device:12/device:19/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:2a -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:2a/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:2b -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:2b/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:2c -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:2c/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:2d -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:2d/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:2e -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:2e/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:2f -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:2f/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:20 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:1b/device:1c/device:1d/device:20/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:21 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:1b/device:1c/device:1d/device:21/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:22 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:1b/device:1c/device:1d/device:22/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:23 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:1b/device:1c/device:1d/device:22/device:23/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:24 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:1b/device:1c/device:1d/device:24/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:25 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:26 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:27 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:27/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:28 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:28/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:29 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:29/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:3a -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:3a/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:3b -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:3b/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:3c -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:3c/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:3d -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3d/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:3e -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3e/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:3f -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3e/device:3f/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:30 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:30/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:31 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:31/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:32 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:31/device:32/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:33 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:33/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:34 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:34/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:35 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:35/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:36 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:36/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:37 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:37/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:38 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:38/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:39 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:25/device:26/device:39/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:4a -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:49/device:4a/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:4b -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:4b/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:4c -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:4c/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:4d -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:4d/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:4e -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/device:4e/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:4f -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/device:4f/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:40 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3e/device:40/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:41 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3e/device:41/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:42 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3e/device:42/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:43 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3e/device:43/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:44 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3e/device:44/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:45 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3e/device:45/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:46 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:3e/device:46/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:47 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:47/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:48 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:48/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:49 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:49/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:50 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/device:50/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:51 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/device:51/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:52 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/device:52/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:53 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/device:53/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:54 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/device:54/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:55 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/device:55/ lrwxrwxrwx 1 root root 0 dec 25 14:04 device:56 -> ../../../devices/LNXSYSTM:00/device:56/
lrwxrwxrwx 1 root root 0 dec 25 14:04 device:57 -> ../../../devices/LNXSYSTM:00/device:57/
lrwxrwxrwx 1 root root 0 dec 25 14:04 DLLK05BD:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/DLLK05BD:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 DLL05BD:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/DLL05BD:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 INT0800:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/INT0800:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 INT3F0D:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/INT3F0D:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXCPU:00 -> ../../../devices/LNXSYSTM:00/LNXCPU:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXCPU:01 -> ../../../devices/LNXSYSTM:00/LNXCPU:01/
lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXCPU:02 -> ../../../devices/LNXSYSTM:00/LNXCPU:02/
lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXCPU:03 -> ../../../devices/LNXSYSTM:00/LNXCPU:03/
lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXCPU:04 -> ../../../devices/LNXSYSTM:00/LNXCPU:04/
lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXCPU:05 -> ../../../devices/LNXSYSTM:00/LNXCPU:05/
lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXCPU:06 -> ../../../devices/LNXSYSTM:00/LNXCPU:06/
lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXCPU:07 -> ../../../devices/LNXSYSTM:00/LNXCPU:07/
lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXPWRBN:00 -> ../../../devices/LNXSYSTM:00/LNXPWRBN:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXSYSTM:00 -> ../../../devices/LNXSYSTM:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXTHERM:00 -> ../../../devices/LNXSYSTM:00/device:56/LNXTHERM:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXVIDEO:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:49/LNXVIDEO:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 LNXVIDEO:01 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:01/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0A08:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0B00:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0B00:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0A:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0A:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0A:01 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0A:01/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0C:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0C:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0D:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0D:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0E:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0E:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0F:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0F:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0F:01 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0F:01/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0F:02 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0F:02/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0F:03 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0F:03/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0F:04 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0F:04/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0F:05 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0F:05/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0F:06 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0F:06/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C0F:07 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C0F:07/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C01:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/PNP0C01:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C02:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0C02:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C02:01 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0C02:01/ lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C02:02 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/PNP0C02:02/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C04:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0C04:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C09:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0C09:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0C14:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0C14:00/
lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0000:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0000:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0100:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0100:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0103:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0103:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0200:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0200:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 PNP0401:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/PNP0401:00/ lrwxrwxrwx 1 root root 0 dec 25 14:04 SMO8810:00 -> ../../../devices/LNXSYSTM:00/device:00/PNP0A08:00/SMO8810:00/

celkom 0
drwxr-xr-x 2 root root 0 dec 27 09:08 ./
drwxr-xr-x 4 root root 0 dec 27 09:08 ../
lrwxrwxrwx 1 root root 0 dec 27 09:08 ACPI0003:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 ALP0001:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ALP0001:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 ATML1000:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ATML1000:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 ATML2000:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ATML2000:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 BCM2E20:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C5:00/BCM2E20:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 CYP0001:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/CYP0001:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 DELLABCE:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/DELLABCE:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:0a -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:09/device:0a/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:0b -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0b/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:0c -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0b/device:0c/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:0d -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0d/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:0e -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0d/device:0e/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:0f -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0f/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:01 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:02 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:01/device:02/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:03 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:03/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:04 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:03/device:04/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:05 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:05/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:06 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:05/device:06/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:07 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:07/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:08 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:07/device:08/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:09 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:09/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:1a -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/device:14/device:15/device:1a/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:1b -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/device:14/device:15/device:1b/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:1c -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/device:14/device:15/device:1c/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:1d -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/device:14/device:15/device:1d/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:1e -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:1f -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e/device:1f/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:10 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0f/device:10/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:11 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:11/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:12 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:13 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:14 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/device:14/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:15 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/device:14/device:15/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:16 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/device:14/device:15/device:16/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:17 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/device:14/device:15/device:17/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:18 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/device:14/device:15/device:18/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:19 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:13/device:14/device:15/device:19/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:2a -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:2a/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:2b -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:2b/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:2c -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:2c/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:2d -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:2d/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:2e -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:2e/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:2f -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:2f/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:20 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e/device:1f/device:20/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:21 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e/device:1f/device:20/device:21/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:22 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e/device:1f/device:20/device:22/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:23 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e/device:1f/device:20/device:23/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:24 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e/device:1f/device:20/device:24/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:25 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e/device:1f/device:20/device:25/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:26 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e/device:1f/device:20/device:25/device:26/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:27 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1e/device:1f/device:20/device:27/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:28 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:29 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:3a -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:3a/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:3b -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:3b/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:3c -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:3c/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:3d -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:3d/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:3e -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:3e/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:3f -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:3f/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:30 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:30/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:31 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:31/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:32 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:32/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:33 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:33/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:34 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:34/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:35 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:34/device:35/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:36 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:36/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:37 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:37/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:38 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:38/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:39 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:28/device:29/device:39/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:4a -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/device:4a/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:4b -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/device:4b/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:4c -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/device:4c/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:4d -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4d/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:4e -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4e/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:4f -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4f/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:40 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:40/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:41 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C6:00/device:41/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:42 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C8:00/device:42/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:43 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C8:00/device:43/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:44 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:45 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/device:45/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:46 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/device:46/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:47 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/device:47/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:48 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/device:48/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:49 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/device:49/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:5a -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/device:5a/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:5b -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/device:5b/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:5c -> ../../../devices/LNXSYSTM:00/device:5c/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:50 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4f/device:50/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:51 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:51/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:52 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:52/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:53 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:53/
lrwxrwxrwx 1 root root 0 dec 27 09:08 device:54 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/device:54/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:55 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/device:55/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:56 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/device:56/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:57 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/device:57/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:58 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/device:58/ lrwxrwxrwx 1 root root 0 dec 27 09:08 device:59 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/device:59/ lrwxrwxrwx 1 root root 0 dec 27 09:08 DLLK05BD:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/DLLK05BD:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 DLL05BD:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/DLL05BD:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 EETI7900:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/EETI7900:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 ELAN1000:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ELAN1000:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 ELAN1001:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ELAN1001:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 ELAN1010:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/ELAN1010:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 ICV0A12:00 -> ../../../devices/LNXSYSTM:00/ICV0A12:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INTL9C60:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INTL9C60:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT0800:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/INT0800:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 INT3F0D:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/INT3F0D:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33A1:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/INT33A1:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33CA:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C2:00/INT33CA:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33CB:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C2:00/INT33CB:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33C0:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C0:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33C1:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C1:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33C2:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C2:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33C3:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33C4:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C4:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33C5:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C5:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33C6:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C6:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33C7:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C7:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33C8:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C8:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33C9:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C2:00/INT33C9:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33D0:00 -> ../../../devices/LNXSYSTM:00/INT33D0:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33D1:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C2:00/INT33D1:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33D7:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C2:00/INT33D7:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33E0:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C4:00/INT33E0:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 INT33E0:01 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C5:00/INT33E0:01/ lrwxrwxrwx 1 root root 0 dec 27 09:08 INT3420:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/INT3420:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXCPU:00 -> ../../../devices/LNXSYSTM:00/LNXCPU:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXCPU:01 -> ../../../devices/LNXSYSTM:00/LNXCPU:01/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXCPU:02 -> ../../../devices/LNXSYSTM:00/LNXCPU:02/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXCPU:03 -> ../../../devices/LNXSYSTM:00/LNXCPU:03/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXCPU:04 -> ../../../devices/LNXSYSTM:00/LNXCPU:04/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXCPU:05 -> ../../../devices/LNXSYSTM:00/LNXCPU:05/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXCPU:06 -> ../../../devices/LNXSYSTM:00/LNXCPU:06/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXCPU:07 -> ../../../devices/LNXSYSTM:00/LNXCPU:07/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXIOBAY:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:44/LNXIOBAY:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXPWRBN:00 -> ../../../devices/LNXSYSTM:00/LNXPWRBN:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXSYBUS:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXSYBUS:01 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:01/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXSYSTM:00 -> ../../../devices/LNXSYSTM:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXTHERM:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:01/LNXTHERM:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXVIDEO:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4f/LNXVIDEO:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 LNXVIDEO:01 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/
lrwxrwxrwx 1 root root 0 dec 27 09:08 MSFT0001:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/MSFT0001:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 MSFT0002:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/MSFT0002:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 MSFT1111:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C2:00/MSFT1111:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 NTRG0001:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C3:00/NTRG0001:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 NXP5442:00 -> ../../../devices/LNXSYSTM:00/NXP5442:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0A08:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0B00:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0B00:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0A:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0A:01 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:01/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0C:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0D:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0E:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0F:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0F:01 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:01/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0F:02 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:02/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0F:03 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:03/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0F:04 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:04/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0F:05 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:05/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0F:06 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:06/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C0F:07 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0F:07/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C01:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C01:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C01:01 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C01:01/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C02:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0C02:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C02:01 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0C02:01/ lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C02:02 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C02:02/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C02:03 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/PNP0C02:03/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C04:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0C04:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C09:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0C09:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0C14:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C14:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0000:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0000:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0100:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0100:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0103:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0103:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0200:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0200:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0401:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0401:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 PNP0501:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/PNP0501:00/ lrwxrwxrwx 1 root root 0 dec 27 09:08 SKTD000:00 -> ../../../devices/LNXSYSTM:00/SKTD000:00/
lrwxrwxrwx 1 root root 0 dec 27 09:08 SMO8810:00 -> ../../../devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/SMO8810:00/

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

nick

2014-12-27 17:31 UTC #5 lore raw

Pali,
This seems to be a likely culprit. Would you mind building a kernel before that commit was merged in order to test if it works.
Regards Nick

Quoted 16 lines · Pali Rohár

Hello,
in attachment is output of ls -l /sys/bus/acpi/devices from both 3.13 and 3.19 kernels.
Anyway Gabriele Mazzotta wrote me that new acpi devices could be created after commit faae404ebdc6bba (ACPICA: Add "Windows 2013" string to _OSI support).
Maybe this another output could help you:
$ cat /sys/bus/acpi/devices/INT33C5\:00/status
0
$ cat /sys/bus/acpi/devices/INT33C5\:00/power_state
(unknown)

Quoted 101 lines

Device INT33C5 is in that dmesg log:
acpi INT33C5:00: Cannot transition to non-D0 state from D3
And status 0 in sysnode could indicate that acpi device is not present right?
Quoted 93 lines · On Thursday 25 December 2014 17:59:36 nick wrote:
Pali,
This was probably to either add better power management or enable some new features related to acpi. Can you send me the files they created in kernel 3.19 r1 as I can probably trace it back to the bad commit. Regards Nick
Quoted 86 lines · Pali Rohár
I know how to use git... first I wanted to report errors because maybe it could be known problem or somebody else can come with quick patch even without bisetcing (like for other problems which I reported).
Anyway those acpi devices which are mentioned in log do not exist in 3.13 kernel (I do not see them in /sys/devices)
Any idea why 3.19 kernel create new acpi devices which 3.13 kernel did not?
Quoted 74 lines · On Thursday 25 December 2014 05:28:27 nick wrote:
Pali,
Do you known how to run git bisect as this is probably the best way to continue. Otherwise, I can teach you how it's not hard if your willing to learn :). Cheers Nick
Quoted 68 lines · Pali Rohár
Hello!
With new 3.19-rc1 kernel every time when I open LID on my laptop, kernel prints these error lines to dmesg:
[25566.368133] [drm:hsw_unclaimed_reg_detect.isra.6
[i915]] *ERROR* Unclaimed register detected. Please use
the i915.mmio_debug=1 to debug this problem.
[25566.368134] [drm:intel_uncore_check_errors [i915]]
*ERROR* Unclaimed register before interrupt
[25566.368192]
[drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem. [25566.368232] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.<4>[25568.446011] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
[25568.447018] pci_bus 0000:02: Allocating resources
[25568.447055] pci_bus 0000:03: Allocating resources
[25568.447135] pci_bus 0000:04: Allocating resources
[25568.447168] pci_bus 0000:05: Allocating resources
[25568.447195] pci_bus 0000:06: Allocating resources
[25568.447228] pci_bus 0000:0e: Allocating resources
[25568.447323] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bogus alignment [25568.447557] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.447735] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.447847] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.448399] i915 0000:00:02.0: BAR 6:
[??? 0x00000000 flags 0x2] has bogus alignment
[25568.448438] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bogus alignment [25568.448566] acpi MSFT1111:00: Cannot transition to power state D3cold for parent in (unknown) [25568.448572] acpi INT33C2:00: Cannot transition to non-D0 state from D3 [25568.448577] acpi MSFT0002:00: Cannot transition to power state D3cold for parent in (unknown) [25568.448581] acpi ELAN1010:00:
Cannot transition to power state D3cold for parent in (unknown) [25568.448587] acpi INT33C3:00: Cannot transition to non-D0 state from D3 [25568.448590] acpi INT33C0:00: Cannot transition to non-D0 state from D3
[25568.448594] acpi INT33C1:00: Cannot transition to
non-D0 state from D3 [25568.448598] acpi INT33C4:00:
Cannot transition to non-D0 state from D3 [25568.448602] acpi INT33C5:00: Cannot transition to non-D0 state from D3 [25568.448623] acpi device:41: Cannot transition to power state D3cold for parent in (unknown) [25568.448627] acpi INT33C6:00: Cannot transition to non-D0 state from D3 [25568.448890] pci_bus 0000:01: Allocating resources
[25568.448905] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bogus alignment [25568.449064] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment [25568.449472] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bogus alignment
With older kernel (3.13) I do not see these errors, so it is regression. Can you look at it? If it is needed, I can provide other logs, ACPI/DSTD dumps, etc.
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

Rafael J. Wysocki

2014-12-27 20:01 UTC #6 lore raw

In reply to Pali Rohár

Quoted 11 lines · Pali Rohár

Hello,
in attachment is output of ls -l /sys/bus/acpi/devices from both 3.13 and 3.19 kernels.
Anyway Gabriele Mazzotta wrote me that new acpi devices could be created after commit faae404ebdc6bba (ACPICA: Add "Windows 2013" string to _OSI support).
Maybe this another output could help you:

Quoted 7 lines

$ cat /sys/bus/acpi/devices/INT33C5\:00/status
0
$ cat /sys/bus/acpi/devices/INT33C5\:00/power_state
(unknown)
Device INT33C5 is in that dmesg log:
acpi INT33C5:00: Cannot transition to non-D0 state from D3

The appended patch should make these messages go away, please test.

Quoted 2 lines

And status 0 in sysnode could indicate that acpi device is not present right?

That's correct.

---
 drivers/acpi/device_pm.c |    7 ++++---
 include/acpi/acpi_bus.h  |    3 ++-
 2 files changed, 6 insertions(+), 4 deletions(-)

include/acpi/acpi_bus.h +2 -1

Index: linux-pm/include/acpi/acpi_bus.h
===================================================================
@@ -589,7 +589,8 @@ static inline u32 acpi_target_system_sta
 
 static inline bool acpi_device_power_manageable(struct acpi_device *adev)
 {
-	return adev->flags.power_manageable;
+	return adev->flags.power_manageable
+		&& (adev->status.present || adev->status.functional);
 }
 
 static inline bool acpi_device_can_wakeup(struct acpi_device *adev)

drivers/acpi/device_pm.c +4 -3

Index: linux-pm/drivers/acpi/device_pm.c
===================================================================
@@ -68,7 +68,8 @@ int acpi_device_get_power(struct acpi_de
 {
 	int result = ACPI_STATE_UNKNOWN;
 
-	if (!device || !state)
+	if (!device || !state
+	    || !(device->status.present || device->status.functional))
 		return -EINVAL;
 
 	if (!device->flags.power_manageable) {

@@ -156,7 +157,7 @@ int acpi_device_set_power(struct acpi_de
 	int result = 0;
 	bool cut_power = false;
 
-	if (!device || !device->flags.power_manageable
+	if (!device || !acpi_device_power_manageable(device)
 	    || (state < ACPI_STATE_D0) || (state > ACPI_STATE_D3_COLD))
 		return -EINVAL;

@@ -361,7 +362,7 @@ bool acpi_bus_power_manageable(acpi_hand
 	int result;
 
 	result = acpi_bus_get_device(handle, &device);
-	return result ? false : device->flags.power_manageable;
+	return result ? false : acpi_device_power_manageable(device);
 }
 EXPORT_SYMBOL(acpi_bus_power_manageable);

Joe Perches

2014-12-27 20:17 UTC #7 lore raw

On Sat, 2014-12-27 at 21:22 +0100, Rafael J. Wysocki wrote:
[]

include/acpi/acpi_bus.h static inline u32 acpi_target_system_sta · line 593

Quoted 8 lines

+++ linux-pm/include/acpi/acpi_bus.h

include/acpi/acpi_bus.h +2 -1

@@ -589,7 +589,8 @@ static inline u32 acpi_target_system_sta
 
 static inline bool acpi_device_power_manageable(struct acpi_device *adev)
 {
-	return adev->flags.power_manageable;
+	return adev->flags.power_manageable
+		&& (adev->status.present || adev->status.functional);

Most code in the kernel has these logical
continuations at the end of the previous line.

Review static inline u32 acpi_target_system_sta · line 594

Quoted 1 line

(quoted diff) +1 -0

+++ linux-pm/drivers/acpi/device_pm.c

[]

drivers/acpi/device_pm.c bool acpi_bus_power_manageable(acpi_hand · line 365

Quoted 6 lines

drivers/acpi/device_pm.c +1 -1

@@ -361,7 +362,7 @@ bool acpi_bus_power_manageable(acpi_hand
 	int result;
 
 	result = acpi_bus_get_device(handle, &device);
-	return result ? false : device->flags.power_manageable;
+	return result ? false : acpi_device_power_manageable(device);

This might read better as:

	if (acpi_bus_get_device(handle, &device))
		return false;

	return acpi_device_power_manageable(device);

_______________________________________________
dri-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/dri-devel

Pali Rohár

author

2015-04-06 10:02 UTC #8 lore raw

4.0-rc6 errors when opening LID

In reply to Rafael J. Wysocki

Quoted 74 lines · On Saturday 27 December 2014 21:22:56 Rafael J. Wysocki wrote:

Quoted 11 lines · Pali Rohár
Hello,
in attachment is output of ls -l /sys/bus/acpi/devices from both 3.13 and 3.19 kernels.
Anyway Gabriele Mazzotta wrote me that new acpi devices could be created after commit faae404ebdc6bba (ACPICA: Add "Windows 2013" string to _OSI support).
Maybe this another output could help you:
Quoted 7 lines
$ cat /sys/bus/acpi/devices/INT33C5\:00/status
0
$ cat /sys/bus/acpi/devices/INT33C5\:00/power_state
(unknown)
Device INT33C5 is in that dmesg log:
acpi INT33C5:00: Cannot transition to non-D0 state from D3
The appended patch should make these messages go away, please test.
Quoted 2 lines
And status 0 in sysnode could indicate that acpi device is not present right?
That's correct.
---
 drivers/acpi/device_pm.c |    7 ++++---
 include/acpi/acpi_bus.h  |    3 ++-
 2 files changed, 6 insertions(+), 4 deletions(-)
Index: linux-pm/include/acpi/acpi_bus.h
==============================================================
===== --- linux-pm.orig/include/acpi/acpi_bus.h
+++ linux-pm/include/acpi/acpi_bus.h
include/acpi/acpi_bus.h +2 -1
@@ -589,7 +589,8 @@ static inline u32 acpi_target_system_sta
 
 static inline bool acpi_device_power_manageable(struct
 acpi_device *adev) {
-	return adev->flags.power_manageable;
+	return adev->flags.power_manageable
+		&& (adev->status.present || adev->status.functional);
 }
 
 static inline bool acpi_device_can_wakeup(struct acpi_device
*adev) Index: linux-pm/drivers/acpi/device_pm.c
==============================================================
===== --- linux-pm.orig/drivers/acpi/device_pm.c
+++ linux-pm/drivers/acpi/device_pm.c
drivers/acpi/device_pm.c +3 -2
@@ -68,7 +68,8 @@ int acpi_device_get_power(struct acpi_de
 {
 	int result = ACPI_STATE_UNKNOWN;
 
-	if (!device || !state)
+	if (!device || !state
+	    || !(device->status.present ||
 device->status.functional)) return -EINVAL;
 
 	if (!device->flags.power_manageable) {
@@ -156,7 +157,7 @@ int acpi_device_set_power(struct acpi_de
 	int result = 0;
 	bool cut_power = false;
 
-	if (!device || !device->flags.power_manageable
+	if (!device || !acpi_device_power_manageable(device)
 
 	    || (state < ACPI_STATE_D0) || (state >
 	    || ACPI_STATE_D3_COLD))
drivers/acpi/device_pm.c +0 -0
 		return -EINVAL;

drivers/acpi/device_pm.c bool acpi_bus_power_manageable(acpi_hand · line 367

Quoted 7 lines

drivers/acpi/device_pm.c +1 -1

@@ -361,7 +362,7 @@ bool acpi_bus_power_manageable(acpi_hand
 	int result;
 
 	result = acpi_bus_get_device(handle, &device);
-	return result ? false : device->flags.power_manageable;
+	return result ? false :
 acpi_device_power_manageable(device); }
 EXPORT_SYMBOL(acpi_bus_power_manageable);

Hello Rafael,

sorry for long delay. Now I tested your patch on top of 4.0-rc6 version and I'm still getting one acpi error message (and lot of others) in dmesg each time I open LID of my laptop:

kernel: [ 62.016803] acpi device:41: Cannot transition to power
state D3cold for parent in (unknown)

If it helps here is more info about that acpi "device:41":

/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C6:00/device:41

$ grep "" *
adr:0x00000001
path:\_SB_.PCI0.SDHC.WI01
power_state:D0
status:15

And here about parent ("../")

/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/INT33C6:00

$ grep "" *
adr:0x00170000
hid:INT33C6
modalias:acpi:INT33C6:PNP0D40:
path:\_SB_.PCI0.SDHC
status:0
uevent:MODALIAS=acpi:INT33C6:PNP0D40:
uid:1

It is OK, that one device has status 0 (not present) and its child has non zero status? Looks like here is problem...

Signature · 2 lines

Pali Rohár
[email protected]

Rafael J. Wysocki

2014-12-26 14:50 UTC #9 lore raw

In reply to Pali Rohár

Quoted 10 lines · Pali Rohár

--nextPart5943893.pKyMBm5Emp
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Hello!
With new 3.19-rc1 kernel every time when I open LID on my laptop, kernel pr= ints these error lines to dmesg:

Does your syste suspend when the lid is closed and resume when it is open?

Quoted 9 lines

[25566.368133] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaim=
ed register detected. Please use the i915.mmio_debug=3D1 to debug this prob=
lem.
[25566.368134] [drm:intel_uncore_check_errors [i915]] *ERROR* Unclaimed reg=
ister before interrupt
[25566.368192] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaim=
ed register detected. Please use the i915.mmio_debug=3D1 to debug this prob=
lem.
[25566.368232] [drm:hsw_unclaimed_reg_detect.isra.6 [i915]] *ERROR* Unclaim=

Quoted 4 lines

ed register detected. Please use the i915.mmio_debug=3D1 to debug this prob= lem.<4>[25568.446011] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2]= =20
has bogus alignment

The above messages are from i915 and don't seem to be related to ACPI.

Quoted 17 lines

[25568.447018] pci_bus 0000:02: Allocating resources
[25568.447055] pci_bus 0000:03: Allocating resources
[25568.447135] pci_bus 0000:04: Allocating resources
[25568.447168] pci_bus 0000:05: Allocating resources
[25568.447195] pci_bus 0000:06: Allocating resources
[25568.447228] pci_bus 0000:0e: Allocating resources
[25568.447323] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bog=
us alignment
[25568.447557] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bog=
us alignment
[25568.447735] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bog=
us alignment
[25568.447847] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bog=
us alignment
[25568.448399] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bog=
us alignment
[25568.448438] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bog=

Quoted 1 line

us alignment

The above too.

Quoted 7 lines

[25568.448566] acpi MSFT1111:00: Cannot transition to power state D3cold fo=
r parent in (unknown)
[25568.448572] acpi INT33C2:00: Cannot transition to non-D0 state from D3
[25568.448577] acpi MSFT0002:00: Cannot transition to power state D3cold fo=
r parent in (unknown)
[25568.448581] acpi ELAN1010:00: Cannot transition to power state D3cold fo=

r parent in (unknown)

Quoted 8 lines

[25568.448587] acpi INT33C3:00: Cannot transition to non-D0 state from D3
[25568.448590] acpi INT33C0:00: Cannot transition to non-D0 state from D3
[25568.448594] acpi INT33C1:00: Cannot transition to non-D0 state from D3
[25568.448598] acpi INT33C4:00: Cannot transition to non-D0 state from D3
[25568.448602] acpi INT33C5:00: Cannot transition to non-D0 state from D3
[25568.448623] acpi device:41: Cannot transition to power state D3cold for =
parent in (unknown)
[25568.448627] acpi INT33C6:00: Cannot transition to non-D0 state from D3

All of the above mean that power transitions were not carried out for some devices, because they were in unexpected power states to start with.

They are devices on the Intel LPSS as far as I can say (CCing Mika and Andy).

Quoted 9 lines

[25568.448890] pci_bus 0000:01: Allocating resources
[25568.448905] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bog=
us alignment
[25568.449064] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bog=
us alignment
[25568.449472] i915 0000:00:02.0: BAR 6: [??? 0x00000000 flags 0x2] has bog=

us alignment

With older kernel (3.13) I do not see these errors, so it is regression.

It only is a regression if it leads to functional problems. Do you see any?

Quoted 2 lines

Ca=n you look at it? If it is needed, I can provide other logs, ACPI/DSTD dump= s, etc.

It looks like 3.13 didn't try to use some devices that are now used in 3.19-rc1 and something doesn't work entirely as expected.

Signature · 2 lines

I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.

Pali Rohár

author

2014-12-26 15:52 UTC #10 lore raw

Quoted 8 lines · On Friday 26 December 2014 16:12:49 Rafael J. Wysocki wrote:

Quoted 7 lines · Pali Rohár
--nextPart5943893.pKyMBm5Emp
Content-Type: Text/Plain;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Quoted 9 lines

Quoted 6 lines
Hello!
With new 3.19-rc1 kernel every time when I open LID on my laptop, kernel pr=
ints these error lines to dmesg:
Does your syste suspend when the lid is closed and resume when it is open?

No, I disabled all autosuspend and autohibernate settings. When I close LID system is running.

Quoted 20 lines

Quoted 13 lines

[25568.448566] acpi MSFT1111:00: Cannot transition to power
state D3cold fo= r parent in (unknown)
[25568.448572] acpi INT33C2:00: Cannot transition to non-D0
state from D3 [25568.448577] acpi MSFT0002:00: Cannot
transition to power state D3cold fo= r parent in (unknown)
[25568.448581] acpi ELAN1010:00: Cannot transition to power
state D3cold fo= r parent in (unknown)
[25568.448587] acpi INT33C3:00: Cannot transition to non-D0
state from D3 [25568.448590] acpi INT33C0:00: Cannot
transition to non-D0 state from D3 [25568.448594] acpi
INT33C1:00: Cannot transition to non-D0 state from D3
[25568.448598] acpi INT33C4:00: Cannot transition to non-D0

Quoted 6 lines

state from D3 [25568.448602] acpi INT33C5:00: Cannot transition to non-D0 state from D3 [25568.448623] acpi device:41: Cannot transition to power state D3cold for = parent in (unknown)
[25568.448627] acpi INT33C6:00: Cannot transition to non-D0
state from D3

Quoted 7 lines

All of the above mean that power transitions were not carried out for some devices, because they were in unexpected power states to start with.
They are devices on the Intel LPSS as far as I can say (CCing Mika and Andy).

Just to note: all above acpi devices do not exist in 3.13 kernel, at least I do not see them in /sys/bus/acpi/.

Quoted 8 lines

[25568.448890] pci_bus 0000:01: Allocating resources
[25568.448905] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bog= us alignment
[25568.449064] i915 0000:00:02.0: BAR 6: [??? 0x00000000
flags 0x2] has bog= us alignment
[25568.449472] i915 0000:00:02.0: BAR 6: [??? 0x00000000

flags 0x2] has bog= us alignment

Quoted 6 lines

Quoted 2 lines
With older kernel (3.13) I do not see these errors, so it is regression.
It only is a regression if it leads to functional problems. Do you see any?

Ok. I do not see functional problems, but I see above messages in dmesg log every time when I open LID.

Quoted 6 lines

Quoted 2 lines
Ca=n you look at it? If it is needed, I can provide other logs, ACPI/DSTD dump= s, etc.
It looks like 3.13 didn't try to use some devices that are now used in 3.19-rc1 and something doesn't work entirely as expected.

Signature · 2 lines

Pali Rohár
[email protected]

_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx