Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*kernel\s+oops\s+with\s+linux\s+2\.4\.17\-xfs\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*kernel\s+oops\s+with\s+linux\s+2\.4\.17\-xfs\s*$/: 27 ]

Total 27 documents matching your query.

1. angs with 2.4.9-xfs-1.0.2 (score: 1): Author: @xxxxxxxxx>; Date: Fri, 18 Jan 2002 12:19:36 +0100; I experienced the following kernel oops today, which seems to be related to the XFS file system. I upgraded to kernel 2.4.17-xfs from 2.4.16-xfs yesterday, before, we did not have any crashes due to; /archives/xfs/2002-01/msg00503.html (9,234 bytes)
2. h 2.4.14 rpms instalation (score: 1): Author: ega@xxxxxx>; Date: Fri, 18 Jan 2002 11:56:05 +0000 (UTC); Have you used the patch for 2.4.17 or the CVS? The patch is out of date, there are some problems fixed in the CVS. Maybe the patch should be removed? Greetings -- Robert Sander Computer Scientist Epi; /archives/xfs/2002-01/msg00505.html (8,889 bytes)
3. h 2.4.14 rpms instalation (score: 1): Author: xxxxxxxxxxx; Date: Fri, 18 Jan 2002 13:05:13 +0100; No, I used the CVS source. -- Johannes; /archives/xfs/2002-01/msg00507.html (7,459 bytes)
4. ape Driver Kernel Bug???? (score: 1): Author: iss1@xxxxxxx>; Date: Wed, 23 Jan 2002 14:54:50 +0000 (UTC); And I got the same oops right now: kernel BUG at /mnt/raid/1/src/linux-2.4.17-xfs-new/include/asm/spinlock.h:86! invalid operand: 0000 CPU: 0 EIP: 0010:[<f88e04d6>] Tainted: P EFLAGS: 00010002 eax: 0; /archives/xfs/2002-01/msg00594.html (11,423 bytes)
5. ops with linux 2.4.17-xfs (score: 1): Author: xxxxxxxxxxxx>; Date: 23 Jan 2002 09:09:29 -0600; Please turn off spinlock debugging, it does not work in the xfs code, we compile with -f unsignedchar and this breaks the check in the spinlock debug where it does a signed comparison on a spinlock.; /archives/xfs/2002-01/msg00595.html (8,419 bytes)
6. ops with linux 2.4.17-xfs (score: 1): Author: lord@xxxxxxx>; Date: Wed, 23 Jan 2002 15:12:58 +0000 (UTC); When using the userspace nfsd I get this oops: kernel BUG at /mnt/raid/1/src/linux-2.4.17-xfs-new/include/asm/spinlock.h:86! invalid operand: 0000 CPU: 0 EIP: 0010:[<f88e422a>] Tainted: P EFLAGS: 000; /archives/xfs/2002-01/msg00596.html (12,951 bytes)
7. ops with linux 2.4.17-xfs (score: 1): Author: xxxxxxxxxxxx>; Date: 23 Jan 2002 09:16:29 -0600; Same as the last one, turn off spinlock debugging, it does not mix with xfs. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@xxxxxxx; /archives/xfs/2002-01/msg00597.html (14,290 bytes)
8. ops with linux 2.4.17-xfs (score: 1): Author: lord@xxxxxxx>; Date: Wed, 23 Jan 2002 15:36:37 +0000 (UTC); I see, I thought of that, I will try again. Should be stated somewhere in big red letters. ;-) Greetings -- Robert Sander Computer Scientist Epigenomics AG Bioinformatics R&D www.epigenomics.com Kast; /archives/xfs/2002-01/msg00598.html (9,070 bytes)
9. ops with linux 2.4.17-xfs (score: 1): Author: xxxxxxxxxxxx>; Date: 23 Jan 2002 09:39:24 -0600; Yes, I was thinking of a #error somewhere in xfs if this option is turned on. Ideally xfs should use unsigned char explicitly rather than assuming it. Yet another thing for the todo list. Steve -- St; /archives/xfs/2002-01/msg00599.html (9,597 bytes)
10. eveloperworks XFS introduction. (score: 1): Author: h Mos <knuffie@xxxxxxxxx>; Date: Fri, 18 Jan 2002 12:19:36 +0100; I experienced the following kernel oops today, which seems to be related to the XFS file system. I upgraded to kernel 2.4.17-xfs from 2.4.16-xfs yesterday, before, we did not have any crashes due to; /archives/xfs/2002-01/msg01432.html (9,234 bytes)
11. kernel oops with linux 2.4.17-xfs (score: 1): Author: el de Vega <mvega@xxxxxx>; Date: Fri, 18 Jan 2002 11:56:05 +0000 (UTC); Have you used the patch for 2.4.17 or the CVS? The patch is out of date, there are some problems fixed in the CVS. Maybe the patch should be removed? Greetings -- Robert Sander Computer Scientist Epi; /archives/xfs/2002-01/msg01434.html (8,889 bytes)
12. el oops with linux 2.4.17-xfs (score: 1): Author: <xfs@xxxxxxxxxxxxxxxxxxx; Date: Fri, 18 Jan 2002 13:05:13 +0100; No, I used the CVS source. -- Johannes; /archives/xfs/2002-01/msg01436.html (7,459 bytes)
13. lty one - was: Re: XFS is innocen t (score: 1): Author: hen Weiss <jweiss1@xxxxxxx>; Date: Wed, 23 Jan 2002 14:54:50 +0000 (UTC); And I got the same oops right now: kernel BUG at /mnt/raid/1/src/linux-2.4.17-xfs-new/include/asm/spinlock.h:86! invalid operand: 0000 CPU: 0 EIP: 0010:[<f88e04d6>] Tainted: P EFLAGS: 00010002 eax: 0; /archives/xfs/2002-01/msg01523.html (11,423 bytes)
14. stream Tape Driver Kernel Bug???? (score: 1): Author: -linux-xfs@xxxxxxxxxxxxxxx>; Date: 23 Jan 2002 09:09:29 -0600; Please turn off spinlock debugging, it does not work in the xfs code, we compile with -f unsignedchar and this breaks the check in the spinlock debug where it does a signed comparison on a spinlock.; /archives/xfs/2002-01/msg01524.html (8,419 bytes)
15. kernel oops with linux 2.4.17-xfs (score: 1): Author: >; Date: Wed, 23 Jan 2002 15:12:58 +0000 (UTC); When using the userspace nfsd I get this oops: kernel BUG at /mnt/raid/1/src/linux-2.4.17-xfs-new/include/asm/spinlock.h:86! invalid operand: 0000 CPU: 0 EIP: 0010:[<f88e422a>] Tainted: P EFLAGS: 000; /archives/xfs/2002-01/msg01525.html (12,951 bytes)
16. kernel oops with linux 2.4.17-xfs (score: 1): Author: -linux-xfs@xxxxxxxxxxxxxxx>; Date: 23 Jan 2002 09:16:29 -0600; Same as the last one, turn off spinlock debugging, it does not mix with xfs. Steve -- Steve Lord voice: +1-651-683-3511 Principal Engineer, Filesystem Software email: lord@xxxxxxx; /archives/xfs/2002-01/msg01526.html (14,290 bytes)
17. kernel oops with linux 2.4.17-xfs (score: 1): Author: >; Date: Wed, 23 Jan 2002 15:36:37 +0000 (UTC); I see, I thought of that, I will try again. Should be stated somewhere in big red letters. ;-) Greetings -- Robert Sander Computer Scientist Epigenomics AG Bioinformatics R&D www.epigenomics.com Kast; /archives/xfs/2002-01/msg01527.html (9,070 bytes)
18. kernel oops with linux 2.4.17-xfs (score: 1): Author: -linux-xfs@xxxxxxxxxxxxxxx>; Date: 23 Jan 2002 09:39:24 -0600; Yes, I was thinking of a #error somewhere in xfs if this option is turned on. Ideally xfs should use unsigned char explicitly rather than assuming it. Yet another thing for the todo list. Steve -- St; /archives/xfs/2002-01/msg01528.html (9,597 bytes)
19. kernel oops with linux 2.4.17-xfs (score: 1): Author: "Johannes Schritz" <johannes@xxxxxxxxxx>; Date: Fri, 18 Jan 2002 12:19:36 +0100; Hello, I experienced the following kernel oops today, which seems to be related to the XFS file system. I upgraded to kernel 2.4.17-xfs from 2.4.16-xfs yesterday, before, we did not have any crashes; /archives/xfs/2002-01/msg02361.html (9,234 bytes)
20. Re: kernel oops with linux 2.4.17-xfs (score: 1): Author: Robert Sander <ml-linux-xfs@xxxxxxxxxxxxxxx>; Date: Fri, 18 Jan 2002 11:56:05 +0000 (UTC); Have you used the patch for 2.4.17 or the CVS? The patch is out of date, there are some problems fixed in the CVS. Maybe the patch should be removed? Greetings -- Robert Sander Computer Scientist Epi; /archives/xfs/2002-01/msg02363.html (8,959 bytes)

Current List: 1 - 20
Page: [1] [2]