Bug 2412

Summary:	n450: Support EFI boot
Product:	[Build System, Metadata & Runtime] BSPs	Reporter:	Darren Hart <dvhart>
Component:	bsps-configuration	Assignee:	Darren Hart <dvhart>
Status:	VERIFIED WONTFIX	QA Contact:
Severity:	minor
Priority:	Low	CC:	corneliux.stoicescu, yp.bsp.watcher, yp.watcher
Version:	1.2
Target Milestone:	1.3
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Darren Hart 2012-05-04 00:22:44 UTC

The n450 has a UEFI capable firmware. Booting fails using EFI currently.

Comment 1 Darren Hart 2012-05-25 22:56:13 UTC

This appears to be a possible firmware issue. Either way, it is a larger issue than we'll be able to address for the 1.2 release. Bumping to 1.3.

Comment 2 Darren Hart 2012-07-17 20:18:08 UTC

Moving to 1.3. I will discuss with the board/firmware guys, but it is possible this will not be fixable without a firmware update.

Comment 3 Darren Hart 2012-07-20 23:49:14 UTC

The 3.4 kernel panics as follows even without CONFIG_EFI_VARS enabled.

BUG: unable to handle kernel paging request at 3edb4494
IP: [<f95486fd>] 0xf95486fc
*pde = 00000000 
Oops: 0000 [#1] PREEMPT SMP 
Modules linked in:

Pid: 1, comm: swapper/0 Tainted: G        W    3.4.4-yocto-standard #1 Intel Corpo.
EIP: 0060:[<f95486fd>] EFLAGS: 00010282 CPU: 1
EIP is at 0xf95486fd
EAX: f6897f18 EBX: f80bbf10 ECX: f6897f1c EDX: f6187800
ESI: f6187800 EDI: c1b61264 EBP: f6897eec ESP: f6897ee8
 DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
CR0: 8005003b CR2: 3edb4494 CR3: 01ae3000 CR4: 000007d0
DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000                            
DR6: ffff0ff0 DR7: 00000400                                                        
Process swapper/0 (pid: 1, ti=f6896000 task=f6898000 task.ti=f6896000)             
Stack:                                                                             
 f6897f1c f6897f04 c102ac53 f6897f18 f6187800 f6897f1c c1b61280 f6897f38           
 c155ed4f f61bad40 c198473c f61bad40 00000400 f61bad40 f68536c0 c197f2e5           
 c198473c 00000000 c1a7a1e6 00000000 f6897f50 c1a7a279 c1967a2c c1984737           
Call Trace:                                                                        
 [<c102ac53>] virt_efi_get_next_variable+0x23/0x30                                 
 [<c155ed4f>] register_efivars+0x7f/0x300                                          
 [<c1a7a1e6>] ? dmi_scan_machine+0xc5/0xc5                                         
 [<c1a7a279>] efivars_init+0x93/0xda                                               
 [<c10011f2>] do_one_initcall+0x112/0x160                                          
 [<c1a53823>] kernel_init+0x114/0x1db                                              
 [<c1a531f0>] ? do_early_param+0x7a/0x7a                                           
 [<c1058f25>] ? schedule_tail+0x25/0xa0                                            
 [<c1721ec6>] ? ret_from_fork+0x6/0x1c                                             
 [<c1a5370f>] ? start_kernel+0x303/0x303                                           
 [<c1a5370f>] ? start_kernel+0x303/0x303                                           
 [<c1722476>] kernel_thread_helper+0x6/0x10

Comment 4 Darren Hart 2012-09-25 21:48:20 UTC

The n450 BIOS currently works and I have received no reports of anyone besides me even attempting to boot with EFI. I'm closing as WONTFIX. If this is an issue for you, please reopen.

Comment 5 Stoicescu Cornel 2012-10-10 11:25:28 UTC

Marking as verified as per last comment.