From: Meelis Roos <mroos@linux.ee>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.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 10:50:53 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1106191029590.14979@math.ut.ee> (raw)
In-Reply-To: <20110618173355.GB4652@localhost>
> > > 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?
Did some log grepping. 3.0-rc2 did not show them on 3 bootups but
3.0-rc3 had it while I did dist-upgrade. I rebooted into the 3.0-rc2
kernel and did todays dist-upgrade but the error did not show up, so
it's probably post-rc2.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2011-06-19 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 9:15 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
2011-06-19 14:21 ` Meelis Roos
2011-06-20 16:50 ` Andi Kleen
2011-06-19 7:50 ` Meelis Roos [this message]
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=alpine.SOC.1.00.1106191029590.14979@math.ut.ee \
--to=mroos@linux.ee \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®