Re: tcp stalls with 2.4 (but not 2.2)

> > I'm seeing stalls sending packets to some clients. I see this problem > > under 2.4 (2.4.1 and 2.4.1ac17) but not under 2.2.17. > > compiled in ECN support? SYNcookies? try disabling through /proc > tcp or udp? if udp check /proc/net/ipv4/ip_udpdloose or such CONFIG_INET_ECN is not set

tcp stalls with 2.4 (but not 2.2)

I'm seeing stalls sending packets to some clients. I see this problem under 2.4 (2.4.1 and 2.4.1ac17) but not under 2.2.17. My theory is there is an ICMP black hole between my server and some of its clients. Is there a tool to pinpoint that black hole if it exists? Can anyone suggest another

tcp stalls with 2.4 (but not 2.2)

I'm seeing stalls sending packets to some clients. I see this problem under 2.4 (2.4.1 and 2.4.1ac17) but not under 2.2.17. My theory is there is an ICMP black hole between my server and some of its clients. Is there a tool to pinpoint that black hole if it exists? Can anyone suggest another

Re: tcp stalls with 2.4 (but not 2.2)

I'm seeing stalls sending packets to some clients. I see this problem under 2.4 (2.4.1 and 2.4.1ac17) but not under 2.2.17. compiled in ECN support? SYNcookies? try disabling through /proc tcp or udp? if udp check /proc/net/ipv4/ip_udpdloose or such CONFIG_INET_ECN is not set in

2.4.2pre3 panic with nfsd

This is a crash from nfsd on 2.4.2pre3. Cpuinfo below ksymoops output. Top state at crash below ksymoops. Exported disks are 3 partitions of one scsi disk device. All three filesystems are ext2. Scsi adapter is buslogic. Two tulip network cards. Two heavy use write-mostly nfs clients. gcc

2.4.2pre3 panic with nfsd

This is a crash from nfsd on 2.4.2pre3. Cpuinfo below ksymoops output. Top state at crash below ksymoops. Exported disks are 3 partitions of one scsi disk device. All three filesystems are ext2. Scsi adapter is buslogic. Two tulip network cards. Two heavy use write-mostly nfs clients. gcc

Re: sysinfo.sharedram not accounted for on i386 ?

> On Mon, Feb 12, 2001 at 12:05:03AM -0700, Brian Grossman wrote: > > On i386, sysinfo.sharedram is not accounted for, leading /proc/meminfo to > > always report MemShared as 0. Is this the intended behavior? > > Yes. Thanks. Is there a preferred way of getting the equi

sysinfo.sharedram not accounted for on i386 ?

On i386, sysinfo.sharedram is not accounted for, leading /proc/meminfo to always report MemShared as 0. Is this the intended behavior? Brian - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at

ext2: block > big ?

What does a message like 'ext2: block > big' indicate? This was kernel 2.2.18aa2. The machine was completely unresponsive when I got there. There were a bunch of block>big messages on the screen, but no oops. In my grogginess, I didn't have the sense to copy down the whole message, but it

ext2: block big ?

What does a message like 'ext2: block big' indicate? This was kernel 2.2.18aa2. The machine was completely unresponsive when I got there. There were a bunch of blockbig messages on the screen, but no oops. In my grogginess, I didn't have the sense to copy down the whole message, but it did

sysinfo.sharedram not accounted for on i386 ?

On i386, sysinfo.sharedram is not accounted for, leading /proc/meminfo to always report MemShared as 0. Is this the intended behavior? Brian - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at