Bug 160831 - isdn fails to load at system startup
isdn fails to load at system startup
Product: Fedora
Classification: Fedora
Component: isdn4k-utils (Show other bugs)
x86_64 Linux
medium Severity high
: ---
: ---
Assigned To: Ngo Than
Depends On:
  Show dependency treegraph
Reported: 2005-06-17 14:26 EDT by Tomasz Kepczynski
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-20 17:43:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tomasz Kepczynski 2005-06-17 14:26:17 EDT
Description of problem:
When system boots up /etc/init.d/isdn start reports failure.
This is probably due to workaround from other bug (133889),
which resulted in makedev subroutine being introduced to create
isdn device nodes on udev introduction. The problem seems to be related
to fact that hisax and other isdn modules seem to be loaded in kernel at
the point when isdn startup script is executed. This results in two
1. module cannot be loaded with parameters specified in
2. It looks like device nodes created in /dev if created AFTER module
   is loaded don't work
I am not sure but the problem is very likely related to udev. As I
understand udev tries very early during boot process to discover connected
hardware which would explain presence of isdn modules in single user mode
(i.e. before isdn script is executed). Unfortunately isdn and udev don't
seem to play nice with each other and udev does not create isdn device nodes.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
This is not the same as during boot but it may show you a point.
1. unload all isdm modules and remove all isdn device nodes from /dev
2. modprobe hisax (or whatever card you have, I don't know the behaviour
   with other hardware modules)
3. service isdn start -> it fails due to isdnctrl failing in line 121
4. service isdn start -> now it works as device nodes in /dev already
   exist and module was unloaded in step 3 as part of script cleanup
Actual results:
isdn does not load during boot

Expected results:
isdn loads during boot

Additional info:
I don't really know if the bug should be filed for isdn4k-utils, kernel
or udev. Please reassign as needed.
And it is high time to have it properly fixed, as workarounds are mess.
Comment 1 Ngo Than 2005-06-20 17:43:26 EDT
it's now fixed in isdn4k-utils-3_2-29, which will be available in rawhide soon.
Could you verify it please. Thanks
Comment 2 Ngo Than 2005-06-20 17:43:53 EDT
it's now fixed in isdn4k-utils-3_2-29, which will be available in rawhide soon.
Could you verify it please. Thanks

Note You need to log in before you can comment on or make changes to this bug.