Re: LSI supported mps(4) driver in stable/9 and stable/8
On Mon, Feb 13, 2012 at 15:08:45 +0100, Ollivier Robert wrote: According to Kenneth D. Merry: The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Thanks. Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. Got an ETA for this? Saying differently, is it reasonable to run stable/9 with the new driver but w/o the CAM changes? What do these changes bring BTW? Sorry, been out-of-touch these days :( No ETA for the CAM changes. I need to talk with Alexander Motin about it, and I haven't gotten around to that. Too busy with other things. The changes just allow the driver to get notification from CAM about read capacity data instead of having the driver probe by itself. The probe in the driver for stable is kludgy, but does work. So it is perfectly fine to run the driver in stable/9 or stable/8 without the CAM changes. The latest mps(4) driver changes have been merged into stable/9 and stable/8, so this would be a good time to try it out. Ken -- Kenneth Merry k...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: LSI supported mps(4) driver in stable/9 and stable/8
According to Kenneth D. Merry: So it is perfectly fine to run the driver in stable/9 or stable/8 without the CAM changes. Excellent, thank you Ken. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.freenix.fr In memoriam to Ondine : http://ondine.keltia.net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: LSI supported mps(4) driver in stable/9 and stable/8
Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello all. I am running FreeBSD 9.0 STABLE now, on a LSI 9211-8i controller and a 16 ports backplane identified as LSI CORP SAS2X28 0717 ses0 pass6 On FreeBSD 9.0RELEASE i have the following order. Seen from the front of the case. da3 da7 da11 da15 da2 da6 da10 da14 da1 da5 da9 da13 da0 da4 da8 da12 But now it has shuffled the order. da8 da 14 da12 da10 da9 da15 da13 da11 da1 da6 da2 da5 da0 da7 da3 da4 There is no logic at all, and it is very hard to figure out when a disk dies which one it is. regards Johan Hendriks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RE: LSI supported mps(4) driver in stable/9 and stable/8
-Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Monday, February 13, 2012 3:34 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello all. I am running FreeBSD 9.0 STABLE now, on a LSI 9211-8i controller and a 16 ports backplane identified as LSI CORP SAS2X28 0717 ses0 pass6 On FreeBSD 9.0RELEASE i have the following order. Seen from the front of the case. da3 da7 da11 da15 da2 da6 da10 da14 da1 da5 da9 da13 da0 da4 da8 da12 But now it has shuffled the order. da8 da 14 da12 da10 da9 da15 da13 da11 da1 da6 da2 da5 da0 da7 da3 da4 There is no logic at all, and it is very hard to figure out when a disk dies which one it is. Can you attach dmesg logs ? Basically now Drive will not ask CAM layer to add device using XPT_ASYC call. It will ask CAM layer to rescan the bus. So how CAM layer detects Drives is beyond Low level driver and it is obviously no guaranty of sequence of daX. If you have some X Drives attached to enclosure, target IDs of those Drive will be generated by Driver based on which mode mapping table is. 1. Enclosure slot mapping 2. Device mapping. For your case best choice will be Enclosure slot mapping. Assume you have Enclosure slop mapping. Target ID assignment is part of Driver which will consistence across all reboot. _but_ when Driver call rescan bus (as part of device add), it will scan bus in sequence and later peripher layer will assing device naming. So it is completely unsure which device will get what device name. e.a I have four Drive in Enclosure slot mapping Drive-A, Drive-B, Drive-C and Drive-D. (Consider alphabetical order is mapped to slot number ) So Driver will assign below target id. (target id 0-7 is reserved for local port of HBA) Drive- A Target ID -8 Drive- B Target ID -9 Drive- C Target ID -10 Drive- D Target ID -11 You cannot expect Drive-A will be assigned to da0. (and similar Drive-D will get da3). In summary, This behavior is visible just because of new change in driver, but it is never *must* follow condition for any driver. Device naming is part of CAM layer. regards Johan Hendriks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable- unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: LSI supported mps(4) driver in stable/9 and stable/8
Desai, Kashyap schreef: -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Monday, February 13, 2012 3:34 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello all. I am running FreeBSD 9.0 STABLE now, on a LSI 9211-8i controller and a 16 ports backplane identified as LSI CORP SAS2X28 0717 ses0 pass6 On FreeBSD 9.0RELEASE i have the following order. Seen from the front of the case. da3 da7 da11 da15 da2 da6 da10 da14 da1 da5 da9 da13 da0 da4 da8 da12 But now it has shuffled the order. da8 da 14 da12 da10 da9 da15 da13 da11 da1 da6 da2 da5 da0 da7 da3 da4 There is no logic at all, and it is very hard to figure out when a disk dies which one it is. Can you attach dmesg logs ? Basically now Drive will not ask CAM layer to add device using XPT_ASYC call. It will ask CAM layer to rescan the bus. So how CAM layer detects Drives is beyond Low level driver and it is obviously no guaranty of sequence of daX. If you have some X Drives attached to enclosure, target IDs of those Drive will be generated by Driver based on which mode mapping table is. 1. Enclosure slot mapping 2. Device mapping. For your case best choice will be Enclosure slot mapping. Assume you have Enclosure slop mapping. Target ID assignment is part of Driver which will consistence across all reboot. _but_ when Driver call rescan bus (as part of device add), it will scan bus in sequence and later peripher layer will assing device naming. So it is completely unsure which device will get what device name. e.a I have four Drive in Enclosure slot mapping Drive-A, Drive-B, Drive-C and Drive-D. (Consider alphabetical order is mapped to slot number ) So Driver will assign below target id. (target id 0-7 is reserved for local port of HBA) Drive- A Target ID -8 Drive- B Target ID -9 Drive- C Target ID -10 Drive- D Target ID -11 You cannot expect Drive-A will be assigned to da0. (and similar Drive-D will get da3). In summary, This behavior is visible just because of new change in driver, but it is never *must* follow condition for any driver. Device naming is part of CAM layer. regards Johan Hendriks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable- unsubscr...@freebsd.org Ok so it is not the mps driver who does the naming but cam, and that also has changed on 9.0 Stable. Well i use gpart labels for the pool, so i can use the gpart labels to yank the right disk. But it would be nicer if there was some kind of logic in the numbering of the devices. Here is the dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Mon Feb 13 10:22:44 CET 2012 root@filer01.testdomain.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC
RE: LSI supported mps(4) driver in stable/9 and stable/8
-Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Monday, February 13, 2012 4:42 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Monday, February 13, 2012 3:34 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello all. I am running FreeBSD 9.0 STABLE now, on a LSI 9211-8i controller and a 16 ports backplane identified as LSI CORP SAS2X28 0717 ses0 pass6 On FreeBSD 9.0RELEASE i have the following order. Seen from the front of the case. da3 da7 da11 da15 da2 da6 da10 da14 da1 da5 da9 da13 da0 da4 da8 da12 But now it has shuffled the order. da8 da 14 da12 da10 da9 da15 da13 da11 da1 da6 da2 da5 da0 da7 da3 da4 There is no logic at all, and it is very hard to figure out when a disk dies which one it is. Can you attach dmesg logs ? Basically now Drive will not ask CAM layer to add device using XPT_ASYC call. It will ask CAM layer to rescan the bus. So how CAM layer detects Drives is beyond Low level driver and it is obviously no guaranty of sequence of daX. If you have some X Drives attached to enclosure, target IDs of those Drive will be generated by Driver based on which mode mapping table is. 1. Enclosure slot mapping 2. Device mapping. For your case best choice will be Enclosure slot mapping. Assume you have Enclosure slop mapping. Target ID assignment is part of Driver which will consistence across all reboot. _but_ when Driver call rescan bus (as part of device add), it will scan bus in sequence and later peripher layer will assing device naming. So it is completely unsure which device will get what device name. e.a I have four Drive in Enclosure slot mapping Drive-A, Drive-B, Drive-C and Drive-D. (Consider alphabetical order is mapped to slot number ) So Driver will assign below target id. (target id 0-7 is reserved for local port of HBA) Drive- A Target ID -8 Drive- B Target ID -9 Drive- C Target ID -10 Drive- D Target ID -11 You cannot expect Drive-A will be assigned to da0. (and similar Drive- D will get da3). In summary, This behavior is visible just because of new change in driver, but it is never *must* follow condition for any driver. Device naming is part of CAM layer. regards Johan Hendriks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable- unsubscr...@freebsd.org Ok so it is not the mps driver who does the naming but cam, and that also has changed on 9.0 Stable. Nope... change is not in CAM, but Driver used rescan API instead of asynchronous reporting of device. At the end *YES* device naming is not guaranteed. Well i use gpart labels for the pool, so i can use the gpart labels to yank the right disk. But it would be nicer if there was some kind of logic in the numbering of the devices. Here is the dmesg
Re: LSI supported mps(4) driver in stable/9 and stable/8
On Mon, Feb 13, 2012 at 12:11:30PM +0100, Johan Hendriks wrote: Ok so it is not the mps driver who does the naming but cam, and that also has changed on 9.0 Stable. Well i use gpart labels for the pool, so i can use the gpart labels to yank the right disk. But it would be nicer if there was some kind of logic in the numbering of the devices. Wire them down in FreeBSD using loader.conf variables and this issue will cease to be a problem. Example is below, despite being for SATA with AHCI -- really doesn't matter, just change the appropriate bits and it should be fine for you. # Wire down device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # hint.scbus.0.at=ahcich0 hint.scbus.1.at=ahcich1 hint.scbus.2.at=ahcich2 hint.scbus.3.at=ahcich3 hint.scbus.4.at=ahcich4 hint.scbus.5.at=ahcich5 hint.ada.0.at=scbus0 hint.ada.1.at=scbus1 hint.ada.2.at=scbus2 hint.ada.3.at=scbus3 hint.ada.4.at=scbus4 hint.ada.5.at=scbus5 -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: LSI supported mps(4) driver in stable/9 and stable/8
On Mon, Feb 13, 2012 at 03:49:41AM -0800, Jeremy Chadwick wrote: On Mon, Feb 13, 2012 at 12:11:30PM +0100, Johan Hendriks wrote: Ok so it is not the mps driver who does the naming but cam, and that also has changed on 9.0 Stable. Well i use gpart labels for the pool, so i can use the gpart labels to yank the right disk. But it would be nicer if there was some kind of logic in the numbering of the devices. Wire them down in FreeBSD using loader.conf variables and this issue will cease to be a problem. Example is below, despite being for SATA with AHCI -- really doesn't matter, just change the appropriate bits and it should be fine for you. # Wire down device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # hint.scbus.0.at=ahcich0 hint.scbus.1.at=ahcich1 hint.scbus.2.at=ahcich2 hint.scbus.3.at=ahcich3 hint.scbus.4.at=ahcich4 hint.scbus.5.at=ahcich5 hint.ada.0.at=scbus0 hint.ada.1.at=scbus1 hint.ada.2.at=scbus2 hint.ada.3.at=scbus3 hint.ada.4.at=scbus4 hint.ada.5.at=scbus5 To be more specific: please see the CAM(4) man page and look at some of the example hint settings shown there. In your case I believe you'd want the below (which is a static map that matches your provided dmesg in the previous mail). If you want different device names tied to the different targets, it should be pretty obvious what to change. hint.scbus.0.at=mps0 hint.da.0.at=scbus0 hint.da.0.target=8 hint.da.0.unit=0 hint.da.1.at=scbus0 hint.da.1.target=9 hint.da.1.unit=0 hint.da.2.at=scbus0 hint.da.2.target=10 hint.da.2.unit=0 hint.da.3.at=scbus0 hint.da.3.target=11 hint.da.3.unit=0 hint.da.4.at=scbus0 hint.da.4.target=12 hint.da.4.unit=0 hint.da.5.at=scbus0 hint.da.5.target=13 hint.da.5.unit=0 hint.da.8.at=scbus0 hint.da.8.target=19 hint.da.8.unit=0 hint.da.9.at=scbus0 hint.da.9.target=20 hint.da.9.unit=0 hint.da.11.at=scbus0 hint.da.11.target=22 hint.da.11.unit=0 hint.da.12.at=scbus0 hint.da.12.target=23 hint.da.12.unit=0 hint.da.13.at=scbus0 hint.da.13.target=24 hint.da.13.unit=0 hint.da.14.at=scbus0 hint.da.14.target=27 hint.da.14.unit=0 hint.da.15.at=scbus0 hint.da.15.target=28 hint.da.15.unit=0 Naturally you can do the same for your AHCI controller bits too, though understand that each channel/port on the controller there matches to a separate scbusX unit, so you may want to start the numbering higher (in the case the LSI controller could ever have more scbusX entries added; e.g. LVMs or similar -- not sure how those are implemented there, but it doesn't matter, you get my drift I hope). -- | Jeremy Chadwick j...@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: LSI supported mps(4) driver in stable/9 and stable/8
Jeremy Chadwick schreef: On Mon, Feb 13, 2012 at 03:49:41AM -0800, Jeremy Chadwick wrote: On Mon, Feb 13, 2012 at 12:11:30PM +0100, Johan Hendriks wrote: Ok so it is not the mps driver who does the naming but cam, and that also has changed on 9.0 Stable. Well i use gpart labels for the pool, so i can use the gpart labels to yank the right disk. But it would be nicer if there was some kind of logic in the numbering of the devices. Wire them down in FreeBSD using loader.conf variables and this issue will cease to be a problem. Example is below, despite being for SATA with AHCI -- really doesn't matter, just change the appropriate bits and it should be fine for you. # Wire down device names (ada[0-5]) to each individual port # on the SATA/AHCI controller. This ensures that if we reboot # with a disk missing, the device names stay the same, and stay # attached to the same SATA/AHCI controller. # http://lists.freebsd.org/pipermail/freebsd-fs/2011-March/011036.html # hint.scbus.0.at=ahcich0 hint.scbus.1.at=ahcich1 hint.scbus.2.at=ahcich2 hint.scbus.3.at=ahcich3 hint.scbus.4.at=ahcich4 hint.scbus.5.at=ahcich5 hint.ada.0.at=scbus0 hint.ada.1.at=scbus1 hint.ada.2.at=scbus2 hint.ada.3.at=scbus3 hint.ada.4.at=scbus4 hint.ada.5.at=scbus5 To be more specific: please see the CAM(4) man page and look at some of the example hint settings shown there. In your case I believe you'd want the below (which is a static map that matches your provided dmesg in the previous mail). If you want different device names tied to the different targets, it should be pretty obvious what to change. hint.scbus.0.at=mps0 hint.da.0.at=scbus0 hint.da.0.target=8 hint.da.0.unit=0 hint.da.1.at=scbus0 hint.da.1.target=9 hint.da.1.unit=0 hint.da.2.at=scbus0 hint.da.2.target=10 hint.da.2.unit=0 hint.da.3.at=scbus0 hint.da.3.target=11 hint.da.3.unit=0 hint.da.4.at=scbus0 hint.da.4.target=12 hint.da.4.unit=0 hint.da.5.at=scbus0 hint.da.5.target=13 hint.da.5.unit=0 hint.da.8.at=scbus0 hint.da.8.target=19 hint.da.8.unit=0 hint.da.9.at=scbus0 hint.da.9.target=20 hint.da.9.unit=0 hint.da.11.at=scbus0 hint.da.11.target=22 hint.da.11.unit=0 hint.da.12.at=scbus0 hint.da.12.target=23 hint.da.12.unit=0 hint.da.13.at=scbus0 hint.da.13.target=24 hint.da.13.unit=0 hint.da.14.at=scbus0 hint.da.14.target=27 hint.da.14.unit=0 hint.da.15.at=scbus0 hint.da.15.target=28 hint.da.15.unit=0 Naturally you can do the same for your AHCI controller bits too, though understand that each channel/port on the controller there matches to a separate scbusX unit, so you may want to start the numbering higher (in the case the LSI controller could ever have more scbusX entries added; e.g. LVMs or similar -- not sure how those are implemented there, but it doesn't matter, you get my drift I hope). Thanks i will look into this, and the enclosure slot mapping. Thank you all for your time. And sorry for using this topic as it was not related. regards Johan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: LSI supported mps(4) driver in stable/9 and stable/8
According to Kenneth D. Merry: The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Thanks. Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. Got an ETA for this? Saying differently, is it reasonable to run stable/9 with the new driver but w/o the CAM changes? What do these changes bring BTW? Sorry, been out-of-touch these days :( Thanks. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- robe...@keltia.net In memoriam to Ondine, our 2nd child: http://ondine.keltia.net/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RE: LSI supported mps(4) driver in stable/9 and stable/8
There is one more instance of similar issue reported on freebsd-scsi mailing list. ~ Kashyap -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Desai, Kashyap Sent: Friday, February 03, 2012 10:59 PM To: Johan Hendriks Cc: freebsd-stable Subject: RE: LSI supported mps(4) driver in stable/9 and stable/8 -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 10:53 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 10:02 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Try attached patch.! (This patch is not taken against upstream code, so you may see some hunk fail.) ~ Kashyap -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 8:42 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Hi Johan, I have already figure out this issue in our lab. I also have fix for this issue. (Just don't want to create regression, that is why I have not posted outside) Since you have seen similar issue, It is worth to try my patch. My machine is not getting IP right now. I will send you patch once my machine is in network ? ~ Kashyap -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Friday, February 03, 2012 8:13 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist ATA WDC WD800JD-60LS 1D07 at scbus0 target 8 lun 0 (pass0,da0) ATA WDC WD800JD-60LS 1D07 at scbus0 target 9 lun 0 (pass1,da1) ATA WDC WD2500AAJS-6 2E25 at scbus0 target 10 lun 0 (pass2,da2) ATA WDC WD2500JS-60M 2E04 at scbus0 target 11 lun 0 (pass3,da3) ATA WDC WD2500JS-60M 2E04 at scbus0 target 12 lun 0 (pass4,da4) ATA ST3250620NS BJH at scbus0 target 13 lun 0 (pass5,da5) LSI CORP SAS2X28 0717 at scbus0 target 16 lun 0 (probe16,ses0,pass6) ATA Maxtor 6L080M0 1G10 at scbus0 target 17 lun 0 (pass7,da6) ATA Maxtor 6L080M0 1G10 at scbus0 target 18 lun 0 (pass8,da7) ATA WDC WD800JD-60LS
Re: LSI supported mps(4) driver in stable/9 and stable/8
Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist ATA WDC WD800JD-60LS 1D07at scbus0 target 8 lun 0 (pass0,da0) ATA WDC WD800JD-60LS 1D07at scbus0 target 9 lun 0 (pass1,da1) ATA WDC WD2500AAJS-6 2E25at scbus0 target 10 lun 0 (pass2,da2) ATA WDC WD2500JS-60M 2E04at scbus0 target 11 lun 0 (pass3,da3) ATA WDC WD2500JS-60M 2E04at scbus0 target 12 lun 0 (pass4,da4) ATA ST3250620NS BJH at scbus0 target 13 lun 0 (pass5,da5) LSI CORP SAS2X28 0717at scbus0 target 16 lun 0 (probe16,ses0,pass6) ATA Maxtor 6L080M0 1G10 at scbus0 target 17 lun 0 (pass7,da6) ATA Maxtor 6L080M0 1G10 at scbus0 target 18 lun 0 (pass8,da7) ATA WDC WD800JD-60LS 1D07at scbus0 target 19 lun 0 (pass9,da8) ATA WDC WD800JD-60LU 1D07at scbus0 target 20 lun 0 (pass10,da9) ATA GB0250EAFJF HPG6 at scbus0 target 21 lun 0 (pass11,da10) ATA ST3250620NS 3BJP at scbus0 target 22 lun 0 (pass12,da11) ATA ST3250620NS 3BJP at scbus0 target 23 lun 0 (pass13,da12) ATA ST3250620NS 3BJP at scbus0 target 24 lun 0 (pass14,da13) ATA ST3250310AS Bat scbus0 target 27 lun 0 (pass15,da14) ATA ST3250620NS 3BJP at scbus0 target 28 lun 0 (pass16,da15) ST3808110AS 3.AJJat scbus1 target 0 lun 0 (ada0,pass17) TSSTcorp CDDVDW SN-208BB SB00at scbus3 target 0 lun 0 (pass18,cd0) The controller is a LSI 9211-8i with IT firmware. here is the dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Fri Feb 3 10:27:18 CET 2012 root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x15bae3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,XSAVE,AVX AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2=0x1LAHF TSC: P-state invariant, performance statistics real memory = 17179869184 (16384 MB) avail memory = 16493441024 (15729 MB) Event timer LAPIC quality 600 ACPI APIC Table: SUPERM SMCI--MB FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 4 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 cpu2 (AP): APIC ID: 4 cpu3 (AP): APIC ID: 6 ioapic0 Version 2.0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: SUPERM SMCI--MB on motherboard acpi0: Power Button (fixed) Timecounter ACPI-fast frequency 3579545 Hz quality 900 acpi_timer0: 24-bit timer at 3.579545MHz port 0x408-0x40b on acpi0 cpu0: ACPI CPU on acpi0 cpu1: ACPI CPU on acpi0 cpu2: ACPI CPU on acpi0
RE: LSI supported mps(4) driver in stable/9 and stable/8
Hi Johan, I have already figure out this issue in our lab. I also have fix for this issue. (Just don't want to create regression, that is why I have not posted outside) Since you have seen similar issue, It is worth to try my patch. My machine is not getting IP right now. I will send you patch once my machine is in network ? ~ Kashyap -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Friday, February 03, 2012 8:13 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist ATA WDC WD800JD-60LS 1D07at scbus0 target 8 lun 0 (pass0,da0) ATA WDC WD800JD-60LS 1D07at scbus0 target 9 lun 0 (pass1,da1) ATA WDC WD2500AAJS-6 2E25at scbus0 target 10 lun 0 (pass2,da2) ATA WDC WD2500JS-60M 2E04at scbus0 target 11 lun 0 (pass3,da3) ATA WDC WD2500JS-60M 2E04at scbus0 target 12 lun 0 (pass4,da4) ATA ST3250620NS BJH at scbus0 target 13 lun 0 (pass5,da5) LSI CORP SAS2X28 0717at scbus0 target 16 lun 0 (probe16,ses0,pass6) ATA Maxtor 6L080M0 1G10 at scbus0 target 17 lun 0 (pass7,da6) ATA Maxtor 6L080M0 1G10 at scbus0 target 18 lun 0 (pass8,da7) ATA WDC WD800JD-60LS 1D07at scbus0 target 19 lun 0 (pass9,da8) ATA WDC WD800JD-60LU 1D07at scbus0 target 20 lun 0 (pass10,da9) ATA GB0250EAFJF HPG6 at scbus0 target 21 lun 0 (pass11,da10) ATA ST3250620NS 3BJP at scbus0 target 22 lun 0 (pass12,da11) ATA ST3250620NS 3BJP at scbus0 target 23 lun 0 (pass13,da12) ATA ST3250620NS 3BJP at scbus0 target 24 lun 0 (pass14,da13) ATA ST3250310AS Bat scbus0 target 27 lun 0 (pass15,da14) ATA ST3250620NS 3BJP at scbus0 target 28 lun 0 (pass16,da15) ST3808110AS 3.AJJat scbus1 target 0 lun 0 (ada0,pass17) TSSTcorp CDDVDW SN-208BB SB00at scbus3 target 0 lun 0 (pass18,cd0) The controller is a LSI 9211-8i with IT firmware. here is the dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Fri Feb 3 10:27:18 CET 2012 root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x15bae3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SS SE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,XSAVE,AVX
Re: LSI supported mps(4) driver in stable/9 and stable/8
Desai, Kashyap schreef: Hi Johan, I have already figure out this issue in our lab. I also have fix for this issue. (Just don't want to create regression, that is why I have not posted outside) Since you have seen similar issue, It is worth to try my patch. My machine is not getting IP right now. I will send you patch once my machine is in network ? ~ Kashyap -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Friday, February 03, 2012 8:13 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist ATA WDC WD800JD-60LS 1D07 at scbus0 target 8 lun 0 (pass0,da0) ATA WDC WD800JD-60LS 1D07 at scbus0 target 9 lun 0 (pass1,da1) ATA WDC WD2500AAJS-6 2E25 at scbus0 target 10 lun 0 (pass2,da2) ATA WDC WD2500JS-60M 2E04 at scbus0 target 11 lun 0 (pass3,da3) ATA WDC WD2500JS-60M 2E04 at scbus0 target 12 lun 0 (pass4,da4) ATA ST3250620NS BJH at scbus0 target 13 lun 0 (pass5,da5) LSI CORP SAS2X28 0717 at scbus0 target 16 lun 0 (probe16,ses0,pass6) ATA Maxtor 6L080M0 1G10 at scbus0 target 17 lun 0 (pass7,da6) ATA Maxtor 6L080M0 1G10 at scbus0 target 18 lun 0 (pass8,da7) ATA WDC WD800JD-60LS 1D07 at scbus0 target 19 lun 0 (pass9,da8) ATA WDC WD800JD-60LU 1D07 at scbus0 target 20 lun 0 (pass10,da9) ATA GB0250EAFJF HPG6 at scbus0 target 21 lun 0 (pass11,da10) ATA ST3250620NS 3BJP at scbus0 target 22 lun 0 (pass12,da11) ATA ST3250620NS 3BJP at scbus0 target 23 lun 0 (pass13,da12) ATA ST3250620NS 3BJP at scbus0 target 24 lun 0 (pass14,da13) ATA ST3250310AS B at scbus0 target 27 lun 0 (pass15,da14) ATA ST3250620NS 3BJP at scbus0 target 28 lun 0 (pass16,da15) ST3808110AS 3.AJJ at scbus1 target 0 lun 0 (ada0,pass17) TSSTcorp CDDVDW SN-208BB SB00 at scbus3 target 0 lun 0 (pass18,cd0) The controller is a LSI 9211-8i with IT firmware. here is the dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Fri Feb 3 10:27:18 CET 2012 root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU) Origin = GenuineIntel Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE ,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Features2=0x15bae3ffSSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SS SE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,POPCNT,TSCDLT,XSAVE,AVX AMD Features=0x28100800SYSCALL,NX,RDTSCP,LM AMD Features2
Re: LSI supported mps(4) driver in stable/9 and stable/8
Desai, Kashyap schreef: Try attached patch.! (This patch is not taken against upstream code, so you may see some hunk fail.) ~ Kashyap -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 8:42 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Hi Johan, I have already figure out this issue in our lab. I also have fix for this issue. (Just don't want to create regression, that is why I have not posted outside) Since you have seen similar issue, It is worth to try my patch. My machine is not getting IP right now. I will send you patch once my machine is in network ? ~ Kashyap -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Friday, February 03, 2012 8:13 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist ATA WDC WD800JD-60LS 1D07 at scbus0 target 8 lun 0 (pass0,da0) ATA WDC WD800JD-60LS 1D07 at scbus0 target 9 lun 0 (pass1,da1) ATA WDC WD2500AAJS-6 2E25 at scbus0 target 10 lun 0 (pass2,da2) ATA WDC WD2500JS-60M 2E04 at scbus0 target 11 lun 0 (pass3,da3) ATA WDC WD2500JS-60M 2E04 at scbus0 target 12 lun 0 (pass4,da4) ATA ST3250620NS BJHat scbus0 target 13 lun 0 (pass5,da5) LSI CORP SAS2X28 0717 at scbus0 target 16 lun 0 (probe16,ses0,pass6) ATA Maxtor 6L080M0 1G10at scbus0 target 17 lun 0 (pass7,da6) ATA Maxtor 6L080M0 1G10at scbus0 target 18 lun 0 (pass8,da7) ATA WDC WD800JD-60LS 1D07 at scbus0 target 19 lun 0 (pass9,da8) ATA WDC WD800JD-60LU 1D07 at scbus0 target 20 lun 0 (pass10,da9) ATA GB0250EAFJF HPG6 at scbus0 target 21 lun 0 (pass11,da10) ATA ST3250620NS 3BJP at scbus0 target 22 lun 0 (pass12,da11) ATA ST3250620NS 3BJP at scbus0 target 23 lun 0 (pass13,da12) ATA ST3250620NS 3BJP at scbus0 target 24 lun 0 (pass14,da13) ATA ST3250310AS B at scbus0 target 27 lun 0 (pass15,da14) ATA ST3250620NS 3BJP at scbus0 target 28 lun 0 (pass16,da15) ST3808110AS 3.AJJ at scbus1 target 0 lun 0 (ada0,pass17) TSSTcorp CDDVDW SN-208BB SB00 at scbus3 target 0 lun 0 (pass18,cd0) The controller is a LSI 9211-8i with IT firmware. here is the dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.0-STABLE #0: Fri Feb 3 10:27:18 CET 2012 root@filer01.neuteboom.local:/usr/obj/usr/src/sys/KRNL amd64 CPU: Intel(R) Xeon(R) CPU E31220 @ 3.10GHz (3093.04-MHz K8-class CPU
RE: LSI supported mps(4) driver in stable/9 and stable/8
-Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 10:02 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Try attached patch.! (This patch is not taken against upstream code, so you may see some hunk fail.) ~ Kashyap -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 8:42 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Hi Johan, I have already figure out this issue in our lab. I also have fix for this issue. (Just don't want to create regression, that is why I have not posted outside) Since you have seen similar issue, It is worth to try my patch. My machine is not getting IP right now. I will send you patch once my machine is in network ? ~ Kashyap -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Friday, February 03, 2012 8:13 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist ATA WDC WD800JD-60LS 1D07 at scbus0 target 8 lun 0 (pass0,da0) ATA WDC WD800JD-60LS 1D07 at scbus0 target 9 lun 0 (pass1,da1) ATA WDC WD2500AAJS-6 2E25 at scbus0 target 10 lun 0 (pass2,da2) ATA WDC WD2500JS-60M 2E04 at scbus0 target 11 lun 0 (pass3,da3) ATA WDC WD2500JS-60M 2E04 at scbus0 target 12 lun 0 (pass4,da4) ATA ST3250620NS BJHat scbus0 target 13 lun 0 (pass5,da5) LSI CORP SAS2X28 0717 at scbus0 target 16 lun 0 (probe16,ses0,pass6) ATA Maxtor 6L080M0 1G10at scbus0 target 17 lun 0 (pass7,da6) ATA Maxtor 6L080M0 1G10at scbus0 target 18 lun 0 (pass8,da7) ATA WDC WD800JD-60LS 1D07 at scbus0 target 19 lun 0 (pass9,da8) ATA WDC WD800JD-60LU 1D07 at scbus0 target 20 lun 0 (pass10,da9) ATA GB0250EAFJF HPG6 at scbus0 target 21 lun 0 (pass11,da10) ATA ST3250620NS 3BJP at scbus0 target 22 lun 0 (pass12,da11) ATA ST3250620NS 3BJP at scbus0 target 23 lun 0 (pass13,da12) ATA ST3250620NS 3BJP at scbus0 target 24 lun 0 (pass14,da13) ATA ST3250310AS B at scbus0 target 27 lun 0 (pass15,da14) ATA ST3250620NS 3BJP at scbus0 target 28 lun 0 (pass16,da15) ST3808110AS 3.AJJ at scbus1 target 0 lun 0 (ada0,pass17) TSSTcorp CDDVDW SN-208BB SB00 at scbus3 target 0 lun 0 (pass18,cd0) The controller is a LSI 9211-8i with IT firmware. here is the dmesg
Re: LSI supported mps(4) driver in stable/9 and stable/8
Desai, Kashyap schreef: -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 10:02 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Try attached patch.! (This patch is not taken against upstream code, so you may see some hunk fail.) ~ Kashyap -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 8:42 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Hi Johan, I have already figure out this issue in our lab. I also have fix for this issue. (Just don't want to create regression, that is why I have not posted outside) Since you have seen similar issue, It is worth to try my patch. My machine is not getting IP right now. I will send you patch once my machine is in network ? ~ Kashyap -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Friday, February 03, 2012 8:13 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist ATA WDC WD800JD-60LS 1D07 at scbus0 target 8 lun 0 (pass0,da0) ATA WDC WD800JD-60LS 1D07 at scbus0 target 9 lun 0 (pass1,da1) ATA WDC WD2500AAJS-6 2E25 at scbus0 target 10 lun 0 (pass2,da2) ATA WDC WD2500JS-60M 2E04 at scbus0 target 11 lun 0 (pass3,da3) ATA WDC WD2500JS-60M 2E04 at scbus0 target 12 lun 0 (pass4,da4) ATA ST3250620NS BJH at scbus0 target 13 lun 0 (pass5,da5) LSI CORP SAS2X28 0717 at scbus0 target 16 lun 0 (probe16,ses0,pass6) ATA Maxtor 6L080M0 1G10 at scbus0 target 17 lun 0 (pass7,da6) ATA Maxtor 6L080M0 1G10 at scbus0 target 18 lun 0 (pass8,da7) ATA WDC WD800JD-60LS 1D07 at scbus0 target 19 lun 0 (pass9,da8) ATA WDC WD800JD-60LU 1D07 at scbus0 target 20 lun 0 (pass10,da9) ATA GB0250EAFJF HPG6at scbus0 target 21 lun 0 (pass11,da10) ATA ST3250620NS 3BJPat scbus0 target 22 lun 0 (pass12,da11) ATA ST3250620NS 3BJPat scbus0 target 23 lun 0 (pass13,da12) ATA ST3250620NS 3BJPat scbus0 target 24 lun 0 (pass14,da13) ATA ST3250310AS B at scbus0 target 27 lun 0 (pass15,da14) ATA ST3250620NS 3BJPat scbus0 target 28 lun 0 (pass16,da15) ST3808110AS 3.AJJ at scbus1 target 0 lun 0 (ada0,pass17) TSSTcorp CDDVDW SN-208BB SB00 at scbus3 target 0 lun 0 (pass18,cd0) The controller is a LSI 9211-8i with IT firmware. here is the dmesg Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University
RE: LSI supported mps(4) driver in stable/9 and stable/8
-Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 10:53 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 10:02 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Try attached patch.! (This patch is not taken against upstream code, so you may see some hunk fail.) ~ Kashyap -Original Message- From: Johan Hendriks [mailto:joh.hendr...@gmail.com] Sent: Friday, February 03, 2012 8:42 PM To: Desai, Kashyap Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Desai, Kashyap schreef: Hi Johan, I have already figure out this issue in our lab. I also have fix for this issue. (Just don't want to create regression, that is why I have not posted outside) Since you have seen similar issue, It is worth to try my patch. My machine is not getting IP right now. I will send you patch once my machine is in network ? ~ Kashyap -Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- sta...@freebsd.org] On Behalf Of Johan Hendriks Sent: Friday, February 03, 2012 8:13 PM To: Kenneth D. Merry Cc: freebsd-stable Subject: Re: LSI supported mps(4) driver in stable/9 and stable/8 Kenneth D. Merry schreef: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken Hello Ken. Just updated our 16 bay server. did a csup today. did try some commands, it looked like the drives got husseled. But after giving the command camcontrol rescan all it does not give back the prompt. Also top shows me the following. 1589 root1 200 16384K 1376K cbwait 3 0:00 0.00% camcontrol # on another console things works filer01# camcontrol devlist ATA WDC WD800JD-60LS 1D07 at scbus0 target 8 lun 0 (pass0,da0) ATA WDC WD800JD-60LS 1D07 at scbus0 target 9 lun 0 (pass1,da1) ATA WDC WD2500AAJS-6 2E25 at scbus0 target 10 lun 0 (pass2,da2) ATA WDC WD2500JS-60M 2E04 at scbus0 target 11 lun 0 (pass3,da3) ATA WDC WD2500JS-60M 2E04 at scbus0 target 12 lun 0 (pass4,da4) ATA ST3250620NS BJH at scbus0 target 13 lun 0 (pass5,da5) LSI CORP SAS2X28 0717 at scbus0 target 16 lun 0 (probe16,ses0,pass6) ATA Maxtor 6L080M0 1G10 at scbus0 target 17 lun 0 (pass7,da6) ATA Maxtor 6L080M0 1G10 at scbus0 target 18 lun 0 (pass8,da7) ATA WDC WD800JD-60LS 1D07 at scbus0 target 19 lun 0 (pass9,da8) ATA WDC WD800JD-60LU 1D07 at scbus0 target 20 lun 0 (pass10,da9) ATA GB0250EAFJF HPG6at scbus0 target 21 lun 0 (pass11,da10) ATA ST3250620NS 3BJPat scbus0 target 22 lun 0 (pass12,da11) ATA ST3250620NS 3BJPat scbus0 target 23 lun 0 (pass13,da12) ATA ST3250620NS 3BJPat scbus0 target 24 lun 0 (pass14,da13) ATA ST3250310AS B at scbus0 target 27 lun 0 (pass15,da14) ATA ST3250620NS
LSI supported mps(4) driver in stable/9 and stable/8
Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! Note that the CAM infrastructure changes that went into FreeBSD/head along with this driver have not gone into either stable/9 or stable/8. Only the driver itself has been merged. The CAM infrastructure changes depend on some other da(4) driver changes that will need to get merged before they can go back. If that merge happens, it will probably only be into stable/9. A couple of notes about issues with this driver: - Unlike the previous mps(4) driver, it probes sequentially. If you have a lot of drives in your system, it will take a while to probe them all. - You may see warning messages like this: _mapping_add_new_device: failed to add the device with handle 0x0019 to persiste nt table because there is no free space available _mapping_add_new_device: failed to add the device with handle 0x001a to persiste nt table because there is no free space available - The driver is not endian safe. (It assumes a little endian machine.) This is not new, the previous version of the driver had the same issue. The LSI folks know about these issues. The driver has passed their testing process. Many thanks to LSI for going through the effort to support FreeBSD. Ken -- Kenneth Merry k...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: LSI supported mps(4) driver in stable/9 and stable/8
Kenneth D. Merry wrote: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! snip can you elaborate on what the symptoms would be before this commit for the 6Bg cards? i have a dual channel LSI card (i can get the exact model tomorrow) connected to a RAID Inc Maverick 8 disk array (one raid6 volume was created on the Mav) which constantly gets hung up with messages similar to: run_interrupt_driven_hooks - waiting for xpt_config every 60 seconds for about 5 iterations after which the box reboots. I am currently trying 9-RELEASE, but saw the same issues on 8.2. These messages happen after the USB stack initializes. Turning off the Maverick allows the system to boot up. i can then turn on the maverick after the system gets to the login prompt and the disks are detected as da0 and work just fine. the LSI device was detected as mpt0. many thanks! Eric ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: LSI supported mps(4) driver in stable/9 and stable/8
On Thu, Feb 02, 2012 at 20:13:55 -0700, Eric wrote: Kenneth D. Merry wrote: Hi folks, The LSI-supported version of the mps(4) driver that supports their 6Gb SAS HBAs as well as WarpDrive controllers, is now in stable/9 and stable/8. Please test it out and let me and Kashyap (CCed) know if you run into any problems. In addition to supporting WarpDrive, the driver also supports Integrated RAID. Thanks to LSI for doing the work on this driver! snip can you elaborate on what the symptoms would be before this commit for the 6Bg cards? i have a dual channel LSI card (i can get the exact model tomorrow) connected to a RAID Inc Maverick 8 disk array (one raid6 volume was created on the Mav) which constantly gets hung up with messages similar to: run_interrupt_driven_hooks - waiting for xpt_config every 60 seconds for about 5 iterations after which the box reboots. I am currently trying 9-RELEASE, but saw the same issues on 8.2. These messages happen after the USB stack initializes. Turning off the Maverick allows the system to boot up. i can then turn on the maverick after the system gets to the login prompt and the disks are detected as da0 and work just fine. the LSI device was detected as mpt0. If you've got an mpt(4) controller, the new driver won't help you. You've got a 3Gb LSI controller, and the mps(4) driver is for 6Gb controllers. It sounds like the mpt driver is getting stuck on boot. Ken -- Kenneth Merry k...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
