[Lenovo ThinkPad SL510] Loud beep on resume from suspend

[[e-mail]]

After upgrading from kernel 3.13.x, my Thinkpad SL510 beeps loudly for ~50ms when opening the lid to resume from suspend. No other issues occur.
The beep when closing the lid is quiet and lasts ~130ms. This is reproducible in 15.10.

---
ApportVersion: 2.14.1-0ubuntu3.15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: uwer 2247 F.... pulseaudio
                      uwer 7833 F.... audacity
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=449bf762-bd99-4fb4-9d33-f86c42cebc06
InstallationDate: Installed on 2015-01-03 (280 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: LENOVO 28477MG
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-50-generic root=UUID=5b1f663b-f520-4c03-8df5-b66bcf2a74e3 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-50-generic N/A
 linux-backports-modules-3.16.0-50-generic N/A
 linux-firmware 1.127.15
Tags: trusty
Uname: Linux 3.16.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/19/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6JET94WW (1.52 )
dmi.board.name: 28477MG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr6JET94WW(1.52):bd06/19/2012:svnLENOVO:pn28477MG:pvrThinkPadSL510:rvnLENOVO:rn28477MG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 28477MG
dmi.product.version: ThinkPad SL510
dmi.sys.vendor: LENOVO

[penalvch (penalvch)]

<email address hidden>, thank you for reporting this and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1504829

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

apport information

[[e-mail] (uwer)]

Here's an audio recording.
Suspend beep first, resume beep second.

[penalvch (penalvch)]

<email address hidden>, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[penalvch (penalvch)]

<email address hidden>, the next step is to fully commit bisect from kernel 3.13 to 3.16 in order to identify the last good kernel commit, followed immediately by the first bad one. This will allow for a more expedited analysis of the root cause of your issue. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

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

[[e-mail] (uwer)]

Using the latest kernel 4.3rc4:
$ uname -a
Linux janeway 4.3.0-040300rc4-generic #201510041330 SMP Sun Oct 4 17:32:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

The suspend / resume behaviour does not seem to have changed.
Closing, waiting for the soft confirmation beep, waiting another 5-10 seconds and opening the lid again ten times yielded 6 loud beeps, 3 soft (normal) beeps and 1 very short, loud beep.

[[e-mail] (uwer)]

FWIW, Kernel 3.14.54 was good and 3.15.0-031500rc1 was bad.
Commit bisection is a little intimidating, since I have never done it before but I heve given it a try anyway.

I did the following

$ git clone git://kernel.ubuntu.com/ubuntu/ubuntu-trusty.git
$ cd ubuntu-trusty/
$ git checkout -b mybisect origin/master
$ git bisect start Ubuntu-3.19.0-12.12_14.04.1 Ubuntu-3.13.0-0.2

then I get:
Bisecting: a merge base must be tested
[7e3528c3660a2e8602abc7858b0994d611f74bc3] slab.h: remove duplicate kmalloc declaration and fix kernel-doc warnings

I'm stuck here, the FAQ section on the wiki page
https://wiki.ubuntu.com/Kernel/KernelBisection#Bisecting:_a_merge_base_must_be_tested
and lots of googling didn't help.

Can anyone sanity check what I have done so far and point me in the right direction as for the "merge base must be tested" message?

[[e-mail] (uwer)]

Bumping this 7 days before expiration. Hope to find some time during the holidays to investigate further.

[Launchpad Janitor (janitor)]

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