Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-05 Thread Stephen Borrill

On Tue, 4 Dec 2018, Martin Husemann wrote:

On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:

One thing that surprised me was that I was testing with the USB install
image but instead of landing in sysinst I ended up at a a login prompt which
was unexpected. Could this be because the USB disk that was my root device
ended up as sd23 and there is a hard coded sd0 somewhere in the install
code?


No hardcoded sd0, but maybe the boot device matching did not properly work
for this case (depends on geometry and stuff that the bootloader gets
from bios USB emulation or something).


Interesting, I noticed exactly the same when booting a -current image to
test the original mfii changes. In my case, sd0 and sd1 are the HW RAID 
arrays and sd2 is the USB stick:


[ 8.177453] sd2 at scsibus1 target 0 lun 0:  
disk removable
[ 8.177453] sd2: 3958 MB, 522 cyl, 255 head, 63 sec, 512 bytes/sect x 
8105984 sectors
[ 8.287566] boot device: sd2
[ 8.287566] root on sd2a dumps on sd2b

--
Stephen



Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-04 Thread Mike Pumford




On 04/12/2018 20:22, Manuel Bouyer wrote:

On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:



On 03/12/2018 22:47, Manuel Bouyer wrote:

Hello,
I synced our mpii(4) driver with the latest OpenBSD one and commited to HEAD.
I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
good if someone could test a SAS3 with some drives (the command setup is
different between SAS2 and SAS3, this is the code path I can't test).


Tested with my SAS3 card and an enclosure. Relevent dmesg bits are:

mpii0 at pci1 dev 0 function 0: vendor 1000 product 0097 (rev. 0x01)
mpii0: interrupting at msi0 vec 0
mpii0: SAS9300-8e, firmware 0.250.110.0, MPI 2.5

scsibus0 at mpii0: 768 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 0 lun 0:  disk fixed
sd1 at scsibus0 target 1 lun 0:  disk fixed
sd2 at scsibus0 target 2 lun 0:  disk fixed
sd3 at scsibus0 target 3 lun 0:  disk fixed
sd4 at scsibus0 target 4 lun 0:  disk fixed
sd5 at scsibus0 target 5 lun 0:  disk fixed
sd6 at scsibus0 target 6 lun 0:  disk fixed
sd7 at scsibus0 target 7 lun 0:  disk fixed
sd8 at scsibus0 target 8 lun 0:  disk fixed
sd9 at scsibus0 target 9 lun 0:  disk fixed
sd10 at scsibus0 target 10 lun 0:  disk fixed
sd11 at scsibus0 target 11 lun 0:  disk fixed
sd12 at scsibus0 target 12 lun 0:  disk fixed
sd13 at scsibus0 target 13 lun 0:  disk fixed
sd14 at scsibus0 target 14 lun 0:  disk fixed
sd15 at scsibus0 target 15 lun 0:  disk fixed
sd16 at scsibus0 target 16 lun 0:  disk fixed
sd17 at scsibus0 target 17 lun 0:  disk fixed

Did some IO to the disks and got read/write performance at exactly the
speeds I'd expect >170MB/s read and a little less for writing.


Was it with one disk, or several disks at once ?
I get 80MB/s with a SATA SEAGATE ST375064 (750GB). With a newer controller
and that much disk, I'd expect more than 170MB/s if several disks are used
in parallel.

It was just the one disk and its a SAS2 drive behind some SAS2 expanders 
so we aren't taking full advantage of the SAS3 speed. Sadly all the SAS3 
drives I have access to are actually in use for real work. :(


I will try a multi-drive test when I'm in the office again on Thursday.

The 170MB is exactly the performance I'd expect for that drive and 
matches what it achieves in linux on the same hardware.



Disk insertion are working with my controller, I've not tested removal yet
(will do tomorow). More testing is always welcome :)

Okay I'll also do some power down/power up cycles on some of the drive 
bays in the enclosure which should test removal and insertion. The 
driver was definately reporting the SAS discovery events. I'll have a 
look at the PCI IDs in the other spare SAS3 systems to see if that will 
test any of the other new bits of code as well.


Mike




Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-04 Thread Manuel Bouyer
On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:
> 
> 
> On 03/12/2018 22:47, Manuel Bouyer wrote:
> > Hello,
> > I synced our mpii(4) driver with the latest OpenBSD one and commited to 
> > HEAD.
> > I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
> > good if someone could test a SAS3 with some drives (the command setup is
> > different between SAS2 and SAS3, this is the code path I can't test).
> > 
> Tested with my SAS3 card and an enclosure. Relevent dmesg bits are:
> 
> mpii0 at pci1 dev 0 function 0: vendor 1000 product 0097 (rev. 0x01)
> mpii0: interrupting at msi0 vec 0
> mpii0: SAS9300-8e, firmware 0.250.110.0, MPI 2.5
> 
> scsibus0 at mpii0: 768 targets, 8 luns per target
> scsibus0: waiting 2 seconds for devices to settle...
> sd0 at scsibus0 target 0 lun 0:  disk fixed
> sd1 at scsibus0 target 1 lun 0:  disk fixed
> sd2 at scsibus0 target 2 lun 0:  disk fixed
> sd3 at scsibus0 target 3 lun 0:  disk fixed
> sd4 at scsibus0 target 4 lun 0:  disk fixed
> sd5 at scsibus0 target 5 lun 0:  disk fixed
> sd6 at scsibus0 target 6 lun 0:  disk fixed
> sd7 at scsibus0 target 7 lun 0:  disk fixed
> sd8 at scsibus0 target 8 lun 0:  disk fixed
> sd9 at scsibus0 target 9 lun 0:  disk fixed
> sd10 at scsibus0 target 10 lun 0:  disk fixed
> sd11 at scsibus0 target 11 lun 0:  disk fixed
> sd12 at scsibus0 target 12 lun 0:  disk fixed
> sd13 at scsibus0 target 13 lun 0:  disk fixed
> sd14 at scsibus0 target 14 lun 0:  disk fixed
> sd15 at scsibus0 target 15 lun 0:  disk fixed
> sd16 at scsibus0 target 16 lun 0:  disk fixed
> sd17 at scsibus0 target 17 lun 0:  disk fixed
> 
> Did some IO to the disks and got read/write performance at exactly the
> speeds I'd expect >170MB/s read and a little less for writing.

Was it with one disk, or several disks at once ?
I get 80MB/s with a SATA SEAGATE ST375064 (750GB). With a newer controller
and that much disk, I'd expect more than 170MB/s if several disks are used
in parallel.

> 
> So this tests one the cards you have brought in. I do have some other 12G
> hosts but I think they are the same chip. They would be more awkward to test
> with as they are serial console only machines that have only ever been
> tested running linux.

Actually I'm quite confident other chips working with OpenBSD will work with
NetBSD too. With your card and mine, all code paths have been tested AFAIK.

> 
> These disk are in an enclosure so if you want me to test hotplug stuff with
> this setup I can. Any data on the disks is entirely sacrificial at the
> moment.

Disk insertion are working with my controller, I've not tested removal yet
(will do tomorow). More testing is always welcome :)

-- 
Manuel Bouyer 
 NetBSD: 26 ans d'experience feront toujours la difference
--


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-04 Thread Manuel Bouyer
On Tue, Dec 04, 2018 at 07:26:09PM +, Mike Pumford wrote:
> 
> 
> On 04/12/2018 19:17, Mike Pumford wrote:
> o this tests one the cards you have brought in. I do have some other
> > 12G hosts but I think they are the same chip. They would be more awkward
> > to test with as they are serial console only machines that have only
> > ever been tested running linux.
> > 
> Just looked at the diff. The old code had an explicit 0,0 entry at the end
> of the PCI Ids array but this has been lost from the new version of the code
> so we are now taking it on faith that the entry one past the end of the
> static array will have a 0 mpii_vendor field. Is this safe?

No, I added back the {0, 0{ entry. Thanks !

-- 
Manuel Bouyer 
 NetBSD: 26 ans d'experience feront toujours la difference
--


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-04 Thread Mike Pumford




On 04/12/2018 19:31, Mike Pumford wrote:



On 04/12/2018 19:25, Martin Husemann wrote:

On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:

One thing that surprised me was that I was testing with the USB install
image but instead of landing in sysinst I ended up at a a login 
prompt which
was unexpected. Could this be because the USB disk that was my root 
device

ended up as sd23 and there is a hard coded sd0 somewhere in the install
code?


No hardcoded sd0, but maybe the boot device matching did not properly 
work

for this case (depends on geometry and stuff that the bootloader gets
from bios USB emulation or something).

Not sure about boot device (I don't have the console in front of me) but 
it definately reported the rootfs as /dev/sd23a and mounted the rootfs 
automatically. Is there any particular output I should look for?


It is quite an ancient machine so the BIOS USB could be odd.

I'm happy to do a retest on Thursday when I've next got access to the 
system.


I had the same problem with an earlier boot of the same system (without 
the mpii disks powered on) in that case the rootfs was sd5 as the system 
has a usb multi-card reader that got detected first.



Just found in the saved dmesg:
[ 6.612498] boot device: sd23
[ 6.612498] root on sd23a dumps on sd23b

So that all looks right.

Mike


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-04 Thread Mike Pumford




On 04/12/2018 19:25, Martin Husemann wrote:

On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:

One thing that surprised me was that I was testing with the USB install
image but instead of landing in sysinst I ended up at a a login prompt which
was unexpected. Could this be because the USB disk that was my root device
ended up as sd23 and there is a hard coded sd0 somewhere in the install
code?


No hardcoded sd0, but maybe the boot device matching did not properly work
for this case (depends on geometry and stuff that the bootloader gets
from bios USB emulation or something).

Not sure about boot device (I don't have the console in front of me) but 
it definately reported the rootfs as /dev/sd23a and mounted the rootfs 
automatically. Is there any particular output I should look for?


It is quite an ancient machine so the BIOS USB could be odd.

I'm happy to do a retest on Thursday when I've next got access to the 
system.


I had the same problem with an earlier boot of the same system (without 
the mpii disks powered on) in that case the rootfs was sd5 as the system 
has a usb multi-card reader that got detected first.


Mike


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-04 Thread Mike Pumford




On 04/12/2018 19:17, Mike Pumford wrote:
o this tests one the cards you have brought in. I do have some other
12G hosts but I think they are the same chip. They would be more awkward 
to test with as they are serial console only machines that have only 
ever been tested running linux.


Just looked at the diff. The old code had an explicit 0,0 entry at the 
end of the PCI Ids array but this has been lost from the new version of 
the code so we are now taking it on faith that the entry one past the 
end of the static array will have a 0 mpii_vendor field. Is this safe?


Mike



Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-04 Thread Martin Husemann
On Tue, Dec 04, 2018 at 07:17:59PM +, Mike Pumford wrote:
> One thing that surprised me was that I was testing with the USB install
> image but instead of landing in sysinst I ended up at a a login prompt which
> was unexpected. Could this be because the USB disk that was my root device
> ended up as sd23 and there is a hard coded sd0 somewhere in the install
> code?

No hardcoded sd0, but maybe the boot device matching did not properly work
for this case (depends on geometry and stuff that the bootloader gets
from bios USB emulation or something).

Martin


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-04 Thread Mike Pumford




On 03/12/2018 22:47, Manuel Bouyer wrote:

Hello,
I synced our mpii(4) driver with the latest OpenBSD one and commited to HEAD.
I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
good if someone could test a SAS3 with some drives (the command setup is
different between SAS2 and SAS3, this is the code path I can't test).


Tested with my SAS3 card and an enclosure. Relevent dmesg bits are:

mpii0 at pci1 dev 0 function 0: vendor 1000 product 0097 (rev. 0x01)
mpii0: interrupting at msi0 vec 0
mpii0: SAS9300-8e, firmware 0.250.110.0, MPI 2.5

scsibus0 at mpii0: 768 targets, 8 luns per target
scsibus0: waiting 2 seconds for devices to settle...
sd0 at scsibus0 target 0 lun 0:  disk fixed
sd1 at scsibus0 target 1 lun 0:  disk fixed
sd2 at scsibus0 target 2 lun 0:  disk fixed
sd3 at scsibus0 target 3 lun 0:  disk fixed
sd4 at scsibus0 target 4 lun 0:  disk fixed
sd5 at scsibus0 target 5 lun 0:  disk fixed
sd6 at scsibus0 target 6 lun 0:  disk fixed
sd7 at scsibus0 target 7 lun 0:  disk fixed
sd8 at scsibus0 target 8 lun 0:  disk fixed
sd9 at scsibus0 target 9 lun 0:  disk fixed
sd10 at scsibus0 target 10 lun 0:  disk fixed
sd11 at scsibus0 target 11 lun 0:  disk fixed
sd12 at scsibus0 target 12 lun 0:  disk fixed
sd13 at scsibus0 target 13 lun 0:  disk fixed
sd14 at scsibus0 target 14 lun 0:  disk fixed
sd15 at scsibus0 target 15 lun 0:  disk fixed
sd16 at scsibus0 target 16 lun 0:  disk fixed
sd17 at scsibus0 target 17 lun 0:  disk fixed

Did some IO to the disks and got read/write performance at exactly the 
speeds I'd expect >170MB/s read and a little less for writing.


So this tests one the cards you have brought in. I do have some other 
12G hosts but I think they are the same chip. They would be more awkward 
to test with as they are serial console only machines that have only 
ever been tested running linux.


These disk are in an enclosure so if you want me to test hotplug stuff 
with this setup I can. Any data on the disks is entirely sacrificial at 
the moment.


One thing that surprised me was that I was testing with the USB install 
image but instead of landing in sysinst I ended up at a a login prompt 
which was unexpected. Could this be because the USB disk that was my 
root device ended up as sd23 and there is a hard coded sd0 somewhere in 
the install code?


Mike


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-03 Thread Mike Pumford




On 03/12/2018 22:47, Manuel Bouyer wrote:

Hello,
I synced our mpii(4) driver with the latest OpenBSD one and commited to HEAD.
I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
good if someone could test a SAS3 with some drives (the command setup is
different between SAS2 and SAS3, this is the code path I can't test).

Just updating my current tree and doing a build. Will then take a USB 
bootable image to work and test it with the SAS3 HBA there.


Mike


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-12-03 Thread Manuel Bouyer
Hello,
I synced our mpii(4) driver with the latest OpenBSD one and commited to HEAD.
I tested it with a SAS2 controller (I don't have SAS3 ones), so it would be
good if someone could test a SAS3 with some drives (the command setup is
different between SAS2 and SAS3, this is the code path I can't test).

I plan to get this in netbsd-8 along with the mfii driver (and my if_bge
improvements).

-- 
Manuel Bouyer 
 NetBSD: 26 ans d'experience feront toujours la difference
--


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-11-30 Thread Mike Pumford




On 30/11/2018 08:50, Stephen Borrill wrote:

I cannot easily attach drives to it (it has external ports only, and I 
would need to drag it to our datacenter to connect it to something). 
Let's see what Mike Pumford's PCI IDs are.


Wasn't able to check as I need to take a live USB stick in as the 
current system disk in that system is broken (its an ex-devtest box) and 
I forgot to pick it up. :( Will try again on Monday but from what I an 
remember all LSI SAS3 chipsets have a totally different driver to the 
SAS2 and SAS cards.


I do have the ability to hook it up to a wide variety of disks though.

Mike


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-11-30 Thread Manuel Bouyer
On Fri, Nov 30, 2018 at 08:50:29AM +, Stephen Borrill wrote:
> On Thu, 29 Nov 2018, Manuel Bouyer wrote:
> > On Thu, Nov 29, 2018 at 03:56:37PM +, Stephen Borrill wrote:
> [snip]
> > > The other missing driver is handled by mpii in OpenBSD (SAS3408). Our mpii
> > > doesn't yet support any SAS3 cards.
> > > [ 1.048805] vendor 1000 product 00af (SAS mass storage, revision 0x01)
> > > at pci4 dev 0 function 0 not configured
> > 
> > Do you have drives connected to this controller ?
> > If so I can probably come up with a patch this week-end.
> > The SAS3 has a sighly different interface, but from looking at the OpenBSD
> > driver it's all in a single function.
> 
> I cannot easily attach drives to it (it has external ports only, and I would
> need to drag it to our datacenter to connect it to something). Let's see
> what Mike Pumford's PCI IDs are.
> 
> If I do go to the datacenter however, I should also be able to MegaRAID 3108
> support (IBM ServeRAID M5210).
> 
> Do you have a gut feel on how easy it would be to backport your mpii changes
> to -7 and -8?

Probably easy, the driver didn't change much since -7 (only minor changes
in kernel interfaces).

-- 
Manuel Bouyer 
 NetBSD: 26 ans d'experience feront toujours la difference
--


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-11-30 Thread Stephen Borrill

On Thu, 29 Nov 2018, Manuel Bouyer wrote:

On Thu, Nov 29, 2018 at 03:56:37PM +, Stephen Borrill wrote:

[snip]

The other missing driver is handled by mpii in OpenBSD (SAS3408). Our mpii
doesn't yet support any SAS3 cards.
[ 1.048805] vendor 1000 product 00af (SAS mass storage, revision 0x01)
at pci4 dev 0 function 0 not configured


Do you have drives connected to this controller ?
If so I can probably come up with a patch this week-end.
The SAS3 has a sighly different interface, but from looking at the OpenBSD
driver it's all in a single function.


I cannot easily attach drives to it (it has external ports only, and I 
would need to drag it to our datacenter to connect it to something). Let's 
see what Mike Pumford's PCI IDs are.


If I do go to the datacenter however, I should also be able to MegaRAID 
3108 support (IBM ServeRAID M5210).


Do you have a gut feel on how easy it would be to backport your mpii 
changes to -7 and -8?


--
Stephen


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-11-30 Thread Manuel Bouyer
On Thu, Nov 29, 2018 at 11:41:41PM +, Mike Pumford wrote:
> 
> 
> On 29/11/2018 18:16, Manuel Bouyer wrote:
> 
> > Do you have drives connected to this controller ?
> > If so I can probably come up with a patch this week-end.
> > The SAS3 has a sighly different interface, but from looking at the OpenBSD
> > driver it's all in a single function.
> > 
> I've got access to a spare LSI SAS3 HBA at work and have some SAS drives I
> could test with. I can get the exact PCI ids to see if its supported by the
> OpenBSD driver.

thanks. Hopefully I'll come up with a patch this week-end

-- 
Manuel Bouyer 
 NetBSD: 26 ans d'experience feront toujours la difference
--


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-11-29 Thread Mike Pumford




On 29/11/2018 18:16, Manuel Bouyer wrote:


Do you have drives connected to this controller ?
If so I can probably come up with a patch this week-end.
The SAS3 has a sighly different interface, but from looking at the OpenBSD
driver it's all in a single function.

I've got access to a spare LSI SAS3 HBA at work and have some SAS drives 
I could test with. I can get the exact PCI ids to see if its supported 
by the OpenBSD driver.


Mike


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-11-29 Thread Manuel Bouyer
On Thu, Nov 29, 2018 at 03:56:37PM +, Stephen Borrill wrote:
> On Mon, 26 Nov 2018, Stephen Borrill wrote:
> > Thanks Manuel!
> > 
> > [ 1.048805] mfii0 at pci11 dev 0 function 0: "RAID 930-8i 2GB
> > Flash", firmware 50.3.0-1075, 2048MB cache
> > [ 1.048805] mfii0: interrupting at ioapic4 pin 2
> > [ 1.048805] scsibus0 at mfii0: 64 targets, 8 luns per target
> > [ 2.161214] scsibus0: waiting 2 seconds for devices to settle...
> > [ 2.161214] mfii0: physical disk inserted id 18 enclosure 134
> > [ 2.161214] mfii0: physical disk inserted id 19 enclosure 134
> > [ 2.161214] mfii0: physical disk inserted id 20 enclosure 134
> > [ 2.161214] mfii0: physical disk inserted id 21 enclosure 134
> > [ 4.163289] sd0 at scsibus0 target 0 lun 0:  > 930-8i-2GB, 5.03> disk fixed
> > [ 4.163289] sd0: fabricating a geometry
> > [ 4.163289] sd0: 2234 GB, 2287864 cyl, 64 head, 32 sec, 512
> > bytes/sect x 4685545472 sectors
> > [ 4.163289] sd0: fabricating a geometry
> > [ 4.163289] sd0: tagged queueing
> > [ 4.163289] sd1 at scsibus0 target 1 lun 0:  > 930-8i-2GB, 5.03> disk fixed
> > [ 4.163289] sd1: fabricating a geometry
> > [ 4.163289] sd1: 744 GB, 761985 cyl, 64 head, 32 sec, 512 bytes/sect
> > x 1560545280 sectors
> > [ 4.163289] sd1: fabricating a geometry
> > [ 4.163289] sd1: tagged queueing
> > [32.192359] mfii0: critical limit on 'mfii0 BBU state'
> > [32.192359] mfii0: normal state on 'mfii0:0' (online)
> > [32.192359] mfii0: normal state on 'mfii0:1' (online)
> 
> The other missing driver is handled by mpii in OpenBSD (SAS3408). Our mpii
> doesn't yet support any SAS3 cards.
> [ 1.048805] vendor 1000 product 00af (SAS mass storage, revision 0x01)
> at pci4 dev 0 function 0 not configured

Do you have drives connected to this controller ?
If so I can probably come up with a patch this week-end.
The SAS3 has a sighly different interface, but from looking at the OpenBSD
driver it's all in a single function.

-- 
Manuel Bouyer 
 NetBSD: 26 ans d'experience feront toujours la difference
--


Re: mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-11-29 Thread Stephen Borrill

On Mon, 26 Nov 2018, Stephen Borrill wrote:

Thanks Manuel!

[ 1.048805] mfii0 at pci11 dev 0 function 0: "RAID 930-8i 2GB Flash", 
firmware 50.3.0-1075, 2048MB cache

[ 1.048805] mfii0: interrupting at ioapic4 pin 2
[ 1.048805] scsibus0 at mfii0: 64 targets, 8 luns per target
[ 2.161214] scsibus0: waiting 2 seconds for devices to settle...
[ 2.161214] mfii0: physical disk inserted id 18 enclosure 134
[ 2.161214] mfii0: physical disk inserted id 19 enclosure 134
[ 2.161214] mfii0: physical disk inserted id 20 enclosure 134
[ 2.161214] mfii0: physical disk inserted id 21 enclosure 134
[ 4.163289] sd0 at scsibus0 target 0 lun 0: 5.03> disk fixed

[ 4.163289] sd0: fabricating a geometry
[ 4.163289] sd0: 2234 GB, 2287864 cyl, 64 head, 32 sec, 512 bytes/sect x 
4685545472 sectors

[ 4.163289] sd0: fabricating a geometry
[ 4.163289] sd0: tagged queueing
[ 4.163289] sd1 at scsibus0 target 1 lun 0: 5.03> disk fixed

[ 4.163289] sd1: fabricating a geometry
[ 4.163289] sd1: 744 GB, 761985 cyl, 64 head, 32 sec, 512 bytes/sect x 
1560545280 sectors

[ 4.163289] sd1: fabricating a geometry
[ 4.163289] sd1: tagged queueing
[32.192359] mfii0: critical limit on 'mfii0 BBU state'
[32.192359] mfii0: normal state on 'mfii0:0' (online)
[32.192359] mfii0: normal state on 'mfii0:1' (online)


The other missing driver is handled by mpii in OpenBSD (SAS3408). Our mpii 
doesn't yet support any SAS3 cards.
[ 1.048805] vendor 1000 product 00af (SAS mass storage, revision 0x01) 
at pci4 dev 0 function 0 not configured


--
Stephen



mfii0 kudos to bouyer@ Was Re: dmesg | grep -c "not configured" = 240...

2018-11-26 Thread Stephen Borrill

Thanks Manuel!

[ 1.048805] mfii0 at pci11 dev 0 function 0: "RAID 930-8i 2GB Flash", 
firmware 50.3.0-1075, 2048MB cache
[ 1.048805] mfii0: interrupting at ioapic4 pin 2
[ 1.048805] scsibus0 at mfii0: 64 targets, 8 luns per target
[ 2.161214] scsibus0: waiting 2 seconds for devices to settle...
[ 2.161214] mfii0: physical disk inserted id 18 enclosure 134
[ 2.161214] mfii0: physical disk inserted id 19 enclosure 134
[ 2.161214] mfii0: physical disk inserted id 20 enclosure 134
[ 2.161214] mfii0: physical disk inserted id 21 enclosure 134
[ 4.163289] sd0 at scsibus0 target 0 lun 0:  
disk fixed
[ 4.163289] sd0: fabricating a geometry
[ 4.163289] sd0: 2234 GB, 2287864 cyl, 64 head, 32 sec, 512 bytes/sect x 
4685545472 sectors
[ 4.163289] sd0: fabricating a geometry
[ 4.163289] sd0: tagged queueing
[ 4.163289] sd1 at scsibus0 target 1 lun 0:  
disk fixed
[ 4.163289] sd1: fabricating a geometry
[ 4.163289] sd1: 744 GB, 761985 cyl, 64 head, 32 sec, 512 bytes/sect x 
1560545280 sectors
[ 4.163289] sd1: fabricating a geometry
[ 4.163289] sd1: tagged queueing
[32.192359] mfii0: critical limit on 'mfii0 BBU state'
[32.192359] mfii0: normal state on 'mfii0:0' (online)
[32.192359] mfii0: normal state on 'mfii0:1' (online)

# bioctl mfii0 show
Volume Status   Size Device/LabelLevel Stripe
=
 0 Online   2.2T   System   RAID 1N/A  65535 seconds
   0:0 Online   2.2T 1:0.0 noencl 
   0:1 Online   2.2T 1:1.0 noencl 
 1 Online   744G   WriteCache   RAID 1N/A  65535 seconds
   1:0 Online   745G 1:2.0 noencl 
   1:1 Online   745G 1:3.0 noencl 


dmesg | grep -c "not configured" = 239 :-)

On Mon, 19 Feb 2018, Stephen Borrill wrote:


So I've just got a Lenovo ThinkSystem SR630 and:
# dmesg | grep -c "not configured"
  240

http://www.netbsd.org/~sborrill/sr630.dmesg.txt

Main issues are missing Ethernet (Intel X722) and RAID controller:
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 0 not configured
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 1 not configured
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 2 not configured
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 3 not configured
vendor 1000 product 0016 (RAID mass storage, revision 0x01) at pci11 dev 0 
function 0 not configured


msaitoh@ - have you looked at the Intel X722 gigabit controllers?

As for the RAID controller, we are missing support for all recent 
LSI/Symbios/Avago/Broadcom controllers meaning no support for lots of servers 
from Lenovo/HP, etc. OpenBSD's mfii supports most of these:


https://www.precedence.co.uk/wiki/Support-KB-IBM/PCIIDs

NetBSD has extended mfi to support a few variants, but OpenBSD has split the 
driver into mfi and mfii which makes porting more tricky.


I tried OpenBSD 6.2 (last release), but the support for the RAID controller 
in this server was added after 6.2. On OpenBSD:

# dmesg | grep -c "not configured"
350

--
Stephen




Re: dmesg | grep -c "not configured" = 240...

2018-02-25 Thread Christos Zoulas
In article <6c9dd7ad-b02e-3932-3102-e609ad336...@execsw.org>,
Masanobu SAITOH  <msai...@execsw.org> wrote:
>On 2018/02/24 18:55, Patrick Welche wrote:
>> On Mon, Feb 19, 2018 at 03:17:48PM +, Stephen Borrill wrote:
>>> So I've just got a Lenovo ThinkSystem SR630 and:
>>> # dmesg | grep -c "not configured"
>>> 240
>>>
>>> http://www.netbsd.org/~sborrill/sr630.dmesg.txt
>>>
>>> Main issues are missing Ethernet (Intel X722) and RAID controller:
>>> vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7
>dev 0 function 0 not configured
>>> vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7
>dev 0 function 1 not configured
>>> vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7
>dev 0 function 2 not configured
>>> vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7
>dev 0 function 3 not configured
>>> vendor 1000 product 0016 (RAID mass storage, revision 0x01) at pci11
>dev 0 function 0 not configured
>>>
>>> msaitoh@ - have you looked at the Intel X722 gigabit controllers?
>
>  X722 is a 10G device which is based on 40G controller. {Free,Open}BSD
>has ixl(4) but NetBSD has no device driver yet :(
>
>  And I have no any ixl(4) devices :)

Would it help of someone bought you one?

christos



Re: dmesg | grep -c "not configured" = 240...

2018-02-25 Thread Masanobu SAITOH

On 2018/02/24 18:55, Patrick Welche wrote:

On Mon, Feb 19, 2018 at 03:17:48PM +, Stephen Borrill wrote:

So I've just got a Lenovo ThinkSystem SR630 and:
# dmesg | grep -c "not configured"
240

http://www.netbsd.org/~sborrill/sr630.dmesg.txt

Main issues are missing Ethernet (Intel X722) and RAID controller:
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 0 not configured
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 1 not configured
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 2 not configured
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 3 not configured
vendor 1000 product 0016 (RAID mass storage, revision 0x01) at pci11 dev 0 
function 0 not configured

msaitoh@ - have you looked at the Intel X722 gigabit controllers?


 X722 is a 10G device which is based on 40G controller. {Free,Open}BSD
has ixl(4) but NetBSD has no device driver yet :(

 And I have no any ixl(4) devices :)







For the second part:


As for the RAID controller, we are missing support for all recent
LSI/Symbios/Avago/Broadcom controllers meaning no support for lots of
servers from Lenovo/HP, etc. OpenBSD's mfii supports most of these:

https://www.precedence.co.uk/wiki/Support-KB-IBM/PCIIDs

NetBSD has extended mfi to support a few variants, but OpenBSD has split the
driver into mfi and mfii which makes porting more tricky.


I had a first stab, for which feedback would have been nice:

https://mail-index.netbsd.org/current-users/2015/07/08/msg027701.html

(Development might be easier now that several USB keyboard bugs have
been fixed since then.)


Cheers,

Patrick




--
---
SAITOH Masanobu (msai...@execsw.org
 msai...@netbsd.org)


Re: dmesg | grep -c "not configured" = 240...

2018-02-24 Thread Patrick Welche
On Mon, Feb 19, 2018 at 03:17:48PM +, Stephen Borrill wrote:
> So I've just got a Lenovo ThinkSystem SR630 and:
> # dmesg | grep -c "not configured"
>240
> 
> http://www.netbsd.org/~sborrill/sr630.dmesg.txt
> 
> Main issues are missing Ethernet (Intel X722) and RAID controller:
> vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
> function 0 not configured
> vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
> function 1 not configured
> vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
> function 2 not configured
> vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
> function 3 not configured
> vendor 1000 product 0016 (RAID mass storage, revision 0x01) at pci11 dev 0 
> function 0 not configured
> 
> msaitoh@ - have you looked at the Intel X722 gigabit controllers?



For the second part:

> As for the RAID controller, we are missing support for all recent
> LSI/Symbios/Avago/Broadcom controllers meaning no support for lots of
> servers from Lenovo/HP, etc. OpenBSD's mfii supports most of these:
> 
> https://www.precedence.co.uk/wiki/Support-KB-IBM/PCIIDs
> 
> NetBSD has extended mfi to support a few variants, but OpenBSD has split the
> driver into mfi and mfii which makes porting more tricky.

I had a first stab, for which feedback would have been nice:

https://mail-index.netbsd.org/current-users/2015/07/08/msg027701.html

(Development might be easier now that several USB keyboard bugs have
been fixed since then.)


Cheers,

Patrick


dmesg | grep -c "not configured" = 240...

2018-02-19 Thread Stephen Borrill

So I've just got a Lenovo ThinkSystem SR630 and:
# dmesg | grep -c "not configured"
   240

http://www.netbsd.org/~sborrill/sr630.dmesg.txt

Main issues are missing Ethernet (Intel X722) and RAID controller:
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 0 not configured
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 1 not configured
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 2 not configured
vendor 8086 product 37d2 (ethernet network, revision 0x09) at pci7 dev 0 
function 3 not configured
vendor 1000 product 0016 (RAID mass storage, revision 0x01) at pci11 dev 0 
function 0 not configured

msaitoh@ - have you looked at the Intel X722 gigabit controllers?

As for the RAID controller, we are missing support for all recent 
LSI/Symbios/Avago/Broadcom controllers meaning no support for lots of 
servers from Lenovo/HP, etc. OpenBSD's mfii supports most of these:


https://www.precedence.co.uk/wiki/Support-KB-IBM/PCIIDs

NetBSD has extended mfi to support a few variants, but OpenBSD has split 
the driver into mfi and mfii which makes porting more tricky.


I tried OpenBSD 6.2 (last release), but the support for the RAID 
controller in this server was added after 6.2. On OpenBSD:

# dmesg | grep -c "not configured"
350

--
Stephen