linux-kernel - Re: Regression: Fixing recursive fault but reboot is needed at boot on HP 6730B

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 18 Mar 2013 00:27:03 +0100
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Roberto Oppedisano <roberto.oppedisano@...racom.it>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"toshi.kani@...com" <toshi.kani@...com>,
	"isimatu.yasuaki@...fujitsu.com" <isimatu.yasuaki@...fujitsu.com>,
	"yinghai@...nel.org" <yinghai@...nel.org>
Subject: Re: Regression: Fixing recursive fault but reboot is needed at boot on HP 6730B - bisected

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@...el.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/