From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754612AbdDDTC2 (ORCPT ); Tue, 4 Apr 2017 15:02:28 -0400 Received: from mail-lf0-f66.google.com ([209.85.215.66]:35331 "EHLO mail-lf0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752518AbdDDTC0 (ORCPT ); Tue, 4 Apr 2017 15:02:26 -0400 MIME-Version: 1.0 From: Tracy Smith Date: Tue, 4 Apr 2017 14:02:24 -0500 Message-ID: Subject: Re: [PATCH 4/8] x86/intel_rct/mba: Add MBA structures and initialize MBA To: Shivappa Vikas Cc: x86@kernel.org, lkml , ravi.v.shankar@intel.com, tony.luck@intel.com, fenghua.yu@intel.com, h.peter.anvin@intel.com, Vikas Shivappa Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Apologies, unrelated to MBA. Resent later with a changed subject line. On Tue, Apr 4, 2017 at 1:50 PM, Shivappa Vikas wrote: > > > > 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 >> > -- Confidentiality notice: This e-mail message, including any attachments, may contain legally privileged and/or confidential information. If you are not the intended recipient(s), please immediately notify the sender and delete this e-mail message.