Kevin, I have since had the chance to verify that the current proclikefs/kernel module combination successfully uninstalls, without patching click-uninstall, on a 32-bit kernel. Do you always get a GPF when unloading, or do packets have to be going through the router?
Eddie [EMAIL PROTECTED] wrote: > Thanks Eddie! > > I've run into a couple complications: > 1) It looks like there is a logic error in Packet::has_network_header(). > I've attached a patch. > > 2) click-uninstall'ing the kernel module results in a general protection > fault. My configure string is "./configure --enable-multithread > --enable-user-multithread --enable-adaptive --enable-intel-cpu CFLAGS=-g > CXXFLAGS=-g". I am building on an x86_64 machine. The click configuration > used or the number of threads doesn't seem to affect the problem. See > gpf.log for more information. > > 3) I'm getting warnings when click descends into the kernel source > directory to build the module. See warning.log. My guess is that this is > due to the improved linuxmodule build process. > > Polling seems to be working with the e1000-7.6.15.5 driver. > > Thanks again, > Kevin Springborn > > > > >> Hi all, >> >> Click has been updated with the patch for Linux 2.6.24.7 support; and the >> Linux 2.6.24.7 patch has been checked into the Click repository. Please >> let >> us know if all of this works. I would love to hear working or not working >> reports from users. >> >> Thanks very much to, especially, Adam Greenhalgh, Joonwoo Park, and Nemean >> Networks for putting together this patch. >> >> Thanks, >> Eddie >> _______________________________________________ >> click mailing list >> [email protected] >> https://amsterdam.lcs.mit.edu/mailman/listinfo/click >> _______________________________________________ click mailing list [email protected] https://amsterdam.lcs.mit.edu/mailman/listinfo/click
