From: Andrew Morton <akpm@linux-foundation.org>
To: "Philipp Tölke" <philipptoelke@web.de>
Cc: dm-devel@redhat.com, linux-kernel@vger.kernel.org,
Alasdair G Kergon <agk@redhat.com>,
Christophe Saout <christophe@saout.de>
Subject: Re: PROBLEM: Oops when using dm-crypt with dpt_i2o
Date: Fri, 3 Aug 2007 13:52:39 -0700 [thread overview]
Message-ID: <20070803135239.42ae6208.akpm@linux-foundation.org> (raw)
In-Reply-To: <46B39416.7040809@web.de>
On Fri, 03 Aug 2007 22:46:14 +0200
Philipp T__lke <philipptoelke@web.de> wrote:
> Hi Andrew, hi everybody!
>
> Thanks for the reply!
>
> Andrew Morton wrote:
> >> The oopses:
> >>
> >> #v+
> >> BUG: unable to handle kernel paging request at virtual address 14001000
> >> [...]
> >
> > So it looks like q->request_fn points at 0x14001000, which is in outer
> > space.
> >
> > I wonder how that could happen, in the middle of heavy IO operations.
> > Possibly a memory scribble. I'd suggest you enable CONFIG_SLAB,
> > CONFIG_DEBUG_SLAB, CONFIG_DEBUG_PAGEALLOC.
>
> That doesn't change anything, apart from adding a line "DEBUG_PAGEALLOC"
> to the oopses.
drat.
> Do I have to enable the debugging manually? After a quick
> grep over the sources and a google-session I think not but I'm no
> kernel-hacker.
No, just enable it.
> > You could also try switching
> > from CONFIG_SLAB to CONFIG_SLUB, then enable CONFIG_SLUB_DEBUG.
>
> Unfortunately the only change seems to be, that the Keyboard-Leds don't
> flash after the crash. Everything else is the same.
drat.
> Could a hardware-error cause this?
It sounds unlikely. One wouldn't expect it to crash in the same way each
time.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: "Philipp Tölke" <philipptoelke@web.de>
Cc: linux-kernel@vger.kernel.org, dm-devel@redhat.com,
Christophe Saout <christophe@saout.de>,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: PROBLEM: Oops when using dm-crypt with dpt_i2o
Date: Fri, 3 Aug 2007 13:52:39 -0700 [thread overview]
Message-ID: <20070803135239.42ae6208.akpm@linux-foundation.org> (raw)
In-Reply-To: <46B39416.7040809@web.de>
On Fri, 03 Aug 2007 22:46:14 +0200
Philipp T__lke <philipptoelke@web.de> wrote:
> Hi Andrew, hi everybody!
>
> Thanks for the reply!
>
> Andrew Morton wrote:
> >> The oopses:
> >>
> >> #v+
> >> BUG: unable to handle kernel paging request at virtual address 14001000
> >> [...]
> >
> > So it looks like q->request_fn points at 0x14001000, which is in outer
> > space.
> >
> > I wonder how that could happen, in the middle of heavy IO operations.
> > Possibly a memory scribble. I'd suggest you enable CONFIG_SLAB,
> > CONFIG_DEBUG_SLAB, CONFIG_DEBUG_PAGEALLOC.
>
> That doesn't change anything, apart from adding a line "DEBUG_PAGEALLOC"
> to the oopses.
drat.
> Do I have to enable the debugging manually? After a quick
> grep over the sources and a google-session I think not but I'm no
> kernel-hacker.
No, just enable it.
> > You could also try switching
> > from CONFIG_SLAB to CONFIG_SLUB, then enable CONFIG_SLUB_DEBUG.
>
> Unfortunately the only change seems to be, that the Keyboard-Leds don't
> flash after the crash. Everything else is the same.
drat.
> Could a hardware-error cause this?
It sounds unlikely. One wouldn't expect it to crash in the same way each
time.
next prev parent reply other threads:[~2007-08-03 20:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 18:45 PROBLEM: Oops when using dm-crypt with dpt_i2o Philipp Tölke
2007-08-03 18:04 ` Andrew Morton
2007-08-03 18:04 ` Andrew Morton
2007-08-03 20:46 ` Philipp Tölke
2007-08-03 20:52 ` Andrew Morton [this message]
2007-08-03 20:52 ` Andrew Morton
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=20070803135239.42ae6208.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=agk@redhat.com \
--cc=christophe@saout.de \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=philipptoelke@web.de \
/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.