Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2013-01-20 Thread Roland Gruber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Ben,

On 19.01.2013 23:12, Ben Hutchings wrote:
 Apologies for the late response.  Does this bug still occur in 
 linux-image-3.2.0-4-amd64, version 3.2.35-2?
 
 If so, does it also occur in linux-image-3.7-trunk-amd64, from the 
 experimental suite?

unfortunately, both 3.2.0-4-amd64 and 3.7-trunk-amd64 still have the
problem. :(

I run setpci -s 00:02.0 F4.B=00 in /etc/rc.local to switch on backlight.


Best regards

Roland
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlD74fYACgkQq/ywNCsrGZ4ocQCfXsfe0MuUXCIODhkDaMUfdhIF
BGcAn3DhMczAB2pBMgHLRi4/yx8NAkqX
=6eTL
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2013-01-20 Thread Ben Hutchings
Control: tag -1 moreinfo

On Sun, 2013-01-20 at 13:24 +0100, Roland Gruber wrote:
 Hi Ben,
 
 On 19.01.2013 23:12, Ben Hutchings wrote:
  Apologies for the late response.  Does this bug still occur in 
  linux-image-3.2.0-4-amd64, version 3.2.35-2?
  
  If so, does it also occur in linux-image-3.7-trunk-amd64, from the 
  experimental suite?
 
 unfortunately, both 3.2.0-4-amd64 and 3.7-trunk-amd64 still have the
 problem. :(
 
 I run setpci -s 00:02.0 F4.B=00 in /etc/rc.local to switch on backlight.

OK, please file a bug report at https://bugs.freedesktop.org/ under
product 'DRI', component 'DRM/Intel'.  Let us know the bug number or URL
so we can track it.

This page explains what information you should include:
https://01.org/linuxgraphics/documentation/how-report-bugs-0

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.


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


Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2013-01-20 Thread Roland Gruber
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Ben,

On 20.01.2013 16:05, Ben Hutchings wrote:
 OK, please file a bug report at https://bugs.freedesktop.org/
 under product 'DRI', component 'DRM/Intel'.  Let us know the bug
 number or URL so we can track it.

bug number is 59628.


- -- 

Best regards

Roland
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlD8EVwACgkQq/ywNCsrGZ7JMACfQblpPCK+ULhJYoUc0xwbfNc/
uQYAn301/O9mibLz0HXe0mneTIzaZkWC
=vyxN
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2013-01-20 Thread Ben Hutchings
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=59628
Control: tag -1 - moreinfo

On Sun, 2013-01-20 at 16:46 +0100, Roland Gruber wrote:
 Hi Ben,
 
 On 20.01.2013 16:05, Ben Hutchings wrote:
  OK, please file a bug report at https://bugs.freedesktop.org/
  under product 'DRI', component 'DRM/Intel'.  Let us know the bug
  number or URL so we can track it.
 
 bug number is 59628.

Thanks.

Ben.

-- 
Ben Hutchings
Never attribute to conspiracy what can adequately be explained by stupidity.


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


Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2013-01-19 Thread Ben Hutchings
Control: tag -1 moreinfo

On Sun, 2012-07-08 at 12:23 +0200, Roland Gruber wrote:
 Package: src
 Version: 3.2.20-1
 Severity: important
 
 Hi,
 
 the screen turns to black at the beginning of the boot process.
 I have to run setpci -s 00:02.0 F4.B=00 via ssh to see anything.
 This is similar to bug 668274.
 
 Booting with the 2.6 kernel does not show this problem.
[...]

Apologies for the late response.  Does this bug still occur in
linux-image-3.2.0-4-amd64, version 3.2.35-2?

If so, does it also occur in linux-image-3.7-trunk-amd64, from the
experimental suite?

Ben.

-- 
Ben Hutchings
All the simple programs have been written, and all the good names taken.


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


Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2013-01-08 Thread Nathan Schulte
Package: src:linux
Version: 3.2.35-2
Followup-For: Bug #680737

I'm having the same issue with a Dell Vostro 1500 laptop; specs below.

Gedalya geda...@gedalya.net noted that his/her issue seemed to be related to 
brightness and was simply a matter of the brightness being turned all of the 
way down; that is not the case here.  I can change the brightness of the screen 
using the hotkeys and notice the backlight changing.

My issue, and I suspect the author's, is a modesetting issue.  Sometimes I 
don't experience this issue and I am dropped to a console as expected; most 
other times I do experience the issue, and once udev loads my screen flickers 
and I'm presented with a black screen.

Using the i915.modeset=0 as a kernel parameter indeed drops me to a standard 
80x25 console, but that isn't suitable for me.

The ArchWiki has a few workarounds:

1) Placing i915 in the initramfs.
2) Using the kernel parameter video=SVIDEO-1:d.

