All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Tyser <ptyser@xes-inc.com>
To: Guenter Roeck <linux@roeck-us.net>, linux-kernel@vger.kernel.org
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	x86@kernel.org, James Ralston <james.d.ralston@intel.com>
Subject: Re: Kernel freeze with v3.13 on Avoton CPUs
Date: Thu, 23 Jan 2014 15:44:05 -0600	[thread overview]
Message-ID: <52E18D25.6070403@xes-inc.com> (raw)
In-Reply-To: <20140123065051.GA1402@roeck-us.net>

On 01/23/2014 12:50 AM, Guenter Roeck wrote:
> Hi folks,
> 
> we are seeing an odd problem with kernel version 3.13 running on Mohan Peak
> with an Avoton 8-core CPU. The kernel boots to the login prompt and then
> freezes silently within a few seconds.
> 
> The problem disappears if we revert patch 8477128fe0 (mfd: lpc_ich: Add support
> for Intel Avoton SoC).
> 
> v3.10.27 runs fine. If we cherry-pick 8477128fe0 on top of 3.10.27 we see
> exactly the same problem.
> 
> Any idea what might be causing this, and/or what we could do to track this down
> further ?

I took a look at the Avoton datasheet, and it looks like its register
layout is close, but not identical to the other ICH chipsets supported
by the lpc_ich driver which could be part of the issue.

Eg the "enable ACPI BAR" bit is in register offset 0x44 of PCI device
31, function 0 on most ICH chipsets, while it's in 0x40 on the Avoton.
So on the Avoton the "enable ACPI BAR" bit isn't being set by the
lpc_ich driver.  If your BIOS didn't set this bit, it could cause
erratic behavior since Linux assumes the ACPI region has been enabled.
The driver is also writing to offset 0x44 which is RO/reserved on the
Avoton.  In theory this should be OK, but clearly isn't "correct".

The same comment applies to the GPIO register in PCI device 31, function
0.  The current lpc_ich driver enables the GPIO region in offset 0x4C
while the Avoton does in 0x48.

I'm not sure if the above explains the specific behavior you saw, but
does indicate that the driver shouldn't be used for the Avoton as-is.

I don't have an Avoton to try and reproduce, but do have access to a Bay
Trail platform which appears to have the same register layout as the
Avoton.  I can give adding it to the lpc_ich driver a shot in the next
week and see if I run into the same issues as you did.

In the short term we could either revert 8477128fe0 or wait a bit until
more investigation is done in hopes that we can fix it.

Peter

  reply	other threads:[~2014-01-23 22:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23  6:50 Kernel freeze with v3.13 on Avoton CPUs Guenter Roeck
2014-01-23 21:44 ` Peter Tyser [this message]
2014-01-23 22:30   ` Guenter Roeck
2014-01-30  5:55   ` Guenter Roeck

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=52E18D25.6070403@xes-inc.com \
    --to=ptyser@xes-inc.com \
    --cc=james.d.ralston@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=sameo@linux.intel.com \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.