[Bug 57381] Radeon HD6950: Resuming from hibernation fails sometimes
https://bugzilla.kernel.org/show_bug.cgi?id=57381 Harald Judt changed: What|Removed |Added Status|NEEDINFO|CLOSED Resolution|--- |CODE_FIX --- Comment #22 from Harald Judt --- This was a problem with the power management of the radeon graphics driver and should be fixed in 3.11, as long as one disables UVD with an unofficial radeon.no_uvd=1 patch. Since this is solved for me now, thanks for your help. -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 57381] Radeon HD6950: Resuming from hibernation fails sometimes
https://bugzilla.kernel.org/show_bug.cgi?id=57381 Harald Judt h.j...@gmx.at changed: What|Removed |Added Status|NEEDINFO|CLOSED Resolution|--- |CODE_FIX --- Comment #22 from Harald Judt h.j...@gmx.at --- This was a problem with the power management of the radeon graphics driver and should be fixed in 3.11, as long as one disables UVD with an unofficial radeon.no_uvd=1 patch. Since this is solved for me now, thanks for your help. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 57381] Radeon HD6950: Resuming from hibernation fails sometimes
https://bugzilla.kernel.org/show_bug.cgi?id=57381 Harald Judt changed: What|Removed |Added Kernel Version||3.8.13 --- Comment #21 from Harald Judt --- It took me a while because it turned out the old cable was faulty after all, and I had to replace it. Now that I got a new one, I installed an initramfs with tuxonice userui and tried to reproduce. Unfortunately, I was not very successful in getting more information. Here are the last lines of the log. Sometimes when it hangs, only the 20%80% line gets printed and nothing more. Sometimes, it goes like this: ... TuxOnIce: Image found.^M^J Using dev_t 8:9, returned by blk_lookup_fs_info.^M^J Console is 67x240.^M^J Freezing user space processes ... (elapsed 0.00 seconds) done.^M^J ...20%...40%...60%...80%^M^J usb usb3: root hub lost power or was reset^M^J usb usb6: root hub lost power or was reset^M^J bttv: 0: reset, reinitialize^M^J bttv: 0: Setting PLL: 28636363 => 35468950 (needs up to 100ms)^M^J ehci-pci :00:1d.0: setting latency timer to 64^M^J usb usb5: root hub lost power or was reset^M^J snd_hda_intel :00:1b.0: irq 45 for MSI/MSI-X^M^J snd_hda_intel :01:00.1: irq 46 for MSI/MSI-X^M^J i8042 kbd 00:0a: System wakeup disabled by ACPI^M^J tg3 :04:00.0 eth0: Link is down^M^J serial 00:0b: activated^M^J ehci-pci :00:1a.0: cache line size of 64 is not supported^M^J ehci-pci :00:1d.0: cache line size of 64 is not supported^M^J bttv: PLL set ok^M^J This happens after tuxoniceui shows me "About to restore original kernel. Press SPACE to continue". I guess this output is not complete, and not everything gets printed to the serial console because the computer hard freezes before that. The lines are similar, but not always in that order. They also appear in dmesg when everything goes right, so they're nothing special. Any idea what else I could do? -- You are receiving this mail because: You are watching the assignee of the bug.
[Bug 57381] Radeon HD6950: Resuming from hibernation fails sometimes
https://bugzilla.kernel.org/show_bug.cgi?id=57381 Harald Judt h.j...@gmx.at changed: What|Removed |Added Kernel Version||3.8.13 --- Comment #21 from Harald Judt h.j...@gmx.at --- It took me a while because it turned out the old cable was faulty after all, and I had to replace it. Now that I got a new one, I installed an initramfs with tuxonice userui and tried to reproduce. Unfortunately, I was not very successful in getting more information. Here are the last lines of the log. Sometimes when it hangs, only the 20%80% line gets printed and nothing more. Sometimes, it goes like this: ... TuxOnIce: Image found.^M^J Using dev_t 8:9, returned by blk_lookup_fs_info.^M^J Console is 67x240.^M^J Freezing user space processes ... (elapsed 0.00 seconds) done.^M^J ...20%...40%...60%...80%^M^J usb usb3: root hub lost power or was reset^M^J usb usb6: root hub lost power or was reset^M^J bttv: 0: reset, reinitialize^M^J bttv: 0: Setting PLL: 28636363 = 35468950 (needs up to 100ms)^M^J ehci-pci :00:1d.0: setting latency timer to 64^M^J usb usb5: root hub lost power or was reset^M^J snd_hda_intel :00:1b.0: irq 45 for MSI/MSI-X^M^J snd_hda_intel :01:00.1: irq 46 for MSI/MSI-X^M^J i8042 kbd 00:0a: System wakeup disabled by ACPI^M^J tg3 :04:00.0 eth0: Link is down^M^J serial 00:0b: activated^M^J ehci-pci :00:1a.0: cache line size of 64 is not supported^M^J ehci-pci :00:1d.0: cache line size of 64 is not supported^M^J bttv: PLL set ok^M^J This happens after tuxoniceui shows me About to restore original kernel. Press SPACE to continue. I guess this output is not complete, and not everything gets printed to the serial console because the computer hard freezes before that. The lines are similar, but not always in that order. They also appear in dmesg when everything goes right, so they're nothing special. Any idea what else I could do? -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 57381] Radeon HD6950: Resuming from hibernation fails sometimes
https://bugzilla.kernel.org/show_bug.cgi?id=57381 Nigel Cunningham changed: What|Removed |Added CC||nigel at tuxonice.net --- Comment #20 from Nigel Cunningham 2013-06-25 20:54:06 --- If you install the userui binary in the initramfs, you'll be able to single step through the process and modify the TuxOnIce debugging settings as you go - perhaps this will help. Press 'P' to pause between steps, 0-9 to modify the level of debugging info that's displayed (9 = max info, including all kernel messages). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug.
[Bug 57381] Radeon HD6950: Resuming from hibernation fails sometimes
https://bugzilla.kernel.org/show_bug.cgi?id=57381 --- Comment #19 from Harald Judt 2013-06-25 19:10:07 --- > echo disabled > > "/sys/devices/pci:00/:00:01.0/:01:00.0/power/async" > echo disabled > > "/sys/devices/pci:00/:00:01.0/:01:00.1/power/async" > > This seems to have a similar effect as "echo 0 > /sys/power/pm_async". I believe I was wrong with this assumption. However, I got serial console debugging working now. Unfortunately, it does not reveal much, but here is the output anyway. Linux version 3.8.13+ (user at localhost) (gcc version 4.7.3 (Gentoo 4.7.3 p1.0, pie-0.5.5) ) #142 SMP PREEMPT Tue Jun 25 18:56:39 CEST 2013^M^J Command line: root=/dev/sda6 rootfstype=ext4 video=DVI-I-1:1920x1080 radeon.pcie_gen2=1 radeon.audio=1 pci=nocrs console=ttyS0,115200n8 console=tty0 no_console_suspend=1^M^J e820: BIOS-provided physical RAM map:^M^J BIOS-e820: [mem 0x-0x0009d7ff] usable^M^J BIOS-e820: [mem 0x0009d800-0x0009] reserved^M^J BIOS-e820: [mem 0x000e-0x000f] reserved^M^J BIOS-e820: [mem 0x0010-0xdd49dfff] usable^M^J BIOS-e820: [mem 0xdd49e000-0xde048fff] reserved^M^J BIOS-e820: [mem 0xde049000-0xde0d5fff] usable^M^J BIOS-e820: [mem 0xde0d6000-0xde177fff] ACPI NVS^M^J BIOS-e820: [mem 0xde178000-0xde976fff] reserved^M^J BIOS-e820: [mem 0xde977000-0xde977fff] usable^M^J BIOS-e820: [mem 0xde978000-0xde9bafff] ACPI NVS^M^J BIOS-e820: [mem 0xde9bb000-0xdf3f5fff] usable^M^J BIOS-e820: [mem 0xdf3f6000-0xdf7f1fff] reserved^M^J BIOS-e820: [mem 0xdf7f2000-0xdf7f] usable^M^J BIOS-e820: [mem 0xf800-0xfbff] reserved^M^J BIOS-e820: [mem 0xfec0-0xfec00fff] reserved^M^J BIOS-e820: [mem 0xfed0-0xfed03fff] reserved^M^J BIOS-e820: [mem 0xfed1c000-0xfed1] reserved^M^J BIOS-e820: [mem 0xfee0-0xfee00fff] reserved^M^J BIOS-e820: [mem 0xff00-0x] reserved^M^J BIOS-e820: [mem 0x0001-0x00041eff] usable^M^J NX (Execute Disable) protection: active^M^J SMBIOS 2.7 present.^M^J No AGP bridge found^M^J e820: last_pfn = 0x41f000 max_arch_pfn = 0x4^M^J x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106^M^J e820: last_pfn = 0xdf800 max_arch_pfn = 0x4^M^J found SMP MP-table at [mem 0x000fd8e0-0x000fd8ef] mapped at [880fd8e0]^M^J init_memory_mapping: [mem 0x-0xdf7f]^M^J init_memory_mapping: [mem 0x1-0x41eff]^M^J ACPI: RSDP 000f0490 00024 (v02 ALASKA)^M^J ACPI: XSDT de169078 0006C (v01 ALASKAA M I 01072009 AMI 00010013)^M^J ACPI: FACP de172f58 0010C (v05 ALASKAA M I 01072009 AMI 00010013)^M^J ACPI: DSDT de169178 09DDD (v02 ALASKAA M I 0022 INTL 20051117)^M^J ACPI: FACS de176080 00040^M^J ACPI: APIC de173068 00092 (v03 ALASKAA M I 01072009 AMI 00010013)^M^J ACPI: FPDT de173100 00044 (v01 ALASKAA M I 01072009 AMI 00010013)^M^J ACPI: MCFG de173148 0003C (v01 ALASKAA M I 01072009 MSFT 0097)^M^J ACPI: AAFT de173188 00112 (v01 ALASKA OEMAAFT 01072009 MSFT 0097)^M^J ACPI: HPET de1732a0 00038 (v01 ALASKAA M I 01072009 AMI. 0005)^M^J ACPI: SSDT de1732d8 0036D (v01 SataRe SataTabl 1000 INTL 20091112)^M^J ACPI: SSDT de173648 00A92 (v01 PmRefCpuPm 3000 INTL 20051117)^M^J ACPI: BGRT de1740e0 00038 (v00 ALASKAA M I 01072009 AMI 00010013)^M^J No NUMA configuration found^M^J Faking a node at [mem 0x-0x00041eff]^M^J Initmem setup node 0 [mem 0x-0x41eff]^M^J NODE_DATA [mem 0x41effc000-0x41eff]^M^J Zone ranges:^M^J DMA [mem 0x0001-0x00ff]^M^J DMA32[mem 0x0100-0x]^M^J Normal [mem 0x1-0x41eff]^M^J Movable zone start for each node^M^J Early memory node ranges^M^J node 0: [mem 0x0001-0x0009cfff]^M^J node 0: [mem 0x0010-0xdd49dfff]^M^J node 0: [mem 0xde049000-0xde0d5fff]^M^J node 0: [mem 0xde977000-0xde977fff]^M^J node 0: [mem 0xde9bb000-0xdf3f5fff]^M^J node 0: [mem 0xdf7f2000-0xdf7f]^M^J node 0: [mem 0x1-0x41eff]^M^J ACPI: PM-Timer IO Port: 0x408^M^J ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)^M^J ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)^M^J ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)^M^J ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)^M^J ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)^M^J ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)^M^J ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)^M^J ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)^M^J ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])^M^J ACPI: IOAPIC (id[0x02] address[0xfec0]
[Bug 57381] Radeon HD6950: Resuming from hibernation fails sometimes
https://bugzilla.kernel.org/show_bug.cgi?id=57381 --- Comment #19 from Harald Judt h.j...@gmx.at 2013-06-25 19:10:07 --- echo disabled /sys/devices/pci:00/:00:01.0/:01:00.0/power/async echo disabled /sys/devices/pci:00/:00:01.0/:01:00.1/power/async This seems to have a similar effect as echo 0 /sys/power/pm_async. I believe I was wrong with this assumption. However, I got serial console debugging working now. Unfortunately, it does not reveal much, but here is the output anyway. Linux version 3.8.13+ (user@localhost) (gcc version 4.7.3 (Gentoo 4.7.3 p1.0, pie-0.5.5) ) #142 SMP PREEMPT Tue Jun 25 18:56:39 CEST 2013^M^J Command line: root=/dev/sda6 rootfstype=ext4 video=DVI-I-1:1920x1080 radeon.pcie_gen2=1 radeon.audio=1 pci=nocrs console=ttyS0,115200n8 console=tty0 no_console_suspend=1^M^J e820: BIOS-provided physical RAM map:^M^J BIOS-e820: [mem 0x-0x0009d7ff] usable^M^J BIOS-e820: [mem 0x0009d800-0x0009] reserved^M^J BIOS-e820: [mem 0x000e-0x000f] reserved^M^J BIOS-e820: [mem 0x0010-0xdd49dfff] usable^M^J BIOS-e820: [mem 0xdd49e000-0xde048fff] reserved^M^J BIOS-e820: [mem 0xde049000-0xde0d5fff] usable^M^J BIOS-e820: [mem 0xde0d6000-0xde177fff] ACPI NVS^M^J BIOS-e820: [mem 0xde178000-0xde976fff] reserved^M^J BIOS-e820: [mem 0xde977000-0xde977fff] usable^M^J BIOS-e820: [mem 0xde978000-0xde9bafff] ACPI NVS^M^J BIOS-e820: [mem 0xde9bb000-0xdf3f5fff] usable^M^J BIOS-e820: [mem 0xdf3f6000-0xdf7f1fff] reserved^M^J BIOS-e820: [mem 0xdf7f2000-0xdf7f] usable^M^J BIOS-e820: [mem 0xf800-0xfbff] reserved^M^J BIOS-e820: [mem 0xfec0-0xfec00fff] reserved^M^J BIOS-e820: [mem 0xfed0-0xfed03fff] reserved^M^J BIOS-e820: [mem 0xfed1c000-0xfed1] reserved^M^J BIOS-e820: [mem 0xfee0-0xfee00fff] reserved^M^J BIOS-e820: [mem 0xff00-0x] reserved^M^J BIOS-e820: [mem 0x0001-0x00041eff] usable^M^J NX (Execute Disable) protection: active^M^J SMBIOS 2.7 present.^M^J No AGP bridge found^M^J e820: last_pfn = 0x41f000 max_arch_pfn = 0x4^M^J x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106^M^J e820: last_pfn = 0xdf800 max_arch_pfn = 0x4^M^J found SMP MP-table at [mem 0x000fd8e0-0x000fd8ef] mapped at [880fd8e0]^M^J init_memory_mapping: [mem 0x-0xdf7f]^M^J init_memory_mapping: [mem 0x1-0x41eff]^M^J ACPI: RSDP 000f0490 00024 (v02 ALASKA)^M^J ACPI: XSDT de169078 0006C (v01 ALASKAA M I 01072009 AMI 00010013)^M^J ACPI: FACP de172f58 0010C (v05 ALASKAA M I 01072009 AMI 00010013)^M^J ACPI: DSDT de169178 09DDD (v02 ALASKAA M I 0022 INTL 20051117)^M^J ACPI: FACS de176080 00040^M^J ACPI: APIC de173068 00092 (v03 ALASKAA M I 01072009 AMI 00010013)^M^J ACPI: FPDT de173100 00044 (v01 ALASKAA M I 01072009 AMI 00010013)^M^J ACPI: MCFG de173148 0003C (v01 ALASKAA M I 01072009 MSFT 0097)^M^J ACPI: AAFT de173188 00112 (v01 ALASKA OEMAAFT 01072009 MSFT 0097)^M^J ACPI: HPET de1732a0 00038 (v01 ALASKAA M I 01072009 AMI. 0005)^M^J ACPI: SSDT de1732d8 0036D (v01 SataRe SataTabl 1000 INTL 20091112)^M^J ACPI: SSDT de173648 00A92 (v01 PmRefCpuPm 3000 INTL 20051117)^M^J ACPI: BGRT de1740e0 00038 (v00 ALASKAA M I 01072009 AMI 00010013)^M^J No NUMA configuration found^M^J Faking a node at [mem 0x-0x00041eff]^M^J Initmem setup node 0 [mem 0x-0x41eff]^M^J NODE_DATA [mem 0x41effc000-0x41eff]^M^J Zone ranges:^M^J DMA [mem 0x0001-0x00ff]^M^J DMA32[mem 0x0100-0x]^M^J Normal [mem 0x1-0x41eff]^M^J Movable zone start for each node^M^J Early memory node ranges^M^J node 0: [mem 0x0001-0x0009cfff]^M^J node 0: [mem 0x0010-0xdd49dfff]^M^J node 0: [mem 0xde049000-0xde0d5fff]^M^J node 0: [mem 0xde977000-0xde977fff]^M^J node 0: [mem 0xde9bb000-0xdf3f5fff]^M^J node 0: [mem 0xdf7f2000-0xdf7f]^M^J node 0: [mem 0x1-0x41eff]^M^J ACPI: PM-Timer IO Port: 0x408^M^J ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)^M^J ACPI: LAPIC (acpi_id[0x02] lapic_id[0x02] enabled)^M^J ACPI: LAPIC (acpi_id[0x03] lapic_id[0x04] enabled)^M^J ACPI: LAPIC (acpi_id[0x04] lapic_id[0x06] enabled)^M^J ACPI: LAPIC (acpi_id[0x05] lapic_id[0x01] enabled)^M^J ACPI: LAPIC (acpi_id[0x06] lapic_id[0x03] enabled)^M^J ACPI: LAPIC (acpi_id[0x07] lapic_id[0x05] enabled)^M^J ACPI: LAPIC (acpi_id[0x08] lapic_id[0x07] enabled)^M^J ACPI: LAPIC_NMI (acpi_id[0xff] high edge lint[0x1])^M^J ACPI: IOAPIC (id[0x02] address[0xfec0]
[Bug 57381] Radeon HD6950: Resuming from hibernation fails sometimes
https://bugzilla.kernel.org/show_bug.cgi?id=57381 Nigel Cunningham ni...@tuxonice.net changed: What|Removed |Added CC||ni...@tuxonice.net --- Comment #20 from Nigel Cunningham ni...@tuxonice.net 2013-06-25 20:54:06 --- If you install the userui binary in the initramfs, you'll be able to single step through the process and modify the TuxOnIce debugging settings as you go - perhaps this will help. Press 'P' to pause between steps, 0-9 to modify the level of debugging info that's displayed (9 = max info, including all kernel messages). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 57381] Radeon HD6950: Resuming from hibernation fails sometimes
https://bugzilla.kernel.org/show_bug.cgi?id=57381 Lan Tianyu changed: What|Removed |Added Component|Hibernation/Suspend |Video(DRI - non Intel) AssignedTo|tianyu.lan at intel.com|drivers_video-dri at kernel-bu ||gs.osdl.org Product|Power Management|Drivers --- Comment #18 from Lan Tianyu 2013-06-17 02:14:18 --- Thanks for test. I think you have done a very good job. (In reply to comment #16) > Ok, the following statements deactivate async for the graphics card (+ its > HDMI > audio): > echo disabled > > "/sys/devices/pci:00/:00:01.0/:01:00.0/power/async" > echo disabled > > "/sys/devices/pci:00/:00:01.0/:01:00.1/power/async" > > This seems to have a similar effect as "echo 0 > /sys/power/pm_async". > This shows the issue is still related with Graphics driver. Disable pm_async is just to make all the driver suspend callback to be executed serially. So reassign this bug to Graphic category. > With this, I ran a series of 30 hibernate/resume cycles. The 7th and the 29th > attempts failed (the last one failed twice), with the usual symptoms. So it > seems that disabling async for the graphics card indeed only alleviates the > problem. I will perform the same tests with pm_async deactivated just to be > sure. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug.
[Bug 57381] Radeon HD6950: Resuming from hibernation fails sometimes
https://bugzilla.kernel.org/show_bug.cgi?id=57381 Lan Tianyu tianyu@intel.com changed: What|Removed |Added Component|Hibernation/Suspend |Video(DRI - non Intel) AssignedTo|tianyu@intel.com|drivers_video-dri@kernel-bu ||gs.osdl.org Product|Power Management|Drivers --- Comment #18 from Lan Tianyu tianyu@intel.com 2013-06-17 02:14:18 --- Thanks for test. I think you have done a very good job. (In reply to comment #16) Ok, the following statements deactivate async for the graphics card (+ its HDMI audio): echo disabled /sys/devices/pci:00/:00:01.0/:01:00.0/power/async echo disabled /sys/devices/pci:00/:00:01.0/:01:00.1/power/async This seems to have a similar effect as echo 0 /sys/power/pm_async. This shows the issue is still related with Graphics driver. Disable pm_async is just to make all the driver suspend callback to be executed serially. So reassign this bug to Graphic category. With this, I ran a series of 30 hibernate/resume cycles. The 7th and the 29th attempts failed (the last one failed twice), with the usual symptoms. So it seems that disabling async for the graphics card indeed only alleviates the problem. I will perform the same tests with pm_async deactivated just to be sure. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
