From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mx3.redhat.com (mx3.redhat.com [172.16.48.32]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id k09I56106585 for ; Mon, 9 Jan 2006 13:05:06 -0500 Received: from sccrmhc11.comcast.net (sccrmhc11.comcast.net [63.240.77.81]) by mx3.redhat.com (8.13.1/8.13.1) with ESMTP id k09I4xRH029948 for ; Mon, 9 Jan 2006 13:04:59 -0500 Subject: Re: [linux-lvm] Re: more info on the hang with 2.6.15-rc5 In-reply-to: <17346.40174.865171.160466@dobie.ylee.org> References: <43C1580B.9020609@tmr.com> <43C28E52.8080104@mattgillen.net> <43C290D4.5030209@projecthugo.co.uk> <17346.40174.865171.160466@dobie.ylee.org> Date: Mon, 09 Jan 2006 11:05:20 -0700 From: Sebastian Kuzminsky Message-Id: Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Yeechang Lee Cc: linux-raid@vger.kernel.org, kernel-lists@projecthugo.co.uk, LVM general discussion and development Yeechang Lee wrote: > Matt Darcy 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 > ? 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Kuzminsky Subject: Re: [linux-lvm] Re: more info on the hang with 2.6.15-rc5 Date: Mon, 09 Jan 2006 11:05:20 -0700 Message-ID: References: <43C1580B.9020609@tmr.com> <43C28E52.8080104@mattgillen.net> <43C290D4.5030209@projecthugo.co.uk> <17346.40174.865171.160466@dobie.ylee.org> Return-path: In-reply-to: <17346.40174.865171.160466@dobie.ylee.org> Sender: linux-raid-owner@vger.kernel.org To: Yeechang Lee Cc: kernel-lists@projecthugo.co.uk, LVM general discussion and development , linux-raid@vger.kernel.org List-Id: linux-raid.ids Yeechang Lee wrote: > Matt Darcy 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 > ? 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