[Fwd: kernel 2.4.21]

[Fwd: kernel 2.4.21]

[Alan Cox]

-----Forwarded Message-----

> From: Cedric Gavage <cedric.gavage@unixtech.be>
> To: linux-kernel@vger.kernel.org
> Subject: kernel 2.4.21
> Date: 19 Jul 2003 16:38:11 +0200
> 
> Hi all,
> 
> I have a little question...
> 
> 
> Summary of changes from v2.4.21-pre4 to v2.4.21-pre5
> ============================================
> 
> Alan Cox <alan@lxorguk.ukuu.org.uk>:
>    o ACPI apparently wasnt bios
>    o fix wrong date in microcode comment
>    o add another legitimate P4 type
>    o must disallow write combine on 450NX
>    o add framework for ndelay (nanoseconds)
>    o first block of parisc resend
>    o second block of parisc merge
>    o third block of parisc merge
>    o Ian Nelson moved
>    o update videobook docs to avoid check_region
>    o docs for IPMI
>    o remove dead init call
>    o add AMD hammer rng
>    o IPMI driver updates
>    o keyboard changes
>    o fix wrong test in raw driver
>    o fix paths for ide
>    o clarify hpt37x config
>    o fix more ide paths
>    o Paul's fix to do ide_cs handling in task context
>    o more ide paths
>    o fix use of check_region in umc driver
>    o more ide comment/doc info updates
>    o promise printk cleanups
>    o another wrong path
>    o IDE printk/cleanup bits
>    o fix padding on eepro driver
> 
> In this patch, is it possible that there is a problem in the fix of 
> eepro driver? Since I upgrade the kernel with 2.4.20-8 (kernel-source 
> tag in debian) which include this patch I have some problem with packets 
> which are sometimes truncated... (the server runs an ircd and the result 
> is a delink).
> 
> Jul 17 06:31:00 fazer kernel: KERNEL: assertion (newsk->state != 
> TCP_SYN_RECV) failed at tcp.c(2229)
> Jul 17 06:31:00 fazer kernel: KERNEL: assertion 
> ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed a
> t af_inet.c(689)
> Jul 17 18:27:53 fazer kernel: KERNEL: assertion (newsk->state != 
> TCP_SYN_RECV) failed at tcp.c(2229)
> Jul 17 18:27:53 fazer kernel: KERNEL: assertion 
> ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed a
> t af_inet.c(689)
> Jul 17 20:52:35 fazer kernel: KERNEL: assertion (newsk->state != 
> TCP_SYN_RECV) failed at tcp.c(2229)
> Jul 17 20:52:35 fazer kernel: KERNEL: assertion 
> ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed a
> t af_inet.c(689)
> Jul 17 21:52:16 fazer kernel: KERNEL: assertion (newsk->state != 
> TCP_SYN_RECV) failed at tcp.c(2229)
> Jul 17 21:52:16 fazer kernel: KERNEL: assertion 
> ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed a
> t af_inet.c(689)
> Jul 17 22:49:31 fazer kernel: KERNEL: assertion (newsk->state != 
> TCP_SYN_RECV) failed at tcp.c(2229)
> Jul 17 22:49:31 fazer kernel: KERNEL: assertion 
> ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed a
> t af_inet.c(689)
> 
> OR
> Jul 12 21:33:58 fazer kernel: recvmsg bug: copied DDDA9120 seq DDDA91E9
> Jul 12 21:33:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
> at tcp.c(1545)
> Jul 12 21:33:58 fazer kernel: recvmsg bug: copied DDDA9120 seq DDDA91E9
> Jul 12 21:33:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
> at tcp.c(1545)
> Jul 12 21:33:58 fazer kernel: recvmsg bug: copied DDDA9120 seq DDDA91E9
> Jul 12 21:33:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
> at tcp.c(1545)
> Jul 12 21:33:58 fazer kernel: recvmsg bug: copied DDDA9120 seq DDDA91E9
> Jul 12 21:33:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
> at tcp.c(1545)
> Jul 12 21:33:58 fazer kernel: recvmsg bug: copied DDDA9120 seq DDDA91E9
> Jul 12 21:33:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
> at tcp.c(1545)
> Jul 12 21:33:58 fazer kernel: recvmsg bug: copied DDDA9120 seq DDDA91E9
> Jul 12 21:33:59 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
> at tcp.c(1545)
> Jul 12 21:33:59 fazer kernel: recvmsg bug: copied DDDA9120 seq DDDA91E9
> Jul 12 21:33:59 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
> at tcp.c(1545)
> 
> 
> If I do a rollback, no more problems... I don't test yet a 2.4.21 kernel.
> 
> Hardware is a Dell PowerAppWeb 120A with one CPU P3 1 GHz / 256 Mo RAM /
> 
> Now Kernel is generated under debian with kernel-source-2.4.20-2 and gcc 
> version 2.95.4 20011002.
> 
> Any idea? (Thanks for your help)
> 
> -- 
>   Cedric Gavage <cedric.gavage@unixtech.be>
>   http://unixtech.be - http://gavage.com - OpenPGP: 0xED325C64
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

