Red Hat Bugzilla – Bug 252287
AMD/ATI SB600/700/800 use same SMBus controller devID
Last modified: 2009-06-19 20:10:27 EDT
+++ This bug was initially created as a clone of Bug #252286 +++
Description of problem:
We find that SB700 and SB800 use the same SMBus device ID as SB600, which is
0x4385, instead of the already submitted 0x4395.
We submitted an error SB700 SMBus patch in the bugzilla# 244195
Please apply the attached new SMBus patch, which can remove the wrong applied
SB700 SMBus patch submitted before.
Besides removing the SB700 wrong patch, the attached patch add SB800 support to
kernel, by renaming the PCI_DEVICE_ID_ATI_IXP600_SMBUS into
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Would you please help to apply this new patch ASAP before the release of
RHEL4.6? Because the error device ID 0x4395 will be used in SB800 SATA
I have sent this new patch to kernel.org, I will send you the upstream commit
after they apply it.
The patch is generated on the base of linux-2.6.23-rc3, so maybe you need do
some small backport to it when you apply it.
-- Additional comment from firstname.lastname@example.org on 2007-08-14 23:46 EST --
Created an attachment (id=161327)
SB600/SB700/SB800 use same SMBus controll device ID
*** Bug 335351 has been marked as a duplicate of this bug. ***
Created attachment 295314 [details]
Fixes SMBus controller Device IDs
This patch was created against -68.11 tree.
*** Bug 299921 has been marked as a duplicate of this bug. ***
Patch tested by AMD chipset QA on SB600, SB700 boards.
Committed in 68.17.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
added to RHEL4.7 Driver Updates:
(x86_64) i2c_piix4: module added to support AMD ATI SB600, SB700, and SB800.
please advise if any further revisions are required. thanks!
the RHEL4.7 release notes deadline is on June 17, 2008 (Tuesday). they will
undergo a final proofread before being dropped to translation, at which point no
further additions or revisions will be entertained.
a mockup of the RHEL4.7 release notes can be viewed here:
please use the aforementioned link to verify if your bugzilla is already in the
release notes (if it needs to be). each item in the release notes contains a
link to its original bug; as such, you can search through the release notes by
~ Attention: ~ Feedback requested regarding this **High Priority** bug.
A fix for this issue should be included in the latest packages contained in
RHEL4.7-Snapshot1--available now on partners.redhat.com.
After you (Red Hat Partner) have verified that this issue has been addressed,
submit a comment describing the passing results of your test in appropriate
detail, along with which snapshot and package version tested. The bugzilla will
be updated by Red Hat Quality Engineering for you when this information has been
If you believe this issue has not properly fixed or you are unable to verify the
issue for any reason, please add a comment describing the most recent issues you
are experiencing, along with which snapshot and package version tested.
If you believe the bug has not been fixed, change the status of the bug to ASSIGNED.
If you are receiving this message in Issue Tracker, please reply with a message
to Issue Tracker about your results and bugzilla will be updated for you.
If you need assistance accessing ftp://partners.redhat.com, please contact your
Red Hat QE Partner Management
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
Partners, I would like to thank you all for your participation in assuring the
quality of this RHEL 4.7 Update Release. My hat's off to you all. Thanks.