Re: isdn stops working when load increases
Alexander et al,
# Still ok. I have rtprio 25 (as from the isdnd.rc.sample, should I tune this?
# Remove the line?) in my isdnd.rc and this at the end of /etc/rc.isdn:
#
# I think Hellmuth choosed a good value for rtprio, and I didn't think it
# solves your problem if you increase the value, but feel free to play a
*De*creasing gives it higher priority, according to rtprio(1).
# little bit with it (I think isdnd slowes down because of a lot of
# interrupts, and if I didn't have a wrong understanding of the system,
# rtprio didn't helps in this case).
#
# echo 'removing previous isp0 config'
# ifconfig isp0 delete -link1 down
# echo 'setting sppp options'
# ispppcontrol isp0 myauthproto=pap myauthname= myauthsecret=
hisauthproto=none callin
# echo 'configuring isp0'
# ifconfig isp0 1.2.3.4 5.6.7.8 netmask 0x link1 2/dev/null
#
# What's your defaultroute? I use -interface isp1.
5.6.7.8 (modified for the purpose of this mail :-)
# BTW: I use /etc/start_if.isp1 to configure the interface, no need to
# modify rc.isdn, e.g.:
# ---snip---
# (11) root@ttyp0 # less /etc/start_if.isp1
# ifconfig isp1 link1 0.0.0.0 0.0.0.1 netmask 255.255.0.0
# ispppcontrol isp1 $(cat /etc/isdn/connect-CBC.parameters) enable-vj
# ifconfig isp1 down
# ---snip---.
Ah, so that's how it's done properly.
# While we're at it, maybe someone wants to commit something like this:
# ---snip---
# --- /usr/src/etc/rc.isdnSat Apr 28 14:49:22 2001
# +++ /etc/rc.isdnSun Apr 29 15:37:04 2001
# @@ -38,6 +38,23 @@
# [Yy][Ee][Ss])
# echo -n 'ISDN subsystem setup:'
#
# + # Terminal type for fullscreen mode, default to syscons driver
# + #
# + if [ ! -n ${isdn_ttype} ]; then
# + isdn_ttype=cons25
# + fi
# + if [ -n ${isdn_screenflags} ]; then
# + /usr/sbin/vidcontrol ${isdn_fsdev} ${isdn_fsdev} 21
${isdn_screenflags}
# + fi
...
# ---snip---
# (I think the isdn_ttype part isn't needed anymore, someone committed
# something like this already, but the screenflags part is useful for me)
Yup, that was me :-)
Can you provide a patch against -current and also a patch adding
isdn_screenflags to /etc/defaults/rc.conf and rc.conf(5)? It's important
to document all the knobs there. Should be easy.
Regards,
Jens
--
Jens Schweikhardt http://www.schweikhardt.net/
SIGSIG -- signature too long (core dumped)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: isdn stops working when load increases
On 3 Mai, Jens Schweikhardt wrote:
# However, as soon as I do a find / or buildworld or some other
# commands increasing the load significantly (about 1 or more),
# isdnd seems to take a nap. No more packets transmitted. If I
# suspend the running programs, isdnd awakes and continues.
# Is anybody else observing the same behavior?
#
# Not with my Apr 29 kernel (no rtprio keyword in isdnd.rc), at least I
# didn't noticed it.
#
# BTW: What about dial-on-demand?
Still ok. I have rtprio 25 (as from the isdnd.rc.sample, should I tune this?
Remove the line?) in my isdnd.rc and this at the end of /etc/rc.isdn:
I think Hellmuth choosed a good value for rtprio, and I didn't think it
solves your problem if you increase the value, but feel free to play a
little bit with it (I think isdnd slowes down because of a lot of
interrupts, and if I didn't have a wrong understanding of the system,
rtprio didn't helps in this case).
echo 'removing previous isp0 config'
ifconfig isp0 delete -link1 down
echo 'setting sppp options'
ispppcontrol isp0 myauthproto=pap myauthname= myauthsecret=
hisauthproto=none callin
echo 'configuring isp0'
ifconfig isp0 1.2.3.4 5.6.7.8 netmask 0x link1 2/dev/null
What's your defaultroute? I use -interface isp1.
BTW: I use /etc/start_if.isp1 to configure the interface, no need to
modify rc.isdn, e.g.:
---snip---
(11) root@ttyp0 # less /etc/start_if.isp1
ifconfig isp1 link1 0.0.0.0 0.0.0.1 netmask 255.255.0.0
ispppcontrol isp1 $(cat /etc/isdn/connect-CBC.parameters) enable-vj
ifconfig isp1 down
---snip---.
While we're at it, maybe someone wants to commit something like this:
---snip---
--- /usr/src/etc/rc.isdnSat Apr 28 14:49:22 2001
+++ /etc/rc.isdnSun Apr 29 15:37:04 2001
@@ -38,6 +38,23 @@
[Yy][Ee][Ss])
echo -n 'ISDN subsystem setup:'
+ # Terminal type for fullscreen mode, default to syscons driver
+ #
+ if [ ! -n ${isdn_ttype} ]; then
+ isdn_ttype=cons25
+ fi
+ if [ -n ${isdn_screenflags} ]; then
+ /usr/sbin/vidcontrol ${isdn_fsdev} ${isdn_fsdev} 21
+${isdn_screenflags}
+ fi
+
+ # Check for pcvt driver (VT100/VT220 emulator)
+ #
+ if [ -x /usr/sbin/ispcvt ]; then
+ if /usr/sbin/ispcvt; then
+ isdn_ttype=pcvt25
+ fi
+ fi
+
case ${isdn_flags} in
[Nn][Oo])
isdn_flags=''
---snip---
(I think the isdn_ttype part isn't needed anymore, someone committed
something like this already, but the screenflags part is useful for me)
Bye,
Alexander.
--
Loose bits sink chips.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: isdn stops working when load increases
On Wed, May 02, 2001 at 09:03:26PM +0200, Jens Schweikhardt wrote: Hello, I've seen some recent mails related to rtprio oddity which seemed to also affect the isdnd. My -current is cvsupped May 1st (and survived; I've still got a fully populated root fs :-) However, as soon as I do a find / or buildworld or some other commands increasing the load significantly (about 1 or more), isdnd seems to take a nap. No more packets transmitted. If I suspend the running programs, isdnd awakes and continues. Is anybody else observing the same behavior? I'm having similar problems: Some minutes/hours (depends on the workload) after each boot 'top' reports about 12% of my CPU time are used for interrupt processing. The interrupt time stays at about 10% even when there's nothing to do (no disk io, no network traffic, no sound). Running FBSD 4.2 on the same box reports about 0.2-1% interrupt usage; the same value which is shown on CURRENT just after a reboot. At the same time the packet loss rate of my isdn interface raises to about 70% while transfering files. (a simple ping does *not* trigger this problem). This behavior seems not related to rtprio oddity since i first noticed it on Apr 9th. (the date this box switched to CURRENT) joerg To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: isdn stops working when load increases
On 2 Mai, Jens Schweikhardt wrote: [Ruslan: I CCed you because of the second part of the mail] I've seen some recent mails related to rtprio oddity which seemed to also affect the isdnd. My -current is cvsupped May 1st (and Yes, it didn't started with the broken version of rtprio (I had to remove the rtprio keyword). survived; I've still got a fully populated root fs :-) I got a kernel panic with no coredump, I hope the npx commit fixed this, will test later. However, as soon as I do a find / or buildworld or some other commands increasing the load significantly (about 1 or more), isdnd seems to take a nap. No more packets transmitted. If I suspend the running programs, isdnd awakes and continues. Is anybody else observing the same behavior? Not with my Apr 29 kernel (no rtprio keyword in isdnd.rc), at least I didn't noticed it. BTW: What about dial-on-demand? I need this patch from Ruslan (attention, will not apply because of tab-space conversation by cutpaste!) ---snip--- Index: raw_ip.c === RCS file: /home/ncvs/src/sys/netinet/raw_ip.c,v retrieving revision 1.75 diff -u -p -r1.75 raw_ip.c --- raw_ip.c2001/03/16 20:00:53 1.75 +++ raw_ip.c2001/03/30 14:09:20 @@ -398,7 +398,9 @@ rip_ctlinput(cmd, sa, vip) * thing to do, but at least if we are running * a routing process they will come back. */ +#if 0 in_ifadown(ia-ia_ifa); +#endif break; } } ---snip--- to get a working dial-on-demand (the defaultroute vanishes after the first ifconfig down, but stays after readding the defaultroute). Bye, Alexander. -- 0 and 1. Now what could be so hard about that? http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: isdn stops working when load increases
On Thu, May 03, 2001 at 01:39:50PM +0200, Alexander Leidinger wrote: # On 2 Mai, Jens Schweikhardt wrote: # # [Ruslan: I CCed you because of the second part of the mail] # # I've seen some recent mails related to rtprio oddity which seemed # to also affect the isdnd. My -current is cvsupped May 1st (and # # Yes, it didn't started with the broken version of rtprio (I had to # remove the rtprio keyword). # # survived; I've still got a fully populated root fs :-) # # I got a kernel panic with no coredump, I hope the npx commit fixed this, # will test later. # # However, as soon as I do a find / or buildworld or some other # commands increasing the load significantly (about 1 or more), # isdnd seems to take a nap. No more packets transmitted. If I # suspend the running programs, isdnd awakes and continues. # Is anybody else observing the same behavior? # # Not with my Apr 29 kernel (no rtprio keyword in isdnd.rc), at least I # didn't noticed it. # # BTW: What about dial-on-demand? Still ok. I have rtprio 25 (as from the isdnd.rc.sample, should I tune this? Remove the line?) in my isdnd.rc and this at the end of /etc/rc.isdn: echo 'removing previous isp0 config' ifconfig isp0 delete -link1 down echo 'setting sppp options' ispppcontrol isp0 myauthproto=pap myauthname= myauthsecret= hisauthproto=none callin echo 'configuring isp0' ifconfig isp0 1.2.3.4 5.6.7.8 netmask 0x link1 2/dev/null Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
isdn stops working when load increases
hello, world\n I've seen some recent mails related to rtprio oddity which seemed to also affect the isdnd. My -current is cvsupped May 1st (and survived; I've still got a fully populated root fs :-) However, as soon as I do a find / or buildworld or some other commands increasing the load significantly (about 1 or more), isdnd seems to take a nap. No more packets transmitted. If I suspend the running programs, isdnd awakes and continues. Is anybody else observing the same behavior? Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
