This bug was fixed in the package linux - 4.4.0-51.72
---
linux (4.4.0-51.72) xenial; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1644611
* 4.4.0-1037-snapdragon #41: kernel panic on boot (LP: #1644596)
- Revert "dma-mapping: introduce the DMA_ATTR_NO_
This bug was fixed in the package linux - 3.13.0-103.150
---
linux (3.13.0-103.150) trusty; urgency=low
[ Luis Henriques ]
* Release Tracking Bug
- LP: #1644489
* Possible regression on 3.13.0-102.149~precise1 x86_64 (gce) (LP: #1644302)
- SAUCE: apparmor: delete extra
Can you test the following two kernels? If 4.7 is good and 4.8-rc1 is
bad, we can bisect between those two:
4.7 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.7/
4.8-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.8-rc1/
If both those kernels are good, we can test later 4.8 release
3 matches
Mail list logo