Re: [Fwd: kernel 2.4.21]

[David S. Miller]

On 19 Jul 2003 18:05:45 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> > Jul 17 06:31:00 fazer kernel: KERNEL: assertion (newsk->state != 
> > TCP_SYN_RECV) failed at tcp.c(2229)

This one was fixed in 2.4.21

Re: [Fwd: kernel 2.4.21]

[Cedric Gavage]

David S. Miller wrote:
> On 19 Jul 2003 18:05:45 +0100
> Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> 
> 
>>>Jul 17 06:31:00 fazer kernel: KERNEL: assertion (newsk->state != 
>>>TCP_SYN_RECV) failed at tcp.c(2229)
> 
> 
> This one was fixed in 2.4.21
> 
Thanks for the information... I'll upgrade and test again...

-- 
  Cedric Gavage <cedric.gavage@unixtech.be>
  http://unixtech.be - http://gavage.com - OpenPGP: 0xED325C64

Re: [Fwd: kernel 2.4.21]

[Cedric Gavage]

David S. Miller wrote:
> 
>>>Jul 17 06:31:00 fazer kernel: KERNEL: assertion (newsk->state != 
>>>TCP_SYN_RECV) failed at tcp.c(2229)
> 
> 
> This one was fixed in 2.4.21
> 

Still this with 2.4.21 kernel: (intel internet card, driver eepro100)

Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
at tcp.c(1563)
Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
at tcp.c(1563)
Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
at tcp.c(1563)
Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
at tcp.c(1563)
Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
at tcp.c(1563)
Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
at tcp.c(1563)
Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
at tcp.c(1563)
Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed 
at tcp.c(1563)


Any idea?

-- 
  Cedric Gavage <cedric.gavage@unixtech.be>
  http://unixtech.be - http://gavage.com - OpenPGP: 0xED325C64

Re: [Fwd: kernel 2.4.21]

[David S. Miller]

On Wed, 23 Jul 2003 11:23:03 +0200
Cedric Gavage <cedric.gavage@unixtech.be> wrote:

> Still this with 2.4.21 kernel: (intel internet card, driver eepro100)
> 
> Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
> Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1563)

What interesting programs are you running on this system?

Are you running and old version of vsftpd?

Re: [Fwd: kernel 2.4.21]

[Cedric Gavage]

David S. Miller wrote:
> On Wed, 23 Jul 2003 11:23:03 +0200
> Cedric Gavage <cedric.gavage@unixtech.be> wrote:
> 
> 
>>Still this with 2.4.21 kernel: (intel internet card, driver eepro100)
>>
>>Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
>>Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1563)
> 
> 
> What interesting programs are you running on this system?
> 
> Are you running and old version of vsftpd?
> 

Thanks for your help...

This server is efnet.skynet.be, ircd server connected on EFnet with 
ircd-hybrid-6.4...

