From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Kenneth Parrish <Kenneth.Parrish@family-bbs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc1-git2 Oops on rmmod serial_core
Date: Sat, 2 Jul 2005 11:40:34 +0100 [thread overview]
Message-ID: <20050702114034.B7790@flint.arm.linux.org.uk> (raw)
In-Reply-To: <503fc0.e20f3b@family-bbs.org>; from Kenneth.Parrish@family-bbs.org on Sat, Jul 02, 2005 at 06:57:54AM +0000
On Sat, Jul 02, 2005 at 06:57:54AM +0000, Kenneth Parrish wrote:
> The serial support code newly allows selecting the max number of serial
> ports. This computer has one s-port so i typed '1'.
>
> config SERIAL_8250_NR_UARTS
> int "Maximum number of 8250/16550 serial ports"
> depends on SERIAL_8250
> default "4"
> help
> Set this to the number of serial ports you want the driver
> to support. This includes any ports discovered via ACPI or
> PCI enumeration and any ports that may be added at run-time
> via hot-plug, or any ISA multi-port serial cards.
>
> I found the value needs to be at least '4' or we oops at rmmod
> serial_core. 2.6.13-rc1-git2 kernels with values from one through four
> were tested.
It's actually worse than that. If you set it to less than 4 on an x86
PC, it'll stamp over memory. All is not lost though - it's fixed in:
http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=44454bcdb90532b372c74e3546043d8a3a468939
I'd advise people _not_ to run -git2. If they do and they see any
oddities, please don't bother reporting them unless you can reproduce
them with a later version or with this set to at least '4'. This
problem can cause oopses in other parts of the kernel.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
prev parent reply other threads:[~2005-07-02 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-02 6:57 2.6.13-rc1-git2 Oops on rmmod serial_core Kenneth Parrish
2005-07-02 10:40 ` Russell King [this message]
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=20050702114034.B7790@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=Kenneth.Parrish@family-bbs.org \
--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