Xen dom0 support in Lucid

Hi -
    I'm interested in seeing Xen dom0 support re-introduced for Lucid.
My understanding was that such support was dropped in Intrepid due to
the difficulty of forward-porting the 2.6.18 patches. Of course, since
then Jeremy Fitzhardinge's patches for a Xen dom0 using paravirt_ops
have been made available, so it seems plausible that such support
could be maintained without as much hard forward-porting work. I would
expect such support to exist as a custom flavor (not integrated into
the core -generic or -server kernels), as it did in Hardy, and I would
be more than fine with seeing it live in universe.

Before I spend too much time seeing exactly how much work it would be
to pull together and maintain such a patchset for Ubuntu, is this
something that the kernel team would be willing to allow? On the
Ubuntu side, what would be the expectations for work done by people
outside the kernel team (both up front and ongoing) in order for this
to be viable?

Thanks,
 - Evan

kernel lockup on resume

Hi,

Suspend to RAM has never worked on my laptop (suspend to disk works)
and I would really like to help fix this issue.

When I try to resume, I always get a black screen and the kernel seems
to be locked up: caps-lock key has no effect, ctrl+alt+del and sysrq
keys not working.
I have to keep the power button pressed to shut down the machine.

According to this page: http://en.opensuse.org/S2ram

"If none of the methods described here seem to work, it is important
to check if the machine is completely dead on resume or only the video
is not resumed properly. A good way to check this is to start with a
minimal system (init=/bin/bash), run s2ram -f, and after resume, when
the display is still off, check if the "Caps Lock" key still works
(you should see a reaction of the Caps Lock LED on the keyboard). If
it does, it is most likely really a video initialization problem. If
it doesn't, then it is most likely a BIOS problem or a bug in the
Linux kernel."

I did this and since the caps lock key is not working, I'm assuming
it's a BIOS or kernel problem. (I did try the different s2ram options
too a while ago, but nothing worked).

I then tried to use pm_trace as described here:
https://wiki.ubuntu.com/DebuggingKernelSuspend

I attached the resulting dmesg.txt to this e-mail.

32bit PAE v.s. non-PAE performance

Gleaned from a discussion on LKML entitled 'Ubuntu 32-bit, 32-bit PAE,
64-bit Kernel Benchmarks'

http://www.phoronix.com/scan.php?page=article&item=ubuntu_32_pae&num=1

It appears that the performance impact of PAE is not as great as was
originally feared (given a normal workload).

rtg
--

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

Re: 32bit PAE v.s. non-PAE performance

On Sun, Jan 3, 2010 at 9:42 AM, Tim Gardner <tim.gardner <at> canonical.com> wrote:
> Gleaned from a discussion on LKML entitled 'Ubuntu 32-bit, 32-bit PAE,
> 64-bit Kernel Benchmarks'
>
> http://www.phoronix.com/scan.php?page=article&item=ubuntu_32_pae&num=1
>
> It appears that the performance impact of PAE is not as great as was
> originally feared (given a normal workload).
>
> rtg
> --
> Tim Gardner tim.gardner <at> canonical.com
>
> --
> kernel-team mailing list
> kernel-team <at> lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/kernel-team
>

I performed some testing a few years ago comparing 32bit PAE vs
non-PAE kernels.  Performance was within 10% or less using micro
benchmarks(lmbench, tiotest, etc).  The real benefit to the PAE Kernel
was seen running database benchmarks such as DB2 or TPCC(Comparing PAE
to non-PAE - excluding 64bit).  For example Oracle can address up to
62GB of memory versus 1.7GB.  So any applications that will benefit
from the ability to address addition memory will have a tremendous
performance boots versus non-PAE kernels.

Thanks,

Recommended Bug List from the QA Team

Hi All,

Here's the updated bug list for the week [1].  I've added 10 new bugs to
the list which includes 1 regression-potential bug.  The current
regression stats are as follows:

29 regression-potential bugs (up 6)
15 regression-update bugs (down 1)
91 regression-release bugs (up 2)
1 regression-proposed bug (no change)

The Carried Forward section is currently at 177 bugs (up 10) and the In
Progress section is at 105 bugs (down 1).  Of the 12 bugs added last
time, the stats are as follows:

2 In Progress
1 Incomplete
9 Triaged

Thanks,
Leann

[1] http://qa.ubuntu.com/reports/ogasawara/kernel-buglist.html

Re: Xen dom0 support in Lucid

Evan Broder wrote:
> Hi -
>     I'm interested in seeing Xen dom0 support re-introduced for Lucid.
> My understanding was that such support was dropped in Intrepid due to
> the difficulty of forward-porting the 2.6.18 patches. Of course, since
> then Jeremy Fitzhardinge's patches for a Xen dom0 using paravirt_ops
> have been made available, so it seems plausible that such support
> could be maintained without as much hard forward-porting work. I would
> expect such support to exist as a custom flavor (not integrated into
> the core -generic or -server kernels), as it did in Hardy, and I would
> be more than fine with seeing it live in universe.
> 
> Before I spend too much time seeing exactly how much work it would be
> to pull together and maintain such a patchset for Ubuntu, is this
> something that the kernel team would be willing to allow? On the
> Ubuntu side, what would be the expectations for work done by people
> outside the kernel team (both up front and ongoing) in order for this
> to be viable?
> 
> Thanks,
>  - Evan
> 

