From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Christian Kujau <lists@nerdbynature.de>
Cc: David Rientjes <rientjes@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-ext4@vger.kernel.org
Subject: Re: [Bug #13666] WARNING: at mm/page_alloc.c:1743 __alloc_pages_nodemask
Date: Sun, 2 Aug 2009 22:26:51 +0200 [thread overview]
Message-ID: <200908022226.52228.rjw@sisk.pl> (raw)
In-Reply-To: <alpine.DEB.2.01.0908021314030.5831@bogon.housecafe.de>
On Sunday 02 August 2009, Christian Kujau wrote:
> Hm,
>
> looks like this *is* reproducible. After a reboot, mounting the very
> same ext4 filesystem triggers this WARNING again:
>
> [ 165.000603] ------------[ cut here ]------------
> [ 165.000726] WARNING: at mm/page_alloc.c:1749 __alloc_pages_nodemask+0x4c4/0x5a0()
> [ 165.000853] Hardware name: Lenovo
> [ 165.000944] Modules linked in: fuse acpi_cpufreq nfsd lockd nfs_acl auth_rpcgss sunrpc lm75 hwmon b43 usb_storage usb_libusual mac80211 cfg80211 uhci_hcd ehci_hcd tg3 ssb usbcore libphy nls_base
> [ 165.002297] Pid: 2789, comm: mount Not tainted 2.6.31-rc4 #1
> [ 165.002397] Call Trace:
> [ 165.002494] [<c1036dda>] ? warn_slowpath_common+0x7a/0xc0
> [ 165.002601] [<c1076be4>] ? __alloc_pages_nodemask+0x4c4/0x5a0
> [ 165.002708] [<c1036e40>] ? warn_slowpath_null+0x20/0x40
> [ 165.002812] [<c1076be4>] ? __alloc_pages_nodemask+0x4c4/0x5a0
> [ 165.002921] [<c106dc72>] ? delayacct_end+0xa2/0xd0
> [ 165.003027] [<c1076d41>] ? __get_free_pages+0x21/0x60
> [ 165.003132] [<c11f02bd>] ? match_number+0x3d/0xc0
> [ 165.003235] [<c1129512>] ? parse_options+0xe2/0x5d0
> [ 165.003340] [<c135116b>] ? out_of_line_wait_on_bit+0xbb/0xf0
> [ 165.003449] [<c10c6ff8>] ? __wait_on_buffer+0x28/0x50
> [ 165.003552] [<c112b5b7>] ? ext4_fill_super+0x457/0x2670
> [ 165.003657] [<c11ee136>] ? vsnprintf+0x516/0x820
> [ 165.003759] [<c11e7f1d>] ? kobject_get+0x1d/0x40
> [ 165.003865] [<c10ef5c7>] ? disk_name+0xd7/0xe0
> [ 165.003967] [<c10a37ca>] ? get_sb_bdev+0x15a/0x1a0
> [ 165.004107] [<c112b160>] ? ext4_fill_super+0x0/0x2670
> [ 165.004216] [<c112822d>] ? ext4_get_sb+0x2d/0x50
> [ 165.004315] [<c112b160>] ? ext4_fill_super+0x0/0x2670
> [ 165.004419] [<c10a24f8>] ? vfs_kern_mount+0x58/0xd0
> [ 165.004522] [<c10a2606>] ? do_kern_mount+0x56/0x120
> [ 165.004625] [<c10bb2da>] ? do_mount+0x23a/0x750
> [ 165.004727] [<c10b91c1>] ? copy_mount_options+0x61/0x160
> [ 165.004831] [<c10bb88f>] ? sys_mount+0x9f/0x100
> [ 165.004934] [<c1003304>] ? syscall_call+0x7/0xb
> [ 165.005044] ---[ end trace d2227ca6268a916a ]---
> [ 165.287930] EXT4-fs (dm-7): barriers enabled
>
> The whole dmesg and proc/meminfo is at:
> http://nerdbynature.de/bits/2.6.31-rc4/
>
> Note: "dm-7" is a dm-crypt device, backed by an external disk which is
> connected via USB. The filesystem itself seems fine however, nothing
> unusual except this warning so far...
The patches supposed to fix this issue went in right before -rc5 AFAIC.
Can you try to reproduce with -rc5?
Rafael
next prev parent reply other threads:[~2009-08-02 20:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Jya1GruKQpD.A.16.2GObKB@chimera>
[not found] ` <3zAHs5O6maO.A.GwE.OIObKB@chimera>
[not found] ` <alpine.DEB.2.00.0907261628180.17123@chino.kir.corp.google.com>
[not found] ` <200907280021.26320.rjw@sisk.pl>
[not found] ` <alpine.DEB.2.00.0907300021330.7540@chino.kir.corp.google.com>
2009-08-01 7:54 ` [Bug #13666] WARNING: at mm/page_alloc.c:1743 __alloc_pages_nodemask Christian Kujau
2009-08-01 19:56 ` David Rientjes
2009-08-01 21:30 ` Christian Kujau
2009-08-02 20:18 ` Christian Kujau
2009-08-02 20:26 ` Rafael J. Wysocki [this message]
2009-08-02 20:35 ` Christian Kujau
2009-08-02 20:53 ` Christian Kujau
2009-08-04 19:44 ` Christian Kujau
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=200908022226.52228.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=akpm@linux-foundation.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
--cc=rientjes@google.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