User`s guide

Chapter 2 Known Issues

This chapter describes the known issues for the Unbreakable Enterprise Kernel Release 3.

ACFS

Oracle ASM Cluster File System (ACFS) is currently not supported for use with UEK R3. (Bug ID

16318126)

ACPI

• On some systems you might see ACPI-related error messages in dmesg similar to the following:

ACPI Error: [CDW1] Namespace lookup failure, AE_NOT_FOUND

ACPI Error: Method parse/execution failed [_SB_._OSC||\||]

ACPI Error: Field [CDW3] at 96 exceeds Buffer [NULL] size 64 (bits)]]>

These messages, which are not fatal, are caused by bugs in the BIOS. Contact your system vendor for a

BIOS update. (Bug ID 13100702)

• The following messages indicate that the BIOS does not present a suitable interface, such as _PSS or

_PPC, that the acpi-cpufreq module requires:

kernel: powernow-k8: this CPU is not supported anymore, using acpi-cpufreq instead.

modprobe: FATAL: Error inserting acpi_cpufreq

There is no known workaround for this error. (Bug ID 17034535)

ASM

Calling the oracleasm init script, /etc/init.d/oracleasm, with the parameter scandisks can

lead to error messages about missing devices similar to the following:

oracleasm-read-label: Unable to open device "device": No such file or directory

However, the device actually exists. You can ignore this error message, which is triggered by a timing

issue. Only use the init script to start and stop the oracleasm service. All other options, such as

scandisks, listdisk, and createdisk, are deprecated. For these and other administrative tasks, use /

usr/sbin/oracleasm instead. (Bug ID 13639337)

bnx2x driver

When using the bnx2x driver in a bridge, disable Transparent Packet Aggregation (TPA) by including the

statement options bnx2x disable_tpa=1 in /etc/modprobe.conf. (Bug ID 14626070)

btrfs

• If you use the --alloc-start option with mkfs.btrfs to specify an offset for the start of the file

system, the size of the file system should be smaller but this is not the case. It is also possible to specify

an offset that is higher than the device size. (Bug ID 16946255)

• The usage information for mkfs.btrfs reports raid5 and raid6 as possible profiles for both data and

metadata. However, the kernel does not support these features and cannot mount file systems that use

them. (Bug ID 16946303)

• The btrfs filesystem balance command does not warn that the RAID level can be changed

under certain circumstances, and does not provide the choice of cancelling the operation. (Bug ID

16472824)