Actions
Bug #12497
closed
bge ape locking left always disabled after 7513
Start date:
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
Description
In addressing 7513, it was important to determine whether or not the hardware supported ape before looking at and initializing the asf related pieces. By doing this, it moved the checks for whether or not the chipsets were of the right type to consider checking that.
However, while it moved the check earlier, it didn't move the initialization of that actual device ID that it needed earlier. This leads to us thinking that ape doesn't exist on any of the devices. The fix at the moment is to just assign that single member that's needed (the PCI device ID) to be before the chipset check.
Related issues
Updated by Marcel Telka about 2 years ago
- Related to Bug #7513: sudden reboot when accessing bge2 on HP Gen9 added
Updated by Robert Mustacchi about 2 years ago
- Related to Bug #12496: bge mac address initialization is wrong added
Updated by Robert Mustacchi about 2 years ago
Please see testing notes on 12496.
Updated by Electric Monk about 2 years ago
- Status changed from New to Closed
- % Done changed from 90 to 100
git commit 9e717e77bf4b9b5ad279c38a2311c076468e85f5
commit 9e717e77bf4b9b5ad279c38a2311c076468e85f5
Author: Robert Mustacchi <rm@fingolfin.org>
Date: 2020-04-22T06:18:18.000Z
12496 bge mac address initialization is wrong
12497 bge ape locking left always disabled after 7513
12498 bge ring interrupt masking logic is broken
Reviewed by: Paul Winder <paul@winders.demon.co.uk>
Approved by: Dan McDonald <danmcd@joyent.com>
Updated by Marcel Telka about 2 years ago
- Related to Bug #12686: dladm: vnic creation over bge0 failed: object already exists added
Actions