I can confirm that both of these work for my hardware, allowing me to use 
modesetting with i915.

I just want to note that this bug still exists in my version.  I will test 
newer kernels from experimental, but I suspect they will resolve this issue.

--
Nate

-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-ker...@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-14) ) #1 SMP Debian 3.2.35-2

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/sda2_crypt ro quiet 
video=SVIDEO-1:d

** Not tainted

** Kernel log:
[   14.013235] ACPI: Lid Switch [LID0]
[   14.013301] input: Power Button as 
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
[   14.013306] ACPI: Power Button [PWRB]
[   14.013367] input: Sleep Button as 
/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input3
[   14.013371] ACPI: Sleep Button [SLPB]
[   14.013460] ACPI: Requesting acpi_cpufreq
[   14.016114] Monitor-Mwait will be used to enter C-1 state
[   14.016124] Monitor-Mwait will be used to enter C-2 state
[   14.016130] Monitor-Mwait will be used to enter C-3 state
[   14.016135] Marking TSC unstable due to TSC halts in idle
[   14.016149] ACPI: acpi_idle registered with cpuidle
[   14.016945] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4
[   14.016951] ACPI: Power Button [PWRF]
[   14.017994] Switching to clocksource hpet
[   14.171977] wmi: Mapper loaded
[   14.209602] dcdbas dcdbas: Dell Systems Management Base Driver (version 
5.6.0-3.2)
[   14.248777] input: PC Speaker as /devices/platform/pcspkr/input/input5
[   14.395409] ACPI: Battery Slot [BAT1] (battery present)
[   14.402152] ACPI: AC Adapter [ACAD] (on-line)
[   14.496229] iTCO_vendor_support: vendor-support=0
[   14.513811] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[   14.513934] iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x1060)
[   14.514012] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   14.556558] ACPI: resource :00:1f.3 [io  0x1c20-0x1c3f] conflicts with 
ACPI region SMBI [io 0x1c20-0x1c2f]
[   14.556562] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   14.685496] Error: Driver 'pcspkr' is already registered, aborting...
[   14.727903] [drm] Initialized drm 1.1.0 20060810
[   14.730832] input: Dell WMI hotkeys as /devices/virtual/input/input6
[   14.811105] cfg80211: Calling CRDA to update world regulatory domain
[   14.909108] i915 :00:02.0: setting latency timer to 64
[   14.953273] mtrr: type mismatch for d000,1000 old: write-back new: 
write-combining
[   14.953277] [drm] MTRR allocation failed.  Graphics performance may suffer.
[   14.953702] i915 :00:02.0: irq 46 for MSI/MSI-X
[   14.953709] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   14.953711] [drm] Driver supports precise vblank timestamp query.
[   14.953761] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   15.005622] fixme: max PWM is zero.
[   15.210813] brcmsmac :06:00.0: bus 6 slot 0 func 0 irq 11
[   15.210873] brcmsmac :06:00.0: setting latency timer to 64
[   15.276400] [drm] initialized overlay support
[   15.276447] [drm] forcing SVIDEO-1 connector OFF
[   15.293276] fbcon: inteldrmfb (fb0) is primary device
[   15.445199] brcmsmac :06:00.0: firmware: agent loaded brcm/bcm43xx-0.fw 
into memory
[   15.459275] brcmsmac :06:00.0: firmware: agent loaded 
brcm/bcm43xx_hdr-0.fw into memory
[   15.494360] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   15.679748] input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input7
[   15.713810] Console: switching to colour frame buffer device 160x50
[   15.721897] input: AlpsPS/2 ALPS GlidePoint as 
/devices/platform/i8042/serio1/input/input8
[   15.723384] fb0: inteldrmfb frame buffer device
[   15.723390] drm: registered panic notifier
[   15.744915] acpi device:08: registered as cooling_device2
[   15.745217] input: Video Bus as 

Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2013-01-08 Thread Julien Cristau
On Tue, Jan  8, 2013 at 11:28:16 -0600, Nathan Schulte wrote:

 My issue, and I suspect the author's, is a modesetting issue.  Sometimes I 
 don't experience this issue and I am dropped to a console as expected; most 
 other times I do experience the issue, and once udev loads my screen flickers 
 and I'm presented with a black screen.
 
 Using the i915.modeset=0 as a kernel parameter indeed drops me to a standard 
 80x25 console, but that isn't suitable for me.
 
 The ArchWiki has a few workarounds:
 
 1) Placing i915 in the initramfs.
 2) Using the kernel parameter video=SVIDEO-1:d.
 
 I can confirm that both of these work for my hardware, allowing me to use 
 modesetting with i915.
 
 I just want to note that this bug still exists in my version.  I will test 
 newer kernels from experimental, but I suspect they will resolve this issue.
 
Please post a dmesg without the video kernel param, and with drm.debug=6
instead.

Thanks,
Julien


signature.asc
Description: Digital signature


Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2013-01-08 Thread Julien Cristau
On Tue, Jan  8, 2013 at 13:28:12 -0600, Nathan Schulte wrote:

 On Tue, Jan 8, 2013 at 12:39 PM, Julien Cristau jcris...@debian.org wrote:
  Please post a dmesg without the video kernel param, and with drm.debug=6
  instead.
 
 As you wish!
 
Thanks.  That seems to detect the SVIDEO as consistently disconnected,
so I don't know why forcing it off makes a difference :/

Cheers,
Julien


signature.asc
Description: Digital signature


Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2013-01-08 Thread Nathan Schulte
On Tue, Jan 8, 2013 at 1:52 PM, Julien Cristau jcris...@debian.org wrote:
 Thanks.  That seems to detect the SVIDEO as consistently disconnected,
 so I don't know why forcing it off makes a difference :/

Attached is the dmesg with drm.debug=6 and video=SVIDEO-1:d

It's interesting that the original dmesg contains these lines, but
perhaps they're to be expected as part of the procedure to detect a
display on the S-Video connector.

[   12.676051] [drm:intel_tv_detect_type], TV detected: c00c7, 7faa
[   12.676059] [drm:intel_tv_detect_type], Unrecognised TV connection

Also, the attached dmesg has this irq output, whereas the initial one does not.

13.540192] [drm:i915_driver_irq_handler], pipe B underrun

I don't know anything about these codes; I couldn't even find
information about the video= options supported.  Any ideas on where I
can look to help?

--
Nate


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2013-01-08 Thread Nathan Schulte
found 680737 3.2.35-2
found 680737 3.7.1-1~experimental.2
quit

Nathan Schulte wrote:
 I just want to note that this bug still exists in my version.  I will test 
 newer kernels from experimental, but I suspect they will resolve this issue.

I tried with 3.7-trunk from experimental.  It appears the same issue
exists there as well, and using video=SVIDEO-1:d appears to workaround
as well.  I have not tried the i915 module in initramfs, but I suspect
it will workaround too.

I have dmesg's from both of these boots, if needed.

Lastly, I had a successful boot without a workaround; I didn't save
the dmesg!  I will try booting with drm.debug=6 until it works.

--
Nate


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2013-01-08 Thread Nathan Schulte
Apologies for all of the messages; I should have waited and sent one
at a time.  Oh well.

