From: Horms <horms@verge.net.au>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-ia64@vger.kernel.org, linux-serial@vger.kernel.org,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: IA64: Broken Serial Console
Date: Sun, 04 Jun 2006 04:57:11 +0000 [thread overview]
Message-ID: <20060604045709.GA18372@verge.net.au> (raw)
In-Reply-To: <20060602115359.GG32143@parisc-linux.org>
On Fri, Jun 02, 2006 at 05:53:59AM -0600, Matthew Wilcox wrote:
> On Fri, Jun 02, 2006 at 08:48:06PM +0900, Horms wrote:
> > I have noticed that the serial console on my ia64 machine seems
> > to have broken since 2.6.16. Thanks to git bisect I have been
> > able to track this problem down to 111c9bf8c5cfa92363b3719c8956d29368b5b9de
> >
> > [SERIAL] remove 8250_acpi (replaced by 8250_pnp and PNPACPI)
> >
> > With the combination of PNPACPI and 8250_pnp, we no longer need
> > 8250_acpi.
> >
> > Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> > Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
> >
> > I haven't had time to look into the code and I have to leave
> > my desk shortly, so I thought I would post here to see if anyone
> > has any ideas.
>
> Well, does your config have PNPACPI and SERIAL_8250_PNP enabled?
Thanks, adding those options (obviously) solved the problem.
--
Horms http://www.vergenet.net/~horms/
next prev parent reply other threads:[~2006-06-04 4:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-10 8:24 [RFC] IA64: Use early_parm to handle mvec_name and nomca Horms
2006-03-10 9:54 ` Jes Sorensen
2006-03-11 3:43 ` Horms
2006-03-11 8:51 ` Jes Sorensen
2006-03-11 20:17 ` Chen, Kenneth W
2006-03-13 4:08 ` Horms
2006-06-02 11:48 ` IA64: Broken Serial Console Horms
2006-06-02 11:53 ` Matthew Wilcox
2006-06-04 4:57 ` Horms [this message]
2006-06-02 11:59 ` Francois WELLENREITER
2006-03-13 6:33 ` [RFC] IA64: Use early_parm to handle mvec_name and nomca Chen, Kenneth W
2006-03-13 8:12 ` Horms
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=20060604045709.GA18372@verge.net.au \
--to=horms@verge.net.au \
--cc=bjorn.helgaas@hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=rmk+kernel@arm.linux.org.uk \
/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