From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Kujau Subject: Re: [Bug #13666] WARNING: at mm/page_alloc.c:1743 __alloc_pages_nodemask Date: Tue, 4 Aug 2009 12:44:22 -0700 (PDT) Message-ID: References: <200908022226.52228.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: David Rientjes , Linux Kernel Mailing List , Andrew Morton , linux-ext4@vger.kernel.org To: "Rafael J. Wysocki" Return-path: Received: from moutng.kundenserver.de ([212.227.126.177]:49934 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753105AbZHDTol (ORCPT ); Tue, 4 Aug 2009 15:44:41 -0400 In-Reply-To: Sender: linux-ext4-owner@vger.kernel.org List-ID: On Sun, 2 Aug 2009 at 13:53, Christian Kujau wrote: > [ 124.683454] ------------[ cut here ]------------ > [ 124.683577] WARNING: at mm/page_alloc.c:1749 __alloc_pages_nodemask+0x4c4/0x5a0() Hm, I just wonder: is this something to worry about? The filesystem itself seems fine so far, but I don't want it to get (silently) corrupted with each mount because of this warning... > [ 124.683704] Hardware name: Lenovo > [ 124.683795] Modules linked in: fuse acpi_cpufreq nfsd lockd nfs_acl auth_rpcgss sunrpc lm75 hwmon usb_storage usb_libusual b43 mac80211 uhci_hcd cfg80211 ehci_hcd tg3 usbcore libphy ssb nls_base > [ 124.685187] Pid: 2743, comm: mount Not tainted 2.6.31-rc5 #1 > [ 124.685286] Call Trace: > [ 124.685383] [] ? warn_slowpath_common+0x7a/0xc0 > [ 124.685489] [] ? __alloc_pages_nodemask+0x4c4/0x5a0 > [ 124.685596] [] ? warn_slowpath_null+0x20/0x40 > [ 124.685700] [] ? __alloc_pages_nodemask+0x4c4/0x5a0 > [ 124.685808] [] ? delayacct_end+0xa2/0xd0 > [ 124.685913] [] ? __get_free_pages+0x21/0x60 > [ 124.686018] [] ? match_number+0x3d/0xc0 > [ 124.686122] [] ? parse_options+0xe2/0x5d0 > [ 124.686225] [] ? out_of_line_wait_on_bit+0xbb/0xf0 > [ 124.686334] [] ? __wait_on_buffer+0x28/0x50 > [ 124.686438] [] ? ext4_fill_super+0x457/0x2670 > [ 124.686542] [] ? vsnprintf+0x516/0x820 > [ 124.686646] [] ? kobject_get+0x1d/0x40 > [ 124.686752] [] ? disk_name+0xd7/0xe0 > [ 124.686855] [] ? get_sb_bdev+0x15a/0x1a0 > [ 124.686958] [] ? ext4_fill_super+0x0/0x2670 > [ 124.687062] [] ? ext4_get_sb+0x2d/0x50 > [ 124.687162] [] ? ext4_fill_super+0x0/0x2670 > [ 124.687265] [] ? vfs_kern_mount+0x58/0xd0 > [ 124.687369] [] ? do_kern_mount+0x56/0x120 > [ 124.687474] [] ? do_mount+0x23a/0x750 > [ 124.687575] [] ? copy_mount_options+0x61/0x160 > [ 124.687679] [] ? sys_mount+0x9f/0x100 > [ 124.687783] [] ? syscall_call+0x7/0xb > [ 124.687883] ---[ end trace e312a7d04db27a01 ]--- > [ 124.981799] EXT4-fs (dm-8): barriers enabled > [ 125.002226] kjournald2 starting: pid 2744, dev dm-8:8, commit interval 5 seconds > [ 125.003346] EXT4-fs (dm-8): internal journal on dm-8:8 > [ 125.003555] EXT4-fs (dm-8): delayed allocation enabled > [ 125.003751] EXT4-fs: file extents enabled > [ 125.343718] EXT4-fs: mballoc enabled > [ 125.343884] EXT4-fs (dm-8): mounted filesystem with ordered data mode > > > Full dmesg and config: http://nerdbynature.de/bits/2.6.31-rc5/ > > No mount options were passed on the commandline but read from fstab: > > $ grep ext4 /etc/fstab > /dev/mapper/wdc0 /mnt/disk0 ext4 nosuid,nodev,noexec,noauto,barrier 0 0 > > > I'm in the process of creating an e2image of this partition, would this > help anyone? > > Thanks, > Christian. -- BOFH excuse #166: /pub/lunch