linux-mvl-dove:2.6.32-216.33 -proposed tracker

This update contains CVE patches.

All packages uploaded to https://launchpad.net/~canonical-kernel-team/+archive/ppa

Accepted linux-mvl-dove into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Accepted linux-meta-mvl-dove into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Accepted linux-mvl-dove into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Accepted linux-meta-mvl-dove into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Upgraded both lucid & maverick test systems. Boot tested ok.

Ok, upon further examination and testing "properly", I have found that this updated kernel corrupts screen output on console (see attached photo). The console works fine with the previous kernel.

Tobin - what is the exact version of the previous kernel that works correctly? There are enough changes in this new kernel that I'll likely have to build some bisected kernels in order to narrow things down.

The latest kernel for maverick on dove was 2.6.32-410.27. I would start there, as both Lucid & Maverick share the same kernels and this was the latest for marvel that was in the pool.

Tobin - this may be an incompatibility with your HW. The last working release for you was just prior to a major BSP update from Marvell. This kernel is in use on 2 released Lucid products, so I think we'd have heard if there were any major regressions. I've asked Sean Feole from OEM to test on those platforms.

I have tried 2.6.32-211.27 and 2.6.32-214.30 on the dove SoC board I have. These are the steps I try to reproduce.

1. Download kernel from http://ports.ubuntu.com/pool/main/l/linux-mvl-dove/ and install it.
2. Restart the board with new kernel.
3. Use "Ctrl-Alt-F1" to enable text console.

The console display is fine with these two kernels. Is there anything I can try to reproduce?

Which rev SOC do you have?

Mine are:
X0
ubuntu@dove-x0:~$ cat /proc/cpuinfo
Processor : Marvell PJ4 v7 Processor-wmmx-wco rev 2 (v7l)
BogoMIPS : 399.76
Features : swp half thumb fastmult vfp edsp iwmmxt thumbee
CPU implementer : 0x56
CPU architecture: 7
CPU variant : 0x0
CPU part : 0x581
CPU revision : 2

Hardware : Marvell DB-MV88F6781-BP Development Board
Revision : 0000
Serial : 000000000000000

And A0:
Processor : Marvell PJ4 v7 Processor-wmmx rev 5 (v7l)
BogoMIPS : 399.76
Features : swp half thumb fastmult vfp edsp iwmmxt thumbee
CPU implementer : 0x56
CPU architecture: 7
CPU variant : 0x0
CPU part : 0x581
CPU revision : 5

Hardware : Marvell DB-MV88F6781-BP Development Board
Revision : 0000
Serial : 0000000000000000

This could very well be hardware specific. Also, I was running this in a non-GUI mode only (i.e. boot to text console - no GDM).

Its A0 processor

ubuntu@ubuntu-laptop:~$ cat /proc/cpuinfo
Processor : Marvell PJ4 v7 Processor-wmmx-wco rev 5 (v7l)
BogoMIPS : 399.76
Features : swp half thumb fastmult vfp edsp iwmmxt thumbee
CPU implementer : 0x56
CPU architecture: 7
CPU variant : 0x0
CPU part : 0x581
CPU revision : 5

Hardware : Marvell MV88F6781-RD Avengers MID Board
Revision : 0000
Serial : 0000000000000000

I can not reproduce with gdm disable and -214 kernel..

I'm wondering what else is needed to move this bug along. Among other things, there are 2 high priority CVE fixes in this kernel.

Jamie, i'm working on it and i found the commit that causes the screen corruption: give a bit more time to test it...

Tobin, can you test those two kernels? They should fix the screen corruption problem that you were experiencing.

http://people.canonical.com/~ppisati/linux-image-2.6.32-214-dove_2.6.32-214.30_armel-lucid-lp712610.deb

http://people.canonical.com/~ppisati/linux-image-2.6.32-414-dove_2.6.32-414.30_armel-maverick-lp712610.deb

Paolo, I installed these kernels on both dove X0 (Lucid) and A0 (Maverick), everything looks good now. Thanks.

We got a new upload, clearing verification-failed.

Accepted linux-mvl-dove into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Accepted linux-mvl-dove into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

It's a bit confusing. There is yet another mvl-dove kernel in the pipeline now with a newer version number, but its tracking bug points to bug 734950. Since that one is already overloaded with two other kernels, I propose that we use this one for the current mvl-dove update.

Accepted linux-mvl-dove into lucid-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Accepted linux-mvl-dove into maverick-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

This bug was fixed in the package linux-mvl-dove - 2.6.32-216.33

