s4 get Error taking CPU down -34

Bug #1718871 reported by Zhanglei Mao
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
Medium
Unassigned
Artful
Won't Fix
Medium
Unassigned

Bug Description

When test S4 on Huawei 1288H V5 server as
 #echo disk>/sys/power/state
It show error of
  Error taking CPU79 down: -34
  Non-boot CPUs are not disabled

The echo command return with error of:
  Write error: Numerical result out of range

From the dmesg it show error of:
  CPU79 disable failed: CPU have 2 vectors assigned and there are only 1 available
  Error taking CPU79 down: -34

This server have been passed 16.04 certification (https://certification.ubuntu.com/hardware/201707-25617/).

The test kernel is lasted 16.04.1 of linux-image-4.4.0-93-generic. It is also failed on 16.04 with kernel of 4.4.9-21-generic, 4.12.0-041200-generic,4.14.0-999-generic which was download from (http://kernel.ubuntu.com/~kernel-ppa/mainline/). But it works on 14.04 with kernel 3.13.0-24-generic and download kernel of 3.13.0-031300-generic from above link.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1718871/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Zhanglei Mao (zhanglei-mao) wrote :

This S4-cpu-down-screen-show.pdf contains the testing screen shot and dmesg of works well testing.

affects: ubuntu → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1718871

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: xenial
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 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.14-rc2/

tags: added: kernel-da-key needs-bisect
Changed in linux (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Zhanglei Mao (zhanglei-mao) wrote :

For the newest upstream kernel of http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc2/linux-image-4.14.0-041400rc2-generic_4.14.0-041400rc2.201709242031_amd64.deb. The S4 test is same error.

tags:kernel-bug-exists-upstream

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of a regression, and when this regression was introduced. If this is a regression, we can perform a kernel bisect to identify the commit that introduced the problem.

Changed in linux (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Zhanglei Mao (zhanglei-mao) wrote :

Tested works well kernel are:
   kernel 3.13.0-24-generic of 14.04
   Kernel 3.13.0-031300-generic on 14.04 from (http://kernel.ubuntu.com/~kernel-ppa/mainline/)

Tested was failed kernel are:

linux-image-4.4.0-93-generic of lasted 16.04.1
4.4.9-21-generic, 4.12.0-041200-generic,4.14.0-999-generic download from http://kernel.ubuntu.com/~kernel-ppa/mainline/) on 16.04

Revision history for this message
Zhanglei Mao (zhanglei-mao) wrote :

The attach file of ap.bug is apport-cli report on 16.04.3 with kernel of 4.10.0-28-generic. This kernel have same issue for s4.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you find the first kernel version from [1], that introduced the regression?

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/

Revision history for this message
Zhanglei Mao (zhanglei-mao) wrote :

For different kernel on http://kernel.ubuntu.com/~kernel-ppa/mainline/ and test on Ubuntu 14.04.1. All version below 4.2 works fine for S4, the kernel of 4.2, 4.3, 4.3 can't works for S4.

The 4.1 and 4.2 dmesg was attach.

Revision history for this message
Zhanglei Mao (zhanglei-mao) wrote :

4.1.demsg is from kernel 4.1 which works fine for s4 suspend.

Revision history for this message
Andy Whitcroft (apw) wrote : Closing unsupported series nomination.

This bug was nominated against a series that is no longer supported, ie artful. The bug task representing the artful nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu Artful):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.