[Dell Inspiron 1525] Trusty freezes on resume from suspend

[Žygimantas Beručka]

Ubuntu Trusty freezes on resume from a suspend. All I see is just LEDs for disk (just blinks for a moment) and wifi (stays lit), fan noise and a black screen. No mouse cursor, no nothing. The magic SysRq (+REISUB) does nothing; a hard manual reboot by pressing the power button is necessary. The problem is gone if booting with a 3.11-20 kernel left from Saucy. The issue is present, however, at least with 3.13.{8,11} and 3.14.{1,2} mainline kernel builds. I haven't tried 3.15rc, though, since it boots with a totally black screen and I have no idea how to bypass it; and my Broadcom wifi driver fails to build with 3.15rc too.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.46
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: monika 2392 F.... pulseaudio
CurrentDesktop: Unity
Date: Fri May 2 09:38:54 2014
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=834effe2-2fd9-44c3-bc7c-aeec1f9792c5
InstallationDate: Installed on 2012-06-12 (688 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Dell Inc. Inspiron 1525
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=a72bb3f2-f87d-4162-8242-7c5485008de5 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-24-generic N/A
 linux-backports-modules-3.13.0-24-generic N/A
 linux-firmware 1.127.1
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-04-12 (19 days ago)
dmi.bios.date: 10/27/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 0U990C
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA17:bd10/27/2009:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1525
dmi.sys.vendor: Dell Inc.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc3-trusty/

[Žygimantas Beručka (zygis)]

Joseph, I've already mentioned that I am unable to test 3.15rc since it boots with a completely black screen start to finish. I don't know what is the cause and how to circumvent it.

[Žygimantas Beručka (zygis)]

By the way, is it possible to collect any freeze data which might shed a light on a possible cause?

When I boot after a unclean/hard reboot and log into a Unity session, I see a number Apport dialog windows (3 to 5 usually). However, when I press 'OK' on one of them, enter my password, it starts collecting data related to previous unclean resume/restart. But once it's done, and I want to submit the data collected and press the button, the dialog window just closes and nothing else happens. The rest 2–4 windows can be just closed, after the 1st they do nothing. Is the data collected stored anywhere so that I could take it from there and submit it manually? Or does it just mean that nothing useful had been collected?

[penalvch (penalvch)]

Žygimantas Beručka, the next step is to fully commit bisect from Saucy to Trusty, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[Žygimantas Beručka (zygis)]

I found out the last working version to be 3.12.19 (latest in the series) and the first buggy one – 3.13rc1. Therefore the offending commit is somewhere in the early 3.13 series. I'm afraid cannot do much more about this, as I am not a too tech-savvy user. I have no experience in doing the bisecting thing, and what is more crucial at the moment, I have no time to learn it in the nearest future.

Maybe someone would be kind enough to look at it and prepare some pre-3.13rc1 kernel builds that I can quickly test or something. That much I'd able to do...

[Iuri Diniz (iuridiniz)]

I have the same problem and I know how to do a bisect, so I can do this, but I'm lost in tags of git repo

Will bisect be between [Ubuntu-3.12.0-3.9] and [Ubuntu-3.13.0-0.2] of 'git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git' ?

[Iuri Diniz (iuridiniz)]

Could Anyone help?

I just want the revisions in order to start bisect, I'm lost in tags!

[penalvch (penalvch)]

luri Diniz, thank you for your comment. 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.

Thank you for your understanding.

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

[Žygimantas Beručka (zygis)]

Dear Chris, have you *actually* read Iuri Diniz's messages you are thanking
him for? At this stage your template messages ARE NOT helpful and are
redundant.

Let me put it this way. First, he's having the same damn hardware as many
other users facing this bug that no one from the Ubuntu kernel wizards help
to deal with.

Secondly, and that's crucial, Iuri is willing to take *actual steps* to pin
point the exact offending commit in the kernel tree. He just needs real
help with something I do not have a slightest clue about.

Please, if you are willing to give him a helping hand, helping to get
Iuri's question a moment of attention of someone from your kernel team,
might be just enough. Else this bug will not get fixed.

2014-06-17 13:53 GMT+02:00 Christopher M. Penalver <
<email address hidden>>:

> luri Diniz, thank you for your comment. 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.
>
> Thank you for your understanding.
>
> Helpful bug reporting tips:
> https://wiki.ubuntu.com/ReportingBugs
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1315277
>
> Title:
> [Dell Inspiron 1525] Trusty freezes on resume from suspend
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315277/+subscriptions
>

[Žygimantas Beručka (zygis)]

Dear Iuri, maybe upstream (or even freedesktop.org's) kernel folks can help
with this? I don't think this bug has been reported to their bugzilla.
Maybe it's worth to report it there and expect their comments that would
help you out with these tags?

2014-06-17 4:24 GMT+02:00 Iuri Diniz <email address hidden>:

> Could Anyone help?
>
> I just want the revisions in order to start bisect, I'm lost in tags!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1315277
>
> Title:
> [Dell Inspiron 1525] Trusty freezes on resume from suspend
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315277/+subscriptions
>

[penalvch (penalvch)]

Žygimantas Beručka, as you can respect, this isn't userspace, and the triaging is done differently, both down and upstream. So, as you put it, he can have the "same damn hardware" but unless he put in a new bug report, nobody could verify that at this point but Iuri and Iuri alone. Also, suggesting someone go do this same thing elsewhere also isn't terribly helpful, and will more than likely have the issue ignored (all of this is already well documented in the links noted in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315277/comments/10 as you are welcome to review).

[Žygimantas Beručka (zygis)]

Dear Chris, thank you for kindly reminding the basics. The problem of Iuri,
however, is a different and a very specific one. He writes:

I have the same problem and I know how to do a bisect, so I can do this,
> but I'm lost in tags of git repo
> Will bisect be between [Ubuntu-3.12.0-3.9] and [Ubuntu-3.13.0-0.2] of
> 'git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git' ?

Following the links you've given, I am unable to find the answer therein.
The point is, should Iuri manage to make the bisect, *I* could also test
the builds on *my own* hardware and provide more info on *this* bugreport
(which should hopefully make you happier). Without his help, it's something
which I am unfortunately unable to do. You could have just looked into the
essence of his question or just replied that answering it is just beyond
your competence (just as I did). For even if he makes a new bug report
(which he might or might not do), Iuri will still have to get past the
question he has raised in order to get this bug pushed from the point of
going nowhere.

Having said this, I invite Iuri to explain his question better, should it
seem too vague for the Ubuntu kernel wizards, and I hope for someone to
help with answering that very exact question.

2014-06-18 1:22 GMT+02:00 Christopher M. Penalver <
<email address hidden>>:

> Žygimantas Beručka, as you can respect, this isn't userspace, and the
> triaging is done differently, both down and upstream. So, as you put it,
> he can have the "same damn hardware" but unless he put in a new bug
> report, nobody could verify that at this point but Iuri and Iuri alone.
> Also, suggesting someone go do this same thing elsewhere also isn't
> terribly helpful, and will more than likely have the issue ignored (all
> of this is already well documented in the links noted in
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315277/comments/10
> as you are welcome to review).
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1315277
>
> Title:
> [Dell Inspiron 1525] Trusty freezes on resume from suspend
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1315277/+subscriptions
>

[Iuri Diniz (iuridiniz)]

I did a bisect and found the bad commit: #1331654 (it's a upstream bug)

[Iuri Diniz (iuridiniz)]

So, could I consider this bug as a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1331654 ?

[Žygimantas Beručka (zygis)]

I believe it indeed is a duplicate of your report. Just let me check if 2b85886a5457f5c5dbcd32edbd4e6bba0f4e8678 solves the issue on my machine.

[Žygimantas Beručka (zygis)]

Since shacharr's prebuilt packages with the cherry-picked 2b85886a5457f5c5dbcd32edbd4e6bba0f4e8678 commit fixed the issue for me and you, I'm marking this as a duplicate. The patch must be included it in the next kernel update for Trusty.