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: <CAE9FiQXX7BXKuVHZ9NRCEmeTnPj4zVJL5gf5eSp6b+4e3jN3EA@mail.gmail.com>
Date:	Mon, 13 Feb 2012 08:52:19 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	Don Zickus <dzickus@...hat.com>
Cc:	linux-kernel@...r.kernel.org, mingo@...hat.com, hpa@...or.com,
	torvalds@...ux-foundation.org, kexec@...ts.infradead.org,
	vgoyal@...hat.com, ebiederm@...ssion.com,
	akpm@...ux-foundation.org, tglx@...utronix.de, mingo@...e.hu,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:x86/debug] x86/kdump: No need to disable ioapic/ lapic in
 crash path

On Mon, Feb 13, 2012 at 7:28 AM, Don Zickus <dzickus@...hat.com> wrote:
> On Sat, Feb 11, 2012 at 05:04:15PM -0800, Yinghai Lu wrote:
>> >
>> > v2: removed the disable lapic code too
>>
>> with this commit, kdump is not working anymore on my setups with
>> Nehalem, Westmere, sandbridge.
>> these setup all have VT-d enabled.
>
> Hi Yinghai,
>
> Thanks for the report.  Can you attach the .config you were using and what
> vendor you were using for Nehalem, Westmere and Sandybridge.  I'll try to
> reproduce it in my lab.

Sure, please check attached one

Yinghai

Download attachment "config.2012_02_11" of type "application/octet-stream" (91818 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