From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755282AbdDDSt5 (ORCPT ); Tue, 4 Apr 2017 14:49:57 -0400 Received: from mga09.intel.com ([134.134.136.24]:14945 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753564AbdDDStz (ORCPT ); Tue, 4 Apr 2017 14:49:55 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,275,1486454400"; d="scan'208";a="1115401479" Date: Tue, 4 Apr 2017 11:50:24 -0700 (PDT) From: Shivappa Vikas X-X-Sender: vikas@vshiva-Udesk To: Tracy Smith cc: x86@kernel.org, vikas.shivappa@intel.com, lkml , ravi.v.shankar@intel.com, tony.luck@intel.com, fenghua.yu@intel.com, h.peter.anvin@intel.com, Vikas Shivappa Subject: Re: [PATCH 4/8] x86/intel_rct/mba: Add MBA structures and initialize MBA In-Reply-To: Message-ID: References: <1491256652-18729-1-git-send-email-vikas.shivappa@linux.intel.com> <1491256652-18729-5-git-send-email-vikas.shivappa@linux.intel.com> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 3 Apr 2017, Tracy Smith wrote: > Hi All, > > No JTAG available and need to understand why Linux 4.8.3 doesn't boot on a > x86_64 corei7-64. Hangs at the typical "Starting kernel" location after > the last message of the U-boot. The bootcmd is given below. Do you see the issue when you apply MBA patches . It seems like you use 4.8 kernel but the mba patches are dependent on : https://marc.info/?l=linux-kernel&m=149125583824700 which is applied on 4.11-rc4. > > See a fault FFS and a message indicating the image didn't load after > failover. > > 1) How can I verify if the kernel image was loaded from uboot > 2) What is this fault? > 3) Has the bootargs or bootcmd changed between 4.1 and 4.8.3? > 4) If the boot cmd/arg has changed, what should the boot cmd/arg be for > 4.8.3 to boot on x86_64 corei7-64? > > Initial RAM disk at linear address 0x20000000, size 11638378 bytes > Kernel command line: "BOOT_IMAGE=/imgx/bzImage LABEL=BOOT root=/dev/ram0 > imgmnt=/media/sda2 imgdir=imgx img=image.rootfs rootdelay=2 slub_debug=F > console=ttyS1,115200 bootcount=1 bootcount_addr=0xa4000 > acpi_enforce_resources=lax pram_size=0x800000 pram_addr=10000000 > pram_loc=ddr crashkernel=128M memmap=0x800000$0x10000000 " > EFI table at 683392c0, mmap 68339300, mmap size 4c0, version 1, descr. size > 0x30 > > Starting kernel ... > > Timer summary in microseconds: > Mark Elapsed Stage > 0 0 reset > 1 1 board_init_r > 105 104 board_init_f > 10,180,048 10,179,943 id=64 > 10,221,985 41,937 id=65 > 10,356,645 134,660 main_loop > 12,366,521 2,009,876 usb_start > 18,747,284 6,380,763 start_kernel > Accumulated time: > 10,162,689 ahci > > On a 4.1.26-yocto-standard #1 SMP it boots with no issues. Basically same > .config used in both cases except for anything deprecated between 4.1 and > 4.8.3. > > root@:~# cat /proc/cmdline > BOOT_IMAGE=/imgy/bzImage LABEL=BOOT root=/dev/ram0 imgmnt=/media/sda2 > imgdir=imgy img=image.rootfs rootdelay=2 slub_debug=F console=ttyS1,115200 > fault=FFS bootcount=3 bootcount_addr=0xa4000 acpi_enforce_resources=lax > pram_size=0x800000 pram_addr=10000000 pram_loc=ddr crashkernel=128M > memmap=0x800000$0x10000000 > root@CLX3001:~# cat /proc/consoles > ttyS1 -W- (EC p a) 4:65 > netcon0 -W- (E ) > > thx, > Tray >