Archive for the ‘ubuntu-kernel’ Category

Andy Whitcroft

[precise] linux kernel-ti-omap 3.2.0-1410.13 uploaded (ABI bump)

We have uploaded a new Precise linux-ti-omap4 kernel. The most notable changes
are as follows:

* rebased on master branch 3.2.0-19.31

The full changelog can be seen at:

https://launchpad.net/ubuntu/+source/linux-ti-omap4/3.2.0-1410.13

 

Andy Whitcroft

[precise] linux kernel-ti-omap 3.2.0-1408.11 uploaded (ABI bump)

We have uploaded a new Precise linux-ti-omap4 kernel. The most notable changes
are as follows:

* rebased on master branch 3.2.0-18.29
* a number of CVE fixes

The full changelog can be seen at:

https://launchpad.net/ubuntu/+source/linux-ti-omap4/3.2.0-1408.11

Andy Whitcroft

[Precise] linux kernel 3.2.0-6.12 uploaded (ABI Bump)

We have uploaded a new Precise linux kernel. Please note the ABI bump.
The most notable changes are as follows:

  * rebase to mainline v3.2-rc6

The full changelog can be seen at:

https://launchpad.net/ubuntu/+source/linux/3.2.0-6.12
Andy Whitcroft

[Precise] linux kernel 3.2.0-1403.3 uploaded (ABI Bump)

We have uploaded a new Precise linux-ti-omap4 kernel. Please note the ABI bump.
The most notable changes are as follows:

  * rebased to Ubuntu-3.2.0-4.10

The full changelog can be seen at:

https://launchpad.net/ubuntu/+source/linux-ti-omap4/3.2.0-1403.3

 

Andy Whitcroft

[Precise] linux-ti-omap4 kernel 3.2.0-1402.2 uploaded

We have uploaded a new Precise linux ti-omap4 kernel. The most notable
changes are as follows:

  * rebase to latest master release Ubuntu-3.2.0-3.9
  * temporary work around for hangs on reboot

The full changelog can be found at:

https://launchpad.net/ubuntu/+source/linux-ti-omap4/3.2.0-1402.2

 

Andy Whitcroft

[Precise] linux-ti-omap4 kernel 3.2.0-1401.1 uploaded

We have uploaded a new Precise linux ti-omap4 kernel. The most notable
changes are as follows:

* update to a 3.2.0 mainline base

The full changelog can be found at:

https://launchpad.net/ubuntu/+source/linux-ti-omap4/3.2.0-1401.1

Jeremy Foshee

First Kernel Triage Summit

On Saturday September 11th the Kernel Team will take the first in what I hope to be a series of steps toward educating ourselves and our community in the triage of the thousands of bugs that pass our way daily.


My goal for this event is to begin the process of training those interested in helping with kernel bugs in the way we process our bug tickets. This first event is meant to help us both educate and document. The information on the first ever Triage Summit is located on the wiki here.


As with everything we do, your feedback is appreciated. Please don’t hesitate to send us e-mail to the team list at kernel-team@lists.ubuntu.com or even on the wiki page itself. Your feedback will go a long way toward our plans for future events like this.


The schedule for Saturday is as follows:


1) at 1400 UTC we will hold a General session centered around providing information as to where to locate us, who our upstreams are and where to find them as well as the new subsystem breakdown of bugs to help us gather related issues more easily and get them in front of the right people.


2) at 1500 UTC there will be a session on Graphics and all of its related bits and bytes. There will be a focus on basic, effective triage for this subset as well as locations to find troubleshooting information and further reading on Graphics issues


3) at 1600 UTC there will be a session on audio bugs and the related subsystem parts involved there. This session will also have a basic troubleshooting and location portion so as to guide those interested in triaging audio bugs with further information.


4) at 1700 UTC we will have something of a lightning round in which we briefly discuss the USB/Firewire and Bluetooth stacks as well as helpful debugging and triage steps for this subset of bugs


