Red Hat Bugzilla – Bug 139272
freeConfModule called with null pointer; don't do that
Last modified: 2014-03-16 22:50:22 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;
T312461; SV1; i-NavFourF; .NET CLR 1.1.4322)
Description of problem:
I just upgraded to latest FC2, rebooted the machine and could not get
nw working anymore. Only loopback is available. Both kudzu and system-
config-network report the same annoying error, "freeConfModule called
with null pointer; don't do that" and I don't have a glue what to do
but start re-installing everything again.
Before the above happened I had upgraded from FC1 to FC2 basic with
YUM (http://linux.duke.edu/~skvidal/misc/fc1-fc2-yum-hints.txt=. Then
I checked the system, it seemed to work. From that I updated, with
YUM, to latest FC2 update and then the system was broken.
What to do?
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Just booth the damn machine
Actual Results: NW i/f is unavailable
Expected Results: NW is available as the config was OK for 10 months
Do you have no modules.conf or no modprobe.conf?
Yep, the modprobe was not there as the damn guide assisted to take
that away. I'll managed to figure that out and you are giving the same
resolution, so there was no sw bug but misconfiguration.
Well, actually, the segfault on no modprobe.conf *is* fixed in FC3, FWIW.