gfjardim Posted April 28, 2012 Share Posted April 28, 2012 This are the kernel change logs related to the mpt2sas driver: Kernel 3.0.5 commit e670d472aaaa51f93a5a49de00dc573eea8a8486 Author: Kashyap, Desai <[email protected]> Date: Tue Jun 14 10:57:31 2011 +0530 mpt2sas: Adding support for customer specific branding commit ab3e5f60d1fc8fe725d02510ff820ff207a8dbef upstream. Signed-off-by: Kashyap Desai <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit db1f8f788b108fa627f011355ff9ba5e3e789fa6 Author: Kashyap, Desai <[email protected]> Date: Tue Jun 14 10:57:08 2011 +0530 mpt2sas: Added DID_NO_CONNECT return when driver remove and avoid shutdown call commit 7821578caa8cb831868989041112ab808029ca65 upstream. Driver should not call shutdown call from _scsih_remove otherwise, The scsi midlayer can be deadlocked when devices are removed from the driver pci_driver->shutdown handler. Signed-off-by: Kashyap Desai <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Kernel 3.0.9 commit ac310457b4fd7634983788faf0c4f29cd2d5384b Author: [email protected] <[email protected]> Date: Fri Oct 21 10:06:33 2011 +0530 mpt2sas: Fix for system hang when discovery in progress commit 0167ac67ff6f35bf2364f7672c8012b0cd40277f upstream. Fix for issue : While discovery is in progress, hot unplug and hot plug of enclosure connected to the controller card is causing system to hang. When a device is in the process of being detected at driver load time then if it is removed, the device that is no longer present will not be added to the list. So the code in _scsih_probe_sas() is rearranged as such so the devices that failed to be detected are not added to the list. Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Kernel 3.0.16 commit fca54d03a85e883b813255c63bbf11049d2eeb7a Author: Nagalakshmi Nandigama <[email protected]> Date: Wed Jan 4 09:25:13 2012 -0600 mpt2sas: fix non-x86 crash on shutdown Upstrem commit: 911ae9434f83e7355d343f6c2be3ef5b00ea7aed There's a bug in the MSIX backup and restore routines that cause a crash on non-x86 (direct access to PCI space not via read/write). These routines are unnecessary and were removed by the above commit, so also remove them from stable to fix the crash. Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit e57a4c768c03a91334759def503b2d7616028a35 Author: Anton Blanchard <[email protected]> Date: Mon Nov 7 22:05:21 2011 +1100 SCSI: mpt2sas: _scsih_smart_predicted_fault uses GFP_KERNEL in interrupt context commit f6a290b419a2675c4b77a6b0731cd2a64332365e upstream. _scsih_smart_predicted_fault is called in an interrupt and therefore must allocate memory using GFP_ATOMIC. Signed-off-by: Anton Blanchard <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Kernel 3.0.17 commit 18366c3fed0c372f9c123489e7061de11b640965 Author: [email protected] <[email protected]> Date: Thu Aug 4 16:47:50 2011 +0530 SCSI: mpt2sas: Added missing mpt2sas_base_detach call from scsih_remove context commit 9ae89b0296e275d5a556068b40b7c2557a556a85 upstream. mpt2sas_base_detach() call was removed from _scsih_remove() while doing some code shuffling. Mainly when we work on adding code for scsih_shutdown(). I have added back mpt2sas_base_detach() which will get callled from _scsih_remove(). Signed-off-by: Kashyap Desai <[email protected]> Signed-off-by: James Bottomley <[email protected]> Kernel 3.0.18 commit 73669debb5f508962ffcc8b632ffb2971c606e5c Author: [email protected] <[email protected]> Date: Thu Dec 1 07:53:08 2011 +0530 SCSI: mpt2sas : Fix for memory allocation error for large host credits commit aff132d95ffe14eca96cab90597cdd010b457af7 upstream. The amount of memory required for tracking chain buffers is rather large, and when the host credit count is big, memory allocation failure occurs inside __get_free_pages. The fix is to limit the number of chains to 100,000. In addition, the number of host credits is limited to 30,000 IOs. However this limitation can be overridden this using the command line option max_queue_depth. The algorithm for calculating the reply_post_queue_depth is changed so that it is equal to (reply_free_queue_depth + 16), previously it was (reply_free_queue_depth * 2). Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit de3f88ba084473ce5365632f0209c3e95aeb55e9 Author: [email protected] <[email protected]> Date: Thu Dec 1 07:52:56 2011 +0530 SCSI: mpt2sas: Release spinlock for the raid device list before blocking it commit 30c43282f3d347f47f9e05199d2b14f56f3f2837 upstream. Added code to release the spinlock that is used to protect the raid device list before calling a function that can block. The blocking was causing a reschedule, and subsequently it is tried to acquire the same lock, resulting in a panic (NMI Watchdog detecting a CPU lockup). Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Quote Link to comment
gfjardim Posted April 28, 2012 Author Share Posted April 28, 2012 Kernel 3.1 commit 2e00d24e7ebae3183aeab0f958ea1142d1af3a02 Author: Kashyap, Desai <[email protected]> Date: Tue Jun 14 10:57:51 2011 +0530 [sCSI] mpt2sas: Bump version 09.100.00.00 Signed-off-by: Kashyap Desai <[email protected]> Signed-off-by: James Bottomley <[email protected]> commit ab3e5f60d1fc8fe725d02510ff820ff207a8dbef Author: Kashyap, Desai <[email protected]> Date: Tue Jun 14 10:57:31 2011 +0530 [sCSI] mpt2sas: Adding support for customer specific branding Signed-off-by: Kashyap Desai <[email protected]> Signed-off-by: James Bottomley <[email protected]> commit 7821578caa8cb831868989041112ab808029ca65 Author: Kashyap, Desai <[email protected]> Date: Tue Jun 14 10:57:08 2011 +0530 [sCSI] mpt2sas: Added DID_NO_CONNECT return when driver remove and avoid shutdown call Driver should not call shutdown call from _scsih_remove otherwise, The scsi midlayer can be deadlocked when devices are removed from the driver pci_driver->shutdown handler. Signed-off-by: Kashyap Desai <[email protected]> Signed-off-by: James Bottomley <[email protected]> commit f93213de5c28d4aeda51b3c03daf7e27f6dd2b7a Author: Kashyap, Desai <[email protected]> Date: Tue Jun 14 10:56:43 2011 +0530 [sCSI] mpt2sas: fix broadcast AEN and task management issue Properly handling of target reset in multi-initiator environment Clean up in broadcast change handling: (1) Need to look at the status of each task management request, and retry the TM when there are failures. (2) Need quiescence IO so the driver doesn't take on more IO request while it's in the middle of sending TM request to firmware (3) Add support to keep track of how many pending broadcast AEN events are received while the broadcast handling is active, then loop back at the end of this routine if there were any events received. Clean up in mpt2sas_scsih_issue_tm routine: (1) Make sure proper status is returned when host reset fails (2) Clean up sanity checks near end of routine, insuring all outstanding IOs were completed. Signed-off-by: Kashyap Desai <[email protected]> Signed-off-by: James Bottomley <[email protected]> commit a3e1e55e4b5ca4d49618c592b4d10814e21e12a7 Author: Kashyap, Desai <[email protected]> Date: Tue Jun 14 10:56:12 2011 +0530 [sCSI] mpt2sas: Set max_sector count from module parameter This feature is to override the default max_sectors setting at load time, taking max_sectors as an command line option when loading the driver. The setting is currently hard-coded in the driver to 8192 sectors (4MB transfers). If max_sectors is specified at load time, minimum specified setting will be 64, and the maximum is 8192. The driver will modify the setting to be on even boundary. If max_sectors is not specified, the driver will default to 8192. Signed-off-by: Kashyap Desai <[email protected]> Signed-off-by: James Bottomley <[email protected]> commit ce7b1810def1e2f0101931f8f339f9d8a694cd19 Author: Kashyap, Desai <[email protected]> Date: Tue Jun 14 10:55:45 2011 +0530 [sCSI] mpt2sas MPI next revision header update mpt2sas driver revision q header update: (1) Modified the descriptions of the LocalAddress bit in the Flags field of the MPI SGE Format description and the MPI Simple Element. (2) Modified Data Location Address Space bits in the Flags field of the IEEE Chain Element. (3) Added more detail to the description of the DataLength field for the SCSI IO Request and Target Assist Request. Removed restriction on using chained SGLs when using multicast or bidirectional support. (4) In Manufacturing Page 7, added ReceptacleID field to ConnectorInfo, and reworked how the Pinout field is used. (5) In IO Unit Page 7, added BoardTemperature and BoardTemperatureUnits fields. (6) In IOC Page 1, changed CoalescingTimeout to units of half-microsecond and updated descriptions. (7) Modified descriptions of SATASlumberTimeout and SASSlumberTimeout fields in SAS IO Unit Page 5 to indicate the timers start after partial mode is entered. ( Added Extended Manufacturing configuration pages. Signed-off-by: Kashyap Desai <[email protected]> Signed-off-by: James Bottomley <[email protected]> commit c97951ec46d4b076c2236b77db34eeed6dddb8eb Author: Kashyap, Desai <[email protected]> Date: Tue Jun 14 10:54:56 2011 +0530 [sCSI] mpt2sas: Fixed Big Indian Issues on 32 bit PPC This patch addresses many endian issues solved by runing sparse with the option __CHECK_ENDIAN__ turned on. Signed-off-by: Kashyap Desai <[email protected]> Signed-off-by: James Bottomley <[email protected]> commit d7e01dc669e3f69d396ce3972ba87b7d678a94e4 Author: Abhijeet Joglekar <[email protected]> Date: Mon Jun 13 21:21:17 2011 -0700 [sCSI] fnic: Update Maintainers list for fnic. Signed-off-by: Abhijeet Joglekar <[email protected]> Signed-off-by: James Bottomley <[email protected]> commit 82a452581230b3ffc9d6475dffdb2568497b5fec Author: Kashyap, Desai <[email protected]> Date: Tue Jul 5 12:40:23 2011 +0530 [sCSI] mpt2sas: WarpDrive Infinite command retries due to wrong scsi command entry in MPI message Issue: This issue is seen on LSI H/W WarpDrive SSS6200 When filed direct I/O is tried as volume I/O the scmd field in internal lookup table get cleared and because of that the retried volume I/O never gets reported as completed to SML. Result: I/O timeout and Error handling thread will kicking off Fix: Setting back the scmd in the lookup table before retrying the failed direct i/o Signed-off-by: Kashyap Desai <[email protected]> Signed-off-by: James Bottomley <[email protected]> Kernel 3.1.1 commit 218782d30177214893625e8d6523191caa5e023b Author: [email protected] <[email protected]> Date: Fri Oct 21 10:06:33 2011 +0530 mpt2sas: Fix for system hang when discovery in progress commit 0167ac67ff6f35bf2364f7672c8012b0cd40277f upstream. Fix for issue : While discovery is in progress, hot unplug and hot plug of enclosure connected to the controller card is causing system to hang. When a device is in the process of being detected at driver load time then if it is removed, the device that is no longer present will not be added to the list. So the code in _scsih_probe_sas() is rearranged as such so the devices that failed to be detected are not added to the list. Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Quote Link to comment
gfjardim Posted April 28, 2012 Author Share Posted April 28, 2012 Kernel 3.1.8 commit ec89dadb52f3dee5e49588613ad3bf66cf140141 Author: Nagalakshmi Nandigama <[email protected]> Date: Wed Jan 4 09:25:13 2012 -0600 mpt2sas: fix non-x86 crash on shutdown Upstrem commit: 911ae9434f83e7355d343f6c2be3ef5b00ea7aed There's a bug in the MSIX backup and restore routines that cause a crash on non-x86 (direct access to PCI space not via read/write). These routines are unnecessary and were removed by the above commit, so also remove them from stable to fix the crash. Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit 4c9ddbf69e5d6ea938804af78df524ea08535c63 Author: Anton Blanchard <[email protected]> Date: Mon Nov 7 22:05:21 2011 +1100 SCSI: mpt2sas: _scsih_smart_predicted_fault uses GFP_KERNEL in interrupt context commit f6a290b419a2675c4b77a6b0731cd2a64332365e upstream. _scsih_smart_predicted_fault is called in an interrupt and therefore must allocate memory using GFP_ATOMIC. Signed-off-by: Anton Blanchard <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Kernel 3.1.10 commit a1f73f501a775496d33b4da523b09f64b6962251 Author: [email protected] <[email protected]> Date: Thu Dec 1 07:53:08 2011 +0530 SCSI: mpt2sas : Fix for memory allocation error for large host credits commit aff132d95ffe14eca96cab90597cdd010b457af7 upstream. The amount of memory required for tracking chain buffers is rather large, and when the host credit count is big, memory allocation failure occurs inside __get_free_pages. The fix is to limit the number of chains to 100,000. In addition, the number of host credits is limited to 30,000 IOs. However this limitation can be overridden this using the command line option max_queue_depth. The algorithm for calculating the reply_post_queue_depth is changed so that it is equal to (reply_free_queue_depth + 16), previously it was (reply_free_queue_depth * 2). Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit 3e70c2626382037b67c97a706cb00788fad93527 Author: [email protected] <[email protected]> Date: Thu Dec 1 07:52:56 2011 +0530 SCSI: mpt2sas: Release spinlock for the raid device list before blocking it commit 30c43282f3d347f47f9e05199d2b14f56f3f2837 upstream. Added code to release the spinlock that is used to protect the raid device list before calling a function that can block. The blocking was causing a reschedule, and subsequently it is tried to acquire the same lock, resulting in a panic (NMI Watchdog detecting a CPU lockup). Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Kernel 3.2.2 commit 312544d8eac340d3ada92dbd2c60c63d229fbcf6 Author: [email protected] <[email protected]> Date: Thu Dec 1 07:53:08 2011 +0530 SCSI: mpt2sas : Fix for memory allocation error for large host credits commit aff132d95ffe14eca96cab90597cdd010b457af7 upstream. The amount of memory required for tracking chain buffers is rather large, and when the host credit count is big, memory allocation failure occurs inside __get_free_pages. The fix is to limit the number of chains to 100,000. In addition, the number of host credits is limited to 30,000 IOs. However this limitation can be overridden this using the command line option max_queue_depth. The algorithm for calculating the reply_post_queue_depth is changed so that it is equal to (reply_free_queue_depth + 16), previously it was (reply_free_queue_depth * 2). Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> commit 7af050182f68de53d4c323367c793c580e956041 Author: [email protected] <[email protected]> Date: Thu Dec 1 07:52:56 2011 +0530 SCSI: mpt2sas: Release spinlock for the raid device list before blocking it commit 30c43282f3d347f47f9e05199d2b14f56f3f2837 upstream. Added code to release the spinlock that is used to protect the raid device list before calling a function that can block. The blocking was causing a reschedule, and subsequently it is tried to acquire the same lock, resulting in a panic (NMI Watchdog detecting a CPU lockup). Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Kernel 3.2.3 commit 4ad2f9e91b23962fe309787512497e2092f6326c Author: [email protected] <[email protected]> Date: Tue Dec 13 09:29:15 2011 +0530 mpt2sas: Removed redundant calling of _scsih_probe_devices() from _scsih_probe commit 2cb6fc8c014b9b00c4487a79b8f6ed0da4121f45 upstream. Removed redundant calling of _scsih_probe_devices() from _scsih_probe as it is getting called from _scsih_scan_finished. Also moved the function scsi_scan_host(shost) to get called after the volumes on warp drive are reported to the OS. Otherwise by the time the (ioc->hide_drives) flags is set, the volumes on warp drive are reported to the OS already. Also modified the initialization of reply queues only in case of driver load time in the function _base_make_ioc_operational(). Signed-off-by: Nagalakshmi Nandigama <[email protected]> Signed-off-by: James Bottomley <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]> Hope this helps Quote Link to comment
gfjardim Posted April 28, 2012 Author Share Posted April 28, 2012 Some research about hdparm: http://kerneltrap.org/mailarchive/linux-scsi/2010/8/31/6886348/thread https://bugzilla.redhat.com/show_bug.cgi?id=548263 https://bugzilla.redhat.com/show_bug.cgi?id=609134 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/906873 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.