From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 38852] Oops in page_waitqueue during large copy to ext4 filesystem
Date: Wed, 6 Jul 2011 14:57:28 GMT [thread overview]
Message-ID: <201107061457.p66EvSwc004847@demeter2.kernel.org> (raw)
In-Reply-To: <bug-38852-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=38852
Jim Paris <jim@jtan.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #2 from Jim Paris <jim@jtan.com> 2011-07-06 14:57:27 ---
Nevermind this report. Besides installing new disks and upgrading the kernel,
I also added more RAM, so I just ran memtester for a while:
pagesize is 4096
pagesizemask is 0xfffffffffffff000
want 4096MB (4294967296 bytes)
got 4096MB (4294967296 bytes), trying mlock ...locked.
Loop 1:
Stuck Address : ok
Random Value : FAILURE: 0xfbb90e87ff7d6321 != 0xfbb90e87ff7d6721 at
offset 0x08ab3585.
FAILURE: 0xf7fcbbb567f370e7 != 0xf7fcbbb567f374e7 at offset 0x08ac3585.
FAILURE: 0xaedce87b7ff0b265 != 0xaedce87b7ff0b665 at offset 0x08b86f85.
FAILURE: 0x237ffcdd3b79d98a != 0x237ffcdd3b79dd8a at offset 0x08bbcd85.
... etc.
I'll go back to my known-good RAM and close this for now. Sorry for the noise.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
prev parent reply other threads:[~2011-07-06 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 13:47 [Bug 38852] New: Oops in page_waitqueue during large copy to ext4 filesystem bugzilla-daemon
2011-07-06 14:49 ` [Bug 38852] " bugzilla-daemon
2011-07-06 14:57 ` bugzilla-daemon [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=201107061457.p66EvSwc004847@demeter2.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).