RE: mps module compilation issue on FreeBSD-9 amd64
> -Original Message- > From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd- > sta...@freebsd.org] On Behalf Of Desai, Kashyap > Sent: Monday, January 30, 2012 2:45 PM > To: freebsd-sta...@freebsd.org; freebsd-current@freebsd.org > Cc: gi...@freebsd.org; Kenneth D. Merry; McConnell, Stephen > Subject: mps module compilation issue on FreeBSD-9 amd64 > > Hi, > > I am seeing some uncommon problem while doing compilation of mps driver > (this is a latest driver from LSI). > > Here are the steps I followed. > > CASE-1 > > 1. remove mps directory from sys/dev and sys/module and overwrite those > two directories with my latest code. > 2. go to sys/module/mps and run "make". [Things works fine.] > > CASE-2. > 1. remove mps directory from sys/dev and sys/module and overwrite those > two directories with my latest code. > 2. go to main directory ( In my case it is "/usr/trees/9.0.0") > 3. Run below command > make -j8 buildkernel KERNCONF=GENERIC MODULES_OVERRIDE=mps > TARGET_ARCH=amd64 SYSDIR=/usr/trees/9.0.0/sys -DNO_CLEAN - > DNO_KERNELCONFIG -DNO_KERNELCLEAN -DNO_KERNELDEPEND > > Here I am seeing mps.ko file is generated, but it is failing at kernel.debug> steps. (this step is only seen in CASE-1). Typo: It should be this step is only seen in CASE-2. Also, I have first finished buildworld before I tried mps (LSI driver) compilation. > Any Idea How to resolve this issue ? > > INFO: I am using FreeBSD-8.2-Release amd64.case-1 and case-2 both passes > for i386. > > --- Compilation failure log for CASE-2 > > ld -d -warn-common -r -d -o mpslsi.ko.debug mps_pci.o mps.o mps_sas.o > mps_table.o mps_user.o mps_config.o mps_mapping.o mps_sas_lsi.o > :> export_syms > awk -f /usr/trees/9.0.0/sys/conf/kmod_syms.awk mpslsi.ko.debug > export_syms | xargs -J% objcopy % mpslsi.ko.debug > /usr/local/bin/svnversion > objcopy --only-keep-debug mpslsi.ko.debug mpslsi.ko.symbols > objcopy --strip-debug --add-gnu-debuglink=mpslsi.ko.symbols > mpslsi.ko.debug mpslsi.ko > cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g - > Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing- > prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer- > sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show- > option -nostdinc -I. -I/usr/trees/9.0.0/sys - > I/usr/trees/9.0.0/sys/contrib/altq -D_KERNEL - > DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline- > limit=8000 --param inline-unit-growth=100 --param large-function- > growth=1000 -fno-omit-frame-pointer -mno-sse -mcmodel=kernel -mno-red- > zone -mno-mmx -msoft-float -fno-asynchronous-unwind-tables - > ffreestanding -fstack-protector -Werror vers.c > linking kernel.debug > mps.o: In function `mps_startup': > /usr/trees/9.0.0/sys/dev/mps/mps.c:1249: undefined reference to > `mps_mapping_initialize' > mps.o: In function `mps_free': > /usr/trees/9.0.0/sys/dev/mps/mps.c:1410: undefined reference to > `mps_mapping_free_memory' > mps.o: In function `mps_attach': > /usr/trees/9.0.0/sys/dev/mps/mps.c:1204: undefined reference to > `mps_base_static_config_pages' > /usr/trees/9.0.0/sys/dev/mps/mps.c:1224: undefined reference to > `mpssas_ir_shutdown' > mps_sas.o: In function `mps_attach_sas': > /usr/trees/9.0.0/sys/dev/mps/mps_sas.c:614: undefined reference to > `mpssas_firmware_event_work' > mps_sas.o: In function `mpssas_register_events': > /usr/trees/9.0.0/sys/dev/mps/mps_sas.c:576: undefined reference to > `mpssas_evt_handler' > mps_sas.o: In function `mpssas_portenable_complete': > /usr/trees/9.0.0/sys/dev/mps/mps_sas.c:3069: undefined reference to > `mps_wd_config_pages' > mps_user.o: In function `mps_user_btdh': > /usr/trees/9.0.0/sys/dev/mps/mps_user.c:2038: undefined reference to > `mps_mapping_get_sas_id_from_handle' > mps_user.o: In function `mps_user_get_adapter_data': > /usr/trees/9.0.0/sys/dev/mps/mps_user.c:1101: undefined reference to > `mps_config_get_bios_pg3' > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > Failed : make -j8 buildkernel KERNCONF=GENERIC MODULES_OVERRIDE=mps > TARGET_ARCH=amd64 SYSDIR=/usr/trees/9.0.0/sys -DNO_CLEAN - > DNO_KERNELCONFIG -DNO_KERNELCLEAN -DNO_KERNELDEPEND > ___ > freebsd-sta...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable- > unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
mps module compilation issue on FreeBSD-9 amd64
Hi, I am seeing some uncommon problem while doing compilation of mps driver (this is a latest driver from LSI). Here are the steps I followed. CASE-1 1. remove mps directory from sys/dev and sys/module and overwrite those two directories with my latest code. 2. go to sys/module/mps and run "make". [Things works fine.] CASE-2. 1. remove mps directory from sys/dev and sys/module and overwrite those two directories with my latest code. 2. go to main directory ( In my case it is "/usr/trees/9.0.0") 3. Run below command make -j8 buildkernel KERNCONF=GENERIC MODULES_OVERRIDE=mps TARGET_ARCH=amd64 SYSDIR=/usr/trees/9.0.0/sys -DNO_CLEAN -DNO_KERNELCONFIG -DNO_KERNELCLEAN -DNO_KERNELDEPEND Here I am seeing mps.ko file is generated, but it is failing at steps. (this step is only seen in CASE-1). Any Idea How to resolve this issue ? INFO: I am using FreeBSD-8.2-Release amd64.case-1 and case-2 both passes for i386. --- Compilation failure log for CASE-2 ld -d -warn-common -r -d -o mpslsi.ko.debug mps_pci.o mps.o mps_sas.o mps_table.o mps_user.o mps_config.o mps_mapping.o mps_sas_lsi.o :> export_syms awk -f /usr/trees/9.0.0/sys/conf/kmod_syms.awk mpslsi.ko.debug export_syms | xargs -J% objcopy % mpslsi.ko.debug /usr/local/bin/svnversion objcopy --only-keep-debug mpslsi.ko.debug mpslsi.ko.symbols objcopy --strip-debug --add-gnu-debuglink=mpslsi.ko.symbols mpslsi.ko.debug mpslsi.ko cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -g -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -nostdinc -I. -I/usr/trees/9.0.0/sys -I/usr/trees/9.0.0/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-omit-frame-pointer -mno-sse -mcmodel=kernel -mno-red-zone -mno-mmx -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror vers.c linking kernel.debug mps.o: In function `mps_startup': /usr/trees/9.0.0/sys/dev/mps/mps.c:1249: undefined reference to `mps_mapping_initialize' mps.o: In function `mps_free': /usr/trees/9.0.0/sys/dev/mps/mps.c:1410: undefined reference to `mps_mapping_free_memory' mps.o: In function `mps_attach': /usr/trees/9.0.0/sys/dev/mps/mps.c:1204: undefined reference to `mps_base_static_config_pages' /usr/trees/9.0.0/sys/dev/mps/mps.c:1224: undefined reference to `mpssas_ir_shutdown' mps_sas.o: In function `mps_attach_sas': /usr/trees/9.0.0/sys/dev/mps/mps_sas.c:614: undefined reference to `mpssas_firmware_event_work' mps_sas.o: In function `mpssas_register_events': /usr/trees/9.0.0/sys/dev/mps/mps_sas.c:576: undefined reference to `mpssas_evt_handler' mps_sas.o: In function `mpssas_portenable_complete': /usr/trees/9.0.0/sys/dev/mps/mps_sas.c:3069: undefined reference to `mps_wd_config_pages' mps_user.o: In function `mps_user_btdh': /usr/trees/9.0.0/sys/dev/mps/mps_user.c:2038: undefined reference to `mps_mapping_get_sas_id_from_handle' mps_user.o: In function `mps_user_get_adapter_data': /usr/trees/9.0.0/sys/dev/mps/mps_user.c:1101: undefined reference to `mps_config_get_bios_pg3' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error Failed : make -j8 buildkernel KERNCONF=GENERIC MODULES_OVERRIDE=mps TARGET_ARCH=amd64 SYSDIR=/usr/trees/9.0.0/sys -DNO_CLEAN -DNO_KERNELCONFIG -DNO_KERNELCLEAN -DNO_KERNELDEPEND ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: LSI supported mps(4) driver available
> -Original Message- > From: owner-freebsd-s...@freebsd.org [mailto:owner-freebsd- > s...@freebsd.org] On Behalf Of Stas Orlov > Sent: Thursday, February 02, 2012 6:48 PM > To: Kenneth D. Merry > Cc: freebsd-s...@freebsd.org; freebsd-current@freebsd.org; Dennis > Glatting > Subject: Re: LSI supported mps(4) driver available > > Hi, > > We have a pack of identical Dell R610 mahcines with H200 cards. > > pciconf from R610 with FreeBSD9 on ZFS, disks in JBOD mode. > > mps0@pci0:3:0:0:class=0x010700 card=0x1f1e1028 chip=0x00721000 > rev=0x02 hdr=0x00 > vendor = 'LSI Logic / Symbios Logic' > device = 'SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]' > class = mass storage > subclass = SAS > bar [10] = type I/O Port, range 32, base 0xfc00, size 256, > enabled > bar [14] = type Memory, range 64, base 0xdf2b, size 65536, > enabled > bar [1c] = type Memory, range 64, base 0xdf2c, size 262144, > enabled > cap 01[50] = powerspec 3 supports D0 D1 D2 D3 current D0 > cap 10[68] = PCI-Express 2 endpoint max data 128(4096) link x4(x8) > cap 03[d0] = VPD > cap 05[a8] = MSI supports 1 message, 64 bit > cap 11[c0] = MSI-X supports 15 messages in map 0x14 enabled > > > We all aware of the state of things with the old mps driver, so I tried > to > pass a hardware array with the new one. > Current snapshot from yesterday fails with following - > http://oi40.tinypic.com/25gdw8o.jpg Can you explain more about your setup and how to reproduce it ? I will have look on this issue if it is reproducible ? Also what is Firmware version you are using on H200 card ? ~ Kashyap > > iirc, Dell has a nasty habit of writing its own firmware. > > > On Thu, Jan 26, 2012 at 8:54 AM, Kenneth D. Merry > wrote: > > > On Wed, Jan 25, 2012 at 20:47:37 -0800, Dennis Glatting wrote: > > > On Fri, 2012-01-20 at 13:44 -0700, Kenneth D. Merry wrote: > > > > The LSI-supported version of the mps(4) driver that supports their > 6Gb > > SAS > > > > HBAs as well as WarpDrive controllers, is available here: > > > > > > > > http://people.freebsd.org/~ken/lsi/mps_lsi.20120120.1.txt > > > > > > > > I plan to check it in to head next week, and then MFC it into > stable/9 > > a > > > > week after that most likely. > > > > > > > > Please test it out and let me 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! > > > > > > > > > > Does this include the SAS2008 series chips? I have two systems, one > a > > > Tyan FT48-B8812 with a S8812 MB and Interlagos chips, where I am > > > interested in using a driver under 9.0 amd64. > > > > Yes. The driver in 9.0 supports the 2008 as well. > > > > Ken > > -- > > Kenneth Merry > > k...@freebsd.org > > ___ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current- > unsubscr...@freebsd.org" > > > ___ > freebsd-s...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: LSI supported mps(4) driver available
From: Stas Orlov [mailto:senn...@gmail.com] Sent: Thursday, February 02, 2012 7:45 PM To: Desai, Kashyap Cc: Kenneth D. Merry; freebsd-s...@freebsd.org; freebsd-current@freebsd.org; Dennis Glatting Subject: Re: LSI supported mps(4) driver available Sure, I've made two RAID (1 and 10 ) arrays within LSI Config Utility and tried to install fresh current, every time I get error linked above, so yes, it's reproducible. -> What I understood here is, you have two raid volumes RAID1 and RAID10, and trying to install FreeBSD (Again clarify which version of FreeBSD you are using) Try erasing a controller FW completely and re-install everything from fresh. (Here make sure you flash completely. Hope you are aware of controller firmware upgrade process) Our board has DPM tables and for Raid volume it is maximum 2 entry. When you have more than two inactive volumes, we cannot add another raid volume. There is some implementation recently done by BIOS team related to this area. Where BIOS itself will erase inactive Raid volume entry from DPM pages. ~ Kashyap MPT Firmware 2.15.63.00-IR Package Version 7.01.33.00 I do have another spare R610 with that card, I'll test it with current later this evening. On Thu, Feb 2, 2012 at 5:53 PM, Desai, Kashyap wrote: > -Original Message- > From: owner-freebsd-s...@freebsd.org [mailto:owner-freebsd- > s...@freebsd.org] On Behalf Of Stas Orlov > Sent: Thursday, February 02, 2012 6:48 PM > To: Kenneth D. Merry > Cc: freebsd-s...@freebsd.org; freebsd-current@freebsd.org; Dennis > Glatting > Subject: Re: LSI supported mps(4) driver available > > Hi, > > We have a pack of identical Dell R610 mahcines with H200 cards. > > pciconf from R610 with FreeBSD9 on ZFS, disks in JBOD mode. > > mps0@pci0:3:0:0: class=0x010700 card=0x1f1e1028 chip=0x00721000 > rev=0x02 hdr=0x00 > vendor = 'LSI Logic / Symbios Logic' > device = 'SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]' > class = mass storage > subclass = SAS > bar [10] = type I/O Port, range 32, base 0xfc00, size 256, > enabled > bar [14] = type Memory, range 64, base 0xdf2b, size 65536, > enabled > bar [1c] = type Memory, range 64, base 0xdf2c, size 262144, > enabled > cap 01[50] = powerspec 3 supports D0 D1 D2 D3 current D0 > cap 10[68] = PCI-Express 2 endpoint max data 128(4096) link x4(x8) > cap 03[d0] = VPD > cap 05[a8] = MSI supports 1 message, 64 bit > cap 11[c0] = MSI-X supports 15 messages in map 0x14 enabled > > > We all aware of the state of things with the old mps driver, so I tried > to > pass a hardware array with the new one. > Current snapshot from yesterday fails with following - > http://oi40.tinypic.com/25gdw8o.jpg Can you explain more about your setup and how to reproduce it ? I will have look on this issue if it is reproducible ? Also what is Firmware version you are using on H200 card ? ~ Kashyap > > iirc, Dell has a nasty habit of writing its own firmware. > > > On Thu, Jan 26, 2012 at 8:54 AM, Kenneth D. Merry > wrote: > > > On Wed, Jan 25, 2012 at 20:47:37 -0800, Dennis Glatting wrote: > > > On Fri, 2012-01-20 at 13:44 -0700, Kenneth D. Merry wrote: > > > > The LSI-supported version of the mps(4) driver that supports their > 6Gb > > SAS > > > > HBAs as well as WarpDrive controllers, is available here: > > > > > > > > http://people.freebsd.org/~ken/lsi/mps_lsi.20120120.1.txt > > > > > > > > I plan to check it in to head next week, and then MFC it into > stable/9 > > a > > > > week after that most likely. > > > > > > > > Please test it out and let me 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! > > > > > > > > > > Does this include the SAS2008 series chips? I have two systems, one > a > > > Tyan FT48-B8812 with a S8812 MB and Interlagos chips, where I am > > > interested in using a driver under 9.0 amd64. > > > > Yes. The driver in 9.0 supports the 2008 as well. > > > > Ken > > -- > > Kenneth Merry > > k...@freebsd.org > > ___ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to "freebsd-current- > unsubscr...@freebsd.org" > > > ___ > freebsd-s...@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: LSI supported mps(4) driver available
From: Stas Orlov [mailto:senn...@gmail.com] Sent: Thursday, February 02, 2012 8:29 PM To: Desai, Kashyap Cc: Kenneth D. Merry; freebsd-s...@freebsd.org; freebsd-current@freebsd.org; Dennis Glatting Subject: Re: LSI supported mps(4) driver available >> (Again clarify which version of FreeBSD you are using) As I've stated earlier it's current snapshot from the other day, to be more specific FreeBSD10-CURRENT r230857 Ok, I'll try to upgrade firmware. On Thu, Feb 2, 2012 at 6:43 PM, Desai, Kashyap wrote: >> Can you switch your mail client to default reply. It is always turning into html format and difficult for inline reply. I have done some analysis on of your logs provided at "http://oi40.tinypic.com/25gdw8o.jpg"; 1. it seems Driver is somehow not handling error condition which should be better handled at driver. e.a driver does not reinit HBA if any config request time out. I will add this feature sometime later, since I have some more item queued up as well. 2. Your logs mentioned there are three different handled got from FW to add as Bare Drive. (it is not a volume entry) So just curious to know why those entries are coming as bare drive. ? (do you have any other bare drives in your topology ? ) ` Kashyap From: Stas Orlov [mailto:senn...@gmail.com] Sent: Thursday, February 02, 2012 7:45 PM To: Desai, Kashyap Cc: Kenneth D. Merry; freebsd-s...@freebsd.org; freebsd-current@freebsd.org; Dennis Glatting Subject: Re: LSI supported mps(4) driver available Sure, I've made two RAID (1 and 10 ) arrays within LSI Config Utility and tried to install fresh current, every time I get error linked above, so yes, it's reproducible. -> What I understood here is, you have two raid volumes RAID1 and RAID10, and trying to install FreeBSD (Again clarify which version of FreeBSD you are using) Try erasing a controller FW completely and re-install everything from fresh. (Here make sure you flash completely. Hope you are aware of controller firmware upgrade process) Our board has DPM tables and for Raid volume it is maximum 2 entry. When you have more than two inactive volumes, we cannot add another raid volume. There is some implementation recently done by BIOS team related to this area. Where BIOS itself will erase inactive Raid volume entry from DPM pages. ~ Kashyap MPT Firmware 2.15.63.00-IR Package Version 7.01.33.00 I do have another spare R610 with that card, I'll test it with current later this evening. On Thu, Feb 2, 2012 at 5:53 PM, Desai, Kashyap wrote: > -Original Message- > From: owner-freebsd-s...@freebsd.org [mailto:owner-freebsd- > s...@freebsd.org] On Behalf Of Stas Orlov > Sent: Thursday, February 02, 2012 6:48 PM > To: Kenneth D. Merry > Cc: freebsd-s...@freebsd.org; freebsd-current@freebsd.org; Dennis > Glatting > Subject: Re: LSI supported mps(4) driver available > > Hi, > > We have a pack of identical Dell R610 mahcines with H200 cards. > > pciconf from R610 with FreeBSD9 on ZFS, disks in JBOD mode. > > mps0@pci0:3:0:0: class=0x010700 card=0x1f1e1028 chip=0x00721000 > rev=0x02 hdr=0x00 > vendor = 'LSI Logic / Symbios Logic' > device = 'SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon]' > class = mass storage > subclass = SAS > bar [10] = type I/O Port, range 32, base 0xfc00, size 256, > enabled > bar [14] = type Memory, range 64, base 0xdf2b, size 65536, > enabled > bar [1c] = type Memory, range 64, base 0xdf2c, size 262144, > enabled > cap 01[50] = powerspec 3 supports D0 D1 D2 D3 current D0 > cap 10[68] = PCI-Express 2 endpoint max data 128(4096) link x4(x8) > cap 03[d0] = VPD > cap 05[a8] = MSI supports 1 message, 64 bit > cap 11[c0] = MSI-X supports 15 messages in map 0x14 enabled > > > We all aware of the state of things with the old mps driver, so I tried > to > pass a hardware array with the new one. > Current snapshot from yesterday fails with following - > http://oi40.tinypic.com/25gdw8o.jpg Can you explain more about your setup and how to reproduce it ? I will have look on this issue if it is reproducible ? Also what is Firmware version you are using on H200 card ? ~ Kashyap > > iirc, Dell has a nasty habit of writing its own firmware. > > > On Thu, Jan 26, 2012 at 8:54 AM, Kenneth D. Merry > wrote: > > > On Wed, Jan 25, 2012 at 20:47:37 -0800, Dennis Glatting wrote: > > > On Fri, 2012-01-20 at 13:44 -0700, Kenneth D. Merry wrote: > > > > The LSI-supported version of the mps(4) driver that supports their > 6Gb > > SAS > > > > HBAs as well as WarpDrive controllers, is available here: > > > > > > > > http://people.freebsd.org/~ken/lsi/mps_lsi.20120120.1.txt >
RE: LSI supported mps(4) driver available
> -Original Message- > From: Stas Orlov [mailto:senn...@gmail.com] > Sent: Monday, February 06, 2012 11:54 PM > To: Desai, Kashyap > Cc: Kenneth D. Merry; freebsd-s...@freebsd.org; freebsd- > curr...@freebsd.org; Dennis Glatting > Subject: Re: LSI supported mps(4) driver available > > Sorry for the swarm of screenshots :) > > Spare drive should be a iDRAC Virtual usb. > > On that particular machine, as I said, two RAID arrays (1 and 10) Is this all SATA drives part of your raid1 and raid10 ? > > http://oi39.tinypic.com/10hlfmg.jpg -- they initialized as they should. > > http://oi43.tinypic.com/2db83g8.jpg -- loader recognizes 3 disks (3rd > one is the iDRAC usb as I suppose) > > So, I flashed the FW and installed the latest one from Dell > (7.15.08.00 \ 7.03.05.00), and things have gone slightly better. > > http://oi39.tinypic.com/69dtuq.jpg -- controller . > > http://oi44.tinypic.com/10s6jxi.jpg -- still. > I am debugging this issue. ! I can understand the issue, but not sure how to progress. Do you willing to make more test with my debug builds ? Here In my setup I am not able to reproduce the issue. ~ Kashyap > http://oi42.tinypic.com/ipmh37.jpg -- It boots in single user, in > multiuser it prints probe errors, skips them and hang on the daemon > startup. > > http://oi43.tinypic.com/13yhz02.jpg -- in single user they > initialized\UFSed\mounted just fine. > > To sum everything up, FW upgrade helped, still some device handle > errors and SCSI errors, hangs in multiuser-mode(may or may not be > related). > > Tested with the same FreeBSD10-CURRENT r230857, I saw ken@'s commit to > -STABLE and will try it somewhere tomorrow. > Thanks for your time:) > > > On Fri, Feb 3, 2012 at 12:10 PM, Desai, Kashyap > wrote: > > > > > > From: Stas Orlov [mailto:senn...@gmail.com] > > Sent: Thursday, February 02, 2012 8:29 PM > > To: Desai, Kashyap > > Cc: Kenneth D. Merry; freebsd-s...@freebsd.org; freebsd- > curr...@freebsd.org; Dennis Glatting > > Subject: Re: LSI supported mps(4) driver available > > > >>> (Again clarify which version of FreeBSD you are using) > > > > As I've stated earlier it's current snapshot from the other day, to be > more specific FreeBSD10-CURRENT r230857 > > > > Ok, I'll try to upgrade firmware. > > On Thu, Feb 2, 2012 at 6:43 PM, Desai, Kashyap > wrote: > > > > > >>> > > Can you switch your mail client to default reply. It is > always turning into html format and difficult for inline reply. > > I have done some analysis on of your logs provided at > "http://oi40.tinypic.com/25gdw8o.jpg"; > > > > 1. it seems Driver is somehow not handling error condition which > should be better handled at driver. > > e.a driver does not reinit HBA if any config request time out. > > I will add this feature sometime later, since I have some more item > queued up as well. > > 2. Your logs mentioned there are three different handled got from FW > to add as Bare Drive. (it is not a volume entry) > > So just curious to know why those entries are coming as bare drive. ? > (do you have any other bare drives in your topology ? ) > > > > > > ` Kashyap > > > > From: Stas Orlov [mailto:senn...@gmail.com] > > Sent: Thursday, February 02, 2012 7:45 PM > > To: Desai, Kashyap > > Cc: Kenneth D. Merry; freebsd-s...@freebsd.org; freebsd- > curr...@freebsd.org; Dennis Glatting > > Subject: Re: LSI supported mps(4) driver available > > Sure, I've made two RAID (1 and 10 ) arrays within LSI Config Utility > and tried to install fresh current, every time I get error linked above, > so yes, it's reproducible. > > -> What I understood here is, you have two raid volumes RAID1 and > RAID10, and trying to install FreeBSD (Again clarify which version of > FreeBSD you are using) > > > > > > Try erasing a controller FW completely and re-install everything from > fresh. > > (Here make sure you flash completely. Hope you are aware of controller > firmware upgrade process) > > > > Our board has DPM tables and for Raid volume it is maximum 2 entry. > > When you have more than two inactive volumes, we cannot add another > raid volume. > > There is some implementation recently done by BIOS team related to > this area. Where BIOS itself will erase inactive Raid volume entry from > DPM pages. > > > > ~ Kashyap > > > > > > MPT Firmware 2.15.63.00-IR > > Package Version 7.01.33.00 > > > > I do have another spare R610 with that card, I'll test it with curre
RE: LSI supported mps(4) driver available
Can you to reproduce issue with below mentioned changes..
In mps.c
mps_get_tunables(struct mps_softc *sc)
{
char tmpstr[80];
/* XXX default to some debugging for now */
sc->mps_debug = MPS_FAULT;
Instead of above line make
sc->mps_debug = 0xd;
This will dump debug prints on screen at the time of boot itself.
~ Kashyap
> -Original Message-
> From: owner-freebsd-curr...@freebsd.org [mailto:owner-freebsd-
> curr...@freebsd.org] On Behalf Of Desai, Kashyap
> Sent: Tuesday, February 07, 2012 8:37 PM
> To: Stas Orlov
> Cc: freebsd-s...@freebsd.org; freebsd-current@freebsd.org; Kenneth D.
> Merry; Dennis Glatting
> Subject: RE: LSI supported mps(4) driver available
>
>
>
> > -Original Message-
> > From: Stas Orlov [mailto:senn...@gmail.com]
> > Sent: Monday, February 06, 2012 11:54 PM
> > To: Desai, Kashyap
> > Cc: Kenneth D. Merry; freebsd-s...@freebsd.org; freebsd-
> > curr...@freebsd.org; Dennis Glatting
> > Subject: Re: LSI supported mps(4) driver available
> >
> > Sorry for the swarm of screenshots :)
> >
> > Spare drive should be a iDRAC Virtual usb.
> >
> > On that particular machine, as I said, two RAID arrays (1 and 10)
>
> Is this all SATA drives part of your raid1 and raid10 ?
>
> >
> > http://oi39.tinypic.com/10hlfmg.jpg -- they initialized as they
> should.
> >
> > http://oi43.tinypic.com/2db83g8.jpg -- loader recognizes 3 disks (3rd
> > one is the iDRAC usb as I suppose)
> >
> > So, I flashed the FW and installed the latest one from Dell
> > (7.15.08.00 \ 7.03.05.00), and things have gone slightly better.
> >
> > http://oi39.tinypic.com/69dtuq.jpg -- controller .
> >
> > http://oi44.tinypic.com/10s6jxi.jpg -- still.
> >
>
> I am debugging this issue. ! I can understand the issue, but not sure
> how to progress.
> Do you willing to make more test with my debug builds ?
>
> Here In my setup I am not able to reproduce the issue.
>
> ~ Kashyap
>
> > http://oi42.tinypic.com/ipmh37.jpg -- It boots in single user, in
> > multiuser it prints probe errors, skips them and hang on the daemon
> > startup.
> >
> > http://oi43.tinypic.com/13yhz02.jpg -- in single user they
> > initialized\UFSed\mounted just fine.
> >
> > To sum everything up, FW upgrade helped, still some device handle
> > errors and SCSI errors, hangs in multiuser-mode(may or may not be
> > related).
> >
> > Tested with the same FreeBSD10-CURRENT r230857, I saw ken@'s commit to
> > -STABLE and will try it somewhere tomorrow.
> > Thanks for your time:)
>
> >
> >
> > On Fri, Feb 3, 2012 at 12:10 PM, Desai, Kashyap
> >
> > wrote:
> > >
> > >
> > > From: Stas Orlov [mailto:senn...@gmail.com]
> > > Sent: Thursday, February 02, 2012 8:29 PM
> > > To: Desai, Kashyap
> > > Cc: Kenneth D. Merry; freebsd-s...@freebsd.org; freebsd-
> > curr...@freebsd.org; Dennis Glatting
> > > Subject: Re: LSI supported mps(4) driver available
> > >
> > >>> (Again clarify which version of FreeBSD you are using)
> > >
> > > As I've stated earlier it's current snapshot from the other day, to
> > > be
> > more specific FreeBSD10-CURRENT r230857
> > >
> > > Ok, I'll try to upgrade firmware.
> > > On Thu, Feb 2, 2012 at 6:43 PM, Desai, Kashyap
> > >
> > wrote:
> > >
> > >
> > >>>
> > > Can you switch your mail client to default reply. It is
> > always turning into html format and difficult for inline reply.
> > > I have done some analysis on of your logs provided at
> > "http://oi40.tinypic.com/25gdw8o.jpg";
> > >
> > > 1. it seems Driver is somehow not handling error condition which
> > should be better handled at driver.
> > > e.a driver does not reinit HBA if any config request time out.
> > > I will add this feature sometime later, since I have some more
> > > item
> > queued up as well.
> > > 2. Your logs mentioned there are three different handled got from FW
> > to add as Bare Drive. (it is not a volume entry)
> > > So just curious to know why those entries are coming as bare drive.
> ?
> > (do you have any other bare drives in your topology ? )
> > >
> > >
> > > ` Kashyap
> > >
> > > From: Stas Orlov [mailto:senn...@gmail.com]
> > > Sent: Thursday, February 02, 2012 7:45 PM
> > > To: Desai, Kashyap
> > > Cc: Kenneth D. Merry; freebsd-s...
RE: LSI supported mps(4) driver available
> -Original Message-
> From: Kenneth D. Merry [mailto:k...@freebsd.org]
> Sent: Tuesday, February 07, 2012 10:30 PM
> To: Desai, Kashyap
> Cc: Stas Orlov; freebsd-s...@freebsd.org; freebsd-current@freebsd.org;
> Dennis Glatting
> Subject: Re: LSI supported mps(4) driver available
>
> On Tue, Feb 07, 2012 at 21:00:28 +0530, Desai, Kashyap wrote:
> > Can you to reproduce issue with below mentioned changes..
> >
> > In mps.c
> >
> > mps_get_tunables(struct mps_softc *sc)
> > {
> > char tmpstr[80];
> >
> > /* XXX default to some debugging for now */
> > sc->mps_debug = MPS_FAULT;
> >
> > Instead of above line make
> > sc->mps_debug = 0xd;
>
> You can also put the following in /boot/loader.conf:
>
> hw.mps.debug_level=0xd
Thanks.! This Is what I was trying since last week, but somehow I did not
entered correct syntax.
>
> Ken
> --
> Kenneth Merry
> k...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
RE: LSI supported mps(4) driver available
> -Original Message-
> From: Stas Orlov [mailto:senn...@gmail.com]
> Sent: Sunday, February 12, 2012 11:01 PM
> To: Desai, Kashyap
> Cc: Kenneth D. Merry; freebsd-s...@freebsd.org; freebsd-
> curr...@freebsd.org; Dennis Glatting
> Subject: Re: LSI supported mps(4) driver available
>
> I build r231557 Current, with recent mps changes, and sc->mps_debug =
> 0xd;
>
> It actually gets to the installer, refuses to boot from raid1 after
> default installation, though.
>
> Complete dmesg attached.
Very quick observation :
You have total six Driver attached in your system.
I guess you have 2 Drive part of Raid-1 and 4 Driver part of Raid-10.
Out of those six Drive, one drive is detected as "1.5Gbps" (see below part in
dmesg log)
PHY[8].AttachedDevHandle: 0x0009
PHY[8].LinkRate: 1.5Gbps (0x80)
PHY[8].PhyStatus: NewTargetAdde
LSI IR does not support mix of mix of different link speed Drivers in a single
Volume.
I am not sure if this is root cause of the issue, but definetly worth to try
why that Particular drive is
At 1.5 Gbps link ?
Can you try to see if it is cable which is causing link to 1.5 OR Drive itself
has 1.5 Gbps max speed. ?
` Kashyap
>
> On Wed, Feb 8, 2012 at 1:42 PM, Desai, Kashyap
> wrote:
> >
> >
> >> -Original Message-
> >> From: Kenneth D. Merry [mailto:k...@freebsd.org]
> >> Sent: Tuesday, February 07, 2012 10:30 PM
> >> To: Desai, Kashyap
> >> Cc: Stas Orlov; freebsd-s...@freebsd.org;
> >> freebsd-current@freebsd.org; Dennis Glatting
> >> Subject: Re: LSI supported mps(4) driver available
> >>
> >> On Tue, Feb 07, 2012 at 21:00:28 +0530, Desai, Kashyap wrote:
> >> > Can you to reproduce issue with below mentioned changes..
> >> >
> >> > In mps.c
> >> >
> >> > mps_get_tunables(struct mps_softc *sc) {
> >> > char tmpstr[80];
> >> >
> >> > /* XXX default to some debugging for now */
> >> > sc->mps_debug = MPS_FAULT;
> >> >
> >> > Instead of above line make
> >> > sc->mps_debug = 0xd;
> >>
> >> You can also put the following in /boot/loader.conf:
> >>
> >> hw.mps.debug_level=0xd
> >
> > Thanks.! This Is what I was trying since last week, but somehow I did
> not entered correct syntax.
> >
> >
> >>
> >> Ken
> >> --
> >> Kenneth Merry
> >> k...@freebsd.org
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
