From: Sebastian Kuzminsky <seb@highlab.com>
To: Yeechang Lee <ylee@pobox.com>
Cc: linux-raid@vger.kernel.org, kernel-lists@projecthugo.co.uk,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Re: more info on the hang with 2.6.15-rc5
Date: Mon, 09 Jan 2006 11:05:20 -0700 [thread overview]
Message-ID: <E1Ew1OS-00034G-Ss@highlab.com> (raw)
In-Reply-To: <17346.40174.865171.160466@dobie.ylee.org>
Yeechang Lee <ylee@pobox.com> wrote:
> Matt Darcy <kernel-lists@projecthugo.co.uk> says:
> > Judging from the ammount of problems with this driver it is %90 the
> > driver and %10 raid interaction with the dirver
> >
> > I don't believe this is an LVM issue, more a case of the driver's
> > just not ready for use, so if you use it with raid and lvm you speed
> > up the crash.
>
> I'm coming into this late, but could your issue be related to
> <URL:https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167173>?
That problem was fixed or worked around by using 8K kernel stacks instead
of 4K. Both my kernels (debug & production) use 8K stacks, so I dont
think that's it.
What I get isn't crashes with stack traces & kernel messages like that
bug, I get hard lockups with no output.
--
Sebastian Kuzminsky
WARNING: multiple messages have this Message-ID (diff)
From: Sebastian Kuzminsky <seb@highlab.com>
To: Yeechang Lee <ylee@pobox.com>
Cc: kernel-lists@projecthugo.co.uk,
LVM general discussion and development <linux-lvm@redhat.com>,
linux-raid@vger.kernel.org
Subject: Re: [linux-lvm] Re: more info on the hang with 2.6.15-rc5
Date: Mon, 09 Jan 2006 11:05:20 -0700 [thread overview]
Message-ID: <E1Ew1OS-00034G-Ss@highlab.com> (raw)
In-Reply-To: <17346.40174.865171.160466@dobie.ylee.org>
Yeechang Lee <ylee@pobox.com> wrote:
> Matt Darcy <kernel-lists@projecthugo.co.uk> says:
> > Judging from the ammount of problems with this driver it is %90 the
> > driver and %10 raid interaction with the dirver
> >
> > I don't believe this is an LVM issue, more a case of the driver's
> > just not ready for use, so if you use it with raid and lvm you speed
> > up the crash.
>
> I'm coming into this late, but could your issue be related to
> <URL:https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=167173>?
That problem was fixed or worked around by using 8K kernel stacks instead
of 4K. Both my kernels (debug & production) use 8K stacks, so I dont
think that's it.
What I get isn't crashes with stack traces & kernel messages like that
bug, I get hard lockups with no output.
--
Sebastian Kuzminsky
next prev parent reply other threads:[~2006-01-09 18:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 5:07 [linux-lvm] more info on the hang with 2.6.15-rc5 Sebastian Kuzminsky
2005-12-22 5:07 ` Sebastian Kuzminsky
2005-12-22 17:13 ` [linux-lvm] " Old Fart
2006-01-08 18:20 ` [linux-lvm] " Bill Davidsen
2006-01-08 18:20 ` Bill Davidsen
2006-01-09 2:33 ` [linux-lvm] " Sebastian Kuzminsky
2006-01-09 2:33 ` Sebastian Kuzminsky
2006-01-09 16:24 ` [linux-lvm] " Matthew Gillen
2006-01-09 16:24 ` Matthew Gillen
2006-01-09 16:35 ` [linux-lvm] " Matt Darcy
2006-01-09 17:27 ` Yeechang Lee
2006-01-09 18:05 ` Sebastian Kuzminsky [this message]
2006-01-09 18:05 ` Sebastian Kuzminsky
2006-01-09 17:13 ` Sebastian Kuzminsky
2006-01-09 17:46 ` Mattias Wadenstein
2006-01-09 9:54 ` Matt Darcy
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=E1Ew1OS-00034G-Ss@highlab.com \
--to=seb@highlab.com \
--cc=kernel-lists@projecthugo.co.uk \
--cc=linux-lvm@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=ylee@pobox.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.