linux-kernel - Re: Unable to boot after "ACPI: Don't let acpi

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]

Message-ID: <AANLkTinrRP_GYZiFRv_WzLnS_XGc9f0n-4V9GfZ-WVBQ@mail.gmail.com>
Date:	Sun, 6 Jun 2010 20:33:49 -0700
From:	Venkatesh Pallipadi <venki@...gle.com>
To:	Tom Gundersen <teg@...m.no>
Cc:	Shaohua Li <shaohua.li@...el.com>, Len Brown <lenb@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Pavel Machek <pavel@....cz>,
	Chen Gong <gong.chen@...ux.intel.com>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: Unable to boot after "ACPI: Don't let acpi_pad needlessly mark 
	TSC unstable"

On Sun, Jun 6, 2010 at 6:00 PM, Tom Gundersen <teg@...m.no> wrote:
> Hi Venkatesh,
>
> It looks like your commit 0dc698b93f3eecdda43b22232131324eb41e510c
> causes init to segfault on one of my computers.
>

Hi Tom,

Hmm... Do you have the actual message you see on fault?
Does the problem happen at the boot time?

> Reverting 0dc698b9 on top of 2.6.35-rc2 solves the problem.
>
> Let me know if you would like more details or if I can help with testing.

If you can provide some addittional info above and 'dmesg'  from no
error case (with this revert) and put them all in a bug at
bugzilla.kernel.org under ACPI, it will be great.

Thanks,
Venki
--
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/