All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryusuke Konishi <ryusuke-sG5X7nlA6pw@public.gmane.org>
To: users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org,
	eric225125-/E1597aS9LQAvxtiuMwx3w@public.gmane.org
Subject: Re: segctord problem
Date: Wed, 12 Aug 2009 12:28:45 +0900 (JST)	[thread overview]
Message-ID: <20090812.122845.28893666.ryusuke@osrg.net> (raw)
In-Reply-To: <229792.17907.qm-f9L/0AEUy02B9c0Qi4KiSlZ8N9CAUha/QQ4Iyu8u01E@public.gmane.org>

Hi!
On Tue, 11 Aug 2009 18:28:05 -0700 (PDT), Eric A wrote:
> I'm using the latest vanilla kernel (2.6.31-rc5-git7).  My distro is Gentoo with nilfs-utils-2.0.14.
> 
> Eric
> 
> 
> 
> ________________________________
> From: Jiro SEKIBA <jir-hfpbi5WX9J54Eiagz67IpQ@public.gmane.org>
> To: NILFS Users mailing list <users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org>
> Sent: Tuesday, August 11, 2009 8:46:45 PM
> Subject: Re: [NILFS users] segctord problem
> 
> Hi,
> 
> > I have been using nilfs as my rootfs for several weeks now and have been
> > experiencing random problems.  X programs will be become unresponsive and top
> > will show that segctord is using ~50%hi (100% of one core).
> 
> Which version of kernel and distro are you using?

According to your log, preemption count of the log-writer thread goes
wrong; it must be equal or greater than 0, but your log shows it
became -1 (0xffffffff) maybe due to some kind of bug in nilfs.

> Aug 11 17:00:59 gentoo klogd: BUG: scheduling while atomic: segctord/1312/0xffffffff

I'm looking at this problem, but I don't have no clue why this
happened.

Is it reproducible after reboot?

Thanks,
Ryusuke Konishi

  parent reply	other threads:[~2009-08-12  3:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11 22:06 segctord problem Eric A
     [not found] ` <949415.6494.qm-CSBWnlGNI82B9c0Qi4KiSlZ8N9CAUha/QQ4Iyu8u01E@public.gmane.org>
2009-08-12  0:46   ` Jiro SEKIBA
     [not found]     ` <877hx9g8p6.wl%jir-27yqGEOhnJbQT0dZR+AlfA@public.gmane.org>
2009-08-12  1:28       ` Eric A
     [not found]         ` <229792.17907.qm-f9L/0AEUy02B9c0Qi4KiSlZ8N9CAUha/QQ4Iyu8u01E@public.gmane.org>
2009-08-12  3:28           ` Ryusuke Konishi [this message]
     [not found]             ` <20090812.122845.28893666.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-12  4:12               ` Eric A
2009-08-12 17:30               ` Eric A
     [not found]                 ` <875433.79601.qm-GGnPTbcu0TGB9c0Qi4KiSlZ8N9CAUha/QQ4Iyu8u01E@public.gmane.org>
2009-08-13  7:10                   ` Ryusuke Konishi
     [not found]                     ` <20090813.161004.39219573.ryusuke-sG5X7nlA6pw@public.gmane.org>
2009-08-27 15:25                       ` Jérôme Poulin
     [not found]                         ` <debc30fc0908270825v747c1734xa59126623cfd5b05-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-27 21:39                           ` Jérôme Poulin
     [not found]                             ` <debc30fc0908271439x63d16227mbf5589c8db455b1e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-29 16:48                               ` Jérôme Poulin
     [not found]                                 ` <debc30fc0908290948g3ee60e81u1f024b3031e36f36-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-29 20:50                                   ` Ryusuke Konishi
     [not found]                                     ` <debc30fc0908291424l1b403bfcy9940b32fdda49b65@mail.gmail.com>
     [not found]                                       ` <debc30fc0908291424l1b403bfcy9940b32fdda49b65-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-30 21:30                                         ` Jérôme Poulin
     [not found]                                           ` <debc30fc0908301430x3b4b6138qab5928389be7ea60-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-08-31  6:11                                             ` Ryusuke Konishi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090812.122845.28893666.ryusuke@osrg.net \
    --to=ryusuke-sg5x7nla6pw@public.gmane.org \
    --cc=eric225125-/E1597aS9LQAvxtiuMwx3w@public.gmane.org \
    --cc=users-JrjvKiOkagjYtjvyW6yDsg@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.