From: Wu Fengguang <fengguang.wu@intel.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Meelis Roos <mroos@linux.ee>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: 3.0-rc3: WARNING: at fs/fs-writeback.c:356 writeback_single_inode+0x3e/0x18f()
Date: Sun, 19 Jun 2011 21:56:18 +0800 [thread overview]
Message-ID: <20110619135618.GA4545@localhost> (raw)
In-Reply-To: <1308438438.32158.62.camel@pasglop>
On Sun, Jun 19, 2011 at 07:07:18AM +0800, Benjamin Herrenschmidt wrote:
> On Sun, 2011-06-19 at 01:33 +0800, Wu Fengguang wrote:
> > Hi Benjamin,
> >
> > On Wed, Jun 15, 2011 at 02:42:56PM +1000, Benjamin Herrenschmidt wrote:
> > > On Tue, 2011-06-14 at 12:15 +0300, Meelis Roos wrote:
> > > > Tested 3.0-rc3 on my PC (2 PATA disks, single duron CPU). Got several of
> > > > these in dmesg:
> > >
> > > Same here on a powerpc64 machine while doing a fresh debian install
> > > (while the installer's installing the packages), -rc3 as well.
> >
> > Do you have some clue that this bug show up in between 3.0-rc1 and
> > 3.0-rc3, or between 2.6.39 and 3.0-rc3?
>
> No idea. I just noticed that as I was re-installing debian on a machine
> (to track down another problem actually).
>
> Maybe Meelis has more data.
OK, thanks.
Andi/Meelis, what's your kconfig? Hope that can give me more better
opportunity to reproduce the bug.
Thanks,
Fengguang
next prev parent reply other threads:[~2011-06-19 13:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 9:15 3.0-rc3: WARNING: at fs/fs-writeback.c:356 writeback_single_inode+0x3e/0x18f() Meelis Roos
2011-06-15 4:42 ` Benjamin Herrenschmidt
2011-06-18 17:33 ` Wu Fengguang
2011-06-18 23:07 ` Benjamin Herrenschmidt
2011-06-19 13:56 ` Wu Fengguang [this message]
2011-06-19 14:21 ` Meelis Roos
2011-06-20 16:50 ` Andi Kleen
2011-06-19 7:50 ` Meelis Roos
2011-06-19 14:34 ` Christoph Hellwig
2011-06-20 5:57 ` Meelis Roos
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=20110619135618.GA4545@localhost \
--to=fengguang.wu@intel.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
/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.