Summary: | net-fs/openafs-kernel-1.4.3_pre20061220 fails to locate system call table in kernel 2.6.19-gentoo-r2 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Volkmar Glauche <volkmar.glauche> |
Component: | [OLD] Core system | Assignee: | Stefaan De Roeck (RETIRED) <stefaan> |
Status: | VERIFIED WORKSFORME | ||
Severity: | minor | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | strace output |
Description
Volkmar Glauche
2007-01-05 07:08:08 UTC
Created attachment 105533 [details]
strace output
OK - this was due to some changes in my kernel config where I somehow lost the AFS config line CONFIG_AFS_FS=m If this is unset, then the kernel symbol table is not accessible to the libafs.ko module. Perhaps this could be checked in the openafs-kernel ebuild? I have tried both 2.6.19-gentoo-r3 and -r2 without the CONFIG_AFS_FS option (I've never had it enabled, because it only activates the very limited in-kernel afs-client). In both cases, I got the following kernel log: Found system call table at 0xffffffff805822e0 (pattern scan) Found 32-bit system call table at 0xffffffff80583130 (pattern scan) Starting AFS cache scan...found 6182 non-empty cache files (12%). Are you sure this is the only thing that changed between the error and a working configuration afterwards? Could you attach your kernel configuration? For completeness, I must note that I tested on an otherwise stable amd64 tree (i.e. glibc 2.4-r2, portage-2.1.1-r2, etc.), though I don't think it should really matter. Sorry, but I can't reproduce this for now :-( I am pretty sure I did not change anything else during the last trial, but perhaps I was still booting an older kernel. The other options I changed between a definitely non-working kernel and my current config were (all were turned off, now turned on) CONFIG_KALLSYMS CONFIG_AUDIT CONFIG_AUDITSYSCALL Once I get around to reboot again, I will try a kernel with these options switched off. I took my kernel config, disabled CONFIG_KALLSYMS, didn't have CONFIG_AUDIT or CONFIG_AUDITSYSCALL, and the system call table is still found. Could it be you did an etc-update in the meanwhile, and replaced the /etc/init.d/openafs-client file only just now with its newer version? No, I did the etc-update right after emerging net-fs/openafs-kernel-1.4.3_pre20061220. I am closing this bug for now until I find some new evidence. |