Christian, was this ever resolved?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679208
Title:
Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with
intel_iommu=on
To manage notifications
I have subscribed to HPE Eddie and Ganesh to this bug whether they have
tested this with old kernel or some parameter needs to be added.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679208
Title:
** Tags removed: kernel-key
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679208
Title:
Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with
intel_iommu=on
Subscribing Narinder to map that to HPE if possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679208
Title:
Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with
intel_iommu=on
To
Hi Joseph,
no regression IMHO.
Only the frequency or signature of the issue changed by Kernel upgrades.
I did not yet go back further than Xenial but that is worth a try as soon as I
find time for it again.
I'd almost think it is a FW issue still, but then there is no better FW.
Do we have a way
Is this bug a regression? Did this issue start happening after an
update/upgrade? Was there a prior kernel version where you were not
having this particular problem?
It might be worth testing the Trusty or Precise kernel.
If it is a regression, we can perform a kernel bisect to identify the
Hard to install when the system is so broken :-/
I installed the latest Mainline which is 4.11.0-041100rc5.201704022131 and
enabled the intel_iommu on it.
- Reboot: ok
- Try to trigger with I/O
- Fio: still ok
- apt: working
- random working on the system: crash
That said verified to fail
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.11 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
** Tags removed: kernel-da-key
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679208
Title:
Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with
intel_iommu=on
After reboot it only took like 10 minutes this time to hit me again :-/
There seems no reliable way to be sure anymore.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1679208
Title:
Zesty
Seems I was happy about the FW being the fix too early, it turns out to still
pop up.
Just not on boot.
About 6 hours working I ran into it again.
... attaching the latest dmesg messages
** Changed in: linux (Ubuntu)
Status: Invalid => New
--
You received this bug notification because
** Attachment added: "failing again even after the FW upgrade to the latest
version"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679208/+attachment/4854345/+files/horsea-failing-again.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
>From there I ran some I/O as on the other system we had the impression tp
>trigger it by further I/O.
But the system is still fine - so the bug might be good documentation for the
next one hitting it, but TL;DR is: "FW bug - FW update".
Per this conclusion I'm setting the kernel task to
Updated the System to latest FW for the storage controller 4.52 (and iLO to
2.50).
With that updated to Zesty again all till working fine.
>From here I enabled intel_iommu=on and it booted which already is an
improvement.
--
You received this bug notification because you are a member of Ubuntu
We just found that the second box we tested just needed some time (or
I/O) to run into the same.
[ 8710.266192] DMAR: DRHD: handling fault status reg 2
[ 8710.289318] DMAR: [DMA Read] Request device [03:00.0] fault addr f8bf5000
[fault reason 06] PTE Read access is not set
[ 8865.745527]
Unassigning myself as "broken HW" no more seems an option, so for the
kernel Team to re-asssign.
Please let me know what the next steps you need would be.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This was brought to my attention:
http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04805565
While it has no relation to why it would be triggered by iommu (it
should isolate, not link access together right?) it might be worth the
FW upgrade to verify if it fixes the issue.
I'll
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Status: Incomplete => Triaged
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
In what appeared similar https://bugzilla.redhat.com/show_bug.cgi?id=649766
it was recommended to set iommu=pt, but in our case that does not help.
It changes the messaging but sitll fails on boot:
[ 75.256554] DMAR: [DMA Read] Request device [03:00.0] fault addr fec0e000
[fault reason 06]
** Attachment added: "Fail on zesty right on boot"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679208/+attachment/4853630/+files/fail-z.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "fail on x later after boot (minutes-hours into working
fine)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1679208/+attachment/4853629/+files/fail-x.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Please note that on the "good" system nobody ever used iommu device
assignment, I'll do so after the next days. That way we should also
learn if the can bring a good system into the failing mode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
22 matches
Mail list logo
