| To: | Emmanuel Florac <eflorac@xxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: XFS crash on linux raid |
| From: | Eric Sandeen <sandeen@xxxxxxxxxxx> |
| Date: | Sat, 05 May 2007 11:50:12 -0500 |
| Cc: | Chris Wedgwood <cw@xxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <20070505171931.6fe9b6f5@xxxxxxxxxxxxxx> |
| References: | <20070503164521.16efe075@xxxxxxxxxxxxxxxxxxxx> <20070504005922.GC32602149@xxxxxxxxxxxxxxxxx> <20070504090613.7c0f97d3@xxxxxxxxxxxxxx> <20070504073344.GL32602149@xxxxxxxxxxxxxxxxx> <20070504152546.614374ac@xxxxxxxxxxxxxxxxxxxx> <463B4962.70904@xxxxxxxxxxx> <20070504173049.14606033@xxxxxxxxxxxxxxxxxxxx> <20070504232028.GA19744@xxxxxxxxxxxxxxxxxxxxx> <20070505171931.6fe9b6f5@xxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Thunderbird 2.0.0.0 (Macintosh/20070326) |
Emmanuel Florac wrote: Le Fri, 4 May 2007 16:20:28 -0700 vous écriviez:You could if you have time try this and enable CONFIG_I386_IRQSTACKS but don't enable CONFIG_I386_4KSTACKS and see if that helps...That sounds very interesting, I'll give it a try monday. There are also stack debugging config options; one that will warn if you are about to overflow (CONFIG_DEBUG_STACKOVERFLOW) and one that will print max stack depth in sysrq-t output (CONFIG_DEBUG_STACK_USAGE). -Eric |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: XFS crash on linux raid, Eric Sandeen |
|---|---|
| Next by Date: | Re: XFS crash on linux raid, Chris Wedgwood |
| Previous by Thread: | Re: XFS crash on linux raid, Emmanuel Florac |
| Next by Thread: | Re: XFS crash on linux raid, Chris Wedgwood |
| Indexes: | [Date] [Thread] [Top] [All Lists] |