System is a Debian stable 3.0 aka woody (standard).

Here is the "cat /proc/version" output
Linux version 2.4.21-dell.poweredge.ppro.nosmp (root@localhost) (gcc 
version 2.95.4 20011002 (Debian prerelease)) #1 Sat Jul 19 16:13:28 CEST 
2003

Here is the "cat /proc/cpu" output:
fazer:/root# cat /proc/cpuinfo
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 8
model name      : Pentium III (Coppermine)
stepping        : 6
cpu MHz         : 993.399
cache size      : 256 KB
fdiv_bug        : no
hlt_bug         : no
f00f_bug        : no
coma_bug        : no
fpu             : yes
fpu_exception   : yes
cpuid level     : 2
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 mmx fxsr sse
bogomips        : 1979.18


Here is the "cat /proc/meminfo" output:
fazer:/root# cat /proc/meminfo
         total:    used:    free:  shared: buffers:  cached:
Mem:  262762496 214491136 48271360        0  6619136 83787776
Swap: 995250176  1622016 993628160
MemTotal:       256604 kB
MemFree:         47140 kB
MemShared:           0 kB
Buffers:          6464 kB
Cached:          80888 kB
SwapCached:        936 kB
Active:          61152 kB
Inactive:       122056 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:       256604 kB
LowFree:         47140 kB
SwapTotal:      971924 kB
SwapFree:       970340 kB

Here is the "cat /proc/modules" output.
fazer:/root# cat /proc/modules
serial                 44160   0 (autoclean)
eepro100               18060   2
mii                     2480   0 [eepro100]



Here is the running process list.
fazer:/root# ps aux
USER       PID %CPU %MEM   VSZ  RSS TTY      STAT START   TIME COMMAND
root         1  0.0  0.1  1272  436 ?        S    Jul22   0:06 init [2]
root         2  0.0  0.0     0    0 ?        SW   Jul22   0:00 [keventd]
root         3  0.0  0.0     0    0 ?        SWN  Jul22   0:00 
[ksoftirqd_CPU0]
root         4  0.0  0.0     0    0 ?        SW   Jul22   0:00 [kswapd]
root         5  0.0  0.0     0    0 ?        SW   Jul22   0:00 [bdflush]
root         6  0.0  0.0     0    0 ?        SW   Jul22   0:00 [kupdated]
root         7  0.0  0.0     0    0 ?        SW   Jul22   0:00 [scsi_eh_0]
root         8  0.0  0.0     0    0 ?        SW   Jul22   0:00 [scsi_eh_1]
root       164  0.0  0.2  1340  556 ?        S    Jul22   1:39 /sbin/syslogd
root       167  0.0  0.4  2012 1188 ?        S    Jul22   0:00 /sbin/klogd
root       170  0.1  1.5  5340 4088 ?        S    Jul22   2:43 
/usr/sbin/named
root       187  0.0  0.1  1248  420 ?        S    Jul22   0:00 
/usr/sbin/inetd
root       190  0.0  0.3  5692  788 ?        S    Jul22   0:00 
/usr/sbin/ippl
root       192  0.0  0.3  5692  788 ?        S    Jul22   0:00 
/usr/sbin/ippl
nobody     193  0.0  0.3  5692  788 ?        S    Jul22   0:01 
/usr/sbin/ippl
nobody     194  1.3  0.3  5692  788 ?        R    Jul22  22:43 
/usr/sbin/ippl
ircd       197  0.6 33.8 111524 86980 ?      S    Jul22  10:53 
/usr/local/ircd-hybrid/ircd
smmsp      224  0.0  0.6  4988 1668 ?        S    Jul22   0:00 sendmail: 
MSP: Queue runner@00:10:0
root       228  0.0  0.8  3140 2100 ?        S    Jul22   0:15 
/usr/sbin/snmpd -s -l /dev/null
root       230  0.0  0.3  2016  860 ?        S    Jul22   0:00 
/usr/sbin/snmptrapd -s
root       236  0.0  0.3  2784 1016 ?        S    Jul22   0:00 
/usr/sbin/sshd
root       239  0.0  0.7  1976 1968 ?        SL   Jul22   0:00 
/usr/sbin/ntpd
daemon     242  0.0  0.2  1384  556 ?        S    Jul22   0:00 /usr/sbin/atd
root       245  0.0  0.2  1652  680 ?        S    Jul22   0:00 
/usr/sbin/cron
root       248  0.0  0.1  1256  412 tty1     S    Jul22   0:00 
/sbin/getty 38400 tty1
root       249  0.0  0.1  1256  412 tty2     S    Jul22   0:00 
/sbin/getty 38400 tty2
root       250  0.0  0.1  1256  412 tty3     S    Jul22   0:00 
/sbin/getty 38400 tty3
root       251  0.0  0.1  1256  412 tty4     S    Jul22   0:00 
/sbin/getty 38400 tty4
root       252  0.0  0.1  1256  412 tty5     S    Jul22   0:00 
/sbin/getty 38400 tty5
root       253  0.0  0.1  1256  412 tty6     S    Jul22   0:00 
/sbin/getty 38400 tty6
root       254  0.0  1.3  8292 3356 ?        S    Jul22   0:00 
/opt/tivoli/tsm/client/ba/bin/dsmc
root       255  0.0  1.3  8292 3356 ?        S    Jul22   0:00 
/opt/tivoli/tsm/client/ba/bin/dsmc
root       256  0.0  1.3  8292 3356 ?        S    Jul22   0:00 
/opt/tivoli/tsm/client/ba/bin/dsmc
root      3366  0.0  0.6  5732 1708 ?        S    11:37   0:00 
/usr/sbin/sshd
root      3368  0.0  0.5  2464 1332 pts/0    S    11:37   0:00 -bash
root      3394  7.0  0.6  5732 1708 ?        R    11:42   0:00 
/usr/sbin/sshd
root      3396  0.0  0.5  2456 1312 pts/1    S    11:42   0:00 -bash
root      3413  0.0  0.6  3544 1568 pts/1    R    11:42   0:00 ps aux

