[tulip-bug] Kingston kne111tx and recompiling tulip on Mandrake8.0

Keith Warno keith.warno@valaran.com
Thu, 12 Jul 2001 14:37:10 -0400


Donald Becker wrote:

> > Hmm, this would not, by chance, be on a box with a 2.4.x kernel?  I had
> > the same issue just last night when upgrading to 2.4.6 from 2.2.19.  My
> > solution, originally, was to grab the 'test' versions of both tulip.c
> > and kern_compat.h (not sure if a more recent kern_compat.h was required)
> > from ftp://ftp.scyld.com/pub/network/test/.  tulip.c then compiled
> > fine.  I used it for a little bit before noticing a slew of syslog
> > messages:
> >
> > Jul 10 16:48:16 foo kernel: Warning: kfree_skb on hard IRQ d88818c4
> 
> Could you please try exactly the same test, making the following source
> code change around line 2742:
> 

Hmm.  I think I may have made an error in my post; I stated I tried to
build tulip.c (v0.92w 7/9/2001) with kernel 2.4.6 when in fact it was
probably 2.4.5 (was a long night that night).

tulip.c v0.92w, with kern_compat.h $Revision: 1.8 $ $Date: 2001/05/18
22:51:18 $, does not build on my box with kernel 2.4.6:

tulip.c: In function `private_ioctl':
tulip.c:3112: `SIOCSPARAMS' undeclared (first use in this function)

I'm currently using the kernel-distributed tulip.c.  Perhaps this is
causing an issue?  Or was something changed from 2.4.5 to 2.4.6 that
breaks the tulip compile?

:/

Regards,
kw
--                           
| Keith Warno                       cell: +1 609-209-5800
| http://www.valaran.com/           work: +1 609-716-7200 x243
| Valaran Corporation Penguin Guy   SMS : kw-mobile@valaran.com
+--------------------------------------------------------------//