Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting

Bug #1648388 reported by Lo
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OEM Priority Project
Triaged
Low
Unassigned
linux (Ubuntu)
Triaged
High
Unassigned
Xenial
Triaged
High
Unassigned

Bug Description

Install Ubuntu16.04 in RAID1 created by Intel RSTe no matter legacy mode or UEFI mode.
System hangs while rebooting

Not found the issue in RAID0
No issue on Ubuntu14.04
Driver-OS inbox support

Below as error messages
===================================================
INFO: task systemd-shutdow:1 blocked for more than 120 seconds.
            Not tainted 4.4.0-21-generic #37-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

INFO: task jbd2/md126p2-8:1732 blocked for more than 120 seconds.
            Not tainted 4.4.0-21-generic #37-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

INFO: task ext4lazyinit:1873 blocked for more than 120 seconds.
            Not tainted 4.4.0-21-generic #37-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

INFO: task kworker/u66:4:3139 blocked for more than 120 seconds.
            Not tainted 4.4.0-21-generic #37-Ubuntu
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
===================================================

WORKAROUND: edit /etc/sysctl.conf with follow commands and the system don't hang while rebooting:
vm.dirty_background_ratio=5
vm.dirty_ratio=10
kernel.panic=3
kernel.hung_task_panic=1
kernel.hung_task_timeout_secs=30

---
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=f578df47-a1b8-4e66-bd37-904f943eb01b
InstallationDate: Installed on 2016-12-15 (10 days ago)
InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3)
MachineType: Dell DCS6430G
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed root=UUID=bc552762-1955-44b8-a83e-2a414f0e0bd1 ro
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-21-generic N/A
 linux-backports-modules-4.4.0-21-generic N/A
 linux-firmware 1.157
RfKill:

Tags: xenial
Uname: Linux 4.4.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 03/22/2016
dmi.bios.vendor: Dell
dmi.bios.version: 2.0.3
dmi.board.name: 038VV0
dmi.board.vendor: Dell
dmi.board.version: X01
dmi.chassis.type: 23
dmi.chassis.vendor: Dell
dmi.modalias: dmi:bvnDell:bvr2.0.3:bd03/22/2016:svnDell:pnDCS6430G:pvr:rvnDell:rn038VV0:rvrX01:cvnDell:ct23:cvr:
dmi.product.name: DCS6430G
dmi.sys.vendor: Dell

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: New → Confirmed
affects: magnum → linux (Ubuntu)
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1648388

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
Lo (cr7)
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 prior kernel version where you were not having this particular problem?

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

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Lo (cr7) wrote :

After update the latest v4.9 kernel ,the issue still exist.

Below as error messages
===================================================
INFO: task systemd-shutdow:1 blocked for more than 120 seconds.
            Not tainted 4.9.0-040900rc8-generic #201612051443
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

INFO: task jbd2/md126p2-8:2710 blocked for more than 120 seconds.
            Not tainted 4.9.0-040900rc8-generic #201612051443
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
===================================================

Thanks

Revision history for this message
Lo (cr7) wrote : JournalErrors.txt

apport information

tags: added: apport-collected xenial
description: updated
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Lo:
1) To clarify https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/comments/4 did you test 4.9-rc8 or 4.9?
2) Could you please boot into the default Ubuntu kernel (not upstream/mainline) and then execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 1648388

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Lo (cr7) wrote : AlsaInfo.txt

apport information

description: updated
Revision history for this message
Lo (cr7) wrote : CRDA.txt

apport information

Revision history for this message
Lo (cr7) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Lo (cr7) wrote : IwConfig.txt

apport information

Revision history for this message
Lo (cr7) wrote : JournalErrors.txt

apport information

Revision history for this message
Lo (cr7) wrote : Lspci.txt

apport information

Revision history for this message
Lo (cr7) wrote : Lsusb.txt

apport information

Revision history for this message
Lo (cr7) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Lo (cr7) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Lo (cr7) wrote : ProcModules.txt

apport information

Revision history for this message
Lo (cr7) wrote : UdevDb.txt

apport information

