From: Matthew Wilcox <willy@debian.org>
To: "b.gunreben" <b.gunreben@web.de>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] kernel update bug?
Date: Fri, 24 Jan 2003 00:52:57 +0000 [thread overview]
Message-ID: <20030124005257.A26567@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <3E305C44.11F38160@web.de>; from b.gunreben@web.de on Thu, Jan 23, 2003 at 10:19:00PM +0100
On Thu, Jan 23, 2003 at 10:19:00PM +0100, b.gunreben wrote:
> Now the reason: I found, that with kernel 2.4.9, there were 3 serial devices
> found
>
> /dev/ttyS0 uart 16550A port 0x0000 irq 90 baud_base 454545 spd_normal
> /dev/ttyS1 uart 16550A port 0x0000 irq 106 baud_base 454545 spd_normal
> /dev/ttyS2 uart 16550A port 0x0000 irq 170 baud_base 454545 spd_normal
>
> the later kernel finds only the first two of these interfaces, and restarts
> when restoring the settings of /dev/ttyS2. Later it crashes completely of
> course. I could fix this behaviour by commenting out the last line in
> /etc/serial.conf.
>
> Now my question: should kernel 2.4.20 find two or three serial devices on a
> C360, and why does the kernel crash if setserial tries to configure a
> (nonexistant?) device?
Well, how many serial ports do you have? ;-)
It was a bug up till (i think) a 2.4.17 kernel that we found a ghost
serial port. And setserial is a broken piece of crap that will crash
the machine if it tries to set serial ports that don't exist.
--
"It's not Hollywood. War is real, war is primarily not about defeat or
victory, it is about death. I've seen thousands and thousands of dead bodies.
Do you think I want to have an academic debate on this subject?" -- Robert Fisk
prev parent reply other threads:[~2003-01-24 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 21:19 [parisc-linux] kernel update bug? b.gunreben
2003-01-24 0:52 ` Matthew Wilcox [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=20030124005257.A26567@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=b.gunreben@web.de \
--cc=parisc-linux@lists.parisc-linux.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