-- 
  Cedric Gavage <cedric.gavage@unixtech.be>
  http://unixtech.be - http://gavage.com - OpenPGP: 0xED325C64

Re: [Fwd: kernel 2.4.21]

[David S. Miller]

On Wed, 23 Jul 2003 11:44:14 +0200
Cedric Gavage <cedric.gavage@unixtech.be> wrote:

> David S. Miller wrote:
> > On Wed, 23 Jul 2003 11:23:03 +0200
> > Cedric Gavage <cedric.gavage@unixtech.be> wrote:
> >>Still this with 2.4.21 kernel: (intel internet card, driver eepro100)
> >>
> >>Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
> >>Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1563)
> > Are you running and old version of vsftpd?
> 
> Thanks for your help...
> 
> This server is efnet.skynet.be, ircd server connected on EFnet with 
> ircd-hybrid-6.4...

Any chance you can try with the e100 driver instead of eepro100?

Re: [Fwd: kernel 2.4.21]

[Cedric Gavage]

David S. Miller wrote:
> On Wed, 23 Jul 2003 11:44:14 +0200
> Cedric Gavage <cedric.gavage@unixtech.be> wrote:
> 
> 
>>David S. Miller wrote:
>>
>>>On Wed, 23 Jul 2003 11:23:03 +0200
>>>Cedric Gavage <cedric.gavage@unixtech.be> wrote:
>>>
>>>>Still this with 2.4.21 kernel: (intel internet card, driver eepro100)
>>>>
>>>>Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
>>>>Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1563)
>>>
>>>Are you running and old version of vsftpd?
>>
>>Thanks for your help...
>>
>>This server is efnet.skynet.be, ircd server connected on EFnet with 
>>ircd-hybrid-6.4...
> 
> 
> Any chance you can try with the e100 driver instead of eepro100?
> 
Could I use it with these cards?

Jul 22 07:55:39 fazer kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker 
http://www.scyld.com/netwo
rk/eepro100.html
Jul 22 07:55:39 fazer kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17 
Modified by Andrey V. Savoc
hkin <saw@saw.sw.com.sg> and others
Jul 22 07:55:39 fazer kernel: eth0: Intel Corp. 82557/8/9 [Ethernet Pro 
100], 00:B0:D0:B0:D0:FB, I
RQ 16.
Jul 22 07:55:39 fazer kernel:   Receiver lock-up bug exists -- enabling 
work-around.
Jul 22 07:55:39 fazer kernel:   Board assembly 07195d-000, Physical 
connectors present: RJ45
Jul 22 07:55:39 fazer kernel:   Primary interface chip i82555 PHY #1.
Jul 22 07:55:39 fazer kernel:   General self-test: passed.
Jul 22 07:55:39 fazer kernel:   Serial sub-system self-test: passed.
Jul 22 07:55:39 fazer kernel:   Internal registers self-test: passed.
Jul 22 07:55:39 fazer kernel:   ROM checksum self-test: passed (0x04f4518b).
Jul 22 07:55:39 fazer kernel:   Receiver lock-up workaround activated.
Jul 22 07:55:39 fazer kernel: eth1: Intel Corp. 82557/8/9 [Ethernet Pro 
100] (#2), 00:B0:D0:B0:D0:
FC, IRQ 17.
Jul 22 07:55:39 fazer kernel:   Receiver lock-up bug exists -- enabling 
work-around.
Jul 22 07:55:39 fazer kernel:   Board assembly 07195d-000, Physical 
connectors present: RJ45
Jul 22 07:55:39 fazer kernel:   Primary interface chip i82555 PHY #1.
Jul 22 07:55:39 fazer kernel:   General self-test: passed.
Jul 22 07:55:39 fazer kernel:   Serial sub-system self-test: passed.
Jul 22 07:55:39 fazer kernel:   Internal registers self-test: passed.
Jul 22 07:55:39 fazer kernel:   ROM checksum self-test: passed (0x04f4518b).
Jul 22 07:55:39 fazer kernel:   Receiver lock-up workaround activated.


-- 
  Cedric Gavage <cedric.gavage@unixtech.be>
  http://unixtech.be - http://gavage.com - OpenPGP: 0xED325C64

Re: [Fwd: kernel 2.4.21]

[David S. Miller]

On Wed, 23 Jul 2003 13:30:09 +0200
Cedric Gavage <cedric.gavage@unixtech.be> wrote:

> David S. Miller wrote:
> > Any chance you can try with the e100 driver instead of eepro100?
> Could I use it with these cards?

Yes, if anything, e100 works with more cards than
eepro100 does.  e100 is supported well, whereas I can't
remember the last time eepro100 had a change made to it :-)

Re: [Fwd: kernel 2.4.21]

[Cedric Gavage]

David S. Miller wrote:
> On Wed, 23 Jul 2003 11:44:14 +0200
> Cedric Gavage <cedric.gavage@unixtech.be> wrote:
> 
> 
>>David S. Miller wrote:
>>
>>>On Wed, 23 Jul 2003 11:23:03 +0200
>>>Cedric Gavage <cedric.gavage@unixtech.be> wrote:
>>>
>>>>Still this with 2.4.21 kernel: (intel internet card, driver eepro100)
>>>>
>>>>Jul 23 07:25:58 fazer kernel: recvmsg bug: copied 7CB284C0 seq 7CB288AE
>>>>Jul 23 07:25:58 fazer kernel: KERNEL: assertion (flags&MSG_PEEK) failed at tcp.c(1563)
>>>
>>>Are you running and old version of vsftpd?
>>
>>Thanks for your help...
>>
>>This server is efnet.skynet.be, ircd server connected on EFnet with 
>>ircd-hybrid-6.4...
> 
> 
> Any chance you can try with the e100 driver instead of eepro100?
> 
Ok, now it's e100 driver, I will wait some hours to see if we have again 
problems, thanks for your help.

