Kernel/1.6 Planning: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(Created page with "=1.6 Kernel Team Bugs= ==1.6 Bug Status by Milestone== {{#bugzilla: |group=milestone |bar=status |status=* |to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield...")
 
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
=1.6 Planning=
==Next Actions==
[x] Agree on terms by September 13 (everyone on To/Cc here needs to sign off, see below)
[ ] Saul to prepare MUT patch to set PREFERRED_PROVIDER to linux-yocto-dev (pending linux-yocto-dev as default kernel, needed for poky and meta-intel)
[x] Bruce to work with Saul to prepare mechanism for generating this patch (PREFERRED_PROVIDE and SRCREV updates for all layers - poky, yocto-bsp, meta-intel)
[x] Addressed backlog
[x] Darren: Open bugs for kernel team commitments for 1.6 (kernel test image, linux-yocto-dev srcrevs, etc)
* Expect large numbers of kernel related bugs in M2
[ ] Bruce: Open bug for linux-yocto-dev M1 (oe-core/yocto-bsps)
[x] All: Size your bugs after this call (just Darren is a slacker)
[ ] Darren: Get more of his urgent work into BZ
[x] Nitin: Open bug for M1 to move meta-intel BSPs to linux-yocto-dev
[ ] Darren: Talk to dave about any LTSI testing commitments
[x] Nitin: Communicate linux-yocto-dev process to ISG (part of larger meta-intel process documentation effort)
==1.6 Priorities==
* Automation and QA Testing
* Meta-Data cleanup
* BSP Hardware Refresh
* BSP Updates
* To linux-yocto-dev by M1
* Deployment
* BSP Variant
* BSP Consolidation
* Continue Poky Tiny
* Minnow2
==1.6 Commitments==
The 3.10 merge caused more churn and surprise breakage than was
considered acceptable 2 days prior to the feature freeze. Despite being
fixed very quickly, this disrupted a number of projects and we need to
mitigate this. We have committed to the following for the 1.6 development cycle.
* The MUT branch will be built using linux-yocto-dev on a regular basis on the Autobuilder starting as soon as possible into the development cycle of 1.6. This alone would have caught all the issues we encountered this time with ample time to resolve the issues prior to feature freeze. To ensure determinism, it is preferable to use fixed SRCREVs on the Autobuilder MUT builds over AUTOREV. Bruce and Saul need to iron out a workable mechanism to autogenerate a patch which sets a known good set of SRCREVs for the subsequent MUT build.
* The kernel team will create a core-image-kerneldev image for their regular development and testing which includes all known kernel-dependent packages, such as lttng-modules and hello-mod. More packages will be added as they are determined to be highly sensitive to kernel version.
* Two weeks prior to the feature freeze date, the kernel team will send a Kernel Status Report detailing the current state of linux-yocto-dev, including the most likely kernel version (98% confidence) based on the known inputs and enumerate any unknowns. The report will include a list of known issues from the MUT builds which will reduce the surprise and scramble following the merge. The issue list is expected to be minimal given the prior runs in MUT. Factors influencing the final linux-yocto kernel version include the base kernel version for PREEMPT_RT, LTSI, stable, etc. which are beyond our control. Depending on the priorities for the release, any of these may impact the final kernel version decision. Should new or late arriving information necessitate a change to the kernel version, it will be raised with the CCB and re will need to weigh the risk (which will be much less with the MUT builds) and possible schedule slippage with the benefits (such as aligning with LTSI or PREEMPT_RT). Note that we cannot always meet all requirements of schedule and external tree support and at each release we must choose between them.
=== linux-yocto-dev ===
* Cannot parse AUTOREV out of the box
* linux-yocto-dev recipe has anon python to prevent AUTOREV unless linux-yocto-dev is the preferred provider
* linux-yocto-dev will use fixed SRCREV recipe-kernel/linux/linux-yocto-dev-revisions.inc if it exists in the layer root, which will override AUTOREV when linux-yocto-dev is the PREFERRED_PROVIDER
* meta-intel CANNOT specifiy linux-yocto-dev as the PREFERRED_PROVIDER (unless we have that file, which we shouldn't as we want people to build with AUTOREV when they select PREFERRED_PROVIDER).
* meta-intel developers should specify PREFERRED_PROVIDER
=1.6 Kernel Team Bugs=
=1.6 Kernel Team Bugs=
==1.6 Bug Status by Milestone==
==1.6 Bug Status by Milestone==
Line 170: Line 228:
   |to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
   |to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
   |milestone=1.6
   |milestone=1.6
  |columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
  |sort=id
  |total=summary,estimated
  |noresultsmessage="No matching bugs found."
}}
===Previous Backlog (!1.6,!Future)===
{{#bugzilla:
  |group=to
  |status=!(RESOLVED,VERIFIED,CLOSED)
  |to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
  |milestone=!(1.6,1.6 M1, 1.6 M2, 1.6 M3, 1.6 M4, 1.6 M5, 1.6 M6, 1.6, Future)
  |columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
  |sort=id
  |total=summary,estimated
  |noresultsmessage="No matching bugs found."
}}
===Meta-Intel Backlog (!Future)===
{{#bugzilla:
  |group=to
  |status=!(RESOLVED,VERIFIED,CLOSED)
  |component=bsps-meta-intel
  |milestone=!(Future)
   |columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
   |columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
   |sort=id
   |sort=id
Line 181: Line 263:
   |status=!(RESOLVED,VERIFIED,CLOSED)
   |status=!(RESOLVED,VERIFIED,CLOSED)
   |to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
   |to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
   |milestone=!(1.6,1.6 M1, 1.6 M2, 1.6 M3, 1.6 M4, 1.6 M5, 1.6 M6, 1.6)
   |milestone=!(1.6,1.6 M1, 1.6 M2, 1.6 M3, 1.6 M4, 1.6 M5, 1.6 M6, 1.6, Future)
   |columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
   |columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
   |sort=id
   |sort=id
Line 188: Line 270:
}}
}}


