From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Wu Fengguang <fengguang.wu@intel.com>
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,
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 09:07:18 +1000 [thread overview]
Message-ID: <1308438438.32158.62.camel@pasglop> (raw)
In-Reply-To: <20110618173355.GB4652@localhost>
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.
Cheers,
Ben.
> Thanks,
> Fengguang
>
> > > [ 842.680141] ------------[ cut here ]------------
> > > [ 842.680172] WARNING: at fs/fs-writeback.c:356 writeback_single_inode+0x3e/0x18f()
> > > [ 842.680178] Hardware name:
> > > [ 842.680182] Modules linked in: mga ppdev lp ipv6 fuse loop snd_ens1371 gameport snd_ac97_codec snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq sg sr_mod snd_timer snd_seq_device pcspkr evdev cdrom snd uhci_hcd ehci_hcd parport_pc rtc_cmos parport soundcore usbcore via686a snd_page_alloc ac97_bus hwmon i2c_viapro processor button
> > > [ 842.680248] Pid: 1341, comm: flush-8:0 Not tainted 3.0.0-rc3 #67
> > > [ 842.680254] Call Trace:
> > > [ 842.680269] [<c1254ada>] ? printk+0x18/0x1a
> > > [ 842.680281] [<c101fb6b>] warn_slowpath_common+0x77/0x8c
> > > [ 842.680288] [<c1092f8e>] ? writeback_single_inode+0x3e/0x18f
> > > [ 842.680294] [<c1092f8e>] ? writeback_single_inode+0x3e/0x18f
> > > [ 842.680300] [<c101fb9d>] warn_slowpath_null+0x1d/0x1f
> > > [ 842.680306] [<c1092f8e>] writeback_single_inode+0x3e/0x18f
> > > [ 842.680313] [<c1093519>] writeback_sb_inodes+0xcb/0x153
> > > [ 842.680320] [<c1093aba>] writeback_inodes_wb+0xb0/0xf1
> > > [ 842.680326] [<c1093c1d>] wb_writeback+0x122/0x1b0
> > > [ 842.680334] [<c1093d15>] wb_check_old_data_flush+0x6a/0x76
> > > [ 842.680340] [<c1093dc1>] wb_do_writeback+0xa0/0xf3
> > > [ 842.680347] [<c1093e53>] bdi_writeback_thread+0x3f/0xd7
> > > [ 842.680354] [<c1093e14>] ? wb_do_writeback+0xf3/0xf3
> > > [ 842.680366] [<c10328cc>] kthread+0x61/0x66
> > > [ 842.680373] [<c103286b>] ? kthread_worker_fn+0xf7/0xf7
> > > [ 842.680383] [<c125ce7e>] kernel_thread_helper+0x6/0xd
> > > [ 842.680388] ---[ end trace c75e8a0e74c129b7 ]---
> > >
> > >
> >
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-06-18 23:07 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 [this message]
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
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=1308438438.32158.62.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=fengguang.wu@intel.com \
--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.