|To:||Christoph Hellwig <hch@xxxxxxxxxxxxx>|
|Subject:||Re: Need some help with cause of Oops in XFS 1.2|
|From:||Steven Dake <sdake@xxxxxxxxxx>|
|Date:||Tue, 25 Mar 2003 13:32:50 -0700|
|References:||<3E809EB1.6000904@xxxxxxxxxx> <20030325193838.A6142@xxxxxxxxxxxxx> <3E80B9C9.5090107@xxxxxxxxxx> <20030325203229.A6850@xxxxxxxxxxxxx>|
|User-agent:||Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20021130|
I suspect the issue wouldn't present itself with a vanilla 2.4.18 +
xfs1.2 tree as it would have already been caught... And unfortunately I
can't apply to a plain vanilla tree, it must go into this particular
tree for my company to release it...
If you have any suggestions on how I could debug, I'd be willing to try them out.
I was really hoping someone had run into this type of problem in the past and could provide some quick pointers on how I could debug.
Thanks -steve Christoph Hellwig wrote:
On Tue, Mar 25, 2003 at 01:19:21PM -0700, Steven Dake wrote:the preempt patch is applied (heavily modified, as I said :) however, I have preemption turned off. The other significant difference is the use of the real time scheduler (which is also turned off). The realtime scheduler was a MontaVista authored scheduler patch prior to O1.Can you please try to reproduce it with a plain 1.2 XFS tree? It's hard to debug some widly different tree we don't even have source to.
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: Need some help with cause of Oops in XFS 1.2, Christoph Hellwig|
|Next by Date:||Re: Need some help with cause of Oops in XFS 1.2, Christoph Hellwig|
|Previous by Thread:||Re: Need some help with cause of Oops in XFS 1.2, Christoph Hellwig|
|Next by Thread:||Re: Need some help with cause of Oops in XFS 1.2, Christoph Hellwig|
|Indexes:||[Date] [Thread] [Top] [All Lists]|