2.6.x SMP and IPv4

[Bas Vermeulen]

On Fri, 2004-08-06 at 14:16, Maurice wrote:
> Note: I've posted this to the Kernel-SMP list, already...
> 
> FYI,
> 
> I'm unable to get IPv4 running correctly when using a 2.6.xSMP kernel,
> but the "same" 2.6.x non-SMP kernel will allown IPv4 to function.

Are you able to make an IPv6 connection? If not, try 'noapic' when
booting, as your interrupt could very well be non-functioning.

It's one of the things I would try first, before swapping out your NIC
for a different one (Intel E100 usually work fine).

Bas Vermeulen

> I have tried a short list of the basics and searched google for help, I
> also posted to my local LUG and tried a few additional things.
> 
> The hardware this is happening on is;
> 
> motherboard: ECS (elitegroup) D6VAA
> NIC: netgear FA311
> DHCP server: Coyote Linux, has run for about two years.
> 
> 
> 
> Below is the posting, two parts, to my local LUG;
> 
> Part I
> 
> I have a box at home that's ran RH9 for about two years (or when ever 
> RH9 first came out plus a month) and I've done regular RHN updates as 
> time went by.
> 
> About a week ago I used some very good online directions to take my RH9 
> box to Fedora C1 (using some basic RPM's and YUM) and eventhing went 
> fairly well, just had to make a few adjustments...
> 
> Then a week after the now FC1 box proved to be stable and correctly 
> operational I used the directions from the same site to update the FC1 
> to FC2, and that seemed to go well -- better than the RH9 to FC1, or so 
> it seemed.
> 
> I re-booted to see what, if anything, would fail on start-up.
> 
> I did have a failure, the FA311 NIC card could no longer get an address 
> from the DHCP server???
> Seems that the NIC now only "runs" IPv6, and the info I've gathered from 
> the Net isn't helping me correct this -- I must be searching the wrong 
> phrase(s).
> 
> Has anyone else followed this upgrade path and had the same problem?
> Has anyone else moved to the 2.6 kernel and had IPv4 problems?
> 
> I've poked around and added line to certain system files and even gave 
> the card a static IPv4 number -- but nothing has corrected this problem.
> 
> --------
> -Maurice
> 
> 
> "Linux -- it not just for breakfast anymore..."
> -Moe
> 
> 
> 
> 
> 
> Part II
> 
> After a lot of off-list help from Phillip, the SMP kernel still wouldn't 
> allow IPv4 activity...
> Thanks for all your help Phillip.
> 
> I then did a fresh install of FC2, just to see, and guess what -- nope 
> -- the SMP kernel still wouldn't allow IPv4 traffic, but the non-SMP 
> kernel worked fine.
> So then I installed SuSE 9.1 PRO, same deal, the SMP kernel would not 
> allow IPv4 traffic.
> 
> I then tested several LiveCD's;
> Knoppix 3.3 ,        Kernel 2.4.24-xfs #1 smp  (NO)
> LindowsOS 4.5.212,   Kernel 2.4.24             (YES)
> Morphix KDE 0.4.1,   Kernel 2.4.21-xfs #13 smp (NO)
> SLAX 4.0.4,          Kernel 2.4.25             (YES)
> 
> The past kernel's used on the SMP box were;
> RH 9,          Kernel 2.4.20-31.9           (YES)
> RH 9,          Kernel 2.4.20-31.9smp        (YES)
> FC1,           Kernel 2.4.22-1.2197.nptl    (YES)
> FC1,           Kernel 2.4.22-1.2197.nptlsmp (YES)
> FC2,           Kernel 2.6.6-1.435.2.3smp    (NO)
> FC2,           Kernel 2.6.6-1.4352.2.3      (YES)
> SuSE 9.1 PRO,  Kernel 2.6.4-52-smp          (NO)
> 
> So there seems to be some issue with the 2.6 kernel and SMP, maybe based 
> on my motherboard and/or NIC combination???
> 
> 
> 
> --------
> -Maurice
> 
> "Linux -- it not just for breakfast anymore..."
> -Moe
> 
> 
> --
> fedora-legacy-list mailing list
> fedora-legacy-list at redhat.com
> http://www.redhat.com/mailman/listinfo/fedora-legacy-list