From: Roberto Oppedisano <roberto.oppedisano@infracom.it>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
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: Sat, 16 Mar 2013 08:10:11 +0100 [thread overview]
Message-ID: <51441AD3.9080700@infracom.it> (raw)
In-Reply-To: <2481455.MbROdCkzQM@vostro.rjw.lan>
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.
Kind regards
R
next prev parent reply other threads:[~2013-03-16 7:10 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 [this message]
2013-03-17 0:59 ` Rafael J. Wysocki
2013-03-17 8:32 ` Roberto Oppedisano
2013-03-17 23:27 ` Rafael J. Wysocki
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=51441AD3.9080700@infracom.it \
--to=roberto.oppedisano@infracom.it \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--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 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.