On 07/04/2012 11:15 PM, Marc MERLIN wrote:
On Wed, Jul 04, 2012 at 01:58:31PM +0800, Liu Bo wrote:
The dmesg log, sysrq log and stack dump info can usually be very helpful.
From your report, we can see the csum error and hang on log,
'no csum' is not that bad while hanging-on is serious
On Wed, Jul 04, 2012 at 01:58:31PM +0800, Liu Bo wrote:
The dmesg log, sysrq log and stack dump info can usually be very helpful.
From your report, we can see the csum error and hang on log,
'no csum' is not that bad while hanging-on is serious and dangerous.
so can you please get any
On 07/03/2012 03:58 AM, Marc MERLIN wrote:
On Fri, Jun 29, 2012 at 05:36:24AM -0700, Marc MERLIN wrote:
On Tue, Jun 26, 2012 at 10:20:12PM -0700, Marc MERLIN wrote:
On Tue, Jun 26, 2012 at 06:38:18PM -0700, Marc MERLIN wrote:
Now, I'm also seeing these below and I have this again (86% CPU):
On Fri, Jun 29, 2012 at 05:36:24AM -0700, Marc MERLIN wrote:
On Tue, Jun 26, 2012 at 10:20:12PM -0700, Marc MERLIN wrote:
On Tue, Jun 26, 2012 at 06:38:18PM -0700, Marc MERLIN wrote:
Now, I'm also seeing these below and I have this again (86% CPU):
6076 root 20 0 000 R
On Tue, Jun 26, 2012 at 12:36:37PM -0700, Marc MERLIN wrote:
I was fine with btrfs until 3.2.16, but when going to 3.4 or 3.4.4, I'm
having my system randomly not wanting to suspend to RAM.
My suspend light started flashing but the system wasn't suspending.
I was able to unlock X, run top,
On Tue, Jun 26, 2012 at 06:38:18PM -0700, Marc MERLIN wrote:
Now, I'm also seeing these below and I have this again (86% CPU):
6076 root 20 0 000 R 86 0.0 29:40.11 btrfs-delalloc-
How bad is it, doctor? I think I'll be going back to 3.2.16 for now though.
Back