-- 
  Cedric Gavage <cedric.gavage@unixtech.be>
  http://unixtech.be - http://gavage.com - OpenPGP: 0xED325C64

Re: [Fwd: kernel 2.4.21]

[David S. Miller]

On Wed, 23 Jul 2003 13:40:37 +0200
Cedric Gavage <cedric.gavage@unixtech.be> wrote:

> Ok, now it's e100 driver, I will wait some hours to see if we have again 
> problems, thanks for your help.

Any problems yet?

Re: [Fwd: kernel 2.4.21]

[Cedric Gavage]

David S. Miller wrote:
> On Wed, 23 Jul 2003 13:40:37 +0200
> Cedric Gavage <cedric.gavage@unixtech.be> wrote:
> 
> 
>>Ok, now it's e100 driver, I will wait some hours to see if we have again 
>>problems, thanks for your help.
> 
> 
> Any problems yet?
> 

It's ok now... I was waiting some hours (days) to see if it was really ok ;)

Thanks for your help.

-- 
  Cedric Gavage <cedric.gavage@unixtech.be>
  http://unixtech.be - http://gavage.com - OpenPGP: 0xED325C64

Re: [Fwd: kernel 2.4.21]

[David S. Miller]

On Mon, 28 Jul 2003 09:39:11 +0200
Cedric Gavage <cedric.gavage@unixtech.be> wrote:

> David S. Miller wrote:
> > On Wed, 23 Jul 2003 13:40:37 +0200
> > Cedric Gavage <cedric.gavage@unixtech.be> wrote:
> >
> >>Ok, now it's e100 driver, I will wait some hours to see if we have again 
> >>problems, thanks for your help.
> > 
> > Any problems yet?
> 
> It's ok now... I was waiting some hours (days) to see if it was really ok ;)
> 
> Thanks for your help.

No problem.

Alan and Jeff, please note, executive summary:

1) 'eepro100' driver in 2.4.x + high end EFNET IRC server == crashes
2) same as #1 using 'e100' driver == works

Re: [Fwd: kernel 2.4.21]

[Jeff Garzik]

On Mon, Jul 28, 2003 at 07:32:40AM -0700, David S. Miller wrote:
> On Mon, 28 Jul 2003 09:39:11 +0200
> Cedric Gavage <cedric.gavage@unixtech.be> wrote:
> 
> > David S. Miller wrote:
> > > On Wed, 23 Jul 2003 13:40:37 +0200
> > > Cedric Gavage <cedric.gavage@unixtech.be> wrote:
> > >
> > >>Ok, now it's e100 driver, I will wait some hours to see if we have again 
> > >>problems, thanks for your help.
> > > 
> > > Any problems yet?
> > 
> > It's ok now... I was waiting some hours (days) to see if it was really ok ;)
> > 
> > Thanks for your help.
> 
> No problem.
> 
> Alan and Jeff, please note, executive summary:
> 
> 1) 'eepro100' driver in 2.4.x + high end EFNET IRC server == crashes
> 2) same as #1 using 'e100' driver == works

My Official Story(tm) is currently

* use e100
* unless you really really want to use eepro100

eepro100 in the kernel tree is essentially unmaintained.  One of the
big reasons I merged e100 is that it has an active maintainer with
full access to docs.

	Jeff

Re: [Fwd: kernel 2.4.21]

[Felix Radensky]

Then maybe it makes sense to enable e100 by default and not eepro100 ?

Felix. 

Jeff Garzik wrote:

>  
>
>My Official Story(tm) is currently
>
>* use e100
>* unless you really really want to use eepro100
>
>eepro100 in the kernel tree is essentially unmaintained.  One of the
>big reasons I merged e100 is that it has an active maintainer with
>full access to docs.
>
>	Jeff
>
>
>
>
>  
>