I have installed the kernel 3.13.11-03131105-generic and the issue is
solved .
On Wed, Sep 3, 2014 at 5:13 PM, Richard Mortimer 1331...@bugs.launchpad.net
wrote:
It looks like linux-image-3.13.0-35-generic (3.13.0-35.62) contains the
fixes for this bug.
I've done some initial testing and
Yes. Works ok with Ubuntu 13.10. Ubuntu 13.10 is still available in my
laptop
Ashraf Ali
On Mon, Apr 14, 2014 at 1:59 AM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Ashraf Ali, did this problem not occur in a release prior to Trusty?
** Tags added: kernel-bug-exists
Sorry. It is beyond my technical ability
Ashraf Ali
On Mon, Apr 14, 2014 at 4:15 PM, Christopher M. Penalver
christopher.m.penal...@gmail.com wrote:
Ashraf Ali, the next step is to fully commit bisect from Saucy to Trusty
in order to identify the offending commit. Could you please do
'kernel-bug-exists-upstream'.
On Thu, Apr 10, 2014 at 9:07 PM, Joseph Salisbury
joseph.salisb...@canonical.com wrote:
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.14 kernel[0].
If this
Public bug reported:
suspend/resume failed. restart required to bring back system
ProblemType: KernelOops
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-23-generic 3.13.0-23.45
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
Annotation:
5 matches
Mail list logo