As stated before, your feedback on these sessions as well as the documentation that will be provided will be most helpful to us. You are also welcome to approach us for other avenues of support. We are always looking for more help on a variety of kernel related areas such as documentation, bugs and spelling/grammar applications :-) so please don’t hesitate to ask how you can help.


I look forward to seeing a great many of you at the Summit on Saturday!


~JFo
Brad Figg

Meeting Minutes

IRC Log of the meeting.

Agenda

2010-06-04 Meeting Agenda

Outstanding actions from last meeting

None this week.

Lucid Release Status: Bugs

Beta 2 Milestoned Bugs Release Targeted Bugs
linux 6 29
linux-fsl-imx51 0 0
linux-ec2 0 0
linux-mvl-dove 0 0

Blueprints: kernel-lucid-bug-handling

All work items done or postponed, only remaining tasks are for release.

Blueprints: kerne-lucid-kernel-config-review

Over-active beep in VT is under investigation. We expect to write up the configuration report in time for Beta-2.

Blueprints: kernel-lucid-kms

We have ongoing issues with Lid detection, currently we have LVDS lid detection reverted and we are looking at the fallout from that change.

Blueprints: kernel-lucid-suspend-resume

apport — allow us to detect frequency of failure:POSTPONED all other work items done

Blueprints: kernel-lucid-apparmor-development

Still looking for the root cause of Bug #552225, Bug #544764, Bug #549428, Bug #458299

  • Launchpad bug 552225 in apparmor “system bogs down when apparmor is running” [Undecided,New] https://launchpad.net/bugs/552225
  • Launchpad bug 544764 in apparmor “unkillable apparmor_parser” [Undecided,New] https://launchpad.net/bugs/544764
  • Launchpad bug 549428 in apparmor “Triggers permanent high i/o load after upgrade” [Undecided,Incomplete] https://launchpad.net/bugs/549428
  • Launchpad bug 458299 in linux “apparmor_parser: page allocation failure. order:5″ [High,Fix released] https://launchpad.net/bugs/458299

Not positive, but very likely one root cause. It is always replacement related, under high memory pressure/fragmented memory where fast path allocation fails and we fall back to vmalloc for the dfa. It seems to be very much related to the use of swap as I have reports that turning off swap makes it go away and in the end may be a bug in the mm and not apparmor. Also verified that the policy compiler is building isomorphs on multi-policy load and not suffering from a bug, and looked at ways to fix this for M so that we can use multi-profile load and have automated policy verification.

We haven’t been using multi-policy load because we have known that it is generating alternate dfas, and haven’t been able to verify them. I found a few more problems with what I was trying to kick out last week so it got delayed into this week, I have been working through, the checks to send out this morning I expect a few more audit changes will be required yet, and the path generation is some what dependent upon the __d_path patch discussion that I am also rekicking out patches for

Other Release Tasks: Lucid Audio Support

More arsenal work. Wrapping up the survey this week.

Other Release Tasks: Lucid Better Power Mgt

Nothing new this week.

Other Release Tasks: EC2 Lucid Kernel Status

We have Bug #532553, which is just a config oversight as far I can tell

  • Launchpad bug 532553 in linux-ec2 “linux-image-2.6.32-302-ec2 is missing iptables module xt_recent” [Low,Confirmed] https://launchpad.net/bugs/532553

The only question being whether we want to turn it on this late. I (apw) would think anything netfilter related is handy to ahve in that environment, and we have a window to respin for release for somethign which only adds a module which is very low risk. Okay, I’ll send a patch out this morning

Status: Lucid

Beta-2 kernels are in an built. We are not expecting to change the kernel before beta-2. We are expecting some change still before release. Otherwise the worst issues are graphics related to my mind, and mostly getting resolved. Doubt they will all get resolved before release however. We are expecting to be getting a stable update too.

Security & Bugfix Kernels

Hardy 2.6.24-27.68 (security) *
  2.6.24-27.69 (proposed) [ 6] 1/ 3 verifications done (+1)
Intrepid 2.6.27-17.46 (security)
Jaunty 2.6.28-18.60 (security)
Karmic 2.6.31-19.58 (security) *
 
