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-next>] [day] [month] [year] [list]
Date:	Thu, 25 Jul 2013 18:32:57 -0400
From:	Ilia Mirkin <imirkin@...m.mit.edu>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: 3.11-rc2: panic in __rdmsr_on_cpu

Hi,

I just built a 3.11-rc2 kernel (+ a few patches, but nothing
arch-related), and I saw the following: http://i.imgur.com/dCTqOyR.jpg

The rough transcription is

Call Trace:
<IRQ>
generic_smp_call_fucntion_single_interrupt
smp_call_function_single_interrupt
call_function_single_interrupt
<EOI>
? default_idle
? default_idle
arch_cpu_idle
cpu_startup_entry
rest_init
start_kernel
? repair_env_string
x86_64_start_reservations
x86_64_start_kernel
Code: ... cc 81 8b 0f <0f> 32 48 c1 e2 20 89 c0 ...
RIP: __rdmsr_on_cpu+0x2e/0x44
Kernel panic - not syncing: Fatal exception in interrupt

A 3.10-rc7 kernel booted just fine. Is this likely a real issue? Or
perhaps a mis-build of some sort?

Thanks for any advice,

  -ilia
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