From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Andrey Borzenkov" <arvidjaar@mail.ru>
Cc: linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: 2.6.24: Serial disabled in BIOS but serial modules still loaded (probably PnP related)
Date: Sat, 24 Nov 2007 15:09:40 -0800 [thread overview]
Message-ID: <86802c440711241509g6e80b49by67d40bb7d364580e@mail.gmail.com> (raw)
In-Reply-To: <200711242336.43712.arvidjaar@mail.ru>
On Nov 24, 2007 12:36 PM, Andrey Borzenkov <arvidjaar@mail.ru> wrote:
> I have no COM port on notebook (without port replicator which I do not have)
> so COM is disabled in BIOS. No ttyS* is detected during boot (and no device
> created) but I just noticed that serial modules are still loaded. Well, this
> partially defeats the purpose of disabling COM port - the intention was to
> free resources by *not* loading unneeded modules ...
>
> This may have something to do with (ACPI) PnP which apparently believes COM is alive.
> Notebook is Toshiba Portege 4000.
>
> {pts/0}% lsmod | grep 82
> 8250_pnp 9792 0
> 8250 24660 1 8250_pnp
> serial_core 22872 1 8250
>
> {pts/0}% lspnp -v
> 00:00 PNP0c01 System board
> state = active
> mem 0x0-0x9ffff
> mem 0xe0000-0xeffff
> mem 0xf0000-0xfffff
> mem 0x100000-0x1ef5ffff
>
> 00:01 PNP0a03 PCI bus
> state = active
> io 0xcf8-0xcff
>
> 00:02 PNP0200 AT DMA controller
> state = active
> io 0x0-0xf
> io 0x81-0x83
> io 0x87-0x87
> io 0x89-0x8b
> io 0x8f-0x8f
> io 0xc0-0xdf
> dma 4
>
> 00:03 PNP0800 AT speaker
> state = active
> io 0x61-0x61
>
> 00:04 PNP0c04 Math coprocessor
> state = active
> io 0xf0-0xff
> irq 13
>
> 00:05 PNP0303 IBM enhanced keyboard (101/102-key, PS/2 mouse support)
> state = active
> io 0x60-0x60
> io 0x64-0x64
> irq 1
>
> 00:06 PNP0f13 PS/2 port for PS/2-style mice
> state = active
> irq 12
>
> 00:07 PNP0b00 AT real-time clock
> state = active
> io 0x70-0x71
> irq 8
>
> 00:08 PNP0c02 Motherboard resources
> state = active
> io 0x2e-0x2f
> io 0x62-0x62
> io 0x66-0x66
> io 0x80-0x80
> io 0x84-0x86
> io 0x88-0x88
> io 0x8c-0x8e
> io 0x92-0x92
>
> 00:09 PNP0501 16550A-compatible serial port
> state = active
> io 0x3f8-0x3ff
> irq 5
>
> 00:0a SMCf010 SMC Fast Infrared Port
> state = disabled
>
> 00:0b PNP0401 ECP printer port
> state = disabled
>
> ..
> [ 126.035809] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
...
> [ 126.107096] serial 00:09: activated
...
Can you cat /sys/firmware/acpi/DSDT and use iasl to decode it?
it seems that your BIOS has problem about com setup.
YH
next prev parent reply other threads:[~2007-11-24 23:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 20:36 Andrey Borzenkov
2007-11-24 23:09 ` Yinghai Lu [this message]
2007-11-25 16:50 ` Andrey Borzenkov
2007-11-25 3:55 ` Michael H. Warfield
2007-11-25 7:54 ` David Newall
[not found] <fa.P01QcmUf2f3DN4etI8KJYFdaLnE@ifi.uio.no>
2007-11-25 18:39 ` Robert Hancock
2007-11-25 20:01 ` Andrey Borzenkov
2007-11-27 8:59 ` Shaohua Li
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=86802c440711241509g6e80b49by67d40bb7d364580e@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=arvidjaar@mail.ru \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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®