&lbsp; 2.6.31-19.59 (proposed) [ 6] 2/19 verifications done (+2)
LBM 2.6.31-20.22 (updates) *
&lbsp; 2.6.31-20.23 (proposed) [ 6] 0/ 2 verifications done
mvl-dove 2.6.31-211.26 (security) *
&lbsp; 2.6.31-213.27 (proposed) [ 6]
fsl-imx51 2.6.31-108.25 (security) *
&lbsp; 2.6.31-110.26 (proposed) [ 6] 0/ 1 verifications done
1/ 1 failed! #507416
ec2 2.6.31-304.13 (security) *
&lbsp; 2.6.31-110.26 (proposed) [ 6]

Nothing new this week.

Incoming Bugs: Regressions

Current regression stats (broken down by release):

regression-potential (up 130)

  • 223 lucid bugs

regression-update (down 1)

  • 11 karmic bugs
  • 5 jaunty bugs
  • 2 intrepid bugs
  • 1 hardy bug

regression-release (down 1)

  • 52 karmic bugs
  • 21 jaunty bugs
  • 11 intrepid bugs
  • 4 hardy bugs

regression-proposed (no change)

  • 1 karmic bug

Incoming Bugs: Bug day report

The next Kernel Team ‘regression-’ bug day is Wednesday, April 7. Thanks for working on these last week.

Open Discussion or Questions

Just FYI — I (kamalm) am working on the “volume keys never release” issue — seems to be a common problem for various laptop models (bug 550979, bug 420473, bug 374884).
The problem can be fixed in ‘udev’ by adding bits to /lib/udev/… scripts — I plan to produce a patched ‘udev’ package for those bug submitters to test.

  • Launchpad bug 550979 in linux “Volume increase & decrease by function buttons never release on Dell Studio 1558″ [Medium,Confirmed] https://launchpad.net/bugs/550979
  • Launchpad bug 420473 in linux “Coolbox QBook 270-02: volume keys produce more than one key event” [Medium,Incomplete] https://launchpad.net/bugs/420473
  • Launchpad bug 374884 in linux “Keyboard quirk is required for Mitac 8050QDA Fn Volume keys to function.” [Undecided,New] https://launchpad.net/bugs/374884
Brad Figg

Meeting Minutes

IRC Log of the meeting.

Agenda

2010-23-03 Meeting Agenda

Outstanding actions from last meeting

  • JFo to send out regression bug day announcements on monday
    e-mail went out last week for the schedule to all bug lists that normal bug days go to

  • JFo to do a wiki page on regression bug days
    In progress, carried forward to next week.
    Wiki page for the Bug Day is located here: https://wiki.ubuntu.com/KernelTeam/KernelBugDay.

Lucid Release Status: Bugs

Beta 2 Milestoned Bugs Release Targeted Bugs
linux 13 32
linux-fsl-imx51 0 0
linux-ec2 1 1
linux-mvl-dove 1 2

Blueprints: kernel-lucid-bug-handling

Only outstanding item for beta 2 still open: [leannogasawara] apport — sub-system directed reporting [amber]:INPROGRESS all other beta 2 tasks are complete

Blueprints: kerne-lucid-kernel-config-review

PATA and SATA pull out is done and some debian installer fallout sorted out (thanks smb), and the review of the builtin sub-systems complete.

Blueprints: kernel-lucid-kms

I’ve just released a test kernel which addresses the flickering problem with some Intel graphics devices. There are five bugs open against this: http://bit.ly/aiKuuL. Otherwise we are continuing to debug issues as they appear.

Blueprints: kernel-lucid-suspend-resume

Nothing new to report.

Blueprints: kernel-lucid-apparmor-development

