Tim Gardner | 1 Dec 2011 03:51
Favicon

APPLIED: [Natty][SRU][PATCH] Kernel Oops : Dentry still in use (1) [unmount of nfs4 0:1d]

On 11/30/2011 12:12 PM, Chris J Arges wrote:
> BugLink:  http://bugs.launchpad.net/bugs/769927
>
> SRU Justification:
>
> Impact:
> If two processes attempt to cause automounting on the same mountpoint at
> the same time, the vfsmount holding the mountpoint will be left with one
> too few references on it, causing a BUG when the kernel tries to clean up.
>
> Fix:
> Fix has been cherry picked from 8aef18845266f5c05904c610088f2d1ed58f6be3t.
> It has been accepted in 3.0 and is present in ubuntu-oneiric.
> It applies cleanly to ubuntu-natty.
>
> Testcase:
> The procedure for replicating this bug is outlined in the patch
> description. Essentially mounting an nfs mount with another mount in it.
> Running a test program, and unmount the submount and original mount.
>
> Patch is attached.
>

--

-- 
Tim Gardner tim.gardner <at> canonical.com

brad.figg | 1 Dec 2011 08:00
Favicon

The Daily Bug Report for Thursday, 01. December 2011 06:37 UTC

The Daily Bug Report
Thursday, 01. December 2011 06:37 UTC

The linux package acquired 4 new bugs in the last 24 hrs.

Bug       Title                                                           Series      Importance      Status          Assignee
-------   ------------------------------------------------------------    --------    ------------   
------------    ---------------------
898112    Xen performance issue: backport acpi-cpufreq.v4 branch to...    precise     Medium          Triaged         Unassigned
898127    system hangs and errors at /build/buildd/linux-3.2.0/arch...    precise     Medium          Confirmed       Unassigned
898283    linux: 2.6.32-37.80 -proposed tracker                           lucid       Medium          In Progress     Unassigned
898347    syslog flooded with "hci_scodata_packet: hci0 SCO packet ...    lucid       Medium          Confirmed       Unassigned

An online version of this report can be found at: http://people.canonical.com/~kernel/reports/1-day-new.html

David Henningsson | 1 Dec 2011 09:52
Favicon

Oneiric SRU (pre-stable): Fix Line out -> Speaker automute for Realtek

SRU Justification:

Fixes a blocks-hwcert bug.

Test case:

Take the Optiplex XE machine specified here:
http://bugs.launchpad.net/bugs/882693

Without this patch:
  - Internal Speaker is not muted when "Line Out" jack is plugged in
With this patch:
  - Internal Speaker is muted when "Line Out" jack is plugged in

Upstream status:
   Acked/reviewed by Takashi Iwai and on its way to 3.0 (and 3.1) stable.

--

-- 
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
SRU Justification:

Fixes a blocks-hwcert bug.

Test case:

Take the Optiplex XE machine specified here:
(Continue reading)

Stefan Bader | 1 Dec 2011 10:45
Favicon

Patch format documentation may need some clarification

This came up today on irc. Basically [1] and [2] talk about the format patches
should be submitted for sru and cves. [1] is much older and maybe needs to be
updated or hidden better.

But generally I can see one issue. But I am not sure whether this is just my
opinion, so I wanted to put it up for discussion.

When talking about the subject line of a patch, this can mean two places:
1. The subject line of the email containing the patch (or the cover letter)
2. The subject line of the actual patch

IMO, there are some things that make sense for 1. but not for 2., like
the target release, tags for sru / cve, or even the cve number (which is
in the body of the patch already). This seems to be even more confusing when the
patch is inlined as the email then has two subject lines (sort of):

Subject: [<releases>] (reason): <summary>

...

--- patch ---
Subject: [PATCH] [UBUNTU: [SAUCE] ...] <patch summary>

That is at least how I think is better because then one just can save the patch
and apply it. While if the patch itself contains the other tags, I would
manually remove them before applying.

In that light [2] sometimes would be confusing to me as it only speaks of patch
and subject. So, is the intention as I wrote it down? Then I would try to update
the wiki page accordingly... Should the older page be removed/updated?
(Continue reading)

Brendan Donegan | 1 Dec 2011 14:20
Favicon

Testing pool for Oneiric SRU

Hi,

As the Oneiric -proposed kernel has become available for testing, we're 
about to commence with it. We're proposing to use our new testing pool 
functionality which you may have heard about to reduce the number of 
systems we need to test while still providing maximum device coverage. 
In a previous mail, Marc showed you the list of components that we've 
proposed as 'important' for the purpose of including at least one of 
each different device of that type in the testing pool. This is the list 
as it stands:

https://docs.google.com/spreadsheet/ccc?key=0AphFraZYTghddElqTHl3NmZsWXVDYkMxcE5zX3EtR0E&hl=en_US#gid=0

and this is the testing pool it created:

https://docs.google.com/spreadsheet/ccc?key=0ApQ2JshzVOLydEtFOWxPZ2h6R3BhcDFDbnV4SHJuT1E

There is a link to the Ubuntu certification page for that system so you 
can have a look at which components it has. This is mainly for 
transparency.

As with Marc's email I would urge you to check the components on the 
first spreadsheet with an X next to them, as these are the ones that 
*are not* considered for the purposes of shrinking the testing pool. 
Marking one of them as important will allow the tool to include at least 
one system that includes each different component of that type and 
potentially *increase* the number of systems in the pool. The goal is to 
cover as much hardware as possible with a reasonably sized testing pool.

Thanks,
(Continue reading)

brad.figg | 1 Dec 2011 14:46
Favicon

The Daily Bug Report for Thursday, 01. December 2011 13:40 UTC

The Daily Bug Report
Thursday, 01. December 2011 13:40 UTC

The linux package acquired 6 new bugs in the last 24 hrs.

Bug       Title                                                           Series      Importance      Status          Assignee
-------   ------------------------------------------------------------    --------    ------------   
------------    ---------------------
898274    Bluetooth adapter is not in lsusb after sleep                   oneiric     Undecided       Confirmed       Unassigned
898283    linux: 2.6.32-37.80 -proposed tracker                           lucid       Medium          In Progress     Unassigned
898347    syslog flooded with "hci_scodata_packet: hci0 SCO packet ...    lucid       Medium          Confirmed       Unassigned
898503    Asus K54HR and K54C does not resume without kernel parame...                High            In Progress     Keng-Y Lin
898523    runing system tst on usb                                        precise     Undecided       Confirmed       Unassigned
898615    [Presario C500] Hibernate command fails and returns to us...    oneiric     Undecided       Confirmed       Unassigned

An online version of this report can be found at: http://people.canonical.com/~kernel/reports/1-day-new.html

The Top 10 Hot List Bugs (based on bug heat)

Bug       Title                                                           Series      Importance      Status          Assignee
-------   ------------------------------------------------------------    --------    ------------   
------------    ---------------------
567334    blocked tasks delay cloud-init for 240 seconds                              Medium          Triaged         Unknown
64587     log says "ata1 is slow to respond, please be patient"                       Medium          Incomplete      Unknown
688703    [lucid] netxen_nic driver and ethernet bonding broken at ...    lucid       Medium          Triaged         Unknown
753071    Include DRM OMAP driver to have proper EDID detection                       High            Incomplete      Leann Ogasawara
793367    ecryptfs corruption during make -j                                          Medium          Fix Committed    Unknown
876996    Ubuntu 11.10 fresh install crashed                              oneiric     High            Triaged         Unknown
891968    Screen turns off when the kernel is loaded                      oneiric     High            Triaged         Unknown
894070    IOMMU error loop early in boot                                  precise     High            Triaged         Unknown
(Continue reading)

Tim Gardner | 1 Dec 2011 14:52
Favicon

ACK: Oneiric SRU (pre-stable): Fix Line out -> Speaker automute for Realtek

On 12/01/2011 01:52 AM, David Henningsson wrote:
> SRU Justification:
>
> Fixes a blocks-hwcert bug.
>
> Test case:
>
> Take the Optiplex XE machine specified here:
> http://bugs.launchpad.net/bugs/882693
>
> Without this patch:
> - Internal Speaker is not muted when "Line Out" jack is plugged in
> With this patch:
> - Internal Speaker is muted when "Line Out" jack is plugged in
>
> Upstream status:
> Acked/reviewed by Takashi Iwai and on its way to 3.0 (and 3.1) stable.
>

Have you also tried this laptop with Precise to make sure the 
"refactored automute for Realtek" still works ?

rtg
--

-- 
Tim Gardner tim.gardner <at> canonical.com

Tim Gardner | 1 Dec 2011 15:13
Favicon

Re: ACK: Oneiric SRU (pre-stable): Fix Line out -> Speaker automute for Realtek

On 12/01/2011 06:52 AM, Tim Gardner wrote:
> On 12/01/2011 01:52 AM, David Henningsson wrote:
>> SRU Justification:
>>
>> Fixes a blocks-hwcert bug.
>>
>> Test case:
>>
>> Take the Optiplex XE machine specified here:
>> http://bugs.launchpad.net/bugs/882693
>>
>> Without this patch:
>> - Internal Speaker is not muted when "Line Out" jack is plugged in
>> With this patch:
>> - Internal Speaker is muted when "Line Out" jack is plugged in
>>
>> Upstream status:
>> Acked/reviewed by Takashi Iwai and on its way to 3.0 (and 3.1) stable.
>>
>
> Have you also tried this laptop with Precise to make sure the
> "refactored automute for Realtek" still works ?
>
> rtg

_And_ have you tested this patch for regressions on other platforms with 
Realtek codecs ?

--

-- 
Tim Gardner tim.gardner <at> canonical.com
(Continue reading)

brad.figg | 1 Dec 2011 15:19
Favicon

The Daily Bug Report for Thursday, 01. December 2011 14:10 UTC

The Daily Bug Report
Thursday, 01. December 2011 14:10 UTC

There were no new bugs found in the last 24 hrs.The linux package acquired 6 new bugs in the last 24 hrs.

Bug       Title                                                           Series      Importance      Status           Assignee
-------   ------------------------------------------------------------    --------    ------------   
-------------    ---------------------
898274    Bluetooth adapter is not in lsusb after sleep                   oneiric     Undecided       Confirmed        Unassigned
898283    linux: 2.6.32-37.80 -proposed tracker                           lucid       Medium          In Progress      Unassigned
898347    syslog flooded with "hci_scodata_packet: hci0 SCO packet ...    lucid       Medium          Confirmed        Unassigned
898503    Asus K54HR and K54C does not resume without kernel parame...                High            In Progress      Keng-Y Lin
898523    runing system tst on usb                                        precise     Undecided       Confirmed        Unassigned
898615    [Presario C500] Hibernate command fails and returns to us...    oneiric     Undecided       Confirmed        Unassigned

An online version of this report can be found at: http://people.canonical.com/~kernel/reports/1-day-new.html

The Top 10 Hot List Bugs (based on bug heat)

Bug       Title                                                           Series      Importance      Status           Heat     Assignee
-------   ------------------------------------------------------------    --------    ------------   
-------------    -----    ---------------------
818830    [Sandy Bridge] serious power regression from kernel 3.0.0...    oneiric     Medium          Triaged          519      Unknown
836250    [Oneiric] [Regression] Intel Corporation Centrino Ultimat...    oneiric     High            Triaged          434      Unknown
843431    Logitech camera microphone does not work / makes "chipmun...    oneiric     Medium          Triaged          406      Unknown
275998    internal mic capture very low volume when routed through ...                Medium          Incomplete       346      Unknown
869502    Kernel-Panic with 3.0.0.12-generic on asus eee pcs and ms...    oneiric     High            Confirmed        326      Unknown
207473    Screen brightness double level changes on Dell laptops                      Low             Confirmed        246      Unknown
790863    Unable to start lxc container after update to 2.6.32-32         lucid       Critical        Confirmed        158      Unknown
892615    3.2.0-1-generic: completely fails to boot on Geode LX           precise     High            Fix Committed    142      Unknown
(Continue reading)

Tim Gardner | 1 Dec 2011 15:23
Favicon

Re: Patch format documentation may need some clarification

On 12/01/2011 02:45 AM, Stefan Bader wrote:
> This came up today on irc. Basically [1] and [2] talk about the format patches
> should be submitted for sru and cves. [1] is much older and maybe needs to be
> updated or hidden better.
>
> But generally I can see one issue. But I am not sure whether this is just my
> opinion, so I wanted to put it up for discussion.
>
> When talking about the subject line of a patch, this can mean two places:
> 1. The subject line of the email containing the patch (or the cover letter)
> 2. The subject line of the actual patch
>
> IMO, there are some things that make sense for 1. but not for 2., like
> the target release, tags for sru / cve, or even the cve number (which is
> in the body of the patch already). This seems to be even more confusing when the
> patch is inlined as the email then has two subject lines (sort of):
>
> Subject: [<releases>] (reason):<summary>
>
> ...
>
> --- patch ---
> Subject: [PATCH] [UBUNTU: [SAUCE] ...]<patch summary>
>
> That is at least how I think is better because then one just can save the patch
> and apply it. While if the patch itself contains the other tags, I would
> manually remove them before applying.
>
> In that light [2] sometimes would be confusing to me as it only speaks of patch
> and subject. So, is the intention as I wrote it down? Then I would try to update
(Continue reading)


Gmane