Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Need\s+some\s+help\s+with\s+cause\s+of\s+Oops\s+in\s+XFS\s+1\.2\s*$/: 16 ]

Total 16 documents matching your query.

1. Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Steven Dake <sdake@xxxxxxxxxx>
Date: Tue, 25 Mar 2003 11:23:45 -0700
XFS Developers, Ok here is what I have done: I have a tree that already had XFS 1.1 (with a bunch of other stuff) included. I hand applied the XFS 1.2 on top of XFS 1.1 patch and everything seems to
/archives/xfs/2003-03/msg00336.html (13,557 bytes)

2. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 25 Mar 2003 19:38:38 +0000
Are you using the preempt patch or other obscure core kernel changes?
/archives/xfs/2003-03/msg00341.html (9,008 bytes)

3. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Steven Dake <sdake@xxxxxxxxxx>
Date: Tue, 25 Mar 2003 13:19:21 -0700
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).
/archives/xfs/2003-03/msg00342.html (10,023 bytes)

4. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 25 Mar 2003 20:32:29 +0000
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.
/archives/xfs/2003-03/msg00344.html (9,468 bytes)

5. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Steven Dake <sdake@xxxxxxxxxx>
Date: Tue, 25 Mar 2003 13:32:50 -0700
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 p
/archives/xfs/2003-03/msg00345.html (10,657 bytes)

6. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 25 Mar 2003 20:54:29 +0000
Maybe get some consultant that knows Linux filesystem code to fix it for your company? I wouldn't expect too much help on a heavily patched tree that's not publically available.
/archives/xfs/2003-03/msg00346.html (10,315 bytes)

7. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Steven Dake <sdake@xxxxxxxxxx>
Date: Tue, 25 Mar 2003 14:02:28 -0700
I understand filesystem code quite well, and the particular problem (if you would have read the oops) is in the memory management layer. But thanks for your advice. -steve Christoph Hellwig wrote: On
/archives/xfs/2003-03/msg00347.html (10,909 bytes)

8. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Rusell Cattelan <cattelan@xxxxxxx>
Date: 25 Mar 2003 18:50:51 -0600
If possible get kbd into your tree. Then open a bug and attach what ever backtraces you can get. bta is a good place to start. That might shed some light on the situation, but without wading through
/archives/xfs/2003-03/msg00353.html (9,591 bytes)

9. Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Steven Dake <sdake@xxxxxxxxxx>
Date: Tue, 25 Mar 2003 11:23:45 -0700
XFS Developers, Ok here is what I have done: I have a tree that already had XFS 1.1 (with a bunch of other stuff) included. I hand applied the XFS 1.2 on top of XFS 1.1 patch and everything seems to
/archives/xfs/2003-03/msg00805.html (13,557 bytes)

10. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 25 Mar 2003 19:38:38 +0000
Are you using the preempt patch or other obscure core kernel changes?
/archives/xfs/2003-03/msg00810.html (9,008 bytes)

11. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Steven Dake <sdake@xxxxxxxxxx>
Date: Tue, 25 Mar 2003 13:19:21 -0700
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).
/archives/xfs/2003-03/msg00811.html (10,023 bytes)

12. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 25 Mar 2003 20:32:29 +0000
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.
/archives/xfs/2003-03/msg00813.html (9,468 bytes)

13. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Steven Dake <sdake@xxxxxxxxxx>
Date: Tue, 25 Mar 2003 13:32:50 -0700
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 p
/archives/xfs/2003-03/msg00814.html (10,657 bytes)

14. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 25 Mar 2003 20:54:29 +0000
Maybe get some consultant that knows Linux filesystem code to fix it for your company? I wouldn't expect too much help on a heavily patched tree that's not publically available.
/archives/xfs/2003-03/msg00815.html (10,315 bytes)

15. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Steven Dake <sdake@xxxxxxxxxx>
Date: Tue, 25 Mar 2003 14:02:28 -0700
I understand filesystem code quite well, and the particular problem (if you would have read the oops) is in the memory management layer. But thanks for your advice. -steve Christoph Hellwig wrote: On
/archives/xfs/2003-03/msg00816.html (10,909 bytes)

16. Re: Need some help with cause of Oops in XFS 1.2 (score: 1)
Author: Rusell Cattelan <cattelan@xxxxxxx>
Date: 25 Mar 2003 18:50:51 -0600
If possible get kbd into your tree. Then open a bug and attach what ever backtraces you can get. bta is a good place to start. That might shed some light on the situation, but without wading through
/archives/xfs/2003-03/msg00822.html (9,591 bytes)


This search system is powered by Namazu