Looking at Bug #458299, Bug #529288, Bug #544764, Bug #549428, which all seem to be inter-related or even possibly symptoms of the same bug

  • Launchpad bug 458299 in linux “apparmor_parser: page allocation failure. order:5″ [High,Confirmed] https://launchpad.net/bugs/458299
  • Launchpad bug 549428 in apparmor “Triggers permanent high i/o load after upgrade” [Undecided,New] https://launchpad.net/bugs/549428
  • apparmor “unkillable apparmor_parser” [Undecided,New] https://launchpad.net/bugs/544764
  • linux “”Kernel Oops” – unable to handle kernel paging request at ffff880323279bf2 RIP is at aa_dfa_match_len+0xd9/0xf0″ [Low,Incomplete] https://launchpad.net/bugs/529288

Blueprints: kernel-lucid-boot-performance

Looks like the remaining ureadahead work will get postponed to Lucid+1 as the userspace bits are not likely to make Lucid. That likely will close off the blueprint.

Other Release Tasks: Lucid Audio Support

Did a bunch of arsenal work, blasted several hundred alsa-driver bugs with automated comments.

Other Release Tasks: Lucid Better Power Mgt

Pushed a new set of packages out and a CFT (call for testing). No news since.

Other Release Tasks: EC2 Lucid Kernel Status

Did lots of testing for Bug #540378, Bug #527208, haven’t been able to trip either so we are looking good for EC2.

  • Launchpad bug 540378 in linux-ec2 “BUG: soft lockup – CPU#1 stuck for 66s! [swapper:0]” [Medium,New] https://launchpad.net/bugs/540378
  • Launchpad bug 527208 in linux-ec2 “ec2 instance fails boot, no console output on c1.xlarge” [High,Confirmed] https://launchpad.net/bugs/527208

Status: Lucid

Lucid is at stable 2.6.32.10+drm33.1. We are prepping to the Beta-2 freeze on Thursday, and expect to upload kernels for that early Wednesday. Anything we need in should be up for review _today_.

Security & Bugfix Kernels

Hardy 2.6.24-27.68 (security) *
  2.6.24-27.69 (proposed) [ 6] 1/ 3 verifications done (+1)
Intrepid 2.6.27-17.46 (security)
Jaunty 2.6.28-18.60 (security)
Karmic 2.6.31-19.58 (security) *
 
&lbsp; 2.6.31-19.59 (proposed) [ 6] 2/19 verifications done (+2)
LBM 2.6.31-20.22 (updates) *
&lbsp; 2.6.31-20.23 (proposed) [ 6] 0/ 2 verifications done
mvl-dove 2.6.31-211.26 (security) *
&lbsp; 2.6.31-213.27 (proposed) [ 6]
fsl-imx51 2.6.31-108.25 (security) *
&lbsp; 2.6.31-110.26 (proposed) [ 6] 0/ 1 verifications done
1/ 1 failed! #507416
ec2 2.6.31-304.13 (security) *
&lbsp; 2.6.31-110.26 (proposed) [ 6]

Karmic ec2 and mvl-dove have no open bug reports but were rebased to the version of master in proposed. Asked for quick re-test.
Karmic fsl-imx51 needs to set the status right. An update for it has been uploaded today (consisting of previous and new changelog).

Incoming Bugs: Regressions

Current regression stats (broken down by release):

regression-potential (up 130)

  • 166 lucid bugs

regression-update (up 1)

  • 12 karmic bugs
  • 5 jaunty bugs
  • 2 intrepid bugs
  • 1 hardy bug

regression-release (down 1)

  • 53 karmic bugs
  • 21 jaunty bugs
  • 11 intrepid bugs
  • 4 hardy bugs

regression-proposed (no change)

  • 1 karmic bug

Incoming Bugs: Bug day report

Today is another Kernel Team ‘regression-’ bug day. Thanks for working on these last week. The next Kernel Regression Bug Day will be on Thursday of this week.

Open Discussion or Questions

  1. Nothing new this week.
Brad Figg

Kernel Team Meeting Minutes

Meeting Minutes

IRC Log of the meeting.

Agenda

2010-23-03 Meeting Agenda

Outstanding actions from last meeting

  1. JFo to send out regression bug day announcements on monday
    Carried forward to next week.
  2. JFo to do a wiki page on regression bug days
    In progress, carried forward to next week.

Lucid Release Status: Bugs

Beta 1 Milestoned Bugs Release Targeted Bugs
linux 13 30
linux-fsl-imx51 0 0
linux-ec2 1 1
linux-mvl-dove 1 2

Blueprints: kernel-lucid-bug-handling

Nothing new to report.

Blueprints: kerne-lucid-kernel-config-review

Nothing new to report.

Blueprints: kernel-lucid-kms

Testing of the beta has been mostly good so far, there are a couple of “blank screen on install” bugs to look at.

Blueprints: kernel-lucid-suspend-resume

Nothing new to report.

Blueprints: kernel-lucid-apparmor-development

Another lkml push going out today, will also issue pull requests for the bug fixes it includes.
Since beta 1 release have picked up another couple bugs to look at with security team
Bug #544819, Bug #544789, Bug #544764 as well as #529288 which I haven’t been able to
reproduce and currently looks as if it is caused by memory corruption.

  • apparmor “apparmor does not work with midori” [Undecided,New] https://launchpad.net/bugs/544819
  • apparmor “apparmor-logprof not working” [Undecided,New] https://launchpad.net/bugs/544789
  • apparmor “unkillable apparmor_parser” [Undecided,New] https://launchpad.net/bugs/544764
  • linux “”Kernel Oops” – unable to handle kernel paging request at ffff880323279bf2 RIP is at aa_dfa_match_len+0xd9/0xf0″ [Low,Incomplete] https://launchpad.net/bugs/529288

Blueprints: kernel-lucid-boot-performance

Nothing new to report.

Other Release Tasks: Lucid Audio Support

Still working on the bug survey. I’ve moved to working on modifications to arsenal
scripts to do more of the work. I’ve done a bit of refactoring of Bryce’s process-new-bugs.py
script and sent it to him. I’ll take his feedback and appy the changes to our scripts
as well. I’m trying to make it so we don’t fork the scripts quite so much.

Other Release Tasks: Lucid Better Power Mgt

Sent some patches upstream to pm-utils and am waiting on feedback. Will push out a new set of packages when I hear back.

Other Release Tasks: EC2 Lucid Kernel Status

Testing fix for Bug #527208, which also seems to fix Bug #540378

  • linux-ec2 “ec2 instance fails boot, no console output on c1.xlarge” [High,Confirmed] https://launchpad.net/bugs/527208
  • linux-ec2 “BUG: soft lockup – CPU#1 stuck for 66s! [swapper:0]” [Medium,New] https://launchpad.net/bugs/540378

Other than those its looking good.

Status: Lucid

Ok, apw uploaded a kernel including 2.6.32.10 and a newer igb driver. Uploaded meta today so it will probably get offered soonish.
Will gather updates till Friday and then do another upload.

Security & Bugfix Kernels

Dapper 2.6.15-55.83 (security)
Hardy 2.6.24-27.68 (security) *
Intrepid 2.6.27-17.46 (security)
Jaunty 2.6.28-18.60 (security)
Karmic 2.6.31-19.58 (security) *
 
LBM 2.6.31-20.22 (updates) *
mvl-dove 2.6.31-211.26 (security) *
fsl-imx51 2.6.31-108.25 (security) *
ec2 2.6.31-304.13 (security) *

Packages marked with ‘*’ have been uploaded to proposed. Planned acceptance into proposed is tomorrow.

Incoming Bugs: Regressions

Current regression stats (broken down by release):

regression-potential (up 40)

  • 128 lucid bugs

regression-update (up 1)

  • 12 karmic bugs
  • 5 jaunty bugs
  • 2 intrepid bugs
  • 1 hardy bug

regression-release (down 1)

  • 53 karmic bugs
  • 22 jaunty bugs
  • 11 intrepid bugs
  • 4 hardy bugs

regression-proposed (no change)

  • 1 karmic bug

Incoming Bugs: Bug day report

Open Discussion or Questions

  1. A warm welcome from all to Kamal Mostafa, the latest kernel team member.