Re: `rmmod mpt3sas` leads to backtraces 'fs/sysfs/group.c:237 sysfs_remove_group+0xa0/0xb0'
Hi, ses module was not built/loaded in my tests (ENCLOSURE_SERVICES was not set in the kernel config), so it's not the case. Also Oracle bug is private, so I can't tell if it's really related. //wbr ojab On Thu, Oct 20, 2016 at 10:08 AM, Chaitra Basappa wrote: > Hi Ojab, > > I would like to clarify that issue is not because of the below mentioned > patch/ mpt3sas driver, its due to some SES module patch which we have seen > earlier without merged/combined (mpt2sas & mpt3sas) driver too. > > > > So before unloading driver try unloading ses module(`rmmod ses`) and then > unload driver, driver unloads successfully. > > > > This confirms issue is not because of driver , so ses module patches needs > to be checked to identify the patch causing this issue. > > > > Also we have reported below Bug with oracle , which we observed on > OEL6.8_UEK(4.1.12-37.4.1_x86_64) > > https://bugzilla.oracle.com/bugzilla/show_bug.cgi?id=15521 > > > > Thanks, > > Chaitra > > > > > > From: mpt-fusionlinux@broadcom.com > [mailto:mpt-fusionlinux@broadcom.com] On Behalf Of Laurence Oberman > Sent: Tuesday, October 18, 2016 4:42 AM > To: ojab; Johannes Thumshirn > Cc: mpt-fusionlinux@broadcom.com; linux-scsi@vger.kernel.org > Subject: RE: `rmmod mpt3sas` leads to backtraces 'fs/sysfs/group.c:237 > sysfs_remove_group+0xa0/0xb0' > > > > > > > > > > > > Sent on the new Sprint Network from my Samsung Galaxy S®4 > > > > ---- Original message ---- > From: ojab > Date: 10/17/2016 17:11 (GMT-05:00) > To: Johannes Thumshirn > Cc: mpt-fusionlinux@broadcom.com, linux-scsi@vger.kernel.org > Subject: Re: `rmmod mpt3sas` leads to backtraces 'fs/sysfs/group.c:237 > sysfs_remove_group+0xa0/0xb0' > > On 2016/10/17 14:42, Johannes Thumshirn wrote: >> On Sun, Oct 16, 2016 at 02:33:28PM +, ojab wrote: >> >> Hi Ojab, >> >> Do you have a known good kernel? If yes can you do a git bisect to see >> which >> commit introduces this? >> >> Thanks, >> Johannes >> > > The issue is reproducible from the start, i. e. from commit > > c84b06a48c4d8ac8270624453132f3fa1a4a0f9d mpt3sas: Single driver module > which supports both SAS 2.0 & SAS 3.0 HBAs > > in which support for my HBA was added. > Before that the same issue can be reproduced using mpt2sas module in > kernels >= 4.1. > > Unfortunately earlier kernels fail to boot on my HW, so I can't > investigate further. > > //wbr ojab > > I have one of these in my lab. I will investigate and try reproduce and > track it down as soon as I get a chance. > > > > Thanks > > -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: `rmmod mpt3sas` leads to backtraces 'fs/sysfs/group.c:237 sysfs_remove_group+0xa0/0xb0'
On 2016/10/17 14:42, Johannes Thumshirn wrote: On Sun, Oct 16, 2016 at 02:33:28PM +, ojab wrote: Hi Ojab, Do you have a known good kernel? If yes can you do a git bisect to see which commit introduces this? Thanks, Johannes The issue is reproducible from the start, i. e. from commit c84b06a48c4d8ac8270624453132f3fa1a4a0f9d mpt3sas: Single driver module which supports both SAS 2.0 & SAS 3.0 HBAs in which support for my HBA was added. Before that the same issue can be reproduced using mpt2sas module in kernels >= 4.1. Unfortunately earlier kernels fail to boot on my HW, so I can't investigate further. //wbr ojab -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: `rmmod mpt3sas` leads to backtraces 'fs/sysfs/group.c:237 sysfs_remove_group+0xa0/0xb0'
On Sun, Oct 16, 2016 at 02:33:28PM +, ojab wrote: > Oh hai! > > I have LSI SAS 9217-8i HBA and `rmmod mpt3sas` leads to multiple backtraces > if any disks are connected to the HBA. > Reproducible on vanilla 4.7.5/4.8.1/4.9-rc1 kernels (haven't tested on > another versions). > > Full output (4.9-rc1 kernel, 3*Seagate ST3000NM0023 drives are connected) is > rather long and can be found here: > https://gist.github.com/ojab/f21ff778a378e88b227a4253d683c6ca Hi Ojab, Do you have a known good kernel? If yes can you do a git bisect to see which commit introduces this? Thanks, Johannes -- Johannes Thumshirn Storage jthumsh...@suse.de+49 911 74053 689 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: Felix Imendörffer, Jane Smithard, Graham Norton HRB 21284 (AG Nürnberg) Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850 -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: `rmmod mpt3sas` leads to backtraces 'fs/sysfs/group.c:237 sysfs_remove_group+0xa0/0xb0'
On 2016/10/16 14:33, ojab wrote:
Oh hai!
I have LSI SAS 9217-8i HBA and `rmmod mpt3sas` leads to multiple
backtraces if any disks are connected to the HBA.
Reproducible on vanilla 4.7.5/4.8.1/4.9-rc1 kernels (haven't tested on
another versions).
Full output (4.9-rc1 kernel, 3*Seagate ST3000NM0023 drives are
connected) is rather long and can be found here:
https://gist.github.com/ojab/f21ff778a378e88b227a4253d683c6ca
…and also on boot I have an error than can be related to the backtrace:
>…
>[Sun Oct 16 18:46:12 2016] sdd: sdd1
>[Sun Oct 16 18:46:12 2016] sd 6:0:1:0: [sdd] Attached SCSI disk
>[Sun Oct 16 18:46:12 2016] udevd[239]: error opening
ATTR{/sys/devices/pci:00/:00:03.0/:02:00.0/host6/scsi_host/host6/link_power_management_policy}
for writing: Permission denied
>…
There is no such file in sysfs after boot completion.
//wbr ojab
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
