Subject: kern/14266: mlx(4) problems with -current kernel
To: None <gnats-bugs@gnats.netbsd.org>
From: None <dmelomed@devonitnet.com>
List: netbsd-bugs
Date: 10/16/2001 10:57:49
>Number:         14266
>Category:       kern
>Synopsis:       mlx(4) problems with -current kernel
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Oct 16 10:59:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Dan Melomedman
>Release:        -current
>Organization:
>Environment:
>Description:
Hi. I am trying to install NetBSD on a machine with Mylex eXtremeRAID 1100 aka DAC1164P aka DAC1100 on an Athlon PC with AMD 761 chipset if that helps. I know the hardware is not faulty since other OSes run just fine on it. Here's the part of my dmesg output: 
mlx0 at pci3 dev 8 function 0: Mylex RAID (v5 interface)
mlx0: interrupting at irq 10
mlx0: initializing (may take some time)...
mlx0: initialization complete
mlx0: DAC1164PVX, 2 channels, firmware 5.08-0-87, 16MB RAM
ld0 at mlx0 unit 0: RAID1, online
ld0: 17357 MB, 8816 cyl, 64 head, 63 sec, 512 bytes/sect x 35547136 sectors
vendor 0x1069 product 0xba55 (RAID mass storage) at pci3 dev 9 function 0 not configured

Then, about every two seconds I am receiving the following messages from the kernel: mlx0: periodic enquiry failed - software timeout (0xdead)
mlx0: bad completion returned

I was able to create a NetBSD partition and FSes (using sysinst), but while extracting packages, most writes to the disk failed and kernel went into panic later. This seems like a geometry issue, but I could be wrong. 

What about that pci 3 dev 9 unconfigured message?

Any help would be greately appreciated.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: