Bug#311559: Bug#311865: kernel-image-2.4.27-2-686: module ip_conntrack fails to load
> Hi,
>
> I am unable to reproduce your problem. On both
> kernel-image-2.4.27-2-686 2.4.27-10 and
> kernel-image-2.4.8-2-686 2.4.8-16 I am able to
> successfully modprobe (not insmod!) ip_conntrack.
>
> On 2.4.27-10 I see
> grep ipfrag_flush /proc/ksyms
> c01dfdf0 ipfrag_flush_R290ad055
>
> And on kernel-image-2.4.8-2-686
> grep ipfrag_flush /proc/kallsyms
> c023ccb0 T ipfrag_flush
> c023ccb0 U ipfrag_flush [ip_conntrack]
>
> For reference, the md5 sum of the image files are
>
> fcbebdc8a6ca001448bd7687f22c5111
> /boot/vmlinuz-2.4.27-2-686
> 9cbb21574407fd163b9007afc87ef2f4
> /boot/vmlinuz-2.6.8-2-686
>
> --
> Horms
>
Hi,
I finally found the source of my problems - not the
kernel, but some fault of mine. I originally had a
separate ext2 /boot partition, but after some
fschk/repair sessions, I decided to get rid of it and
put the boot stuff directly into the /boot directory
of my root reiserfs partition. So I copied the
contents of the /boot partition to the directory and
adapted the entries in /boot/grub/menu.lst. However, I
was not aware of those Debian-specific automagic
options like groot. After the kernel upgrade, the
installation routine updated the /boot/grub/menu.lst,
but the root entries were set back to my old /boot
partition (groot still pointed to it).
The old boot partition was still fully functional,
i.e. it contained the old kernel, so the system now
happily booted the old kernel from the it, the modules
and System.map were taken from the new kernel (/lib
and /boot directories in the root partition) and the
symbol ipfrag_flush which appeared in the new kernel
could not be found.
Sorry for the inconvenience I caused and thanks a lot
for your work on that great release.
Urs
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
Reply to: