Bug 148818 - FC3 2.6.10 serial ports for multiport cards get wrong numbers
Summary: FC3 2.6.10 serial ports for multiport cards get wrong numbers
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL: none
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-02-15 20:55 UTC by Jerry Geis
Modified: 2015-01-04 22:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-10-03 00:38:13 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jerry Geis 2005-02-15 20:55:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040616

Description of problem:
I have a multiport serial card (8 ports)
when I install the card. instead of getting serial ports ttyS4 - ttyS11
I get ttyS14, ttyS15 then ttyS44 - ttyS49.

The tty numbers assigned should be sequential starting at 4.
This the behaviour in 2.4.X and seems logical enough.

Thanks,

Version-Release number of selected component (if applicable):
kernel.2.6.9 and 2.6.10

How reproducible:
Always

Steps to Reproduce:
1. insert multiport serial card quatech ESC100M
2. boot with 2.6.10
3. serial ports assigned are NOT sequential.
    

Actual Results:  serial ports ar 14,15, 44-49

Expected Results:  I expected the serial ports to be 4 - 11.



Additional info:

I get the exact same results with a different vendor 
multiport card also.

Comment 1 Dave Jones 2005-07-15 19:57:19 UTC
An update has been released for Fedora Core 3 (kernel-2.6.12-1.1372_FC3) which
may contain a fix for your problem.   Please update to this new kernel, and
report whether or not it fixes your problem.

If you have updated to Fedora Core 4 since this bug was opened, and the problem
still occurs with the latest updates for that release, please change the version
field of this bug to 'fc4'.

Thank you.

Comment 2 Dave Jones 2005-10-03 00:38:13 UTC
This bug has been automatically closed as part of a mass update.
It had been in NEEDINFO state since July 2005.
If this bug still exists in current errata kernels, please reopen this bug.

There are a large number of inactive bugs in the database, and this is the only
way to purge them.

Thank you.


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