Revision history for this message
Lo (cr7) wrote : WifiSyslog.txt

apport information

Revision history for this message
Lo (cr7) wrote :

To : Christopher M. Penalver

1 )
    I test kernel version is 4.9-rc8

2 )
    Done. The default kernel version is 4.4.0-21-generic

Thanks

Revision history for this message
penalvch (penalvch) wrote :

Lo, could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description, or the result of a terminal command)?

description: updated
tags: added: regression-release
tags: added: kernel-bug-exists-upstream-4.9-rc8 needs-upstream-testing
Revision history for this message
Douglas Haunsperger (dhaunsperger) wrote :

Christopher,
That's a tougher question than you might think. :)

The full system is a rack-scale product developed by Dell's Data Center Solutions division called DSS9000. This is not a generally-available system, but is produced only for hyperscale and other large-volume clients. However, the motherboard used in the system (DSS 9500M) in question is also used in the PowerEdge C6320 product, which is a generally available product.

Canonical has qualified the half-width (DSS 9520) and full-width (DSS 9500) sled options within the DSS 9000 framework on Ubuntu 16.04.

Revision history for this message
penalvch (penalvch) wrote :

Lo, to keep this relevant to upstream, one would want to periodically check for, and test the latest mainline kernel (now 4.10-rc3) as it is released.

Could you please advise?

Revision history for this message
Lo (cr7) wrote :

Christopher,
I try the latest mainline kernel v4.10-rc3 still found the issue.
Thanks

Revision history for this message
penalvch (penalvch) wrote :

Lo, the next step is to fully commit bisect from kernel 3.13 to 4.4 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, or providing a commit from a kernel version bisect 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.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.10-rc3 needs-bisect
removed: kernel-bug-exists-upstream-4.9-rc8 needs-upstream-testing
Revision history for this message
Lo (cr7) wrote :

Christopher,
I try mainline kernel from 3.12 to 3.19 in Ubuntu16.04.
Still found the issue.

Thanks

Revision history for this message
Lo (cr7) wrote :

I try install Ubuntu14.04 in RAID1 and update mainline kernel v4.10-rc3.
It reboots successfully without any error.
Thanks

penalvch (penalvch)
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
assignee: nobody → Joseph Salisbury (jsalisbury)
status: Confirmed → In Progress
Changed in linux (Ubuntu Xenial):
status: New → In Progress
importance: Undecided → Medium
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

@Lo, It sounds like the 4.10-rc3 kernel exhibits the bug on 16.04 but not on 14.04, is that correct? That might indicate the bug outside of the kernel.

Can you test the 4.11-rc1 kernel with 16.04? That kernel can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11-rc1/

It might also be worth while to test the current daily iso image from:
Desktop:
http://cdimage.ubuntu.com/daily-live/current/
Server:
http://cdimage.ubuntu.com/ubuntu-server/daily/current/

Changed in linux (Ubuntu):
importance: Medium → High
Changed in linux (Ubuntu Xenial):
importance: Medium → High
assignee: nobody → Joseph Salisbury (jsalisbury)
Revision history for this message
Lo (cr7) wrote :

Hi Joseph

The kernel 4.11-rc1 with 16.04 still has the issue.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Does the 4.11-rc1 kernel exhibit the bug on 14.04?

Changed in oem-priority:
assignee: nobody → Yuan-Chen Cheng (ycheng-twn)
status: New → Triaged
Changed in oem-priority:
importance: Undecided → Medium
assignee: Yuan-Chen Cheng (ycheng-twn) → nobody
Changed in oem-priority:
importance: Medium → Low
Changed in linux (Ubuntu):
assignee: Joseph Salisbury (jsalisbury) → nobody
Changed in linux (Ubuntu Xenial):
assignee: Joseph Salisbury (jsalisbury) → nobody
Changed in linux (Ubuntu):
status: In Progress → Triaged
Changed in linux (Ubuntu Xenial):
status: In Progress → Triaged
Brad Figg (brad-figg)
tags: added: cscc
Rex Tsai (chihchun)
tags: added: oem-priority
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.