Description of problem: Restarting or stopping the service isdn locks system, this happens in the running system but also upon shutdown. Version-Release number of selected component (if applicable): redhat-network-config: 1.2.13-1 and 1.3.1-1 redhat-network-config-tui: 1.2.13-1 and 1.3.1-1 How reproducible: Always Steps to Reproduce: 1. /etc/rc.d/init.d/isdn stop 2. /etc/rc.d/init.d/isdn restart 3. Menu Services isdn stop Actual results: System lockup without error message, no error log entry Expected results: Additional info: starting isdn causes no problems
for debugging, i need some infos: which kernel version do you have on your machine? which isdn card do you have? please send to me your isdn config files /etc/sysconfig/network-scripts/ifcfg-ipppX /etc/sysconfig/isdncard
Thabnk you for the quick response. Here is the information you asked for: uname -a on my machine outputs: Linux my_pc_name 2.4.20-8 #1 i686 i686 i386 GNU/linux I use an AVM Fritz PCMCIA isdn Card The content of /etc/sysconfug/isdncard: VENDOR_ID= FIRMWARE= NAME='AVM Fritz Card PCMCIA' MODULE=avma1_cs RESOURCES='protocol=2' There is no ifcfg-ippp0 in /etc/sysconfig/network-scripts, only ifcfg-Tiscali (Tiscali is the name of my provider). The contents of this file: # Please read /usr/share/doc/initscripts-*/sysconfig.txt # for the documentation of these parameters. USERCTL=yes PEERDNS=yes TYPE=ISDN DEVICE=ippp0 BOOTPROTO=dialup ONBOOT=no DEFROUTE=no PERSIST=off SECURE=off BUNDLING=on HUPTIMEOUT=600 DIALMODE=manual ENCAP=syncppp USER=silke.maurer PHONE_OUT=0193792 AUTH='+pap -chap' PROVIDER=Tiscali CALLBACK=off CCP=on PC=on AC=on BSDCOMP=on VJ=on VJCCOMP=on NAME=Tiscali DEMAND=no SLAVE_DEVICE=ippp1 Perhaps the error has to do with the name of this file?
it looks like a problem in isdn driver. I assigned it to correct component
Removing redhat-network-config 1.2.13-1 or 1.3.1-1 and redhat-network-config-tui 1.2.13-1 or 1.3.1-1 and reinstalling redhat-network-config 1.2.0-2 and redhat-network-config-tui 1.2.0-2 eliminates the above problem. Is it perhaps necessary for me to match the isdn4k-utils (currently 3.1-62) to the redhat-network-config releases?
strange, redhat-config-network is only used for creating network config files. It cannot cause such problem, because your config files look ok for me! Are you sure that you only downgraded redhat-config-network? nothing else? Have you reconfigured your isdn card with 1.2.0-2?
You are right, of course. I have repeated the up and downgrading of the redaht-network-config packets, and now the lock up problem prevailes. Also, stopping the pcmcia service causes a lockup The removal of isdn4k-utils also causes a lock up. A forced installation of isdn4k-utils works but changes nothing The problem seems to be at the stage of loading the isdn-module during boot, which fails. After all this, I should congratulate you to the journaling file system! I will continue to try to find the cause, perhaps you have a tip or two?
Installation of Shrike 9A has resolved the problems