From: Christoph Hellwig <hch@infradead.org>
To: Alexander Beregalov <a.beregalov@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: 2.6.39-rc0: xfs: kernel BUG at mm/page_alloc.c:738
Date: Tue, 22 Mar 2011 04:47:55 -0400 [thread overview]
Message-ID: <20110322084755.GA14129@infradead.org> (raw)
In-Reply-To: <AANLkTincs+MyYf+2tt2Y3LMQdmF8PUAxKMxMXuKB72hZ@mail.gmail.com>
On Mon, Mar 21, 2011 at 04:34:46AM +0300, Alexander Beregalov wrote:
> Hi
>
> Steps to reproduce:
> run xfs_fsr on xfs device
>
> arch is x86 UP, kernel is 2.6.38-06507-ga952baa
>
> kernel BUG at mm/page_alloc.c:738!
> invalid opcode: 0000 [#1]
> last sysfs file: /sys/devices/system/cpu/cpu0/cpufreq/scaling_setspeed
> Modules linked in: hwmon_vid sata_sil i2c_nforce2
I don't really see anything XFS-specific in here. The page allocator
is unhappy, and we get there through the generic read code, which just
has a tiny xfs wrapper.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-03-22 8:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 1:34 2.6.39-rc0: xfs: kernel BUG at mm/page_alloc.c:738 Alexander Beregalov
2011-03-22 8:47 ` Christoph Hellwig [this message]
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=20110322084755.GA14129@infradead.org \
--to=hch@infradead.org \
--cc=a.beregalov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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