From: Sonny Rao <sonny@burdell.org>
To: Phil Dier <phil@icglink.com>
Cc: Neil Brown <neilb@cse.unsw.edu.au>,
linux-kernel@vger.kernel.org, ziggy@icglink.com,
scott@icglink.com, jack@icglink.com
Subject: Re: 2.6.13-rc6 Oops with Software RAID, LVM, JFS, NFS
Date: Fri, 12 Aug 2005 14:35:48 -0400 [thread overview]
Message-ID: <20050812183548.GA2255@kevlar.burdell.org> (raw)
In-Reply-To: <20050812123505.1515634c.phil@icglink.com>
On Fri, Aug 12, 2005 at 12:35:05PM -0500, Phil Dier wrote:
> On Fri, 12 Aug 2005 12:07:21 +1000
> Neil Brown <neilb@cse.unsw.edu.au> wrote:
> > You could possibly put something like
> >
> > struct bio_vec *from;
> > int i;
> > bio_for_each_segment(from, bio, i)
> > BUG_ON(page_zone(from->bv_page)==NULL);
> >
> > in generic_make_requst in drivers/block/ll_rw_blk.c, just before
> > the call to q->make_request_fn.
> > This might trigger the bug early enough to see what is happening.
>
>
> I've got tests running with this code in place, by I/O is so slow now
> I don't think it's going to oops (or if it does, it'll be a while)..
>
> Is there any other info I can collect to help track this down?
Well, while we are slowing things down in the name of debugging..
you might try setting the following debug options in your config:
CONFIG_DEBUG_PAGEALLOC
CONFIG_DEBUG_HIGHMEM
CONFIG_DEBUG_SLAB
CONFIG_FRAME_POINTER
Can anyone think of anything else?
According to the website you don't have these on right now.
Sonny
next prev parent reply other threads:[~2005-08-12 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 15:59 Phil Dier
2005-08-12 2:07 ` Neil Brown
2005-08-12 4:17 ` Phil Dier
2005-08-12 17:35 ` Phil Dier
2005-08-12 18:35 ` Sonny Rao [this message]
2005-08-15 2:03 ` Phil Dier
2005-08-15 2:40 ` Zwane Mwaikambo
2005-08-15 3:08 ` Robert Love
2005-08-15 3:20 ` Zwane Mwaikambo
2005-08-15 17:44 ` Phil Dier
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=20050812183548.GA2255@kevlar.burdell.org \
--to=sonny@burdell.org \
--cc=jack@icglink.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--cc=phil@icglink.com \
--cc=scott@icglink.com \
--cc=ziggy@icglink.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome