Re: `rmmod mpt3sas` leads to backtraces 'fs/sysfs/group.c:237 sysfs_remove_group+0xa0/0xb0'

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
<chaitra.basappa@xxxxxxxxxxxx> 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.pdl@xxxxxxxxxxxx
> [mailto:mpt-fusionlinux.pdl@xxxxxxxxxxxx] On Behalf Of Laurence Oberman
> Sent: Tuesday, October 18, 2016 4:42 AM
> To: ojab; Johannes Thumshirn
> Cc: MPT-FusionLinux.pdl@xxxxxxxxxxxx; linux-scsi@xxxxxxxxxxxxxxx
> 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 <ojab@xxxxxxx>
> Date: 10/17/2016 17:11 (GMT-05:00)
> To: Johannes Thumshirn <jthumshirn@xxxxxxx>
> Cc: MPT-FusionLinux.pdl@xxxxxxxxxxxx, linux-scsi@xxxxxxxxxxxxxxx
> 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 +0000, 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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [SCSI Target Devel]     [Linux SCSI Target Infrastructure]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Linux IIO]     [Samba]     [Device Mapper]
  Powered by Linux