Havard Eidnes
unread,Aug 28, 2013, 8:10:44 AM8/28/13You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to curren...@netbsd.org
Hi,
I recently had occasion to boot up NetBSD 6.1 and -current on a
Supermicro X9DRW board equipped witn a Xeon E5 processor. The
board uses the Intel C602 chipset.
There are many "not configured" PCI devices. Notable is perhaps
vendor 0x8086 product 0x1d6b (SAS mass storage, revision 0x06) at pci6 dev 0 function 0 not configured
which is the SAS controller.
The ahcisata device is probed, but the installed 60GB SATA SSD is
not probed.
Looking at the source for NetBSD-current, we don't appear to have
a driver for the SAS controller in the Intel C602 chipset in our
system. Over in FreeBSD it seems this corresponds to their isci
device driver, which uses an Intel-provided OS-agnostic
abstraction layer to talk to the hardware (scil). Porting it
looks like a largish project.
For reference I include the dmesg outputs which I could capture
since the network device *is* supported.
Is the lack of specific driver support for the rest of the PCI
devices likely to be responsible for me not being able to probe
the SATA SSD drive?
I'll also note that the OS+machine didn't give the impression of
being stable, at least not with -current: I would get hangs and
once it bombed with a panic during boot-up (sorry, I didn't note
the details, something about a failed assertion related to
IPI(?)). At least the ACPI errors are gone in -current. :)
I'm not sure whether the instabilities are caused by -current or
it's the hardware support which isn't sufficiently mature.
Regards,
- Håvard