[Intel-gfx] Tizen IVI EFI 3.0 graphics failure with FSP/OTM on Bayley Bay
Jesse Barnes
jesse.barnes at intel.com
Mon Oct 28 19:05:27 CET 2013
The "drm_kms_helper" function is mentioned only because the kernel is
switching back to the text console when the panic occurs. It's not
actually the source of the panic.
The graphics driver does have some code for booting without any BIOS
support. But depending on the specific platform configuration, we may
need to add additional support to get things working.
However, I think your platform has other issues here that prevent you
from booting fully.
Jesse
On Tue, 29 Oct 2013 01:58:52 +0800
"Wang, Stephanie" <stephanie.wang at intel.com> wrote:
> Jani and Jesse,
> There are two failures in the log file. One appears to be irq related, the other is related to "drm_kms_helper" which you can find under kernel source drivers\gpu\. That being said, the intention is not to point finger at the graphics driver. As I stated in the original email, the Tizen image (together with the graphics driver) is an efi image which boots with efi BIOS perfectly fine. The failure happens with FSP/OTM boot loader only. FSP+OTM does not support efi. The help I need from the graphics driver team is to identify that 1) Tizen graphics driver does or does not rely on any BIOS efi run time services which OTM does not support, 2) Tizen graphics driver does or does not rely on specific setup from BIOS or OTM other than the graphics resources. The first failure mentioned in the beginning of the email is the main focus on my side of the debug. Given that we booted many Tizen images from Ark OS sever, it is probably not a traditional PCI IRQ issue. There are LPSS devices in the SOC which can run in PCI mode or ACPI mode. In theory, the OS should be able to support both modes, but I don't know if it does. The OS may be built with LPSS set to ACPI mode. Anyway, If any of you could help answering the graphics questions, that will be a big help.
> Thanks
> Stephanie
>
> -----Original Message-----
> From: Barnes, Jesse
> Sent: Monday, October 28, 2013 9:03 AM
> To: Jani Nikula
> Cc: Wang, Stephanie; intel-gfx at lists.freedesktop.org
> Subject: Re: [Intel-gfx] Tizen IVI EFI 3.0 graphics failure with FSP/OTM on Bayley Bay
>
> On Mon, 28 Oct 2013 13:47:03 +0200
> Jani Nikula <jani.nikula at linux.intel.com> wrote:
>
> >
> > FWIW there's nothing in the logs indicating it's a "graphics failure".
> >
> > BR,
> > Jani.
> >
> >
> > On Fri, 25 Oct 2013, "Wang, Stephanie" <stephanie.wang at intel.com> wrote:
> > > [ 4.354140] rtc_cmos 00:00: alarms up to one month, y3k, 242 bytes nvram, hpet irqs
> > > [ 4.366970] i2c /dev entries driver
> > > [ 4.376039] BUG: unable to handle kernel paging request at a4003230
> > > [ 4.387406] IP: [<c04240b5>] __add_pin_to_irq_node+0x15/0x6a
> > > [ 4.398146] *pde = 00000000
> > > [ 4.405714] Oops: 0000 [#1] PREEMPT SMP
> > > [ 4.414434] Modules linked in:
> > > [ 4.422132] CPU: 2 PID: 1 Comm: swapper/0 Tainted: G W 3.11.0-09202013 #8
> > > [ 4.435053] task: f6070000 ti: f606e000 task.ti: f606e000
> > > [ 4.445435] EIP: 0060:[<c04240b5>] EFLAGS: 00010286 CPU: 2
> > > [ 4.455907] EIP is at __add_pin_to_irq_node+0x15/0x6a
> > > [ 4.465892] EAX: a4003230 EBX: 00000000 ECX: 00000000 EDX: ffffffff
> > > [ 4.477230] ESI: f61bf6b8 EDI: 00000012 EBP: f606fcc0 ESP: f606fcb0
> > > [ 4.481880] scsi 2:0:0:0: Direct-Access Kingston DataTraveler G3 PMAP PQ: 0 ANSI: 0 CCS
> > > [ 4.482250] sd 2:0:0:0: Attached scsi generic sg0 type 0
> > > [ 4.482739] sd 2:0:0:0: [sda] 60978816 512-byte logical blocks: (31.2 GB/29.0 GiB)
> > > [ 4.482911] sd 2:0:0:0: [sda] Write Protect is off
> > > [ 4.482915] sd 2:0:0:0: [sda] Mode Sense: 23 00 00 00
> > > [ 4.483087] sd 2:0:0:0: [sda] No Caching mode page present
> > > [ 4.483089] sd 2:0:0:0: [sda] Assuming drive cache: write through
> > > [ 4.484879] sd 2:0:0:0: [sda] No Caching mode page present
> > > [ 4.484881] sd 2:0:0:0: [sda] Assuming drive cache: write through
> > > [ 4.485830] sda: sda1 sda2
> > > [ 4.487128] sd 2:0:0:0: [sda] No Caching mode page present
> > > [ 4.487131] sd 2:0:0:0: [sda] Assuming drive cache: write through
> > > [ 4.487134] sd 2:0:0:0: [sda] Attached SCSI removable disk
> > > [ 4.627721] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
> > > [ 4.638027] CR0: 8005003b CR2: a4003230 CR3: 01130000 CR4: 001007d0
> > > [ 4.649366] Stack:
> > > [ 4.655884] ffffffff ffffffea ffffffff f606fd28 f606fce0 c0424a3c 00000012 00000012
> > > [ 4.669057] f61c80d4 00000012 00000000 00000000 f606fd00 c0425714 f600a908 c113abcc
> > > [ 4.682295] f606fd14 00000012 f606fd28 f606fd10 f606fd18 c042577e 00000012 c042577e
> > > [ 4.695575] Call Trace:
> > > [ 4.702860] [<c0424a3c>] io_apic_setup_irq_pin+0x2d/0x4b
> > > [ 4.713540] [<c0425714>] io_apic_setup_irq_pin_once+0x5d/0x79
> > > [ 4.724722] [<c042577e>] io_apic_set_pci_routing+0x44/0x4b
> > > [ 4.735636] [<c042577e>] ? io_apic_set_pci_routing+0x44/0x4b
> > > [ 4.746793] [<c041f36a>] mp_register_gsi+0xbe/0xc8
> > > [ 4.757014] [<c041f37f>] acpi_register_gsi_ioapic+0xb/0xd
> > > [ 4.767903] [<c041f13f>] acpi_register_gsi+0xc/0x13
> > > [ 4.778145] [<c06b50ed>] acpi_pci_irq_enable+0x10f/0x1d3
> > > [ 4.788842] [<c068db25>] ? pci_enable_resources+0x22/0xd1
> > > [ 4.799620] [<c09c320c>] pcibios_enable_device+0x22/0x25
> > > [ 4.810293] [<c09c320c>] ? pcibios_enable_device+0x22/0x25
> > > [ 4.821133] [<c068a31c>] do_pci_enable_device+0x25/0x3b
> > > [ 4.831697] [<c068a3c2>] pci_enable_device_flags+0x90/0xa3
> > > [ 4.842555] [<c068a3e2>] pci_enable_device+0xd/0xf
> > > [ 4.852582] [<c068a44c>] pcim_enable_device+0x68/0x85
> > > [ 4.862872] [<c08d4dad>] i2c_dw_pci_probe+0x3c/0x2a7
> > > [ 4.873070] [<c068af0a>] ? pci_match_device+0xa1/0xac
> > > [ 4.883340] [<c068b9f8>] pci_device_probe+0x44/0x72
> > > [ 4.893395] [<c0772e29>] really_probe+0xc1/0x22b
> > > [ 4.903139] [<c0b23e61>] ? __mutex_lock_slowpath+0x24c/0x26a
> > > [ 4.914051] [<c07730c7>] driver_probe_device+0x5d/0x69
> > > [ 4.924406] [<c07730c7>] ? driver_probe_device+0x5d/0x69
> > > [ 4.934928] [<c0773116>] __driver_attach+0x43/0x5f
> > > [ 4.944834] [<c0773116>] ? __driver_attach+0x43/0x5f
> > > [ 4.954916] [<c0771a16>] bus_for_each_dev+0x3d/0x5e
> > > [ 4.964863] [<c0772aa4>] driver_attach+0x17/0x1c
> > > [ 4.974513] [<c07730d3>] ? driver_probe_device+0x69/0x69
> > > [ 4.984967] [<c07726fd>] bus_add_driver+0xd0/0x1eb
> > > [ 4.994810] [<c06656fb>] ? kset_find_obj+0x5b/0x63
> > > [ 5.004621] [<c07734d6>] driver_register+0x72/0xdd
> > > [ 5.014429] [<c07734d6>] ? driver_register+0x72/0xdd
> > > [ 5.024409] [<c0773534>] ? driver_register+0xd0/0xdd
> > > [ 5.034330] [<c068bab8>] __pci_register_driver+0x45/0x48
> > > [ 5.044651] [<c10cfe97>] ? dw_i2c_init_driver+0x14/0x14
> > > [ 5.054853] [<c10cfeab>] dw_i2c_driver_init+0x14/0x16
> > > [ 5.064811] [<c0400406>] do_one_initcall+0x29/0x9b
> > > [ 5.074447] [<c109d493>] ? do_early_param+0x6f/0x6f
> > > [ 5.084150] [<c045141c>] ? __wake_up+0x32/0x3b
> > > [ 5.093338] [<c109d978>] ? do_basic_setup+0x69/0x98
> > > [ 5.103026] [<c109d98e>] do_basic_setup+0x7f/0x98
> > > [ 5.112521] [<c109da3e>] kernel_init_freeable+0x97/0x109
> > > [ 5.122672] [<c0b0c5b0>] kernel_init+0x8/0xb4
> > > [ 5.131691] [<c0b26837>] ret_from_kernel_thread+0x1b/0x28
> > > [ 5.141882] [<c0b0c5a8>] ? rest_init+0x70/0x70
> > > [ 5.150982] Code: f0 e8 46 17 0b 00 89 d8 ba 01 00 00 00 e8 6a 41 06 00 5b 5e 5d c3 55 89 e5 57 56 89 c6 53 89 cb 57 8b 7d 08 8b 00 89 55 f0 eb 0f <39> 18 75 05 39 78 04 74 42 8d 70 08 8b 40 08 85 c0 75 ed a1 34
> > > [ 5.176996] EIP: [<c04240b5>] __add_pin_to_irq_node+0x15/0x6a SS:ESP 0068:f606fcb0
> > > [ 5.189901] CR2: 00000000a4003230
> > > [ 5.197976] ---[ end trace 0d8d6036f0c4ca5a ]---
> > > [ 5.207489] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
> > > [ 5.207489]
> > > [ 5.226405] drm_kms_helper: panic occurred, switching back to text consol
>
> Right, what makes you think there's a gfx problem? The oops above looks like something else, maybe ACPI/PCI problem in the platform.
>
> Jesse
More information about the Intel-gfx
mailing list