** Tags added: cscc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu Bionic)
Assignee: Joseph Salisbury (jsalisbury) => (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress => Confirmed
** Changed in: linux (Ubuntu Bionic)
I think our best bet is to perform the bisect. When you have a chance,
can you test the kernel posted in comment #34? I'll build the next test
kernel based on that test result.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tested the 4.17 kernel, and this is the issue I now see:
[...]
[ 17.340040] raid6: sse2x1 xor() 2828 MB/s
[ 17.408036] raid6: sse2x2 gen() 7445 MB/s
[ 17.472037] raid6: sse2x2 xor() 5425 MB/s
[ 17.540032] raid6: sse2x4 gen() 10259 MB/s
[ 17.604037] raid6: sse2x4 xor() 6286
Thanks for testing. The panic was not caused from anything you did.
That is a new bug in the 4.18 kernel. We will have to monitor this new
bug, since Cosmic will eventually be 4.18 based. We should also test
the latest Cosmic kernel, which is 4.17 based. It is available from:
Maybe I did something wrong, but this kernel (4.18) causes a kernel
panic. The process I followed was same as always, to wget the *.deb,
dpkg -i *.deb && update-grub at the end to ensure this kernel is used:
[6.538003] evm: security.SMACK64
[6.539108] evm: security.SMACK64EXEC
[
The problem with having the kernels pre-built is the bisect needs to
know whether a test kernel has the bug or not. Based on that input, the
bisect decides the next SHA1 to test.
Since it's been some time, maybe it would be best to first test the latest
mainline kernel again.
That will tell
Hi Joseph,
Sorry for such a late reply, but with all the recent business travel
I've been unable to continue working on this.
That said, now that things are calmer I can continue, however, I don't
have easy access the hardware in question and it is very time consuming
getting access to this
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Incomplete
** Changed in: linux (Ubuntu)
Status: In Progress => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I built the next test kernel, up to the following commit:
abb62c46d4949d44979fa647740feff3f7538799
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1761796
Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on
@Joseph:
Issue still exists:
ubuntu@superb-whale:~$ uname -a
Linux superb-whale 4.15.0-041500rc6-generic #201805171959 SMP Thu May 17
20:02:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
ubuntu@superb-whale:~$ sudo reboot
===
Stopping LVM2 metadata daemon...
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I started a kernel bisect between v4.15-rc6 and v4.15-rc7. The kernel
bisect will require testing of about 6 test kernels.
I built the first test kernel, up to the following commit:
d8887f1c7289848e74c92bd4322789a9cd7de699
The test kernel can be downloaded from:
So I've tested all the way from rc2 -> rc7, and confirm that rc7 is the
issue. In two different machines:
machine1: running kernel was rc3
machine2: running kernel was rc4
In both cases, after install of rc7, and reboot, I see the issue. Logs
for the latest:
Just to confirm, 4.15-rc1 does not have the issue, but 4.15 final does?
If that is the case, we can try to narrow it down further. Could you
test v4.15-rc9:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.15-rc9/
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Finally got around to test this. ANd this are my findings:
1. Installed 4.15-rc1 above, rebooted the machine, and did not see the
issue.
ubuntu@just-pika:~$ uname -a
Linux just-pika 4.15.0-041500rc1-generic #201711262030 SMP Mon Nov 27
I'd like to perform a bisect to figure out what commit caused this
regression. We need to identify the earliest kernel where the issue
started happening as well as the latest kernel that did not have this
issue.
Can you test the following kernels and report back? We are looking for
the first
This issue is not present in Artful. This issue is only present in
Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1761796
Title:
Rebooting bionic fails with hardware error on ProLiant DL360
Can you see if this bug happens with the Artful kernel? It is available from:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/ppa/+build/14537150
Since this bug does not happen with Xenial, we can perform a kernel
bisect to identify the commit that introduced the bug. We first need
collecting logs with mainline kernel.
** Summary changed:
- Rebooting bionic fails with hardware error
+ Rebooting bionic fails with hardware error on ProLiant DL360 Gen9
** Description changed:
From an ephemeral environment in an HPGen9, the machine fails to reboot
when the ephemeral
20 matches
Mail list logo