Interestingly: I hibernated the machine while booting with the
3.7-trunk kernel without any workarounds.  Upon coming back from the
hibernate, the display/console are working as expected.

--
Nate


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2012-07-16 Thread Gedalya
Package: src
Version: 3.2.21-3
Followup-For: Bug #680737

I think this is the same problem here.. using an HP dm4t-1200 laptop.
The backlight is set to zero brightness as soon as the kernel begins to load.
In my case I can set the brightness higher by simply using the appropriate fn
key combination, but until then everything looks black.

It looks to me like the following is the fix:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=7bd90909bbf9ce7c40e1da3d72b97b93839c188a
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=4dca20efb1a9c2efefc28ad2867e5d6c3f5e1955

found some discussion here
https://bbs.archlinux.org/viewtopic.php?id=131747




-- Package-specific info:
** Version:
Linux version 3.2.0-3-amd64 (Debian 3.2.21-3) (debian-ker...@lists.debian.org) 
(gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Thu Jun 28 09:07:26 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-3-amd64 root=/dev/mapper/dml_vg0-rootfs ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[126929.403902] Disabling non-boot CPUs ...
[126929.507481] CPU 1 is now offline
[126929.611451] CPU 2 is now offline
[126929.715414] CPU 3 is now offline
[126929.716044] Extended CMOS year: 2000
[126929.716255] ACPI: Low-level resume complete
[126929.716317] PM: Restoring platform NVS memory
[126929.716907] Extended CMOS year: 2000
[126929.716953] Enabling non-boot CPUs ...
[126929.717127] Booting Node 0 Processor 1 APIC 0x1
[126929.717128] smpboot cpu 1: start_ip = 98000
[126929.728155] Calibrating delay loop (skipped) already calibrated this CPU
[126929.748519] NMI watchdog enabled, takes one hw-pmu counter.
[126929.748862] CPU1 is up
[126929.749006] Booting Node 0 Processor 2 APIC 0x4
[126929.749007] smpboot cpu 2: start_ip = 98000
[126929.760034] Calibrating delay loop (skipped) already calibrated this CPU
[126929.780482] NMI watchdog enabled, takes one hw-pmu counter.
[126929.780840] CPU2 is up
[126929.781030] Booting Node 0 Processor 3 APIC 0x5
[126929.781031] smpboot cpu 3: start_ip = 98000
[126929.792056] Calibrating delay loop (skipped) already calibrated this CPU
[126929.812621] NMI watchdog enabled, takes one hw-pmu counter.
[126929.813138] CPU3 is up
[126929.815702] ACPI: Waking up from system sleep state S3
[126930.140757] i915 :00:02.0: restoring config space at offset 0x1 (was 
0x97, writing 0x900407)
[126930.140819] ehci_hcd :00:1a.0: restoring config space at offset 0x1 
(was 0x296, writing 0x292)
[126930.140853] ehci_hcd :00:1a.0: wake-up capability disabled by ACPI
[126930.140857] ehci_hcd :00:1a.0: PME# disabled
[126930.140881] snd_hda_intel :00:1b.0: restoring config space at offset 
0x1 (was 0x16, writing 0x12)
[126930.140983] ehci_hcd :00:1d.0: restoring config space at offset 0x1 
(was 0x296, writing 0x292)
[126930.141008] ehci_hcd :00:1d.0: wake-up capability disabled by ACPI
[126930.141013] ehci_hcd :00:1d.0: PME# disabled
[126930.141025] pci :00:1e.0: restoring config space at offset 0xa (was 
0x, writing 0x0)
[126930.141099] ahci :00:1f.2: restoring config space at offset 0x1 (was 
0x2b7, writing 0x2b00407)
[126930.141213] r8169 :01:00.0: restoring config space at offset 0x1 (was 
0x17, writing 0x100407)
[126930.141301] brcmsmac :02:00.0: restoring config space at offset 0xf 
(was 0x100, writing 0x10a)
[126930.141320] brcmsmac :02:00.0: restoring config space at offset 0x4 
(was 0x4, writing 0xb244)
[126930.141326] brcmsmac :02:00.0: restoring config space at offset 0x3 
(was 0x0, writing 0x10)
[126930.141332] brcmsmac :02:00.0: restoring config space at offset 0x1 
(was 0x10, writing 0x16)
[126930.141454] PM: early resume of devices complete after 0.746 msecs
[126930.141561] i915 :00:02.0: setting latency timer to 64
[126930.141567] ehci_hcd :00:1a.0: PCI INT A - GSI 16 (level, low) - IRQ 
16
[126930.141574] ehci_hcd :00:1a.0: setting latency timer to 64
[126930.141606] snd_hda_intel :00:1b.0: PCI INT A - GSI 22 (level, low) - 
IRQ 22
[126930.141611] snd_hda_intel :00:1b.0: setting latency timer to 64
[126930.141617] ehci_hcd :00:1d.0: PCI INT A - GSI 20 (level, low) - IRQ 
20
[126930.141624] ehci_hcd :00:1d.0: setting latency timer to 64
[126930.141644] pci :00:1e.0: setting latency timer to 64
[126930.141657] snd_hda_intel :00:1b.0: irq 43 for MSI/MSI-X
[126930.141659] ahci :00:1f.2: setting latency timer to 64
[126930.141710] pci :00:1f.3: PCI INT C - GSI 19 (level, low) - IRQ 19
[126930.141757] brcmsmac :02:00.0: PCI INT A - GSI 17 (level, low) - IRQ 
17
[126930.141763] brcmsmac :02:00.0: setting latency timer to 64
[126930.141833] sd 0:0:0:0: [sda] Starting disk
[126930.180638] r8169 :01:00.0: wake-up capability disabled by ACPI
[126930.180644] r8169 :01:00.0: PME# disabled
[126930.286766] Extended CMOS year: 2000
[126930.391986] usb 2-1.6: reset high-speed USB device number 3 

Bug#680737: linux-image-3.2.0-2-amd64: Intel i915: black display after boot

2012-07-08 Thread Roland Gruber
Package: src
Version: 3.2.20-1
Severity: important

Hi,

the screen turns to black at the beginning of the boot process.
I have to run setpci -s 00:02.0 F4.B=00 via ssh to see anything.
This is similar to bug 668274.

Booting with the 2.6 kernel does not show this problem.


Best regards

Roland


-- Package-specific info:
** Version:
Linux version 3.2.0-2-amd64 (Debian 3.2.20-1) (debian-ker...@lists.debian.org) 
(gcc version 4.6.3 (Debian 4.6.3-7) ) #1 SMP Mon Jun 11 17:24:18 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/sda2_crypt ro quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[ 2204.412078] ehci_hcd :00:1d.7: PCI INT A disabled
[ 2204.976104] PM: suspend of devices complete after 671.660 msecs
[ 2204.992352] ehci_hcd :00:1d.7: PME# enabled
[ 2204.992361] ehci_hcd :00:1d.7: wake-up capability enabled by ACPI
[ 2205.008327] uhci_hcd :00:1d.0: wake-up capability enabled by ACPI
[ 2205.008803] ehci_hcd :00:1a.7: PME# enabled
[ 2205.008809] ehci_hcd :00:1a.7: wake-up capability enabled by ACPI
[ 2205.024156] uhci_hcd :00:1a.0: wake-up capability enabled by ACPI
[ 2205.024249] PM: late suspend of devices complete after 48.140 msecs
[ 2205.024392] ACPI: Preparing to enter system sleep state S3
[ 2205.024540] PM: Saving platform NVS memory
[ 2205.026163] Disabling non-boot CPUs ...
[ 2205.128167] CPU 1 is now offline
[ 2205.128773] ACPI: Low-level resume complete
[ 2205.128773] PM: Restoring platform NVS memory
[ 2205.128773] CPU0: Thermal monitoring handled by SMI
[ 2205.128773] Enabling non-boot CPUs ...
[ 2205.128773] Booting Node 0 Processor 1 APIC 0x1
[ 2205.128773] smpboot cpu 1: start_ip = 99000
[ 2205.027732] Calibrating delay loop (skipped) already calibrated this CPU
[ 2205.153608] NMI watchdog enabled, takes one hw-pmu counter.
[ 2205.159549] CPU1 is up
[ 2205.160962] ACPI: Waking up from system sleep state S3
[ 2205.163681] i915 :00:02.0: restoring config space at offset 0x6 (was 
0xc, writing 0xc00c)
[ 2205.163688] i915 :00:02.0: restoring config space at offset 0x1 (was 
0x97, writing 0x900407)
[ 2205.163743] uhci_hcd :00:1a.0: restoring config space at offset 0x1 (was 
0x295, writing 0x291)
[ 2205.163772] uhci_hcd :00:1a.0: wake-up capability disabled by ACPI
[ 2205.163811] ehci_hcd :00:1a.7: restoring config space at offset 0x1 (was 
0x296, writing 0x292)
[ 2205.163831] ehci_hcd :00:1a.7: wake-up capability disabled by ACPI
[ 2205.163837] ehci_hcd :00:1a.7: PME# disabled
[ 2205.163856] snd_hda_intel :00:1b.0: restoring config space at offset 0xf 
(was 0x100, writing 0x10b)
[ 2205.163877] snd_hda_intel :00:1b.0: restoring config space at offset 0x3 
(was 0x0, writing 0x10)
[ 2205.163883] snd_hda_intel :00:1b.0: restoring config space at offset 0x1 
(was 0x16, writing 0x12)
[ 2205.163915] pcieport :00:1c.0: restoring config space at offset 0xf (was 
0x100, writing 0x10b)
[ 2205.163927] pcieport :00:1c.0: restoring config space at offset 0x9 (was 
0x10001, writing 0xd131d041)
[ 2205.163932] pcieport :00:1c.0: restoring config space at offset 0x8 (was 
0x0, writing 0xd660d570)
[ 2205.163946] pcieport :00:1c.0: restoring config space at offset 0x1 (was 
0x11, writing 0x100407)
[ 2205.163996] pcieport :00:1c.1: restoring config space at offset 0xf (was 
0x200, writing 0x20b)
[ 2205.164030] pcieport :00:1c.1: restoring config space at offset 0x9 (was 
0x10001, writing 0xd231d141)
[ 2205.164036] pcieport :00:1c.1: restoring config space at offset 0x8 (was 
0x0, writing 0xd560d460)
[ 2205.164051] pcieport :00:1c.1: restoring config space at offset 0x1 (was 
0x17, writing 0x100407)
[ 2205.164102] pcieport :00:1c.2: restoring config space at offset 0xf (was 
0x300, writing 0x30b)
[ 2205.164114] pcieport :00:1c.2: restoring config space at offset 0x9 (was 
0x10001, writing 0xd331d241)
[ 2205.164119] pcieport :00:1c.2: restoring config space at offset 0x8 (was 
0x0, writing 0xd450d350)
[ 2205.164133] pcieport :00:1c.2: restoring config space at offset 0x1 (was 
0x17, writing 0x100407)
[ 2205.164195] uhci_hcd :00:1d.0: restoring config space at offset 0x1 (was 
0x295, writing 0x291)
[ 2205.164222] uhci_hcd :00:1d.0: wake-up capability disabled by ACPI
[ 2205.164253] uhci_hcd :00:1d.1: restoring config space at offset 0x1 (was 
0x295, writing 0x291)
[ 2205.164291] uhci_hcd :00:1d.2: restoring config space at offset 0x1 (was 
0x295, writing 0x291)
[ 2205.164330] uhci_hcd :00:1d.3: restoring config space at offset 0x1 (was 
0x295, writing 0x291)
[ 2205.164376] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 
0x296, writing 0x292)
[ 2205.164396] ehci_hcd :00:1d.7: wake-up capability disabled by ACPI
[ 2205.164401] ehci_hcd :00:1d.7: PME# disabled
[ 2205.164421] pci :00:1e.0: restoring config space