From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Roberto Oppedisano <roberto.oppedisano@infracom.it>
Cc: LKML <linux-kernel@vger.kernel.org>,
"toshi.kani@hp.com" <toshi.kani@hp.com>,
"isimatu.yasuaki@jp.fujitsu.com" <isimatu.yasuaki@jp.fujitsu.com>,
"yinghai@kernel.org" <yinghai@kernel.org>
Subject: Re: Regression: Fixing recursive fault but reboot is needed at boot on HP 6730B - bisected
Date: Mon, 18 Mar 2013 00:27:03 +0100 [thread overview]
Message-ID: <2925166.8AVI1SWGSM@vostro.rjw.lan> (raw)
In-Reply-To: <51457F9F.7000204@infracom.it>
On Sunday, March 17, 2013 09:32:31 AM Roberto Oppedisano wrote:
> Il 17/03/2013 01:59, Rafael J. Wysocki ha scritto:
> > On Saturday, March 16, 2013 08:10:11 AM Roberto Oppedisano wrote:
> >> Il 15/03/2013 18:13, Rafael J. Wysocki ha scritto:
> >>>> Here's the new suspect:
> >>>>
> >>>> f95988de06ea62ef5bd861f06e9ef56cea405ed1 is the first bad commit
> >>>> commit f95988de06ea62ef5bd861f06e9ef56cea405ed1
> >>>> Author: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >>>> Date: Mon Jan 7 21:17:02 2013 +0100
> >>>>
> >>>> ACPI / scan: Treat power resources in a special way
> >>> In that case, please try to comment out the following two lines:
> >>>
> >>> device_set_wakeup_capable(dev, true);
> >>> acpi_pci_sleep_wake(pci_dev, false);
> >>>
> >>> in pci_acpi_setup() in drivers/pci/pci-acpi.c and see if that improves things
> >>> for you.
> >> Current git still hangs with those two lines commented out.
> > What about commenting out the entire contents of pci_acpi_setup(), then?
>
> Still no luck, still hangs at boot.
>
> > Also, please send the output of acpidump from the affected machine.
>
> You can find acpidump and dmesg at:
>
> http://62.196.71.254/kernel/acpidump.gz
> http://62.196.71.254/kernel/dmesg.txt.gz
>
> I noticed that booting with serial console enabled succeeds also with
> failing kernels;
> I've to do more testing to see if it's a 100% success ratio.
>
> dmesg is relative to vanilla current git kernel, booted without docking
> station and with serial
> console enabled. Inside it you can find some acpi related error; I don't
> know if they're relevant.
Thanks for the files.
Please try to boot with initcall_debug in the kernel command line and see
if that works around the problem and if not, whether or not it provides a
clue about the point where boot is stuck (and if that point is always the
same).
Thanks,
Rafael
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
next prev parent reply other threads:[~2013-03-17 23:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-11 8:00 Regression: Fixing recursive fault but reboot is needed at boot on HP 6730B Roberto Oppedisano
2013-03-14 8:20 ` Regression: Fixing recursive fault but reboot is needed at boot on HP 6730B - bisected Roberto Oppedisano
2013-03-14 14:37 ` Toshi Kani
2013-03-15 9:46 ` Roberto Oppedisano
2013-03-14 17:27 ` Rafael J. Wysocki
2013-03-15 9:42 ` Roberto Oppedisano
2013-03-15 13:10 ` Roberto Oppedisano
2013-03-15 17:13 ` Rafael J. Wysocki
2013-03-16 7:10 ` Roberto Oppedisano
2013-03-17 0:59 ` Rafael J. Wysocki
2013-03-17 8:32 ` Roberto Oppedisano
2013-03-17 23:27 ` Rafael J. Wysocki [this message]
2013-03-18 8:02 ` Roberto Oppedisano
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=2925166.8AVI1SWGSM@vostro.rjw.lan \
--to=rjw@sisk.pl \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roberto.oppedisano@infracom.it \
--cc=toshi.kani@hp.com \
--cc=yinghai@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
Powered by JetHome