From: Jeff Wiegley <jeffw@cyte.com>
To: linux-kernel@vger.kernel.org
Subject: 8250_pnp is confused... (udev?)
Date: Mon, 21 May 2007 23:05:05 -0700 [thread overview]
Message-ID: <46528811.2010302@cyte.com> (raw)
I've used serial ports a lot in the past but not for the
past year so. Did something fundamental change?
I have serial_core, 8250 and 8250_pnp modules installed
and things are quite weird... I get all of the /dev/ttyS's
that I DON'T have and none of the ones that I do!
$modprobe -a 8250_pnp
$tail /var/log/message
May 21 22:59:35 home Serial: 8250/16550 driver $Revision: 1.90 $ 4
ports, IRQ sharing disabled
May 21 22:59:35 home pnp: Device 00:07 activated.
May 21 22:59:35 home 00:07: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
So, yes it looks like it sees the one serial port that I also
think I have. but...
$ls -al /dev/ttyS*
crw-rw---- 1 root uucp 4, 65 May 21 22:59 /dev/ttyS1
crw-rw---- 1 root uucp 4, 66 May 21 22:59 /dev/ttyS2
crw-rw---- 1 root uucp 4, 67 May 21 22:59 /dev/ttyS3
It seems that somehow either 8250_pnp (or maybe udev) gets the
logic inverted. It doesn't create a device for the one device
that 8250_pnp found and yet it does create devices for everything
NOT found??
If I rmmod 8250_pnp 8250 serial_core then all the serial devices
go away. So it's 8250/udev creating these oddities and not me.
I am using gentoo with kernel v2.6.21.1 on an intel 64 bit dual-core
with Nvidia 580i chipset. I haven't tweaked any udev rules. udev is
version 104-r12.
Any help is appreciated. Thanks!
- Jeff
next reply other threads:[~2007-05-22 6:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-22 6:05 Jeff Wiegley [this message]
2007-05-22 8:30 ` Konstantin Kletschke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46528811.2010302@cyte.com \
--to=jeffw@cyte.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®