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  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:	Thu, 06 Mar 2014 14:08:41 -0500
From:	Peter Hurley <>
To:	Peter Senna Tschudin <>
CC:	Bjorn Helgaas <>,
	"" <>,,
	"" <>,
	Stoney Wang <>,
	Yinghai Lu <>,
	Suresh Siddha <>,
	Joerg Roedel <>,
	Jiang Liu <>,
	Linux PM list <>,
	Pavel Machek <>,
	"Rafael J. Wysocki" <>
Subject: Re: My Kernel bug is celebrating 2 years. Can you help me fix it?

On 03/06/2014 01:27 PM, Bjorn Helgaas wrote:
> [+cc Stoney, Yinghai, Suresh, Joerg, Jiang, Pavel, Rafael, linux-pm]
> Let's add some folks who know about x2apic and VT-d.  It's hard for
> people to magically pick stuff out of the LKML firehose :)
> On Tue, Mar 4, 2014 at 2:26 PM, Peter Senna Tschudin
> <> wrote:
>> I have reported a bug more than two years ago and it is still
>> affecting me. The bug report gives some information:
>> I have tried basic debug instructions from:
>> And everything works as expected when:
>> # echo freeze > /sys/power/state
>> # echo disk > /sys/power/state
>> I have asked for help for fixing it:
>> But I don't have a serial port. How can I debug this issue without a
>> "real" serial port? Or what else can I try? How can I explore the hint
>> about the problem only happening with VT-d enabled in BIOS? How can I
>> explore the hint about the problem not happening if the option
>> nox2apic is passed to the Kernel?
>> Thank you,
>> Peter
>> P.S Yes, it works on Windows.

Windows 7 doesn't use x2apic mode.
Windows 8 does and this same problem happened with this model: see

Seems like your model was recently added to Toshiba's Windows 8
compatibility list:

Check for a more recent BIOS update that may fix this problem.

Peter Hurley

PS - kernel bugs are better filed on the kernel bugzilla
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists