[OpenAFS-devel] Kernel 2.4.2 Compile

Carl Fischer muskr@umich.edu
Fri, 16 Mar 2001 22:59:37 -0500


I got the kernel module to compile on 2.4.2 by using the following make
command:
make build-it VERS_DEF=" -include
/usr/src/linux/include/linux/modversions.h -DAFS_LINUX24_ENV"
LNX24_SRCDIR=/usr/src/linux-2.4.2

The important thing is the first parameter.  I'm not even sure if you need
the others, but it worked, so I left it.

I'm not sure if it's all necessary, but it makes a .o file without
complaints.  The problem I'm having now is that my kernel panics. 
(bummer, eh?)  Here's all the junk it put in my log.  It doesn't mean much
to me.  Maybe someone on the openafs-devel list knows what to do with it.

..... SERVICES STARTING UP .....
afs: Starting AFS services..... 
afs: /etc/rc5.d/S60afs: line 183:   723 Segmentation fault     
/usr/vice/etc/afsd ${OPTIONS}kernel: Starting AFS cache scan...Can't open
inode 117811
kernel: Unable to handle kernel paging request at virtual address ffffffff
kernel:  printing eip:
kernel: d0c43e94
kernel: *pde = 00001063
kernel: *pte = 00000000
kernel: Oops: 0002
kernel: CPU:    0
kernel: EIP:    0010:[<d0c43e94>]
kernel: EFLAGS: 00010286
kernel: eax: 00000018   ebx: ccb13700   ecx: cd042000   edx: c1563c80
kernel: esi: cca33380   edi: cca333f4   ebp: fffffffb   esp: cd043c14
kernel: ds: 0018   es: 0018   ss: 0018
rc: Starting afs:  succeeded
kernel: Process afsd (pid: 723, stackpage=cd043000)
kernel: Stack: cca33380 cca333f4 00000000 d0c4c492 d0c5d28c 0001cc33
00000000 00000000 
kernel:        d0c678c0 00000001 cd043f74 cc860000 cca33580 00000000
cd043ea0 d0c1ab3e 
kernel:        0001cc33 00000000 cd043c74 00000010 0806f79c 0001cc33
cd043f74 0806f79c 
kernel: Call Trace: [<d0c4c492>] [<d0c5d28c>] [<d0c678c0>] [<d0c1ab3e>]
[<d0c4fff4>] [<d0c5e7a4>] [ide_set_handler+85/96] 
kernel:        [do_rw_disk+300/736] [read_intr+0/320]
[start_request+304/512] [start_request+393/512] [schedule+614/912]
[__wait_on_buffer+128/144] [is_tree_node+55/96] [search_by_key+2047/3168] 
kernel:        [search_by_entry_key+228/464] [pathrelse+28/48]
[reiserfs_readdir+1156/1216] [mmx_copy_page+41/48] [do_wp_page+461/576]
[do_wp_page+526/576] [<d0c50589>] [fput+116/208] 
kernel:        [filp_close+92/112] [system_call+51/56] 
kernel: 
kernel: Code: c6 05 ff ff ff ff 2a 83 c4 0c c3 90 55 57 56 53 8b 74 24 14
. . . . . OTHER SERVICES START UP HERE . . . . . . 
This is the last thing I see before the reboot.  Sorry, but I'm not sure
how to capture the kernel panic info (or even if it's necessary).
Jan 28 07:40:00 muskr CROND[16452]: (root) CMD (   /sbin/rmmod -as) 
Jan 28 07:43:00 muskr keMar 16 22:33:11 muskr syslogd 1.4-0: restart.


Let me know if you'd like me to experiment.  As far as I can tell, it just
happens after a small amount of use of the kernel module.

Cheers
	- Carl


--
Carl Fischer IV <muskr@umich.edu>      Graduate Student Research Assistant
Electrical Engin. and Comp. Sci.       Founder, Theta Gamma of Theta Tau
The University of Michigan                      Est. April 17, 1999
Office: (734) 764-3305                 Home: (734) 668-8771
               Homepage: http://www.JulieAndCarl.org/