Advice I have been given is that if network traffic exceeds 15 - 20%
theoretical, the number of collisions will increase exponentially, and
completely clog the network. With a hub, all clients will see all ather
clients traffic, and delay their transmission untill quiet, then several
clients will try to send at the same time, crash, then all try again.
Shane
Evgueni Limarenko wrote:
>
> I've got occasional Kernel Panic during client's boot up.
> The ratio of successful attempts to unsuccessful is about 2:1.
> See the console messages below (I type it in manually :-0 ):
>
> Unknown Flash Type
>
> Bootrom v1.4
>
> Etherboot/32 v4.5.8 (GPL) For more info, visit
> www.DisklessWorkstations.Com
> ROM segment 0xC800 length 0x4000 reloc 0x9800
> Etherboot/32 version 4.5.8 (GPL) for [RTL8139]
> Found Realtek 8139 at )xC000, ROM address 0x00370000
> Probing...[RTL8139] - ioaddr 0xC000, addr 00:50:2C:60:76:C7 10Mbps
> full-duplex
> Searching for server (DHCP)...
> Me: 172.16.11.139, Server: 172.16.1.40, Gateway 172.16.3.254
> Loading /lts/vmlinuz-2.4.9-ltsp-5 (NBI)... done
> mknbi-1.2-6/first32.c (GPL)
> 66496k total memory
> Ramdisk at 0X0407F000, size 0X00071000
> Uncompressing Linux... Ok, booting the kernel.
> Linux version 2.4.9-ltsp-5 (root@server) (gcc version 2.96 20000731 (Red
> Hat Linux 7.1.2.96-98)) #7 Mon Dec 10 00:59:58 EST 2001
> BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000010009fc00 (usable)
> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000000bf00000 (usable)
> BIOS-e820: 00000000ffb00000 - 0000000100000000 (reserved)
> On node 0 totalpages: 48896
> zone(0): 4096 pages.
> zone(1): 44800 pages.
> zone(2): 0 pages.
> Kernel command line: rw root=/dev/ram0 init=/linuxrc rw
> Initializing CPU#0
> Detected 534.556 MHz processor.
> Console: colour VGA+ 80x25
> Calibrating delay loop... 1064.96 BogoMIPS
> Memory: 190128k/195584k available (867k kernel code, 5068k reserved, 204k
> data,
> 68k init, 0k highmem)
> Dentry-cache hash table entries: 32768 (order: 6, 262144 bytes)
> Inode-cache hash table entries: 16384 (order: 5, 131072 bytes)
> Mount-cache hash table entries: 4096 (order: 3, 32768 bytes)
> Buffer-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Page-cache hash table entries: 65536 (order: 6, 262144 bytes)
> CPU: L1 I cache: 16K, L1 D cache: 16K
> CPU: L2 cache: 128K
> Intel machine check architecture supported.
> Intel machine check reporting enabled on CPU#0
> CPU: Intel Celeron (Coppermine) stepping 03
> Enabling fast FPU save and restore... done.
> Enabling unmasked SIMD FPU exception support... done.
> Checking 'hlt' instruction... PK.
> Checking for popad bug... OK.
> POSIX conformance testing by UNIFIX
> PCI: PCI BIOS revision 2.10 entry at 0xfb2c0, last bus=1
> PCI: Using configuration type 1
> PCI: Probing PCI hardware
> Unknown bridge resource 2: assuming transparent
> Linux NET4.0 for Linux 2.4
> Based upon Swansea University Computer Society NET3.039
> Starting kswapd v1.8
> devfs: v0.107 (20010709) Richard Gooch ([EMAIL PROTECTED])
> devfs: boot_options: 0x0
> pty: 256 Unix98 ptys configured
> block: 128 slots per queue, batch=16
> RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP
> IP: routing cache hash table of 1024 buckets, 8Kbytes
> TCP: Hash tables configured (established 16384 bind 16384)
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 452k freed
> VFS: Mounted root (ext2 filesystem).
> Freeing unused kernel memory: 68k freed
> ========================================================================
> =======
> Running /linuxrc
> Mounting /proc
> linuxrc: Installing 8139too driver
> insmod /lib/modules/net/8139too.o
> Using /lib/modules/net/8139too.o
> 8139too Fast Ethernet driver 0.9.18a
> invalid operand: 0000
> CPU: 0
> EIP: 0010:[<c010c4f0>]
> EFLAGS: 00010246
> eax: 00000000 ebx: c406b800 ecx: 00000cf8 edx: 00000cfc
> esi: 000000fc edi: c406b800 ebp: xx802da0 esp: c41ade78
> ds: 0018 es: 0018 ss: 0018
> Process insmod (pid: 25, stackpage=c41ad000)
> Stack: c010cc6b c406b800 ...
> Call Trace: [<c010cc6b>] [<c017f96f>] ...
>
> Code: ff ff ff ff ff ff 00 20 e0 67 42 6e 08 06 00 01 08 00 06 04
> Segmentation fault
>
> ERROR! Failed to install the NIC driver module!
> This could be caused by the wrong module for your particular
> network interface card. Double check the 'option-129' entry
> in your /etc/dhcpd.conf file.
>
> Kernel panic: Attempted to kill init!
>
> -------------------------------------------------------------------------
> My /etc/dhcpd.conf file:
>
> deny unknown-clients ;
> option domain-name "company.com" ;
> option domain-name-servers 172.16.1.4 ;
>
> subnet 172.16.0.0 netmask 255.255.0.0
> {
> option routers 172.16.3.254 ;
> }
>
> group {
> option root-path "172.16.1.40:/opt/ltsp/i386";
> filename "/lts/vmlinuz-2.4.9-ltsp-5";
> next-server 172.16.1.40 ;
> use-host-decl-names on;
> host node133 {
> hardware ethernet 00:50:2c:60:7a:34 ;
> fixed-address 172.16.11.133 ;
> }
> -------------------------------------------------------------------------
>
> Additional question:
> We had certain network problems with the clients, using 10Mbps
> half-duplex
> network connection. Those clients could have 5-10 freezings and even
> crashes, especially when they were connected to the old slow HUB.
> If I rlogin to the client node and type in
> /sbin/ifconfig:
> eth0 Link encap:Ethernet HWaddr 00:90:27:B6:BA:F5
> inet addr:172.16.1.20 Bcast:172.16.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:195126 errors:0 dropped:0 overruns:0 frame:0
> TX packets:188318 errors:5 dropped:0 overruns:0 carrier:5
> collisions:64622 txqueuelen:100
> Interrupt:20 Base address:0xdcc0
> Take a look at collision number!
>
> Recently we connected every client to the new and fast switch.
> So, now every client has 10Mbps full-duplex.
> No more freezings, no more crashes (so far). Collision number is 0.
>
> The problem has been solved, but still, why can't we use slow network?
>
> _____________________________________________________________________
> Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
> https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
> For additional LTSP help, try #ltsp channel on irc.openprojects.net
_____________________________________________________________________
Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto:
https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help, try #ltsp channel on irc.openprojects.net