My experiences with Xen dom0 have not been positive. The Hardy xen
flavour is quite difficult to maintain, so we stopped doing custom
binaries (essentially a patch set applied at build time on top of core
sources). I do not foresee us resurrecting dom0 within the standard
kernel package until it is supported upstream.

rtg

Re: V2 - Karmic LBM request pull

Daniel Chen wrote:
> On Wed, Dec 23, 2009 at 12:28 PM, Tim Gardner <timg <at> tpi.com> wrote:
>>      UBUNTU: Update to ALSA 1.0.22
> ...
>>  .../alsa-driver/alsa-kernel/pci/hda/hda_codec.c    |  674 ++-
> ...
>>  .../alsa-driver/alsa-kernel/pci/hda/hda_local.h    |   79 +-
> ...
>>  .../alsa-driver/alsa-kernel/pci/hda/patch_analog.c |  115 +-
> ...
>>  .../alsa-driver/alsa-kernel/pci/hda/patch_cirrus.c |   39 +-
>>  .../alsa-driver/alsa-kernel/pci/hda/patch_cmedia.c |   18 +-
> ...
>>  .../alsa-kernel/pci/hda/patch_realtek.c            |  578 +-
> ...
>>  .../alsa-driver/alsa-kernel/pci/hda/patch_via.c    |  345 +-
> 
> alsa-driver 1.0.22 is broken for the above HDA codecs: it contains a
> commit that incorrectly maps NID entries and results in hda_codec.c
> bailing and never completing mixer setup. Sound is therefore
> busticated.
> 
> Backporting the following commit is necessary:
> http://git.kernel.org/?p=linux/kernel/git/tiwai/sound-2.6.git;a=commitdiff_plain;h=21949f00a022e090a7e8bc9a01dfca88273c6146
> (ALSA: hda - Fix NID association for capture mixers)
> 
> -Dan
> 

Nothing in the recently released 1.0.22.1 changelog indicates these

Re: V2 - Karmic LBM request pull

On Mon, Jan 4, 2010 at 9:09 AM, Tim Gardner <tim.gardner <at> canonical.com> wrote:
> Nothing in the recently released 1.0.22.1 changelog indicates these
> problems have been addressed, correct?

1.0.22.1 contains the fix
(http://www.alsa-project.org/main/index.php/Changes_v1.0.22_v1.0.22.1#HDA_Codec_driver).

Thanks,
-Dan

Upcoming Ubuntu Kernel Team Meeting - Tuesday, 5th of January - 17:00 (UTC)

The next Ubuntu Kernel Team Meeting is scheduled for Tuesday, January 5th, 17:00
UTC in #ubuntu-meeting on Freenode.

If there are any discussion points or items for decision that you would like to
add to the agenda [1], add an item to it and begin preparations to present a
short introduction to the topic on #ubuntu-meeting during the scheduled session.
Outstanding Action Items from last week are included in the agenda.

[1]: https://wiki.ubuntu.com/KernelTeam/Meeting

As usual, anyone interested in the development of Ubuntu Kernel is welcome to
attend.

--

-- 
Brad Figg brad.figg <at> canonical.com http://www.canonical.com

V3 - Karmic LBM request pull

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

The following changes since commit 76d59ad9f2377674f3422456c1dc0f7c4099f1bc:
  Tim Gardner (1):
        UBUNTU: Minor documentation update

are available in the git repository at:

  git://kernel.ubuntu.com/rtg/ubuntu-karmic-lbm.git master

Tim Gardner (3):
      UBUNTU: compat-wireless: update to 2.6.32.2
      UBUNTU: Update to ALSA 1.0.22
      UBUNTU: Update ALSA to 1.0.22.1

 updates/BOM                                        |    4 +-
 updates/alsa-driver/HEAD                           |   10 -
 updates/alsa-driver/Makefile                       |   73 +-
 updates/alsa-driver/Makefile.conf.in               |    1 +
 updates/alsa-driver/acinclude.m4                   |  269 +-
 updates/alsa-driver/aclocal.m4                     |    4 +-
 updates/alsa-driver/acore/Makefile                 |    5 +-
 updates/alsa-driver/acore/control.patch            |   10 +-
 updates/alsa-driver/acore/hrtimer.patch            |    8 +-
 updates/alsa-driver/acore/memalloc.patch           |   24 +-
 updates/alsa-driver/acore/pcm.patch                |   12 +-
 updates/alsa-driver/acore/pcm_memory.c             |    3 -