Re: [coreboot] Inteal Leafhill : Linux SATA driver fails when used with coreboot+grub
Dear Gailu, Am Montag, den 06.03.2017, 00:28 +0530 schrieb Gailu Singh: > I tried to find out the details for following error > > ata1: SATA link down (SStatus 4 SControl 300) > > As per status register description > > SStatus 4 : Phy in offline mode as a result of the interface being disabled > or running in a BIST loopback mode > > Is there any chance that coreboot/grub/Linux is putting SATA in to BIST > loopback mode? > > I am trying to understand who is responsible for SATA Linux status 4 and > possible candidates are > a) coreboot > b) grub > c) Linux Please try the latest Linux kernel version [1] – currently 4.10.1 – to rule out any problems in that regard. Please post the logs from that Linux kernel. Thanks, Paul PS: Please just send plain text messages to mailing lists. [1] https://www.kernel.org/ signature.asc Description: This is a digitally signed message part -- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Inteal Leafhill : Linux SATA driver fails when used with coreboot+grub
Hi, For multiple Intel SOCs I see sata initialization in sata.c file but that seems to be missing for apollolake. Could that be a reason? ./soc/intel/skylake/sata.c ./soc/intel/broadwell/sata.c ./soc/intel/baytrail/sata.c ./soc/intel/braswell/sata.c Thanks On Mon, Mar 6, 2017 at 12:28 AM, Gailu Singh wrote: > Hi Again, > > I tried to find out the details for following error > > ata1: SATA link down (SStatus 4 SControl 300) > > As per status register description > > SStatus 4 : Phy in offline mode as a result of the interface being > disabled or running in a BIST loopback mode > > Is there any chance that coreboot/grub/Linux is putting SATA in to BIST > loopback mode? > > I am trying to understand who is responsible for SATA Linux status 4 and > possible candidates are > a) coreboot > b) grub > c) Linux > > Looking forward to your expert advice > > > Thanks > > On Fri, Mar 3, 2017 at 9:29 PM, Gailu Singh wrote: > >> Hi Experts, >> >> I am trying to boot Linux 4.1 with coreboot and grub but SATA drive fails >> with error "ata1: SATA link down (SStatus 4 SControl 300)". It is >> interesting that GRUB2 can use the SATA drive without issue and able to >> load kernel from SATA disk. >> >> If I use same SATA Drive with Coreboot+UEFI payload then Linux driver >> just works fine and I am able to boot linux. >> >> Any Idea What might be going wrong with Linux Driver. Does it expect >> something from BIOS/Coreboot that is not fulfilled >> >> Linux boot logs: >> - >> Initializing cgroup subsys cpuset >> Initializing cgroup subsys cpu >> Initializing cgroup subsys cpuacct >> Linux version 4.1.21-WR8.0.0.11_standard (vgahlaut@ubuntu) (gcc version >> 5.2.0 (Wind River Linux 5.2.0-8.0-intel-apollolake-i-64) ) #1 SMP >> PREEMPT Mon Feb 6 18:38:46 PST 2017 >> Command line: BOOT_IMAGE=(ahci0,msdos1)/boot/bzImage root=/dev/sda1 >> rootdelay=10 console=ttyS2,115200 >> KERNEL supported cpus: >> Intel GenuineIntel >> AMD AuthenticAMD >> Centaur CentaurHauls >> e820: BIOS-provided physical RAM map: >> BIOS-e820: [mem 0x-0x0fff] type 16 >> BIOS-e820: [mem 0x1000-0x0009] usable >> BIOS-e820: [mem 0x000a-0x000f] reserved >> BIOS-e820: [mem 0x0010-0x0fff] usable >> BIOS-e820: [mem 0x1000-0x12150fff] reserved >> BIOS-e820: [mem 0x12151000-0x7a64] usable >> BIOS-e820: [mem 0x7a65-0x7aff] type 16 >> BIOS-e820: [mem 0x7b00-0x7fff] reserved >> BIOS-e820: [mem 0xd000-0x] reserved >> BIOS-e820: [mem 0x0001-0x00017fff] usable >> NX (Execute Disable) protection: active >> SMBIOS 2.7 present. >> e820: last_pfn = 0x18 max_arch_pfn = 0x4 >> PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC >> e820: last_pfn = 0x7a650 max_arch_pfn = 0x4 >> Scanning 1 areas for low memory corruption >> Using GB pages for direct mapping >> init_memory_mapping: [mem 0x-0x000f] >> init_memory_mapping: [mem 0x17fe0-0x17fff] >> init_memory_mapping: [mem 0x16000-0x17fdf] >> init_memory_mapping: [mem 0x0010-0x0fff] >> init_memory_mapping: [mem 0x12151000-0x7a64] >> init_memory_mapping: [mem 0x1-0x15fff] >> ACPI: Early table checksum verification disabled >> ACPI: RSDP 0x000F 24 (v02 CORE ) >> ACPI: XSDT 0x7A6690E0 5C (v01 CORE COREBOOT CORE >> ) >> ACPI: FACP 0x7A66BA60 00010C (v05 CORE COREBOOT CORE >> 0001) >> ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aEventBlock: >> 32/16 (20150410/tbfadt-623) >> ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aEventBlock: 16, >> using default 32 (20150410/tbfadt-704) >> ACPI: DSDT 0x7A669280 0027D8 (v05 COREv4 COREBOOT 20110725 INTL >> 20160831) >> ACPI: FACS 0x7A669240 40 >> ACPI: FACS 0x7A669240 40 >> ACPI: SSDT 0x7A66BB70 000774 (v02 CORE COREBOOT 002A CORE >> 002A) >> ACPI: MCFG 0x7A66C2F0 3C (v01 CORE COREBOOT CORE >> ) >> ACPI: TCPA 0x7A66C330 32 (v02 CORE COREBOOT CORE >> ) >> ACPI: TPM2 0x7A66C370 34 (v04 CORE COREBOOT CORE >> ) >> ACPI: APIC 0x7A66C3B0 6C (v01 CORE COREBOOT CORE >> ) >> ACPI: HPET 0x7A66C420 38 (v01 CORE COREBOOT CORE >> ) >> Zone ranges: >> DMA [mem 0x1000-0x00ff] >> DMA32[mem 0x0100-0x] >> Normal [mem 0x0001-0x00017fff] >> Movable zone start for each node >> Early memory node ranges >> node 0: [mem 0x1000-0x0009] >> node 0: [mem 0x0010-0x0fff] >> node 0: [mem 0x12151000-0x7a64] >> node 0: [mem 0x0001
Re: [coreboot] Inteal Leafhill : Linux SATA driver fails when used with coreboot+grub
On 03/05/2017 10:58 AM, Gailu Singh wrote: Hi Again, I tried to find out the details for following error ata1: SATA link down (SStatus 4 SControl 300) As per status register description SStatus 4 : Phy in offline mode as a result of the interface being disabled or running in a BIST loopback mode Is there any chance that coreboot/grub/Linux is putting SATA in to BIST loopback mode? I am trying to understand who is responsible for SATA Linux status 4 and possible candidates are a) coreboot b) grub c) Linux You already mentioned coreboot+tianocore worked fine under Linux. I think it is safe to assume the problem is not originating from the kernel. Why don't you check what tianocore does about SATA? I suspect tianocore may be injecting some ACPI tables for SATA controller which kernel picks up. Perhaps you can dump, decompile and compare asl from coreboot+tianocore and coreboot+grub and see what is different? Andrey -- coreboot mailing list: coreboot@coreboot.org https://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Inteal Leafhill : Linux SATA driver fails when used with coreboot+grub
Hi Again, I tried to find out the details for following error ata1: SATA link down (SStatus 4 SControl 300) As per status register description SStatus 4 : Phy in offline mode as a result of the interface being disabled or running in a BIST loopback mode Is there any chance that coreboot/grub/Linux is putting SATA in to BIST loopback mode? I am trying to understand who is responsible for SATA Linux status 4 and possible candidates are a) coreboot b) grub c) Linux Looking forward to your expert advice Thanks On Fri, Mar 3, 2017 at 9:29 PM, Gailu Singh wrote: > Hi Experts, > > I am trying to boot Linux 4.1 with coreboot and grub but SATA drive fails > with error "ata1: SATA link down (SStatus 4 SControl 300)". It is > interesting that GRUB2 can use the SATA drive without issue and able to > load kernel from SATA disk. > > If I use same SATA Drive with Coreboot+UEFI payload then Linux driver just > works fine and I am able to boot linux. > > Any Idea What might be going wrong with Linux Driver. Does it expect > something from BIOS/Coreboot that is not fulfilled > > Linux boot logs: > - > Initializing cgroup subsys cpuset > Initializing cgroup subsys cpu > Initializing cgroup subsys cpuacct > Linux version 4.1.21-WR8.0.0.11_standard (vgahlaut@ubuntu) (gcc version > 5.2.0 (Wind River Linux 5.2.0-8.0-intel-apollolake-i-64) ) #1 SMP PREEMPT > Mon Feb 6 18:38:46 PST 2017 > Command line: BOOT_IMAGE=(ahci0,msdos1)/boot/bzImage root=/dev/sda1 > rootdelay=10 console=ttyS2,115200 > KERNEL supported cpus: > Intel GenuineIntel > AMD AuthenticAMD > Centaur CentaurHauls > e820: BIOS-provided physical RAM map: > BIOS-e820: [mem 0x-0x0fff] type 16 > BIOS-e820: [mem 0x1000-0x0009] usable > BIOS-e820: [mem 0x000a-0x000f] reserved > BIOS-e820: [mem 0x0010-0x0fff] usable > BIOS-e820: [mem 0x1000-0x12150fff] reserved > BIOS-e820: [mem 0x12151000-0x7a64] usable > BIOS-e820: [mem 0x7a65-0x7aff] type 16 > BIOS-e820: [mem 0x7b00-0x7fff] reserved > BIOS-e820: [mem 0xd000-0x] reserved > BIOS-e820: [mem 0x0001-0x00017fff] usable > NX (Execute Disable) protection: active > SMBIOS 2.7 present. > e820: last_pfn = 0x18 max_arch_pfn = 0x4 > PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC > e820: last_pfn = 0x7a650 max_arch_pfn = 0x4 > Scanning 1 areas for low memory corruption > Using GB pages for direct mapping > init_memory_mapping: [mem 0x-0x000f] > init_memory_mapping: [mem 0x17fe0-0x17fff] > init_memory_mapping: [mem 0x16000-0x17fdf] > init_memory_mapping: [mem 0x0010-0x0fff] > init_memory_mapping: [mem 0x12151000-0x7a64] > init_memory_mapping: [mem 0x1-0x15fff] > ACPI: Early table checksum verification disabled > ACPI: RSDP 0x000F 24 (v02 CORE ) > ACPI: XSDT 0x7A6690E0 5C (v01 CORE COREBOOT CORE > ) > ACPI: FACP 0x7A66BA60 00010C (v05 CORE COREBOOT CORE > 0001) > ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aEventBlock: > 32/16 (20150410/tbfadt-623) > ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aEventBlock: 16, using > default 32 (20150410/tbfadt-704) > ACPI: DSDT 0x7A669280 0027D8 (v05 COREv4 COREBOOT 20110725 INTL > 20160831) > ACPI: FACS 0x7A669240 40 > ACPI: FACS 0x7A669240 40 > ACPI: SSDT 0x7A66BB70 000774 (v02 CORE COREBOOT 002A CORE > 002A) > ACPI: MCFG 0x7A66C2F0 3C (v01 CORE COREBOOT CORE > ) > ACPI: TCPA 0x7A66C330 32 (v02 CORE COREBOOT CORE > ) > ACPI: TPM2 0x7A66C370 34 (v04 CORE COREBOOT CORE > ) > ACPI: APIC 0x7A66C3B0 6C (v01 CORE COREBOOT CORE > ) > ACPI: HPET 0x7A66C420 38 (v01 CORE COREBOOT CORE > ) > Zone ranges: > DMA [mem 0x1000-0x00ff] > DMA32[mem 0x0100-0x] > Normal [mem 0x0001-0x00017fff] > Movable zone start for each node > Early memory node ranges > node 0: [mem 0x1000-0x0009] > node 0: [mem 0x0010-0x0fff] > node 0: [mem 0x12151000-0x7a64] > node 0: [mem 0x0001-0x00017fff] > Initmem setup node 0 [mem 0x1000-0x00017fff] > ACPI: PM-Timer IO Port: 0x408 > IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-119 > ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) > ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) > Using ACPI (MADT) for SMP configuration information > ACPI: HPET id: 0x8086a701 base: 0xfed0 > smpboot: Allowing 4 CPUs, 0 ho
[coreboot] Inteal Leafhill : Linux SATA driver fails when used with coreboot+grub
Hi Experts, I am trying to boot Linux 4.1 with coreboot and grub but SATA drive fails with error "ata1: SATA link down (SStatus 4 SControl 300)". It is interesting that GRUB2 can use the SATA drive without issue and able to load kernel from SATA disk. If I use same SATA Drive with Coreboot+UEFI payload then Linux driver just works fine and I am able to boot linux. Any Idea What might be going wrong with Linux Driver. Does it expect something from BIOS/Coreboot that is not fulfilled Linux boot logs: - Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Initializing cgroup subsys cpuacct Linux version 4.1.21-WR8.0.0.11_standard (vgahlaut@ubuntu) (gcc version 5.2.0 (Wind River Linux 5.2.0-8.0-intel-apollolake-i-64) ) #1 SMP PREEMPT Mon Feb 6 18:38:46 PST 2017 Command line: BOOT_IMAGE=(ahci0,msdos1)/boot/bzImage root=/dev/sda1 rootdelay=10 console=ttyS2,115200 KERNEL supported cpus: Intel GenuineIntel AMD AuthenticAMD Centaur CentaurHauls e820: BIOS-provided physical RAM map: BIOS-e820: [mem 0x-0x0fff] type 16 BIOS-e820: [mem 0x1000-0x0009] usable BIOS-e820: [mem 0x000a-0x000f] reserved BIOS-e820: [mem 0x0010-0x0fff] usable BIOS-e820: [mem 0x1000-0x12150fff] reserved BIOS-e820: [mem 0x12151000-0x7a64] usable BIOS-e820: [mem 0x7a65-0x7aff] type 16 BIOS-e820: [mem 0x7b00-0x7fff] reserved BIOS-e820: [mem 0xd000-0x] reserved BIOS-e820: [mem 0x0001-0x00017fff] usable NX (Execute Disable) protection: active SMBIOS 2.7 present. e820: last_pfn = 0x18 max_arch_pfn = 0x4 PAT configuration [0-7]: WB WC UC- UC WB WC UC- UC e820: last_pfn = 0x7a650 max_arch_pfn = 0x4 Scanning 1 areas for low memory corruption Using GB pages for direct mapping init_memory_mapping: [mem 0x-0x000f] init_memory_mapping: [mem 0x17fe0-0x17fff] init_memory_mapping: [mem 0x16000-0x17fdf] init_memory_mapping: [mem 0x0010-0x0fff] init_memory_mapping: [mem 0x12151000-0x7a64] init_memory_mapping: [mem 0x1-0x15fff] ACPI: Early table checksum verification disabled ACPI: RSDP 0x000F 24 (v02 CORE ) ACPI: XSDT 0x7A6690E0 5C (v01 CORE COREBOOT CORE ) ACPI: FACP 0x7A66BA60 00010C (v05 CORE COREBOOT CORE 0001) ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Pm1aEventBlock: 32/16 (20150410/tbfadt-623) ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aEventBlock: 16, using default 32 (20150410/tbfadt-704) ACPI: DSDT 0x7A669280 0027D8 (v05 COREv4 COREBOOT 20110725 INTL 20160831) ACPI: FACS 0x7A669240 40 ACPI: FACS 0x7A669240 40 ACPI: SSDT 0x7A66BB70 000774 (v02 CORE COREBOOT 002A CORE 002A) ACPI: MCFG 0x7A66C2F0 3C (v01 CORE COREBOOT CORE ) ACPI: TCPA 0x7A66C330 32 (v02 CORE COREBOOT CORE ) ACPI: TPM2 0x7A66C370 34 (v04 CORE COREBOOT CORE ) ACPI: APIC 0x7A66C3B0 6C (v01 CORE COREBOOT CORE ) ACPI: HPET 0x7A66C420 38 (v01 CORE COREBOOT CORE ) Zone ranges: DMA [mem 0x1000-0x00ff] DMA32[mem 0x0100-0x] Normal [mem 0x0001-0x00017fff] Movable zone start for each node Early memory node ranges node 0: [mem 0x1000-0x0009] node 0: [mem 0x0010-0x0fff] node 0: [mem 0x12151000-0x7a64] node 0: [mem 0x0001-0x00017fff] Initmem setup node 0 [mem 0x1000-0x00017fff] ACPI: PM-Timer IO Port: 0x408 IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-119 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) Using ACPI (MADT) for SMP configuration information ACPI: HPET id: 0x8086a701 base: 0xfed0 smpboot: Allowing 4 CPUs, 0 hotplug CPUs PM: Registered nosave memory: [mem 0x-0x0fff] PM: Registered nosave memory: [mem 0x000a-0x000f] PM: Registered nosave memory: [mem 0x1000-0x12150fff] PM: Registered nosave memory: [mem 0x7a65-0x7aff] PM: Registered nosave memory: [mem 0x7b00-0x7fff] PM: Registered nosave memory: [mem 0x8000-0xcfff] PM: Registered nosave memory: [mem 0xd000-0x] e820: [mem 0x8000-0xcfff] available for PCI devices clocksource refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns: 1910969940391419 ns setup_percpu: NR_CPUS:4 nr_cpumask_bits:4 nr_cpu_ids:4 nr_node_ids:1 PERCPU: Embedded 32 pages/cpu @88017fc0 s93912 r8192 d28968 u524288 Built 1 zonelists in Zone order, mob
