4.8.16 only reports a single core in /proc/cpuinfo
Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Debian, RHEL, Solaris, various others and LFS
Posts: 19
Rep:
4.8.16 only reports a single core in /proc/cpuinfo
Not sure if this is a kernel config issue during my build but I am only
seeing a single core in my processor and there should be two :
# cat version
Linux version 4.8.16_genunix_201701076203645 (root@vesta) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Sat Jan 7 21:23:47 EST 2017
root@vesta:/proc#
Distribution: Debian, RHEL, Solaris, various others and LFS
Posts: 19
Original Poster
Rep:
Not sure how helpful this is :
$ uname -a
Linux vesta 4.8.16_genunix_201701076203645 #1 SMP Sat Jan 7 21:23:47 EST 2017 x86_64 GNU/Linux
dclarke@vesta:~$ dmesg|grep SMP
[ 0.000000] Linux version 4.8.16_genunix_201701076203645 (root@vesta) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Sat Jan 7 21:23:47 EST 2017
[ 0.000000] found SMP MP-table at [mem 0x000fe1b0-0x000fe1bf] mapped at [ffff8800000fe1b0]
[ 0.000000] Using ACPI (MADT) for SMP configuration information
[ 15.608500] Freeing SMP alternatives memory: 32K (ffffffff82560000 - ffffffff82568000)
Also, is there some way to enforce a fixed width font in these forums?
also the kmemcheck really does catch bad things early :
Code:
[ 15.922948] kmemcheck: Limiting number of CPUs to 1.
[ 15.923536] kmemcheck: Initialized
[ 16.840319] NMI watchdog: enabled on all CPUs, permanently consumes one hw-PMU counter.
[ 16.841856] x86: Booted up 1 node, 1 CPUs
[ 16.842363] smpboot: Total of 1 processors activated (3291.74 BogoMIPS)
[ 16.897732] WARNING: kmemcheck: Caught 8-bit read from freed memory (ffff880184ed0008)
[ 16.897824] e01ced840188ffffffffffff00000000ffffffffffffffffa89c0a83ffffffff
[ 16.899098] i i i i i i i i f f f f f f f f f f f f f f f f f f f f f f f f
[ 16.900364] ^
[ 16.900418] RIP: 0010:[<ffffffff81290939>] [<ffffffff81290939>] copy_mount_options+0x119/0x2c0
[ 16.902502] RSP: 0018:ffff880184ecfde0 EFLAGS: 00010202
[ 16.902559] RAX: ffffffffffffffff RBX: ffff880184ed0008 RCX: ffff88018464dbff
[ 16.902615] RDX: 0000000000000000 RSI: 0000000000000e2e RDI: 0000000000000000
[ 16.902671] RBP: ffff880184ecfde8 R08: ffff880184db91d2 R09: 0000000000001000
[ 16.902727] R10: 0000000000000000 R11: ffff880184db9000 R12: ffff880185806180
[ 16.902784] R13: ffff880185806190 R14: ffff880184ecfe36 R15: 0000000000008000
[ 16.902841] FS: 0000000000000000(0000) GS:ffff880186200000(0000) knlGS:0000000000000000
[ 16.902907] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 16.902961] CR2: ffff88018582837c CR3: 0000000002006000 CR4: 00000000000006f0
[ 16.903017] [<ffffffff81292491>] SyS_mount+0x81/0x110
[ 16.903110] [<ffffffff816cc087>] devtmpfsd+0x77/0x210
[ 16.903201] [<ffffffff81099828>] kthread+0x138/0x170
[ 16.903292] [<ffffffff819508bf>] ret_from_fork+0x1f/0x40
[ 16.903383] [<ffffffffffffffff>] 0xffffffffffffffff
[ 16.904233] devtmpfs: initialized
so the trick is to remove kmemcheck and maybe go with kasan
This option enables tracing of dynamically allocated kernel memory to see if memory is used before it has been given an initial value. Be aware that this requires half of your memory for bookkeeping(!!) and will insert extra code at every read and write to tracked memory thus slow down the kernel code (but user code is unaffected).
The kernel may be started with kmemcheck=0 or kmemcheck=1 to disable or enable kmemcheck at boot-time. If the kernel is started with kmemcheck=0, the large memory and CPU overhead is not incurred.
Yes, these tools can save your butt when you are debugging a kernel module, but they're not meant for production use.
Last edited by sundialsvcs; 01-17-2017 at 09:54 AM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.