Some (non-critical) odds and ends with mlx(4)

Oliver Schonefeld oschonef at TechFak.Uni-Bielefeld.DE
Tue Sep 7 12:05:10 PDT 2004


I installed a machine with a Mylex 1164P with a RELENG_5 snapshot and
noticed a problem with mlxcontrol(8). Using the "status -v" command,
mlxcontrol is unable to identify the drives and it will never complete the
command (whether with or without "-v" or "-q" makes no difference).
Using ktrace it seems it loops calling a ioctl.

relevent dmesg output:
mlx0: <Mylex version 5 RAID interface> port 0xd800-0xd87f mem
0xfa000000-0xfbffffff,0xfcfff800-0xfcfff87f irq 11 at device 8.0 on pci2
mlx0: controller initialisation in progress...
mlx0: initialisation complete.
mlx0: DAC1164PVX, 3 channels, firmware 5.08-0-87, 32MB RAM
mlxd0: <Mylex System Drive> on mlx0
mlxd0: 4461MB (9136128 sectors) RAID 1 (online)
mlxd1: <Mylex System Drive> on mlx0
mlxd1: 4287MB (8779776 sectors) RAID 1 (online)
mlxd2: <Mylex System Drive> on mlx0
mlxd2: 210309MB (430712832 sectors) RAID 5 (online)

"mlxcontrol status -v" and kdump output attached. 4.10 was able to identify
the drives but also hung at the status command. Unfortunatly it's not
installed anymore, so i cannot run the command with ktrace.

And remember: "To Infinity And Far Beyond ... Somehow?!"

Hi! I'm a .signature virus! Copy me in your ~/.signature
to help me spread!             <- Save this lifeform ;-)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mlx.tar.gz
Type: application/octet-stream
Size: 8954 bytes
Desc: not available
Url :

More information about the freebsd-current mailing list