Ubuntu
linux-source-2.6.22 package

7.10 support of new AMD PowerNow! (family 0x11 and beyond)

Bug #185649 reported by Tim Gardner on 2008-01-24

Affects		Status	Importance	Assigned to	Milestone
	linux-source-2.6.22 (Ubuntu)	Fix Released	Medium	Unassigned	Ubuntu gutsy-updates

Bug Description

Binary package hint: linux-source-2.6.22

The PowerNow! driver included in Ubuntu 7.10 has a flaw that prevents it from loading on AMD family 0x11 processors (which have not been released). AMD considers Ubuntu 7.10 an important software platform for family 0x11 processors. We would like to get a patch added so that the driver can work.

-Mark Langsdorf
Operating System Research Center
AMD

Related branches

lp://staging/ubuntu/gutsy-security/linux-source-2.6.22

CVE References

Revision history for this message

Tim Gardner (timg-tpi) wrote on 2008-01-24:

powernow-k8.patch Edit (829 bytes, text/plain)

Fix from AMD.

Tim Gardner (timg-tpi) on 2008-01-24

Changed in linux-source-2.6.22:
importance:	Undecided → Medium
milestone:	none → gutsy-updates
status:	New → Fix Committed

Revision history for this message

Mark Langsdorf (mark-langsdorf) wrote on 2008-01-24:

Fix for all future processors families, from AMD Edit (4.3 KiB, text/plain)

Revision history for this message

Tim Gardner (timg-tpi) wrote on 2008-01-24:

Mark - this patch can't be correct. The last hunk that modifies print_basics() does not apply and would leave incorrect code. Can you take a closer look? Thanks.

Revision history for this message

Mark Langsdorf (mark-langsdorf) wrote on 2008-01-24:

Fix for all future processors families, from AMD (full patch) Edit (21.7 KiB, text/plain)

This is the full, untruncated patch. I applied it to the ubuntu 2.6.22-14.47 kernel and it applied without difficulty.

Jose De la Rosa (jose-de-la-rosa) on 2008-01-25

Changed in dell:
importance:	Undecided → Medium
status:	New → Fix Committed

Revision history for this message

Tim Gardner (timg-tpi) wrote on 2008-01-29:

Well, the full untruncated patch doesn't compile so I went with the original http://launchpadlibrarian.net/11525533/powernow-k8.patch.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-02-04:

This bug was fixed in the package linux-source-2.6.22 - 2.6.22-14.51

---------------
linux-source-2.6.22 (2.6.22-14.51) gutsy-security; urgency=low

[Amit Kucheria]

  * Poulsbo: Mass update of all patches from moblin repo
  * Update config.lpia to reflect new patches
  * [sata_sil][sata->ide-bridg] failed to set xfermode
    - LP: #153096
  * Poulsbo: remove extra patch

[Kees Cook]

* fix NFSv4 client mount regression
- LP: #164231

[Tim Gardner]

* Support of new AMD PowerNow! (family 0x11 and beyond)
- LP: #185649

[Upstream Kernel Changes]

  * minixfs: limit minixfs printks on corrupted dir i_size (CVE-2006-6058)
  * [JFFS2] Fix ACL vs. mode handling. (CVE-2007-4849)
  * [IEEE80211]: avoid integer underflow for runt rx frames (CVE-2007-4997)
  * [TCP]: Make sure write_queue_from does not begin with NULL ptr
    (CVE-2007-5501)
  * wait_task_stopped: Check p->exit_state instead of TASK_TRACED
    (CVE-2007-5500)
  * fix DLM regression
  * CVE-2008-0001: Use access mode instead of open flags to determine
    needed permissions
  * hrtimers: avoid overflow for large relative timeouts (CVE-2007-5966)
  * isdn: avoid copying overly-long strings (CVE-2007-6063)
  * I4L: fix isdn_ioctl memory overrun vulnerability (CVE-2007-6151)
  * vfs: coredumping fix (CVE-2007-6206)
  * tmpfs: restore missing clear_highpage (CVE-2007-6417)
  * [UBUNTU] fs/dlm: Fix regression introduced with last security fix.

-- Tim Gardner <email address hidden> Mon, 28 Jan 2008 13:46:21 -0700

Changed in linux-source-2.6.22:
status:	Fix Committed → Fix Released

Jose De la Rosa (jose-de-la-rosa) on 2008-02-19

Changed in dell:
status:	Fix Committed → Fix Released

Timothy R. Chavez (timrchavez) on 2014-04-10

Changed in somerville:
importance:	Undecided → Medium
status:	New → Fix Released
no longer affects:	dell

Revision history for this message

Timothy R. Chavez (timrchavez) wrote on 2014-04-10:

The bug task for the somerville project has been removed by an automated script. This bug has been cloned on that project and is available here: https://bugs.launchpad.net/bugs/1306081

no longer affects:

somerville