Re: Kernel halts rock solid on assigning ip (ne2k-pci)

[Aschwin van der Woude]

Paul Gortmaker wrote:
> 
> Aschwin van der Woude wrote:
> >
> > I have a problem with a network-driver.
> > The ne2k-pci modules loads fine, no problem at all. Everything works
> > like a sunshine.
> > But as soon as I try to assign an IP-adress the whole system halts
> > rock-solid, the magic sysrq combinations don't even work anymore.
> >
> > I am not sure if this is due to an IRQ-conflict. But I do know it all
> > happens to work perfectly fine with 2.4.0-test10. This happens on both
> > 2.4.0-prerelease and the 2.4.0-kernel.
> >
> > I attached some info about my configuration. I hope you/somebody can
> > help me solve this, I am eager to start using 2.4.0.
> > So far I have been very happy using 2.4.0-test10.
> 
> The test11 patch has the ne2k-pci changes for FD support, and the
> test12 patch has the Tx timeout relocation in 8390 (which ne2k-pci
> uses).  Can you see which one of those (if either) causes the
> breakage?  You should be able to put the 8390.c and ne2k-pci.c
> from test10 directly into 2.4.0 proper (one at a time and then
> both if required) to see which (if either) is responsible.

Hmm. I tried your suggestion but with no luck. Might it there be another
source for my problem.
Here is how I tried it :

# cd /usr/src/linux-2.4.0/drivers/net
# mv 8390.c 8390.c.bck
# mv 8390.h 8390.h.bck
# ln -s /usr/src/linux-2.4.0-test10/drivers/net/8390.c
/usr/src/linux-2.4.0/drivers/net/8390.c
# ln -s /usr/src/linux-2.4.0-test10/drivers/net/8390.h
/usr/src/linux-2.4.0/drivers/net/8390.h
# mv ne2k-pci.c ne2k-pci.c.bck
# ln -s /usr/src/linux-2.4.0-test10/drivers/net/ne2k-pci.c
/usr/src/linux-2.4.0/drivers/net/ne2k-pci.c
# cd /usr/src/linux-2.4.0
# make dep
# make modules
# make modules_install

I did try 8390 only at first. The problem remains. Unabling the
bios-setting 'PnP OS' doesn't have any effect.
The modules load fine without problems.
I hoped this would have solved my problem, but no such luck. Did I do
something wrong. I am no kernel or C expert, altough I can read and
modify C and have been following kernel-development for quite a while.

Thanks,

Aschwin

-- 
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.