From: okaya@codeaurora.org
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux PCI <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci-owner@vger.kernel.org
Subject: Re: [GIT PULL] ACPI fixes for v4.7-rc7
Date: Sun, 10 Jul 2016 22:16:03 +0300 [thread overview]
Message-ID: <b8b6998677cec3e26a903c2194181888@codeaurora.org> (raw)
In-Reply-To: <d3bc7758-2f97-474e-bd48-19457bda8b1d@leemhuis.info>
On 2016-07-10 14:00, Thorsten Leemhuis wrote:
> Hi Rafael!
>
> On 08.07.2016 01:43, Rafael J. Wysocki wrote:
>>
>> Please pull from
>>
>> git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
>> acpi-4.7-rc7
>>
>> to receive ACPI fixes for v4.7-rc7 with top-most commit
>> […]
>> All of these fix recent regressions in ACPICA, in the ACPI PCI IRQ
>> management code and in the ACPI AML debugger.
>
> FYI, it seems these changes lead to a new regression. Quoting
> https://bugzilla.kernel.org/show_bug.cgi?id=121701
>
> """
>> Kernel fails to boot with this commit. With the commit reverted,
>> everything is fine. I cannot bisect any further - git is failing with
>> "you are trying to use to much memory"(?!)
>>
>> This is a Dell Precision 5510 with the latest (1.2.10) BIOS applied.
>>
>> Let me know what additional information I can provide."""
> """
Can you attach the boot log to the bugzilla?
Unfortunately, this code turned out to be the most fragile code. I fixed
one issue and it looks like it broke yours.
>
> Cheers, Thorsten
> --
> To unsubscribe from this list: send the line "unsubscribe linux-pci" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-07-10 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 23:43 Rafael J. Wysocki
2016-07-10 11:00 ` Thorsten Leemhuis
2016-07-10 15:50 ` Linus Torvalds
2016-07-10 19:16 ` okaya [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=b8b6998677cec3e26a903c2194181888@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci-owner@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=regressions@leemhuis.info \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®