linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiang Liu <jiang.liu@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>, Hudd <hedede.l@gmail.com>
Cc: Prakash Punnoor <prakash@punnoor.de>,
	rafael.j.wysocki@intel.com, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: ACPI regression with 3.19+
Date: Tue, 03 Mar 2015 09:32:42 +0800	[thread overview]
Message-ID: <54F50F3A.5090508@linux.intel.com> (raw)
In-Reply-To: <2682430.9eTeHiC8BR@vostro.rjw.lan>

On 2015/3/3 6:03, Rafael J. Wysocki wrote:
> On Monday, March 02, 2015 10:07:20 PM Hudd wrote:
>> On Sun, 2015-03-01 at 01:00 +0100, Rafael J. Wysocki wrote:
>>> On Saturday, February 28, 2015 10:35:21 AM Prakash Punnoor wrote:
>>>> This is a multi-part message in MIME format.
>>>> --------------080704070901080904040008
>>>> Content-Type: text/plain; charset=utf-8
>>>> Content-Transfer-Encoding: 7bit
>>>>
>>>> Hallo,
>>>>
>>>> my system won't boot with current GIT kernel (see attached screenshot).
>>>> The system seems somewhat frozen (cannot ssh into it), but magic sysrq
>>>> still works. I bisected the problem to commit
>>>> 593669c2ac0fe18baee04a3cd5539a148aa48574.
>>>
>>> Thanks for reporting, we're working on it.
>>
>> Hello folks,
>>
>> I've tried out 4.0-rc1, and it does not boot  on  my  system.   It  just
>> freezes without any messages (The only message I see is “Loading initial
>> ramdisk” from GRUB).  I bisected the problem down to the same commit  as
>> in this  report.
>>
>> # first bad commit: [593669c2ac0fe18baee04a3cd5539a148aa48574]
>> x86/PCI/ACPI: Use common ACPI resource interfaces to simplify implementation
> 
> So at the moment I'm inclined to revert it.  Clearly, it wasn't thought
> through enough, so my suggestion would be to revert it for 4.0 and try again
> in the next cycle and be more careful this time.
> 
> Gerry, would it cause problems to happen if I reverted this one?
Hi Rafael,
	I will send out a patch today for this issue. On Thomas
Voegtle's system, the issue is caused by that BIOS report incorrect
length for ACPI address space descriptor. For example,
[    0.761553] acpi: address space [80000000-d0716ffe] len 50717000
[    0.767572] ACPI: invalid or unassigned resource mem
[0000000080000000 - 00000000d0716ffe] length [0000000050717000]

BIOS should report length of 0x50716fff instead of 0x50717000.
So seems we need to relax the length check code to workaround
such bios issues.

Will send out a patch for it soon.
Thanks!
Gerry
> 
> 

  reply	other threads:[~2015-03-03  1:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-28  9:35 ACPI regression with 3.19+ Prakash Punnoor
2015-03-01  0:00 ` Rafael J. Wysocki
2015-03-02 19:07   ` Hudd
2015-03-02 22:03     ` Rafael J. Wysocki
2015-03-03  1:32       ` Jiang Liu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-02-28  9:32 Prakash Punnoor

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=54F50F3A.5090508@linux.intel.com \
    --to=jiang.liu@linux.intel.com \
    --cc=hedede.l@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prakash@punnoor.de \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rjw@rjwysocki.net \
    /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;
as well as URLs for NNTP newsgroup(s).