** Tags removed: needs-reverse-bisect
** Tags added: cherry-pick reverse-bisect-done
** Changed in: linux (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Now I think I have found the commit that fixes the issue by reverse bisecting
first kernel versions and the commits.
Since it is a reverse bisection it says first bad commit instead of good commit:
# first bad commit: [e92c1e0d40c50472f80820bd829645ce9fefd6c1] NFSv4:
Fix a nograce recovery hang
Happy to be able to help! It will take me a couple of days I guess but I'll
come back when
I have found the breakpoint.
Den 2016-02-12 kl. 22:26, skrev Christopher M. Penalver:
> Seved Torstendahl, the next step is to fully reverse commit bisect from
> kernel 4.2 to 4.5-rc3 in order to
Seved Torstendahl, the next step is to fully reverse commit bisect from
kernel 4.2 to 4.5-rc3 in order to identify the last bad commit, followed
immediately by the first good one. Once this good commit has been
identified, it may be reviewed for backporting. Could you please do this
following
** Tags added: kernel-fixed-upstream-4.5-rc3 needs-reverse-bisect
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1544462
Title:
automount fails on resume after suspend if file open for writing
To
** Description changed:
- For a couple of years I have usually not shut down my pc after using it, I
just leave it and let it hibernate.
+ For a couple of years I have usually not shut down my pc after using it, I
just leave it and let it suspend.
(Of course I have also shut down the system
I have just tested the new kernel and it works ok so far!
I'll update the bug reports now
Den 2016-02-11 kl. 18:34, skrev Joseph Salisbury:
> Would it be possible for you to test the latest upstream kernel? Refer
> to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
> v4.5
I have just tested the new kernel and it works ok so far!
But now I don't understand how to add a tag. On this page displaying the
bug activity I can't find tags or how to add one.
I want to add the tag 'kernel-fixed-upstream' and mark the bug as
"Confirmed"
--
You received this bug
I finally found the place for tags so the bug is now marked as it should
be
** Tags added: kernel-fixed-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Actually the system works ok until the program that is writing to the
file reaches a point where data must be written. E.g. in the example
above, continue writing after resume. When a limit is reached the buffer
shall be written to the file. Bang!! The terminal hangs and when I try
to examine the
I had used the information from the wiki page DebuggingKernelSuspend
"resume-trace" debugging procedure for finding buggy drivers
and made the system suspend by
sudo sh -c "sleep 720 && sync && echo 1 > /sys/power/pm_trace && pm-suspend"
i.e. wait 12 minutes before suspend. So dmesg.log4
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.5 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
12 matches
Mail list logo
