From: Ingo Molnar <mingo@elte.hu>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Gary Hade <garyhade@us.ibm.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
LKML <linux-kernel@vger.kernel.org>,
x86 maintainers <x86@kernel.org>, Len Brown <lenb@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Regression with commit f9cde5f in 2.6.30-gitX
Date: Wed, 24 Jun 2009 17:16:34 +0200 [thread overview]
Message-ID: <20090624151634.GC15037@elte.hu> (raw)
In-Reply-To: <4A423686.8050905@lwfinger.net>
* Larry Finger <Larry.Finger@lwfinger.net> wrote:
> Jaswinder Singh Rajput wrote:
> > On Tue, 2009-06-23 at 20:33 -0500, Larry Finger wrote:
> >> My latest pull from Linus's tree fails to boot. Bisection leads to the
> >> commit entitled "x86/ACPI: Correct maximum allowed _CRS returned
> >> resources and warn if exceeded" with hash
> >> f9cde5ffed17bf74f6bef042d99edb0622f58576. I have been unable to
> >> capture the first error message as it scrolls off the screen, but the
> >> second hits the WARN_ON at drivers/ata/ahci.c:695 in routine
> >> ahci_enable_ahci() because HOST_AHCI_EN is not set.
> >>
> >
> > This patch fixes boot failure on my AMD 64 laptop, can you please test
> > this patch:
> >
> > [PATCH] x86: fix _CRS resources return handling
> >
> > We need to check for info->res_num and only handle for < PCI_BUS_NUM_RESOURCES
> >
> > Also set info->bus->resource[info->res_num] for _CRS resources return handling
> >
> > Fixed boot failure on some machine.
> >
> > Reported-by: Larry Finger <Larry.Finger@lwfinger.net>
> > Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@gmail.com>
> > ---
> > arch/x86/pci/acpi.c | 16 ++++++++++------
> > 1 files changed, 10 insertions(+), 6 deletions(-)
>
> Tested-by: Larry Finger <Larry.Finger@lwfinger.net>
>
> Thanks for the patch. With it, my machine boots with the latest
> 2.6.30-gitX.
Please note the comments from Yinghai and Thomas. The fix does
something weird after injecting unrelated cleanups and the changelog
does not cover that.
Ingo
next prev parent reply other threads:[~2009-06-24 15:16 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-24 1:33 Regression with commit f9cde5f in 2.6.30-gitX Larry Finger
2009-06-24 5:31 ` Larry Finger
2009-06-24 12:16 ` Jaswinder Singh Rajput
2009-06-24 12:22 ` Ingo Molnar
2009-06-24 12:30 ` Jaswinder Singh Rajput
2009-06-24 14:46 ` Gary Hade
2009-06-24 14:21 ` Larry Finger
2009-06-24 15:16 ` Ingo Molnar [this message]
2009-06-24 15:19 ` Thomas Gleixner
2009-06-24 15:42 ` Larry Finger
2009-06-24 15:57 ` Jaswinder Singh Rajput
2009-06-24 16:13 ` Gary Hade
2009-06-24 16:33 ` Jaswinder Singh Rajput
2009-06-24 16:44 ` Jesse Barnes
2009-06-24 17:55 ` Gary Hade
2009-06-24 18:28 ` Jesse Barnes
2009-06-24 18:45 ` Thomas Gleixner
2009-06-24 19:48 ` Gary Hade
2009-06-24 20:05 ` Larry Finger
2009-06-24 21:24 ` Gary Hade
2009-06-24 22:12 ` Gary Hade
2009-06-24 21:32 ` Yinghai Lu
2009-06-24 21:42 ` Larry Finger
2009-06-24 21:44 ` Yinghai Lu
2009-06-24 22:04 ` Larry Finger
2009-06-24 22:11 ` Yinghai Lu
2009-06-24 22:53 ` Yinghai Lu
2009-06-24 23:33 ` Larry Finger
2009-06-24 23:44 ` Linus Torvalds
2009-06-24 19:28 ` Gary Hade
2009-06-24 16:52 ` Larry Finger
2009-06-24 14:51 ` Thomas Gleixner
2009-06-24 15:55 ` Jaswinder Singh Rajput
2009-06-24 16:17 ` Thomas Gleixner
2009-06-24 15:56 ` Gary Hade
2009-06-24 16:15 ` Jaswinder Singh Rajput
2009-06-24 16:33 ` Gary Hade
2009-06-24 16:25 ` Jesse Barnes
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=20090624151634.GC15037@elte.hu \
--to=mingo@elte.hu \
--cc=Larry.Finger@lwfinger.net \
--cc=garyhade@us.ibm.com \
--cc=jaswinder@kernel.org \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox