Today's Hug Day will focus on The Kernel! With the recent Beta release of Intrepid Ibex 8.10, it's an ideal time to take a look at kernel bugs. It's important to verify if bugs still exist or have been resolved with the Beta release. Additionally, it's good to be aware of any New bugs being reported against the Beta release. Today we'll be focusing on a subset of these types of bugs.

After you have triaged or fixed a bug put your name in the last column and set the row's background to green by adding lightgreen in the first cell of the column after rowbgcolor=. This will let people know that the bug in that row has been hugged.

5-a-day-ing

During hug days you can also do 5-A-Day for this one you can do the following in order to tag your work on the hug day:

100 New Bugs

If the latest kernel has been tested and the debugging information provided, set the status to Triaged, determine an appropriate Importance, and assign the bug to the ubuntu-kernel-team

Otherwise, instruct the bug reporter what is missing from the report, set the status to Incomplete, and subscribe yourself to the report

A possible stock reply would be:

The 2.6.27-5 Ubuntu kernel was most recently released. It would be great if you could test and verify if this is still an issue with this newest kernel. If the issue still exists, per the kernel team's bug policy, can you please attach the following information. Please be sure to attach each file as a separate attachment.
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log
For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

I'm using 140 apparmor HAT profiles with apache2 and mod_apparmor, when I tried to restart apparmor with apparmor_restart the kernel traced out, the process hanged, I wasnt even able to kill it with kill -9

150 Call for Testing Bugs

When deciding to move to the 2.6.27 kernel for Intrepid, a call for testing the 2.6.27 kernel was posted to every open linux bug. The Status of these bugs were not marked as Incomplete as it would have been a logistical nightmare changing each of those bug's status back to their original state if a decision to not go with the 2.6.27 kernel was made. The kernel team has however decided to use the 2.6.27 kernel for Intrepid. For bugs which have not yet responded to the 2.6.27 call for testing and are currently in a New, Confirmed, or Triaged state, it makes sense to now set them to Incomplete. A recommended stock reply would be:

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

To mark it off the list you should:

Verify the bug indeed has not responded to the 2.6.27 call for testing

i have a Sony VGN S-660 and when i wanted to install ubuntu 8,its hard led stop in working mode and on the screen was an error ata1.00: status: {DRDY} and the installation stoped here and every 2 min the error or warning repeat,

200 Incomplete Bugs

These bugs have been in an Incomplete state for more than 6 weeks and should be closed due to lack of response. A recommended stock reply to use would be:

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks.