From: Andrea Arcangeli <aarcange@redhat.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: linux-mm@kvack.org, Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] BUG: unable to handle kernel paging request at fffba000
Date: Wed, 19 Jan 2011 21:01:06 +0100 [thread overview]
Message-ID: <20110119200106.GL9506@random.random> (raw)
In-Reply-To: <20110119124047.GA30274@kwango.lan.net>
Hello,
thanks for the report!
On Wed, Jan 19, 2011 at 02:40:47PM +0200, Ilya Dryomov wrote:
> Hello,
>
> I just built a fresh 38-rc1 kernel with transparent huge page support
> built-in (TRANSPARENT_HUGEPAGE=y) and it failed to boot with the
> following bug. However after the reboot everything went fine. It turns
> out it only happens when fsck checks one or more filesystems before they
> are mounted.
>
> It's easily reproducable it with touch /forcefsck and reboot on one of
> my 32-bit machines. Haven't tried it on others yet.
Could you send me the vmlinux (or bzImage)? I can't see where it crash
otherwise.
Most certainly it's 32bit bug only.
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Arcangeli <aarcange@redhat.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: linux-mm@kvack.org, Rik van Riel <riel@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] BUG: unable to handle kernel paging request at fffba000
Date: Wed, 19 Jan 2011 21:01:06 +0100 [thread overview]
Message-ID: <20110119200106.GL9506@random.random> (raw)
In-Reply-To: <20110119124047.GA30274@kwango.lan.net>
Hello,
thanks for the report!
On Wed, Jan 19, 2011 at 02:40:47PM +0200, Ilya Dryomov wrote:
> Hello,
>
> I just built a fresh 38-rc1 kernel with transparent huge page support
> built-in (TRANSPARENT_HUGEPAGE=y) and it failed to boot with the
> following bug. However after the reboot everything went fine. It turns
> out it only happens when fsck checks one or more filesystems before they
> are mounted.
>
> It's easily reproducable it with touch /forcefsck and reboot on one of
> my 32-bit machines. Haven't tried it on others yet.
Could you send me the vmlinux (or bzImage)? I can't see where it crash
otherwise.
Most certainly it's 32bit bug only.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-01-19 20:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-19 12:40 [BUG] BUG: unable to handle kernel paging request at fffba000 Ilya Dryomov
2011-01-19 12:40 ` Ilya Dryomov
2011-01-19 20:01 ` Andrea Arcangeli [this message]
2011-01-19 20:01 ` Andrea Arcangeli
2011-01-19 22:19 ` Andrea Arcangeli
2011-01-19 22:19 ` Andrea Arcangeli
2011-01-19 22:49 ` Ilya Dryomov
2011-01-19 22:49 ` Ilya Dryomov
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=20110119200106.GL9506@random.random \
--to=aarcange@redhat.com \
--cc=idryomov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.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 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.