Bug 235737 - Forcedeth module causes bmc access to fail while machine is off
Forcedeth module causes bmc access to fail while machine is off
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel (Show other bugs)
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Andy Gospodarek
Martin Jenner
Depends On:
  Show dependency treegraph
Reported: 2007-04-09 16:50 EDT by Sarah Prelutsky
Modified: 2014-06-29 18:58 EDT (History)
3 users (show)

See Also:
Fixed In Version: RHBA-2007-0959
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-07 14:46:29 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Sarah Prelutsky 2007-04-09 16:50:08 EDT
Description of problem:

loose ipmi access when machine is powered off.

Version-Release number of selected component (if applicable): Rhel5 Server x86_64

How reproducible:

Steps to Reproduce:
1. power down machine with forcedeth .56 driver
2. ping ipmi ip of target machine
3. ping will fail when machine is shut down. (ipmitool accesability is gone too)
Actual results:
ping/access fails
you cannot do "ipmitool -H chassis power on"

Expected results:
should ping. should be accessible with ipmitool

Additional info:
Using forcedeth v .59 or v.60 resolves the issue.
From the upstream forcedeth.c for v.60
 *      0.59: 31 May 2006: Added support for sideband management unit.

This change allowed ping and regular access to the BMC while the machine is
turned off.
Comment 1 Ernie Petrides 2007-09-11 18:08:33 EDT
This problem should be fixed with the update of the forcedeth driver
(to version 0.60) made during RHEL5.1, which is currently in beta.

Don, this is the relevant patch tracking file:

Comment 2 Andy Gospodarek 2007-09-11 18:16:19 EDT
This is true -- in fact I'm quite sure I saw an almost identical report where
the update to the forcedeth driver for 5.1 resolved this. 

Feel free to test kernels from



Comment 5 errata-xmlrpc 2007-11-07 14:46:29 EST
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 the 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.


Note You need to log in before you can comment on or make changes to this bug.