According to [EMAIL PROTECTED]: While burning my CPU.
>
> Hi
>
> Hm.. it didn�t work after i�ll defined SCC_DELAY, now on the morning the
> RTS/PTT stop working again,
> but the other 3 ports still works.. (scc0�s PTT down) :/
> (I have now the �tx_int watchdog� patch and SCC_DELAY)
SCC_DELAY is not the problem here, what you are experiancing is something
else, a problem which i have also, the symptoms are,
the interface recieves all packets as normal, but you cant call out, if a
ax25 connect request is recieved your system does nothing, it does not
answer, it will not even answer an incomming telnet session, you cant telnet
or ftp out either, in otherwords the interface is now "one way".
The solution is to down the interface with ifconfig and up it again, i know
this is not the "complete" solution, the solution will need to come from
Joerg DL1BKE. I gather from his past corrispondace on this matter that he
does not have or has never experianced this problem.
He did however point out that using "soft dcd" will cause this problem, it
does solve the problem on one of my machines but not on the other.
What i have noticed about the interface "half" dissapiering is it stops
working under the following senario.
Very heavy ip traffic to one host, this could be an ftp session, mail or
other, the system has mutiple connectees via ax25 and netrom, the system is
transmitting constanly, as soon as a netrom broadcast is transmitted on the
interface the interface just dies.
The interface concerned uses mode datagram.
I wrote a small shell script which checks the results of pings sent and
received, if no pings are received from a certain host on that interface
then the script will down the interface, up it again configure it add
routes, kill processes connected with that interface and start them again.
It runs under cron and it mails the sysop to inform him/her that there was
problem. Of course if thre is no host whois 24/7 on that interface then it
would not work ;-)
If you would like a copy let me know.
Of course if your interface has different symptoms as those described above,
then sorry for the bandwidth.
>
> First when i�ll started up, the driver complain on the 2 first ports, the
> driver didn�t find scc0 & scc1,
> scc2 & scc3 it found nicely, i�ll putted in a delay of 4sec between "insmod"
> and "sccinit",
> then the driver found all nice, i�ll did also change the bus clock to BIOS
> default (ATclock/8).
> (The computer is 486dx-2 66MHz, not to fast in my oppinion.. hi)
>
> BTW
> I compiled the scc.c in the kernel, and the scc.c who is in the
> "z8530drv-2.4c" archive,
> och compared the scc.o�s , slight differnt in size, perhaps a gcc optimzie
> bug thats fools me around?
>
> When i�ll compares the files, the only differnces is some #includes.
> (This compile was done with clean src of kernel and clean src of
> z8530drv-2.4c)
>
> (z8530drv-2.4c archive)
> -rw-r--r-- 1 root root 33852 Dec 16 07:07 scc.o
>
> (2.0.35 kernel)
> -rw-r--r-- 1 root root 33260 Dec 16 06:59 scc.o
>
> 73 de Morgan
>
> ---
> 'The box said "Windows 95, Windows NT 4.0 or better", so i installed Linux.'
> Morgan Wemanis - Marks Kommun IT-Section - e-mail: [EMAIL PROTECTED]
> Phone: +46 320-17060 , Fax: +46 320-14722 , Mobile: 070-635 85 47
> AMPRnet: [EMAIL PROTECTED] , AX25net: [EMAIL PROTECTED]
>
>
--
Regards Richard.
[EMAIL PROTECTED]
Merry Xmas to all, and may all your troubles be small (ones).
