Fan on full speed without noapic or nolapic on HP 6715s

[Carl Englund]

Without adding noapic or nolapic to boot parameters the fan will run on full speed, the system is sluggish (can almost see windows redrawing on screen). On some kernel versions tested, rebooting also fails.

The parameter(s) were not required in Trusty. I also tested some Mainline kernels and discovered 3.19.8 and 4.0.9 works without the parameters. At least 4.1.29 and onward requires noapic or nolapic for this machine to work properly but I have yet to investigate the versions between 4.0.9 and 4.1.29.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-34-generic 4.4.0-34.53
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: diskdoc 2700 F.... pulseaudio
CurrentDesktop: XFCE
Date: Wed Aug 10 01:15:07 2016
HibernationDevice: RESUME=UUID=522810df-638a-412b-9aab-791e2e2bc545
InstallationDate: Installed on 2016-06-07 (63 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard HP Compaq 6715s (RU655ET#AK8)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=3a37ee65-4c02-4a95-b814-f4538a4a308d ro quiet splash noapic acpi_force_32bit_fadt_addr vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-34-generic N/A
 linux-backports-modules-4.4.0-34-generic N/A
 linux-firmware 1.157.2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68YTT Ver. F.20
dmi.board.name: 30C2
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.2D
dmi.chassis.asset.tag: CNU7201T8J
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68YTTVer.F.20:bd12/01/2011:svnHewlett-Packard:pnHPCompaq6715s(RU655ET#AK8):pvrF.20:rvnHewlett-Packard:rn30C2:rvrKBCVersion71.2D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6715s (RU655ET#AK8)
dmi.product.version: F.20
dmi.sys.vendor: Hewlett-Packard

[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 v4.8 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'.

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/v4.8-rc1

[Carl Englund (englundc)]

Tested 4.8.0 rc2, problem persists.

[Carl Englund (englundc)]

I have done some testing of different kernels from the mainline repository, omitting the noapic parameter to see if they start and how the fan behaves. This is the result. Kernels using 64-bit FADT cause the machine to malfunction, as per: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590154

4.1.0: fan ok, 32-bit FADT
4.1.10: fan ok, 64-bit FADT. X.org freeze.
4.1.11: fan ok, boot freeze
4.1.12: fan ok, boot freeze
4.1.13: fan ok, boot freeze
4.1.17: fan ok, boot freeze
4.1.23: fan ok, 64-bit FADT
4.1.24: fan ok, boot freeze
4.1.25: fan ok, boot freeze
4.1.26: fan ok, boot freeze
4.1.30: fan ok, 64-bit FADT, X.org freeze.
4.2.0: fan ok, boot freeze
4.2.4: fan full, very dark screen (but working?)
4.2.7: fan full, 64-bit FADT
(U) 4.4.0-21: fan full, 32-bit FADT
(U) 4.4.0-34: fan ok, 32-bit FADT
4.8.0-rc2: fan full, 32-bit FADT

The kernels marked (U) are downloaded from the normal repositories. This machine is currently running Mint 18 but I understand Mint uses Ubuntu kernels so I hope it's alright testing in Mint.

I'm thinking it could be interesting to bisect 4.4.0-21 to 4.4.0-34 and see what causes the fan to start behaving normally.

[Carl Englund (englundc)]

I made a mistake, 4.4.0-34 does not boot with normal fan speed without noapic. Instead, it seems the change/break appears between 4.2.3 and 4.2.4. I will try to bisect there. Here is the updated list:

4.1.0: fan ok, 32-bit FADT
4.1.1: fan ok, 32-bit FADT
4.1.2: fan ok, 32-bit FADT
4.1.3: fan ok, 32-bit FADT
4.1.4: ?, boot freeze
4.1.5: ?, boot freeze
4.1.10: fan ok, 64-bit FADT. Freezes after a bit in Xorg.
4.1.11: fan ok, boot freeze
4.1.12: fan ok, boot freeze
4.1.13: fan ok, boot freeze
4.1.17: fan ok, boot freeze
4.1.23: fan ok, 64-bit FADT
4.1.24: fan ok, boot freeze
4.1.25: fan ok, boot freeze
4.1.26: fan ok, boot freeze
4.1.30: fan ok, X freeze, 64-bit fadt
4.2.0: fan ok, boot freeze
4.2.1: ??, boot freeze
4.2.2: fan ok, boot freeze
4.2.3: fan ok, boot freeze
4.2.4: fan full, boot freeze or dark screen (but working?)
4.2.7: fan full, 64-bit fadt
4.4.0-21: fan full, 32-bit fadt
4.4.0-34: fan full, 32-bit fadt
4.8.0-rc2: fan full, 32-bit fadt

[penalvch (penalvch)]

Carl Englund, to keep this relevant to upstream, one would want to test the latest mainline kernel (now 4.8-rc4) as it is released.

Could you please advise?

[Carl Englund (englundc)]

Tested 4.8-rc8, problem remains

[penalvch (penalvch)]

Carl Englund, the next step is to fully commit bisect from kernel 4.0.9 to 4.1.29 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.

Also, the kernel release names are irrelevant for the purposes of bisecting.

It is most helpful that after the fix commit (not kernel version) has been identified, you then mark this report Status Confirmed.

Thank you for your help.

[Carl Englund (englundc)]

I could use some help, but nobody answered. Is there some IRC channel I should turn to instead?

https://ubuntuforums.org/showthread.php?t=2338146

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

Carl Englund, please see https://community.ubuntu.com/contribute/support/irc/ .

In addition to the bisect, to keep this relevant to upstream, one would want to periodically check for, and test the latest mainline kernel (now 4.9) as it is released.

Could you please advise?

[Carl Englund (englundc)]

I scrapped the two 6715s I had and can no longer test them.

/ Carl

Den 20 dec 2016 18:25 skrev "Christopher M. Penalver" <
<email address hidden>>:

> Carl Englund, please see
> https://community.ubuntu.com/contribute/support/irc/ .
>
> In addition to the bisect, to keep this relevant to upstream, one would
> want to periodically check for, and test the latest mainline kernel (now
> 4.9) as it is released.
>
> Could you please advise?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1611536
>
> Title:
> Fan on full speed without noapic or nolapic on HP 6715s
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1611536/+subscriptions
>

[penalvch (penalvch)]

Carl Englund, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1611536/comments/13 regarding you no longer have the hardware. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.