On Thu, 2017-06-01 at 23:36 +0200, garjola@garjola.net wrote: > On Thu 01-Jun-2017 at 00:15:29 +0200, Ben Hutchings <ben@decadent.org > .uk> wrote: > > Control: tag -1 moreinfo > > > > On Wed, 31 May 2017 21:34:59 +0200 Garjola Dindi <garjola@garjola.net> > > wrote: > > [...] > > > For several weeks now I have been having issues after resume (both > > > > from RAM or from disk): my /home seems not to be accessible (at least > > for writing). This does not happen every time, but more something like > > once every 10 or 20 resume cycles. > > [...] > > > > Please send the messages that appear in the kernel log when you resume. > > (Run 'dmesg' as root to show the kernel log.) > > > > Ben. > > Hi, > > The problem appeared again. I ran dmesg and piped the output to a file > (in one of the non encrypted partitions) just after the problematic > resume, but after reboot (to be able to send this message), the file was > gone. > > Below is the output of dmesg after a fresh reboot and one successful > suspend/resume cycle. I dont't know if is is useful, since the problem > has not happened since the reboot. [...] I really need to see what happens in the failing case. Ben. -- Ben Hutchings The most exhausting thing in life is being insincere. - Anne Morrow Lindberg
Attachment:
signature.asc
Description: This is a digitally signed message part