openafs on suse9/amd64
Hi, I am having big troubles setting up openafs client/server on suse9 for AMD64. openafs-1.2.10-36 on k_smp-2.4.21-149 does not work at all. For server I have tried openafs-1.3.51 development version and got it work with few modifications for missing declarations (mostly string.h and inet_ntoa). openafs-1.2.10 is much harder, because there are lots of implicit functions returning int instead of char* (or similar). Anyway, the server part of openafs runs also ok in 32bit mode. I did not have any luck with client part (libafs kernel module). With k_smp-2.4.21-149 kernel, there are always oopses, almost never at the same place. Oops occurs quite soon after accesing few mbytes in afs, reading or writting, with token or without. So I tried fedora preview from http://fedora.linux.duke.com/. I have built the kernel with xfs support (2.4.22-1.2135.nptl_27.rhfc1.atsmp) from http://atrpms.physik.fu-berlin.de/dist/fc1/kernel/, and compiled openafs-1.2.10 module with gcc32. That worked OK. I have installed this kernel and libafs module to suse9, and that also worked without problems. However, If I had compiled libafs module on fedora with gcc 3.3.2 ( and not 3.2.3), there was always rxkad error=19270410, and tokens were discarded. That happens also after transfering few mbytes to afs. openafs-1.3.51 client behaves the same way. I suspect there is the same problem with official 3.3.1 compiler on suse9 With fedora kernel, there were no oopses, even with gcc 3.3.2. So, in short, libafs with suse kernel always oopses, and libafs should not be compiled with gcc 3.3.x. Is there any solutions to this mess? Thanks, Andrej
Sorry, the correct fedora preview link is http://fedora.linux.duke.edu/fc1_x86_64/ Andrej
On Tue, 6 Jan 2004 20:06:35 +0100 (CET)
Andrej Filipcic
I am having big troubles setting up openafs client/server on suse9 for AMD64.
openafs-1.2.10-36 on k_smp-2.4.21-149 does not work at all.
openafs on AMD64 is known to be broken. We currently don't have a solution. There is a project to completely reimplement a new afs kernel client for Linux, that may be the best bet longer term (an early version is already in the 2.6 kernel). For Fedora issues you are on the wrong list. -Andi
On Wed, 7 Jan 2004, Andi Kleen wrote:
openafs-1.2.10-36 on k_smp-2.4.21-149 does not work at all.
openafs on AMD64 is known to be broken. We currently don't have a solution. There is a project to completely reimplement a new afs kernel client for Linux, that may be the best bet longer term (an early version is already in the 2.6 kernel).
-------------- Today I have tested openafs client with 2.4.21-171-smp kernel. I have compiled the libafs module with gcc32-3.2.3-6 (from fedora) and it seems to work ok. Andrej
On Wed, 7 Jan 2004 10:35:41 +0100 (CET)
Andrej Filipcic
On Wed, 7 Jan 2004, Andi Kleen wrote:
openafs-1.2.10-36 on k_smp-2.4.21-149 does not work at all.
openafs on AMD64 is known to be broken. We currently don't have a solution. There is a project to completely reimplement a new afs kernel client for Linux, that may be the best bet longer term (an early version is already in the 2.6 kernel).
--------------
Today I have tested openafs client with 2.4.21-171-smp kernel. I have compiled the libafs module with gcc32-3.2.3-6 (from fedora) and it seems to work ok.
So you're saying it breaks as soon as being compiled with gcc 3.3 ? The openafs code builds outside the kernel tree, right? Can you check it is using -mno-red-zone to build the kernel module? gcc 3.2 didn't need that and I've seen this problem with other drivers too. -Andi
On Wed, 7 Jan 2004, Andi Kleen wrote:
On Wed, 7 Jan 2004 10:35:41 +0100 (CET) Andrej Filipcic
wrote: On Wed, 7 Jan 2004, Andi Kleen wrote:
openafs-1.2.10-36 on k_smp-2.4.21-149 does not work at all.
openafs on AMD64 is known to be broken. We currently don't have a solution. There is a project to completely reimplement a new afs kernel client for Linux, that may be the best bet longer term (an early version is already in the 2.6 kernel).
--------------
Today I have tested openafs client with 2.4.21-171-smp kernel. I have compiled the libafs module with gcc32-3.2.3-6 (from fedora) and it seems to work ok.
So you're saying it breaks as soon as being compiled with gcc 3.3 ?
The openafs code builds outside the kernel tree, right?
Can you check it is using -mno-red-zone to build the kernel module? gcc 3.2 didn't need that and I've seen this problem with other drivers too.
-Andi
Yes, that solves the problem. gcc 3.3.1 + -mno-red-zone flag works!. I am still using openafs-server from i386 distribution... Thanks, Andrej
participants (2)
-
Andi Kleen
-
Andrej Filipcic