From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Josh Boyer <jwboyer@redhat.com>, Sean Young <sean@mess.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
tkil@scrye.com, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Stable kernel 3.8.4/3.9-rc3 breaks PNP serial port
Date: Tue, 2 Apr 2013 09:23:36 -0700 [thread overview]
Message-ID: <20130402162336.GB318@kroah.com> (raw)
In-Reply-To: <20130402155344.GA29980@hansolo.jdub.homelinux.org>
On Tue, Apr 02, 2013 at 11:53:44AM -0400, Josh Boyer wrote:
> Hi All,
>
> We've had a report [1] that the 3.8.4 stable kernel makes a PNP serial
> port stop working. After testing 3.8.3, the reporter narrowed it down
> to stable commit eec98f82c637 (tty/8250_pnp: serial port detection
> regression since v3.7) (upstream commit 77e372a3d82). Reverting that
> single commit from 3.8.5 allows the serial port to continue working.
>
> The machine in question is using an AMI UEFI implementation as the
> firmware, and on 3.8.3 the serial port has the following in
> /sys/bus/pnp/devices/00:0a/resources
>
> state = active
> io disabled
> irq 4
> dma disabled
>
> With 3.8.[45], the same file has:
>
> state = disabled
> io disabled
> irq 4
> dma disabled
>
> In both cases, the io and dma resources are disabled, and an IRQ is
> assigned. However, the state remains active for the port on 3.8.3.
>
> The offending commit mentions this is a BIOS bug from InsydeH2O and that
> the port is bogus in that case, but we have something similar here with
> an AMI UEFI implementation (Version: 0406 Release Date: 06/06/2012)
> where the port isn't bogus.
>
> I'm not sure exactly what the solution should be here. Any thoughts?
Sean, should I just revert this patch now, and wait for a better fix
later?
thanks,
greg k-h
next prev parent reply other threads:[~2013-04-02 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 15:53 Stable kernel 3.8.4/3.9-rc3 breaks PNP serial port Josh Boyer
2013-04-02 16:23 ` Greg Kroah-Hartman [this message]
2013-04-02 16:34 ` Sean Young
2013-04-02 22:11 ` Sean Young
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=20130402162336.GB318@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sean@mess.org \
--cc=tkil@scrye.com \
/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