Interesting: The release note is suppressed since the bug is in the "Closed" state, which means it is recognized as an undesirable behavior and documented, but Cisco does not intend to provide a fix. I think that may be a problem with bug toolkit that the Closed (C) state bugs do not display the release note.
Regarding the bug:
The problem occurs because of memory fragmentation that happend when too many VLANs are on a trunk port to a phone.
Here is the original release note:
Symptom:
A cat3524xl switch can experience memory allocation errors. After these errors the
memory is freed up but it becomes fragmented. The following error message might be
displayed:
Dec 5 15:51:31 MET: %SYS-2-MALLOCFAIL: Memory allocation of 568 bytes failed from 0x192C20, pool Processor, alignment 0
-Process= "STP Queue Handler", ipl= 6, pid= 56
-Traceback= 1C6CA4 1C8798 192C24 192F70 193468 2718D8 27012C 27173C 271E08 272218 272CA0 1E3B9C
Additional Information:
The switch is connected to IP Phones, and are configured with dot1q trunks down to
the IP Phones. The switch is also configured with a number of VLANs. As a result,
the switch must send spanning-tree BPDUs for all VLANs to every phone, which is not
efficient.
Workaround:
Configure an allowed VLAN list on all voice ports using the following command:
switchport trunk allowed vlan
{
addvlan-list
|
all
|
exceptvlan-list
|
removevlan-list
}
The allowed VLAN list should only include those that are absolutely necessary on
that port, usually just the voice and data VLANs.
