Bug 222731 - problem in isdn_free_channel blocks new ISDN connection
problem in isdn_free_channel blocks new ISDN connection
Product: Fedora
Classification: Fedora
Component: isdn4k-utils (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ngo Than
Depends On:
  Show dependency treegraph
Reported: 2007-01-15 16:38 EST by Peter Bieringer
Modified: 2008-04-04 05:39 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-04-04 05:39:12 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 Peter Bieringer 2007-01-15 16:38:55 EST
Description of problem:
Sometimes, the ISDN channel is not freed after connection, resulting in that
ISDN can't be no longer used.

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

How reproducible:

Steps to Reproduce:
1. dial in to Linux box to ippp1 (single or dual channel)
2. hang up
3. retry
4. try to use ISDN on Linux box with minicom
Actual results:
Channels busy

Expected results:
Free channels

Additional info:
I do not know what happens, the only hint I see was a flashing green LED on the
HiSaX card.

After disabling the ISDN getty's from inittab and shutting down the ippp1
interface I was able to remove the hisax module.

Here an interesting log entry shows up:

Jan 15 22:27:33 server kernel: isdn: HiSax,ch0 cause: E001B
Jan 15 22:27:58 server kernel: HiSax: debugging flags card 1 set to 3ff
Jan 15 22:28:18 server kernel: isdn_free_channel: called with invalid drv(-1) or
Jan 15 22:28:18 server kernel: isdn_free_channel: called with invalid drv(-1) or
Jan 15 22:28:18 server kernel: ippp_ccp: freeing reset data structure da86e000
Jan 15 22:28:18 server kernel: ippp_ccp: freeing reset data structure dfd87800

I filed this bug against isdn4k-utils, but perhaps it's more a kernel problem.
Comment 1 Bug Zapper 2008-04-04 01:37:02 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 2 Peter Bieringer 2008-04-04 05:39:12 EDT
I'm currently no longer playing with ISDN links, so this issue can be closed for
now as unresolved.

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