[Samsung NP535U3C-A03DE] Blank screen on resume from suspend

[Vsevolod Kukol]

when resuming from suspend, the screen remains blank, while the system ist still operational (logging in using ssh works).

* restarting X doesn't help ("sudo restart lightdm" through ssh)
* disabling KMS (nomodeset) doesn't help, still blank screen after pm-suspend
* updating to xorg-edgers kernel 3.7.0-7 doesn't help
* mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/ (3.8.0.999) didn't work either
* playing around with acpi_os_name had no effect

I tried following the debugging instructions from https://wiki.ubuntu.com/DebuggingKernelSuspend, but I have no /sys/power/pm_trace (even on mainline kernel)

The system is a brand new Samsung 535U3C-A03 with an AMD A4-4355M (integrated Radeon HD 7400G).

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: linux-image-3.5.0-21-generic 3.5.0-21.32
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: galina 2104 F.... pulseaudio
 /dev/snd/controlC0: galina 2104 F.... pulseaudio
CRDA:
 country DE:
  (2400 - 2483 @ 40), (N/A, 20)
  (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
  (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
  (5470 - 5725 @ 40), (N/A, 26), DFS
Date: Tue Dec 25 16:44:14 2012
InstallationDate: Installed on 2012-12-24 (0 days ago)
InstallationMedia: Ubuntu GNOME Remix 12.10 "Quantal Quetzal" - Release amd64(20121023)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C
MarkForUpload: True
ProcEnviron:
 LANGUAGE=de_DE:en
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-21-generic.efi.signed root=UUID=3d942843-dad1-48c0-b9d8-51ccff317810 ro quiet splash "acpi_os_name=Microsoft Windows NT" vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.5.0-21-generic N/A
 linux-backports-modules-3.5.0-21-generic N/A
 linux-firmware 1.98
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/24/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P06RAS.W70.121224.LEO
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP535U3C-A03DE
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP06RAS.W70.121224.LEO:bd12/24/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U3C:pvrP06RAS:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP535U3C-A03DE:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 535U3C
dmi.product.version: P06RAS
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Vsevolod Kukol, thank you for reporting this and helping make Ubuntu better. Did this problem not occur in a release prior to Quantal?

[Vsevolod Kukol (v-kukol)]

I've tried Precise first, but it didn't even boot (with or without uefi, tried many different boot settings in BIOS). The only release that I was able to install is Quantal 12.10.1 Gnome Remix. The official 12.10 boots flawless but destroyed my Windows 8 during the installation process.

I didn't look into it deeply, but Precise didn't even start to boot. The Kernel stopps simply without any errors (not even a kernel panic).

I've played around with pm-suspend during a live dvd session (the normal Ubuntu Quantal), but it behaves the same. Even the Backlight settings, freq scaling and fan control do not work with its 3.5 kernel. The battery drain is extremely high.

With the 3.7 kernel from the xorg-edgers ppa the notebook works much better (cpu scaling works, brightness works, battery lasts for more then two hours, still the half of Windows with 4h, but its enough for me).

Is there anything I could do to find the problem? Maybe some debugging settings somewhere?

[Vsevolod Kukol (v-kukol)]

And maybe I should mention that I've tested it with and without the updated xorg* packages. But since it doesn't even work without X running at all, it shouldn't be a xorg problem.

And I've tried "pm-suspend --quirk-radeon-off" without success.

[penalvch (penalvch)]

Vsevolod Kukol, thank you for providing the requested information. Could you please provide the information following https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Vsevolod Kukol (v-kukol)]

Thanks for your support.

As I have written, no of the kernels I have tested has the capability of "/sys/power/pm_trace". I'm now on 3.8.0-999-generic (from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/) and have no "/sys/power/pm_trace" (see ls_sys_power.txt attached).

1. Full computer manufacturer and model: "SAMSUNG ELECTRONICS CO., LTD." "NP535U3C-A03DE"
2. latest BIOS installed (by SM Update tool under Windows)
3. "cat /proc/acpi/wakeup > wakeup" on current mainline (3.8.0-999-generic): see wakeup.txt attached
4. can't proceed due to lack of pm_trace support?field.comment=Thanks for your support.

As I have written, no of the kernels I have tested has the capability of "/sys/power/pm_trace". I'm now on 3.8.0-999-generic (from http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/current/) and have no "/sys/power/pm_trace" (see ls_sys_power.txt attached).

1. Full computer manufacturer and model: "SAMSUNG ELECTRONICS CO., LTD." "NP535U3C-A03DE"
2. latest BIOS installed (by SM Update tool under Windows)
3. "cat /proc/acpi/wakeup > wakeup" on current mainline (3.8.0-999-generic): see wakeup.txt attached
4. can't proceed due to lack of pm_trace support

[penalvch (penalvch)]

Vsevolod Kukol, what is the BIOS version number as per your BIOS screen (please do not copy/paste what Launchpad pulled from your computer)?

[Vsevolod Kukol (v-kukol)]

"NP535U3C-A03DE" IS the model (http://www.samsung.com/de/support/model/NP535U3C-A03DE-techspecs), so Launchad did it right (and dmidecode too, doublechecked it before posting), or do you mean something else? Sorry for the double post, it happened as I clicked on "Add attachment or patch" link.

The BIOS Version from the BIOS screen: P06RAS
(same as MICOM if it matters, is right below the BIOS version, no idea what that is)

Thanks!

[Matt Wilson (mattswilson)]

I have a very similar setup, and had the same issue.
Samsung NP535U3C-B01US
AMD A6-4455M APU with Radeon(tm) HD 7500G Graphics
3.5.0-17-generic
Ubuntu 12.10

Suspend ok, resume with blank screen, no backlight, but system was fully function

*Not an expert; actually, I have no idea what I'm doing*

1. Installed FGLRX drivers from "additional drivers", did not work, black screen on reboot
2. Updated kernel to 3.5.0-23 and then 3.8 mainline, did not work. Ended up causing some boot issues. Unistalled everything but 3.5.0-17
3. Installed driver directly from AMD. New version released 1/17/2013
http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx
Did not work, had an install issue, ended up my header was not installed. No idea what that means.

4. Installed header. Maybe I messed something up with the kernel updates. Sucess
sudo apt-get install linux-headers-$(uname -r)

5. Installed driver directly from AMD. Success

Suspend and Resume now work correctly, and the screen comes back on as it should. However, brightness function keys no longer work.
My root cause was a driver issue.

I was able to run "dmesg" and "/sys/power/pm_trace" before the fix, so if you are interested in seeing that, please let me know. Similar setup to Mr. Kukol

[Vsevolod Kukol (v-kukol)]

Thanks for the report. I'll try to update the AMD drivers with 3.5 kernel tomorrow and report back.

It would be nice if you could attach the logs you mentioned, so I can compare them. Could you also post your current working /var/log/Xorg.0.log, "dpkg -l | grep fglrx" and dmesg output after a clean reboot?

[penalvch (penalvch)]

Matt Wilson, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[penalvch (penalvch)]

Vsevolod Kukol, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.10-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Vsevolod Kukol (v-kukol)]

Hi,

I didn't realize that, cause I've disabled the suspend option in Gnome and didn't use it since my last testings.

It seems to be working now! There must have been some update (I've enabled security, updates, proposed and backports and the XOrg Edgers PPA) that made it work.

Since I have not much time and its my mothers laptop now, its impossible for me to test the mainline kernel right now. Would it help if I provide some detailed information about the current working system? If yes, something special?

[penalvch (penalvch)]

Vsevolod Kukol, what would be needed is a test of the live environment via http://cdimage.ubuntu.com/daily-live/current/ . This would require no modification of your current install.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[penalvch (penalvch)]

husfeldt, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[leon_ti (leon-ti)]

ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ubuntu 3242 F.... pulseaudio
 /dev/snd/controlC0: ubuntu 3242 F.... pulseaudio
CasperVersion: 1.337
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 535U3C
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper quiet splash -- persistent BOOT_IMAGE=/casper/vmlinuz.efi
ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-11-generic N/A
 linux-backports-modules-3.13.0-11-generic N/A
 linux-firmware 1.125
Tags: trusty
Uname: Linux 3.13.0-11-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 05/14/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P00RAG.N40.120514.LEO
dmi.board.asset.tag: No Asset Tag
dmi.board.name: SAMSUNG_NP1234567890
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SEC_SW_REVISION_1234567890ABCD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP00RAG.N40.120514.LEO:bd05/14/2012:svnSAMSUNGELECTRONICSCO.,LTD.:pn535U3C:pvrP00RAG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A:
dmi.product.name: 535U3C
dmi.product.version: P00RAG
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

apport information

[leon_ti (leon-ti)]

Dear Ubuntu team,

This bug is definitely exists still in 14.04 LTS development build. I have the same laptop
Also I have to mention that this bug doesn't exist with ATI propietary driver (but it has another annoying issues).

Probably it is the same bug as reported here: https://bugs.freedesktop.org/show_bug.cgi?id=23103 , but there is no activity unfortunately :(

[leon_ti (leon-ti)]

One more tip: this laptop resumes an external display (HDMI in my case) well. So I get HDMI working and LCD (LVDS-1) display non-working after resume.
Please consider this bug as higher priority, as it seems to affect all integrated AMD APUs laptops. I think so as I googled a lot about this issue, and I saw a lot of bug reports and no good solutions.

[penalvch (penalvch)]

leon_ti, please do not apport-collect to another person's report. If you have a bug in Ubuntu, and so your hardware and problem may be tracked, please feel free to file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[sajeev z (sajeev-zacharias4)]

Just goto amd website. In the navigation, go to drivers, goto linux drivers download the 121 mb zip file unzip and follow the instructions. After all the steps, reboot the system. Revoke from suspend works.

[Mihara (medvedev)]

...now seriously, how a description of switching to AMD's proprietary driver becomes "fix committed" when it is neither a fix of the actual problem, nor actually committed anywhere?...

[penalvch (penalvch)]

sajeev z, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[jose (o1485726)]

Hey guys, *this* is the correct bug report for the bug in system running the radeon driver that have AMD APUs:
https://bugs.freedesktop.org/show_bug.cgi?id=42960
and there is a workaround here: https://bugs.freedesktop.org/show_bug.cgi?id=42960#c15 and here: https://bugs.freedesktop.org/show_bug.cgi?id=42960#c34

[penalvch (penalvch)]

jose, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[jose (o1485726)]

@penalvch
I don't know if this is a bot, but... yes, this bug DOES affect me, and yes, it's the same bug. Notice that the reporter, and other affected, had/have AMD APUs, and are also using the "radeon" kernel module? It's the same bug in the "radeon" open source driver, and it's still present.
AMD A6-4455M APU with Radeon(tm) HD 7500G Graphics
AMD A4-4355M (integrated Radeon HD 7400G).
Mine is a A6-3400M, with a Radeon HD 6520G APU, and I also have this problem.
The freedesktop bug #23103 linked here affects different generation of ATI/AMD systems.

And BTW, I'm sure there are other reports in launchpad related to this one. If you only had bots that, instead of posting random comments in the reporta, did the researching and linking job for you... lp.net wouldn't be the mess it is.

[penalvch (penalvch)]

jose, please again see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1093644/comments/44 . As well, please do not toggle the status further as you are not the original reporter.

[jose (o1485726)]

And that's why I don't report bugs to lp.net / canonical. It's a waste of time, most of its employees and volunteers are a waste of time and they barely care about fixing the problems. Instead, they prefer to add even more bureaucracy to show how good they are at their job (and some get paid for that).
I'll keep reporting bugs upstream, and ignoring bugs.lp.net, thanks for nothing.
At least my comment was useful for those who will find this report in google; yours, on the other hand...

[jose (o1485726)]

Reposting https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1313804/comments/10
The fix has been commited: https://bugs.freedesktop.org/show_bug.cgi?id=42960#c57 , but apparently the patch hasn't been merged in any kernel in ubuntu.
Could you guys please merge it?

[jose (o1485726)]

Can someone affected by this bug try installing either the lattest "LTS enablement stack" kernel (3.16), or linux-image-extra-3.13.0-51-generic from trusty-proposed? The fix should be already there, so please install said packages and confirm/deny that it works. Remember to remove the pm-suspnd quirks.

[atimonin (atimonin)]

All of a sudden I've found out that suspend-resume is working.
Maybe after one of updates, I havn't checked it regelary.
So I think the bug is fixed in Ubuntu.

[jose (o1485726)]

@atimonin: I suspect it's this: https://bugs.launchpad.net/ubuntu/trusty/+source/linux/+bug/1313804
Can someone ask the original reporter if the bug is still there for him/her?