[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681313
T
I've updated to BIOS version 1.2.4, but it doesn't change this
behaviour.
> Does this only happen after suspend/resume? Or any specific usage pattern?
I think suspend/resume makes it easier to trigger. But I've seen these
showing up also without suspend/resume.
Also - just found a way to repro
BTW the latest BIOS is 1.2.4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681313
Title:
"port does not support device sleep" on Dell Precision 5520
To manage notifications about this bug go to:
Does this only happen after suspend/resume? Or any specific usage
pattern?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681313
Title:
"port does not support device sleep" on Dell Precision 5520
T
It's still showing up with pcie_aspm=off (and ppa kernel):
$ cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-4.11.0-041100rc6-generic
root=UUID=e38db0de-7f52-4cab-839b-6bfb046d4665 ro acpi_rev_override quiet
splash vt.handoff=7 pcie_aspm=off
$ dmesg
(...)
[ 352.877941] ata2.00: exception Emask 0x
Try booting with the following kernel parameter: pcie_aspm=off
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1681313
Title:
"port does not support device sleep" on Dell Precision 5520
To manage not
I think it was happening from the very beginning.
I'm still seeing this with ppa kernel 4.11.0-041100rc6-generic #201704091331:
[ 1889.428907] ata2.00: exception Emask 0x10 SAct 0x3c00 SErr 0x405 action
0xe frozen
[ 1889.428915] ata2.00: irq_stat 0x0040, connection status changed
[ 1889
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.11 kernel[
apport information
** Tags added: apport-collected xenial
** Description changed:
I'm seeing messages like below on Dell Precision 5520, which is on an
Ubuntu certified hardware list:
https://certification.ubuntu.com/hardware/201610-25144/
BIOS is updated to the latest version avai