===Meta-Intel Backlog===
===Future===
{{#bugzilla:
{{#bugzilla:
   |group=to
   |group=to
   |status=!(RESOLVED,VERIFIED,CLOSED)
   |status=!(RESOLVED,VERIFIED,CLOSED)
   |component=bsps-meta-intel
   |to=dvhart@linux.intel.com,tom.zanussi@intel.com,bruce.ashfield@windriver.com,nitin.a.kamble@intel.com
  |milestone=Future
   |columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
   |columns=id,summary,severity,priority,milestone,to,status,whiteboard,estimated
   |sort=id
   |sort=id

Latest revision as of 16:48, 22 January 2014

1.6 Planning

Next Actions

[x] Agree on terms by September 13 (everyone on To/Cc here needs to sign off, see below)

[ ] Saul to prepare MUT patch to set PREFERRED_PROVIDER to linux-yocto-dev (pending linux-yocto-dev as default kernel, needed for poky and meta-intel)

[x] Bruce to work with Saul to prepare mechanism for generating this patch (PREFERRED_PROVIDE and SRCREV updates for all layers - poky, yocto-bsp, meta-intel)

[x] Addressed backlog

[x] Darren: Open bugs for kernel team commitments for 1.6 (kernel test image, linux-yocto-dev srcrevs, etc)

  • Expect large numbers of kernel related bugs in M2

[ ] Bruce: Open bug for linux-yocto-dev M1 (oe-core/yocto-bsps)

[x] All: Size your bugs after this call (just Darren is a slacker)

[ ] Darren: Get more of his urgent work into BZ

[x] Nitin: Open bug for M1 to move meta-intel BSPs to linux-yocto-dev

[ ] Darren: Talk to dave about any LTSI testing commitments

[x] Nitin: Communicate linux-yocto-dev process to ISG (part of larger meta-intel process documentation effort)

1.6 Priorities

  • Automation and QA Testing
  • Meta-Data cleanup
  • BSP Hardware Refresh
  • BSP Updates
  • To linux-yocto-dev by M1
  • Deployment
  • BSP Variant
  • BSP Consolidation
  • Continue Poky Tiny
  • Minnow2

1.6 Commitments

The 3.10 merge caused more churn and surprise breakage than was considered acceptable 2 days prior to the feature freeze. Despite being fixed very quickly, this disrupted a number of projects and we need to mitigate this. We have committed to the following for the 1.6 development cycle.

  • The MUT branch will be built using linux-yocto-dev on a regular basis on the Autobuilder starting as soon as possible into the development cycle of 1.6. This alone would have caught all the issues we encountered this time with ample time to resolve the issues prior to feature freeze. To ensure determinism, it is preferable to use fixed SRCREVs on the Autobuilder MUT builds over AUTOREV. Bruce and Saul need to iron out a workable mechanism to autogenerate a patch which sets a known good set of SRCREVs for the subsequent MUT build.
  • The kernel team will create a core-image-kerneldev image for their regular development and testing which includes all known kernel-dependent packages, such as lttng-modules and hello-mod. More packages will be added as they are determined to be highly sensitive to kernel version.
  • Two weeks prior to the feature freeze date, the kernel team will send a Kernel Status Report detailing the current state of linux-yocto-dev, including the most likely kernel version (98% confidence) based on the known inputs and enumerate any unknowns. The report will include a list of known issues from the MUT builds which will reduce the surprise and scramble following the merge. The issue list is expected to be minimal given the prior runs in MUT. Factors influencing the final linux-yocto kernel version include the base kernel version for PREEMPT_RT, LTSI, stable, etc. which are beyond our control. Depending on the priorities for the release, any of these may impact the final kernel version decision. Should new or late arriving information necessitate a change to the kernel version, it will be raised with the CCB and re will need to weigh the risk (which will be much less with the MUT builds) and possible schedule slippage with the benefits (such as aligning with LTSI or PREEMPT_RT). Note that we cannot always meet all requirements of schedule and external tree support and at each release we must choose between them.

linux-yocto-dev

  • Cannot parse AUTOREV out of the box
  • linux-yocto-dev recipe has anon python to prevent AUTOREV unless linux-yocto-dev is the preferred provider
  • linux-yocto-dev will use fixed SRCREV recipe-kernel/linux/linux-yocto-dev-revisions.inc if it exists in the layer root, which will override AUTOREV when linux-yocto-dev is the PREFERRED_PROVIDER
  • meta-intel CANNOT specifiy linux-yocto-dev as the PREFERRED_PROVIDER (unless we have that file, which we shouldn't as we want people to build with AUTOREV when they select PREFERRED_PROVIDER).
  • meta-intel developers should specify PREFERRED_PROVIDER


1.6 Kernel Team Bugs

1.6 Bug Status by Milestone

1.6 
RESOLVED (16)
 
17
1.6 M1 
RESOLVED (2)
2
1.6 M2 
VERIFIED (2)
2
1.6 M3 
RESOLVED (3)
VERIFIED (1)
4
1.6 M4 
RESOLVED
VERIFIED (4)
5
1.6 M5 
RESOLVED (4)
4
total34

1.6 Open Bug Priority by Milestone

no bugzilla tickets were found

1.6 Weekly Activity

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0      0

1.6 Resolved Bugs

IDSummary (26 tasks) ⇒SeverityPMilestoneAssigneeStatusWhiteboardE
 0      0
Darren Hart
4337[SYS940X] S3 issue when booting the installed yocto on sd cardnormalMedium1.6Darren HartRESOLVED
5645[FRI2] Reboot hangsnormalLow1.6Darren HartRESOLVED
5668[Autobuilder] nightly-intel-gpl failure due to grub-efi-native recipe renamenormalMedium1.6Darren HartRESOLVED
5685Cannot extend linux-yocto-custom with FILES_${PN}majorMedium1.6Darren HartRESOLVED
6082do_package fails if no modules are builtnormalUndecided1.6 M5Darren HartRESOLVED
 5      0
Nitin Kamble
2465add/enable more jasperforest drivers (NTB and Crystal Beach 3 DMA/DCA drivers)enhancementMedium1.6Nitin KambleRESOLVED5
3885define site macros for x32 in the x32-linux site config fileenhancementMedium1.6Nitin KambleRESOLVED3
3946[NUC] dmesg MUX INFO call failed errornormalMedium1.6Nitin KambleRESOLVED2
4515EMGD and X version information should not be in the machine confignormalMedium1.6Nitin KambleRESOLVED3
4529x32 build fails with gmp_5.1.1 do_configurenormalMedium1.6Nitin KambleRESOLVED3
5297Support 2013Q3 Intel Graphics Stack Release in Yocto ProjectenhancementMedium1.6Nitin KambleRESOLVED
5497move all the meta-intel BSPs to linux-yocto-dev kernelnormalMedium1.6 M1Nitin KambleRESOLVED3
5568meta-intel: lms7_7.1.20.bb tarball no longer existsnormalMedium1.6 M1Nitin KambleRESOLVED
5699emenlow-noemgd build failed with kernel 3.8normalMedium1.6 M3Nitin KambleRESOLVED
5764QA Issue: libva: configure was passed unrecognised optionsnormalMedium1.6 M4Nitin KambleRESOLVED
5903x32 build fails at lttng do_packagenormalMedium1.6 M5Nitin KambleRESOLVED
6123parameters are silently getting disabled in the common kernel configurationmajorUndecided1.6Nitin KambleRESOLVED
6171Crownbay: hda-codec: No codec parser is availablenormalMedium1.6Nitin KambleRESOLVED
6347video - play (ogg) not working on NUCnormalMedium1.6Nitin KambleRESOLVED
 14      19
Tom Zanussi
2364crownbay: bad_page_state with BLDK2 bootnormalMedium1.6Tom ZanussiRESOLVED3
4441ftrace event triggersnormalUndecided1.6Tom ZanussiRESOLVED20
5476[yocto-bsp] find_bblayers fails with Python error if bitbake_env_cmd failsnormalMedium1.6Tom ZanussiRESOLVED
5486Update kernel lab to 1.5 (dora)enhancementLow1.6 M3Tom ZanussiRESOLVED
5495yocto-bsp 1.6 upgrade and automation enhancementsenhancementMedium1.6 M5Tom ZanussiRESOLVED11 April 2014: Documentation flag set to "Done."10
5835wic doesn't abort when it can't find mcopynormalMedium1.6 M3Tom ZanussiRESOLVED
6122Crosstap does not work on QemuPPCnormalMedium1.6 M5Tom ZanussiRESOLVED
 7      33

1.6 Targeted Bugs

1.6 M1

Completed Bugs

IDSummary (2 tasks) ⇒SeverityPMilestoneAssigneeStatusWhiteboardE
 0      0
Nitin Kamble
5497move all the meta-intel BSPs to linux-yocto-dev kernelnormalMedium1.6 M1Nitin KambleRESOLVED3
5568meta-intel: lms7_7.1.20.bb tarball no longer existsnormalMedium1.6 M1Nitin KambleRESOLVED
 2      3

Scheduled Bugs

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0      0

1.6 M2

Completed Bugs

IDSummary (2 tasks) ⇒SeverityPMilestoneAssigneeStatusWhiteboardE
 0      0
Tom Zanussi
5630perf test shows multiple errors and fails on qemux86normalMedium1.6 M2Tom ZanussiVERIFIED
5636No IP address for eth0 on qemu at the first bootnormalMedium+1.6 M2Tom ZanussiVERIFIED
 2      0

Scheduled Bugs

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0      0

1.6 M3

Completed Bugs

IDSummary (4 tasks) ⇒SeverityPMilestoneAssigneeStatusWhiteboardE
 0      0
Darren Hart
5779Parse error at minnow.confnormalHigh1.6 M3Darren HartVERIFIED
 1      0
Nitin Kamble
5699emenlow-noemgd build failed with kernel 3.8normalMedium1.6 M3Nitin KambleRESOLVED
 1      0
Tom Zanussi
5486Update kernel lab to 1.5 (dora)enhancementLow1.6 M3Tom ZanussiRESOLVED
5835wic doesn't abort when it can't find mcopynormalMedium1.6 M3Tom ZanussiRESOLVED
 2      0

Scheduled Bugs

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0      0

1.6 M4

Completed Bugs

IDSummary (5 tasks) ⇒SeverityPMilestoneAssigneeStatusWhiteboardE
 0      0
Darren Hart
1635Add gummiboot as a grub-efi alternative (was Drop Grub for Syslinux/Gummiboot)enhancementMedium+1.6 M4Darren HartVERIFIED(Test Case Completed) Development5
4082Replace grub-efi with gummibootenhancementMedium+1.6 M4Darren HartVERIFIED2
5456Consolidate meta-intel BSPs where possibleenhancementMedium+1.6 M4Darren HartVERIFIED10 April 2014: Setting documentation flag to "Done."5
 3      12
Nitin Kamble
5764QA Issue: libva: configure was passed unrecognised optionsnormalMedium1.6 M4Nitin KambleRESOLVED
 1      0
Tom Zanussi
5753wic rootfs creation use wrong file ownernormalMedium+1.6 M4Tom ZanussiVERIFIED
 1      0

Scheduled Bugs

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0      0

1.6 M5

Completed Bugs

IDSummary (4 tasks) ⇒SeverityPMilestoneAssigneeStatusWhiteboardE
 0      0
Darren Hart
6082do_package fails if no modules are builtnormalUndecided1.6 M5Darren HartRESOLVED
 1      0
Nitin Kamble
5903x32 build fails at lttng do_packagenormalMedium1.6 M5Nitin KambleRESOLVED
 1      0
Tom Zanussi
5495yocto-bsp 1.6 upgrade and automation enhancementsenhancementMedium1.6 M5Tom ZanussiRESOLVED11 April 2014: Documentation flag set to "Done."10
6122Crosstap does not work on QemuPPCnormalMedium1.6 M5Tom ZanussiRESOLVED
 2      10

Scheduled Bugs

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0      0

1.6 Backlog

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0      0

Previous Backlog (!1.6,!Future)

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0      0

Meta-Intel Backlog (!Future)

IDSummary (3 tasks) ⇒SeverityPMilestoneAssigneeStatusWhiteboardE
 0      0
Chee Yang
13548meta-intel do_testimage tasks failednormalMedium5.99Chee YangIN PROGRESS IMPLEMENTATION
 1      0
Unassigned
11816secure boot implementation using systemd-boot bootloaderenhancementMedium+5.99UnassignedNEW4
12755Separate boot config recipes are at odds with setting APPEND at the image levelnormalMedium+5.99UnassignedNEW
 2      4

Previous Backlog

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0      0

Future

IDSummarySeverityPMilestoneAssigneeStatusWhiteboardE
 0      0
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Kernel/1.6_Planning&oldid=11900"