Bug 212501
Summary: | Unknown boot option 8250.nr_uarts | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tom Horsley <horsley1953> |
Component: | kernel-xen | Assignee: | Markus Armbruster <armbru> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6 | CC: | bstein, xen-maint |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-03-28 09:09:04 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: |
Description
Tom Horsley
2006-10-27 01:52:31 UTC
The x86 version of xen also suffers from this, but its not in making the /dev/ices, it in the kernels detection of the hardware during boot. There is no mention in dmesg of it detecting and initializing anything but the ps2 ports. Reverting to a regular i686 kernel fixes things right up. The main reason for the parameter not to be working is that in xen kernels, is that 8250 is put as a module, not builtin, rendering the boot option useless. There's large discussion about it being modular, in bug #204825 This is not a bug, it works as designed. As explained in bug #204825, 8250 must be a module in Xen kernels. Kernel parameters specified on the kernel command line apply only to modules that are built into the kernel image. Module parameters for loadable modules need to be specified with modprobe, either on its command line or in its config files. I suggest to configure nr_uarts in your modprobe.conf for use with Xen. If that doesn't work for you, feel free to reopen the bug. Mark, This may not be a technical bug. However, this sounds like a serious usability issue wtih Red Hat, effectively putting us back to the 70s. For all non-Unix Administrators, like myself, how do I get RH OS to recognize serial devices? [root@some etc]# setserial -bg /dev/ttyS[0-9]* /dev/ttyS1: No such device or address /dev/ttyS2: No such device or address << One serial device is installed on this port /dev/ttyS3: No such device or address Peter, Having to specify 8250.nr_uarts to get your devices working isn't terribly usable regardless of whether you have to do it on the kernel command line or with modprobe. Still, the difference between Xen and non-Xen kernel is unfortunate. There's really nothing we can do about that, I'm afraid. See bug #204825 for why. That bug got resolved by a udev update. Does that help you? |