[HP Pavilion 11-n038ca x360 PC] Boots very unreliably

[Rick Spencer]

Boots very unreliably.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-24-generic 3.13.0-24.47
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: rick 1911 F.... pulseaudio
CurrentDesktop: Unity
Date: Tue May 13 14:47:04 2014
HibernationDevice: RESUME=UUID=bd1e0db9-24a6-4fb7-a9c0-32c457348b08
InstallationDate: Installed on 2014-05-13 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
 Bus 001 Device 002: ID 05c8:036e Cheng Uei Precision Industry Co., Ltd (Foxlink)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Pavilion 11 x360 PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed root=UUID=5fb0f2a1-a777-4483-81cf-b488d59fc309 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.2
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/15/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2209
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 57.19
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.04:bd02/15/2014:svnHewlett-Packard:pnHPPavilion11x360PC:pvr0975100002405F00010420180:rvnHewlett-Packard:rn2209:rvr57.19:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 11 x360 PC
dmi.product.version: 0975100002405F00010420180
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Rick Spencer, thank you for reporting this and helping make Ubuntu better. As per http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4158&lc=en&cc=us&dlc=en&sw_lang=&product=6846607#N1394 an update to your BIOS is available (F.06). If you update to this following https://help.ubuntu.com/community/BiosUpdate does it change anything? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Thank you for your understanding.

[Gnu (dasgnu)]

Hello,
I have same issue. I tried with several kernel parameters (nomodeset or acpi=force, boot=...) but nothing helps. Ubuntu boots irregularly. After switching off the Hardware for more than 30 minutes the first boot seems to be fine.
A BIOS Update to F.06 doesn't change anything for me.

Shutdown of the HP x360 from ubuntu 14.04. is also not possible. Hardware is never switched off after shutdown and I need to hit the power button for 4+ seconds. Maybee it's related?

Kind regards

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[penalvch (penalvch)]

Gnu, 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 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

[Joseph Salisbury (jsalisbury)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

  With the recent release of this Ubuntu release, would like to confirm if this bug is still present. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Scott Ashcroft (scott-ashcroft)]

Hi,

I've been fiddling around with this for a while. Booting with init=/bin/bash allowed poweroff -f to work.
So I then booted into full userspace and started to rip modules out with rmmod.

It appears that the laptop has a Synopsys DesignWare controller embedded in it.
This makes the kernel load the dw_dmac_core and dw_dmac modules.
An rmmod of dw_dmac produces an instant lockup.
I think it is the same lockup happening at shutdown and reboot.
Blacklisting both modules makes shutdown and reboot work correctly for me.

I suspect that some sort of DMI based blacklist will be required in the kernel.
Exposing the hardware to user space probably isn't the best idea anyway.

Cheers,
Scott

[penalvch (penalvch)]

Scott Ashcroft, 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

[Scott Ashcroft (scott-ashcroft)]

What an odd response. I'm not reporting a new problem I'm offering a solution.
Surely it would be more useful if the original reporter tried blacklisting the modules which I suggest.
If he confirms that this is the required fix then what hardware I've got or kernel I'm running is irrelevant.

Cheers,
Scott

[Bart Monhemius (bart452)]

@Scott Ashcroft,

Can you please make a guide how to to that for other users?
I don' t have the knowledge to do it all by my self.

Thanks,

Bart

[Gnu (dasgnu)]

I can commit. Blacklisting of dw_dmac and dw_dmac_core modules results in booting and shutdown without any probles also on my machine.

@bart-96
try by typing:
echo "blacklist dw_dmac" | sudo tee -a /etc/modprobe.d/blacklist.conf
echo "blacklist dw_dmac_core" | sudo tee -a /etc/modprobe.d/blacklist.conf

[penalvch (penalvch)]

gnu, 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

[Bart Monhemius (bart452)]

@dasgnu

Thanks!

[Scott Ashcroft (scott-ashcroft)]

The Debian solution is just not to build those modules in the i386 and amd64 kernels.

Cheers,
Scott

[SignedAdam (signedadam)]

HP pavilion 11 x360, does not boot at all now in Ubuntu 14.10, booting stops at "(942) killed by TERM signal (OK)" I've tried booting in UEFI mode on and Legacy, also secure and not secure, still cant get to the desktop by live desktop or install

[penalvch (penalvch)]

SignedAdam, thank you for your comment. Unfortunately, this bug report is not scoped to you, your hardware, 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
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
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

[Launchpad Janitor (janitor)]

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