Messages in this thread |  | | Date | Sat, 14 Dec 1996 12:13:38 -0600 (CST) | From | Jason Burrell <> | Subject | Modules and bugs in 2.1.15 |
| |
I compiled 2.1.15 and got hit by these things:
* Traceroute is broken. crl:~# traceroute 165.113.1.12 traceroute to 165.113.1.12 (165.113.1.12), 30 hops max, 40 byte packets sendto: Bad address 1 traceroute: wrote 165.113.1.12 40 chars, ret=-1
But I'm fairly sure this is a known bug.
* I'm getting loads of "TCPv4 bad checksum" errors in my syslog. An example is this:
Dec 14 12:03:05 crl kernel: TCPv4 bad checksum from 180171a5:0077 to 07774ba8:06e3, len=532/532/552 Dec 14 12:05:44 crl kernel: TCPv4 bad checksum from 180171a5:0077 to 07774ba8:04e3, len=532/532/552
I've no clue what this is. Ifconfig doesn't seem to note any errors, and I am running error correction on my modem (which I need to remember to turn off ;). It seems harmless, though.
* Some modules still hose themselves for some reason.
crl:~# depmod -a *** Unresolved symbols in module /lib/modules/2.1.15/fs/nfs.o *** Unresolved symbols in module /lib/modules/2.1.15/ipv6/ipv6.o
This seems fairly random. I've never gotten ipv6 to link properly, though. I'm going to link it directly into the kernel rather than as a module, but I'm interested to know whether this is an error with my setup or my development utilities. Likewise with the seemingly random unresolved symbols I get with the other modules.
An interesting sidebar for this, though, is that I recently discovered while developing something else that sometimes my GCC (or specifically g++) decides to throw in symbols such as .L1684 and such, which causes the compiled object file not to link to the rest of my program. I was compiling with -O6 and -fhandle-exceptions on. I wonder if this is related. Looking through "nm"'s output on ipv6.o, I don't see anything of the sort.
Would it be possible for depmod to say _what_ symbols are unresolved?
Regards.
-- Good government. Good government. Sit. Stay.
|  |