Bug 82345
| Summary: | setserial close_delay and closing_wait change randomly w/ autoconfig option | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | Lawson Reilly <lreilly> |
| Component: | kernel | Assignee: | Arjan van de Ven <arjanv> |
| Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 8.0 | CC: | lreilly, twaugh |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2004-09-30 15:40:25 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Works fine on this Dell Precision 420. Kernel thing? Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |
Description of problem: when using "setserial -av /dev/ttyS0 autoconfig", the reported closing_wait and close_delay values change apparently randomly. If setting close_delay or closing_wait using setserial, the values that get assigned are not the values that I used in the setserial command. For example: [root@morpheous exe]# setserial -av /dev/ttyS0 close_delay 50 /dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4 Baud_base: 115200, close_delay: 256, divisor: 0 closing_wait: 15360 Flags: spd_normal skip_test Version-Release number of selected component (if applicable): How reproducible: very easy to reproduce Steps to Reproduce: 1. setserial -av /dev/ttyS0 autoconfig 2. 3. Actual results: /dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4 Baud_base: 115200, close_delay: 6707, divisor: 0 closing_wait: 1571 Flags: spd_normal skip_test Expected results: /dev/ttyS0, Line 0, UART: 16550A, Port: 0x03f8, IRQ: 4 Baud_base: 115200, close_delay: 50, divisor: 0 closing_wait: 3000 Flags: spd_normal skip_test Additional info: System is an unmodified Dell Precision 220 running 2.4.18-19.8.0 SMP kernel setserial does not seem to be working properly with either serial port. We discovered this while troubleshooting a failure to read data from a serial device (read() returns 0 bytes) using code that works fine on Red Hat 7.2. update: this problem also occurs on a Dell Precision 530 server running Red Hat Linux 8.0 Server kernel, so it's not machine-specific.