All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 45621] Kernel ooops: BUG: unable to handle kernel paging request at 000000080000001c
Date: Wed,  7 Nov 2012 09:58:40 +0000 (UTC)	[thread overview]
Message-ID: <20121107095840.2D82111FB59@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-45621-13602@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=45621


Ivan Shapovalov <intelfx100@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |intelfx100@gmail.com




--- Comment #7 from Ivan Shapovalov <intelfx100@gmail.com>  2012-11-07 09:58:39 ---
This (or similar) seems to be reproducible with reiser4 (another out-of-tree
filesystem) on a custom kernel.

Symptoms:
1) on newly allocated pages, sometimes page_private(pg) != 0ul
2) sometimes BUGs happen on 0000_0000_0000_000e in a following scenario:
pg = find_or_create_page(...);
// check for pg != NULL
// pg->mapping is accessed

Happens 2-3 times a day. Also different BUGs happened (addresses 0016, 00b0,
0f91) but the backtraces seem to be invalid and I can't describe the actual
in-code scenario.

Directly observed on kernels 3.2 to latest stable (but current reiser4
maintainer, Edward Shishkin, seen this on 2.6.39 - though just 1-2 times at
all).

In my case, the kernel is vanilla + -ck patchset + various config changes (KSM,
big pagetables, cleancache+frontswap+zcache, sparse memory model, transparent
hugepages).
The config is here: ftp://intelfx.homeip.net/kernel_config
Hardware is Acer 3830TG (HM65 chipset, SNB cpu, 4 GB of RAM). Running in x86_64
mode.

I know that this is too small level of detail - but can anything be done to
track down/collect more info?

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2012-11-07  9:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-04 23:33 [Bug 45621] New: Kernel ooops: BUG: unable to handle kernel paging request at 000000080000001c bugzilla-daemon
2012-08-04 23:45 ` [Bug 45621] " bugzilla-daemon
2012-08-05 22:12 ` bugzilla-daemon
2012-08-05 22:24 ` bugzilla-daemon
2012-08-05 22:36 ` bugzilla-daemon
2012-08-06 15:15 ` bugzilla-daemon
2012-08-06 22:14 ` bugzilla-daemon
2012-08-06 22:21   ` Gordan Bobic
2012-11-07  9:58 ` bugzilla-daemon [this message]
2012-11-07 12:42 ` bugzilla-daemon
2012-11-07 14:18 ` bugzilla-daemon
2013-11-19 23:43 ` bugzilla-daemon

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=20121107095840.2D82111FB59@bugzilla.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 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.