---------------
linux-mvl-dove (2.6.32-216.33) lucid-proposed; urgency=low

  [ Ubuntu: 2.6.32-31.60 ]

  * Release Tracking Bug
    - LP: #734950
  * SAUCE: Clear new_profile in error path
    - LP: #732700
  * [Config] CONFIG_BOOT_PRINTK_DELAY=y
    - LP: #733191
  * Revert "drm/radeon/bo: add some fallback placements for VRAM only
    objects."
    - LP: #652934
  * drm/radeon: fall back to GTT if bo creation/validation in VRAM fails.
    - LP: #652934
  * drm/radeon/kms: Fix retrying ttm_bo_init() after it failed once.
    - LP: #652934
  * xfs: always use iget in bulkstat
    - LP: #692848
  * drm/radeon/kms: make the mac rv630 quirk generic
    - LP: #728687
  * drm/radeon/kms: add pll debugging output
    - LP: #728687
  * drm/radeon: remove 0x4243 pci id
    - LP: #728687
  * drm/radeon/kms: fix s/r issues with bios scratch regs
    - LP: #728687
  * drm/i915/lvds: Add AOpen i915GMm-HFS to the list of false-positive LVDS
    - LP: #728687
  * drm/i915: Add dependency on CONFIG_TMPFS
    - LP: #728687
  * Linux 2.6.32.29+drm33.14
    - LP: #728687
  * NFSD: memory corruption due to writing beyond the stat array
    - LP: #728687
  * mptfusion: mptctl_release is required in mptctl.c
    - LP: #728687
  * mptfusion: Fix Incorrect return value in mptscsih_dev_reset
    - LP: #728687
  * ocfs2_connection_find() returns pointer to bad structure
    - LP: #728687
  * x25: decrement netdev reference counts on unload
    - LP: #728687
  * x86, hpet: Disable per-cpu hpet timer if ARAT is supported
    - LP: #728687
  * OHCI: work around for nVidia shutdown problem
    - LP: #728687
  * x86/pvclock: Zero last_value on resume
    - LP: #728687
  * av7110: check for negative array offset
    - LP: #728687
  * CRED: Fix get_task_cred() and task_state() to not resurrect dead
    credentials
    - LP: #728687
  * bonding/vlan: Avoid mangled NAs on slaves without VLAN tag insertion
    - LP: #728687
  * CRED: Fix kernel panic upon security_file_alloc() failure.
    - LP: #728687
  * CRED: Fix BUG() upon security_cred_alloc_blank() failure
    - LP: #728687
  * CRED: Fix memory and refcount leaks upon security_prepare_creds()
    failure
    - LP: #728687
  * sendfile(): check f_op.splice_write() rather than f_op.sendpage()
    - LP: #728687
  * isdn: hisax: Replace the bogus access to irq stats
    - LP: #728687
  * ixgbe: add support for 82599 based Express Module X520-P2
    - LP: #728687
  * ixgbe: prevent speculative processing of descriptors before ready
    - LP: #728687
  * scsi_dh_alua: add netapp to dev list
    - LP: #728687
  * scsi_dh_alua: Add IBM Power Virtual SCSI ALUA device to dev list
    - LP: #728687
  * dm raid1: fail writes if errors are not handled and log fails
    - LP: #728687
  * GFS2: Fix bmap allocation corner-case bug
    - LP: #728687
  * dm raid1: fix null pointer dereference in suspend
    - LP: #728687
  * sunrpc/cache: fix module refcnt leak in a failure path
    - LP: #728687
  * be2net: Maintain tx and rx counters in driver
    - LP: #728687
  * tcp: Make TCP_MAXSEG minimum more correct.
    - LP: #728687
  * nfsd: correctly handle return value from ...

This bug was fixed in the package linux-meta-mvl-dove - 2.6.32.216.18

---------------
linux-meta-mvl-dove (2.6.32.216.18) lucid; urgency=low

  * Bump linux-mvl-dove ABI to 216

linux-meta-mvl-dove (2.6.32.215.17) lucid; urgency=low

  * No change rebuild. Launchpad hates me.

linux-meta-mvl-dove (2.6.32.215.16) lucid; urgency=low

  * Bump linux-mvl-dove ABI to 215 for proposed upload
    - LP: #712610

linux-meta-mvl-dove (2.6.32.214.15) lucid; urgency=low

  * Bump linux-mvl-dove ABI to 214 for proposed upload
    - LP: #712610

linux-meta-mvl-dove (2.6.32.212.14) lucid-proposed; urgency=low

  * Bump linux-mvl-dove ABI to 212 for proposed upload
    - LP: #677498

linux-meta-mvl-dove (2.6.32.211.13) lucid-proposed; urgency=low

  * Bump linux-mvl-dove ABI to 211 for proposed upload
 -- Tim Gardner <email address hidden> Fri, 18 Mar 2011 07:21:16 -0600