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>] [day] [month] [year] [list]
Message-ID: <1443291579.9694.6.camel@falcon.homelinux.org>
Date:	Sat, 26 Sep 2015 14:19:39 -0400
From:	Donald Parsons <dparsons@...ghtdsl.net>
To:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Linux 4.3-rc2

Neither linux-4.3-rc1 nor linux-4.3-rc2 boot properly on my Intel
Core 2 E6600---lost one of two cores.   Google search found one
other person reporting linux-4.3-rc1 also booting with only one core.
His Intel CPU was a year or two newer than mine.

linux-4.3-rc1 showed more problems during boot including something
about mtrr and another thing I forgot.   The mtrr and ? are not
showing in -rc2.   I had to photograph early boot to capture boot
change from a normal working kernel.  (My Fedora is 14, gcc 4.5.1).


     (start insert 3 screen photos transcribed)
AMIBIOS
ASUS P5B-Deluxe ACPI BIOS Revision 1238
CPU : Intel Core 2 CPU 6600 @ 2.4GHz
 --
Booting Fedora (4.3.0-rc2) in 5 seconds...
 --
early console in decompress_kernel
 (next 5 lines never appear with 4.2.1 and older kernels)
input_data: 0x000000000181026e
input_len:  0x00000000003c93c3
output:     0x0000000001000000
output_len: 0x0000000000bc7870
run_size:   0x0000000000c72000

Decompressing Linux... Parsing ELF... done.
Booting the kernel.
smpboot: do_boot_cpu failed(-1) to wakeup CPU#1
     (end insert)

but continues to bootup and works with one CPU.

/proc/cpuinfo shows only one of two CPU cores:
siblings	: 1
cpu cores	: 1
(both should be : 2 )

With -rc2, /proc/mtrr is same as a working kernel (-rc1?):
reg00: base=0x0d0000000 ( 3328MB), size=  256MB, count=1: uncachable
reg01: base=0x0e0000000 ( 3584MB), size=  512MB, count=1: uncachable
reg02: base=0x000000000 (    0MB), size= 8192MB, count=1: write-back

How can I fix this?

Thanks,
Don


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