Re: [PATCH] scsi: cxlflash: Select SCSI_SCAN_ASYNC

2018-02-20 Thread Matthew R. Ochs
On Tue, Feb 20, 2018 at 07:56:35PM +1100, Michael Ellerman wrote: > Vaibhav Jain writes: > > > The cxlflash driver uses "Asynchronous SCSI scanning" enabled by > > CONFIG_SCSI_SCAN_ASYNC. Without this enabled the modprobe of cxlflash > > module gets hung with

Re: [PATCH] scsi: cxlflash: Select SCSI_SCAN_ASYNC

2018-02-20 Thread Matthew R. Ochs
On Tue, Feb 20, 2018 at 07:56:35PM +1100, Michael Ellerman wrote: > Vaibhav Jain writes: > > > The cxlflash driver uses "Asynchronous SCSI scanning" enabled by > > CONFIG_SCSI_SCAN_ASYNC. Without this enabled the modprobe of cxlflash > > module gets hung with following backtrace: > > > > Call

Re: [PATCH] scsi: cxlflash: Select SCSI_SCAN_ASYNC

2018-02-20 Thread Michael Ellerman
Vaibhav Jain writes: > The cxlflash driver uses "Asynchronous SCSI scanning" enabled by > CONFIG_SCSI_SCAN_ASYNC. Without this enabled the modprobe of cxlflash > module gets hung with following backtrace: > > Call Trace: > __switch_to+0x2cc/0x470 >

Re: [PATCH] scsi: cxlflash: Select SCSI_SCAN_ASYNC

2018-02-20 Thread Michael Ellerman
Vaibhav Jain writes: > The cxlflash driver uses "Asynchronous SCSI scanning" enabled by > CONFIG_SCSI_SCAN_ASYNC. Without this enabled the modprobe of cxlflash > module gets hung with following backtrace: > > Call Trace: > __switch_to+0x2cc/0x470 > __schedule+0x288/0xab0 > schedule+0x40/0xc0

[PATCH] scsi: cxlflash: Select SCSI_SCAN_ASYNC

2018-02-18 Thread Vaibhav Jain
The cxlflash driver uses "Asynchronous SCSI scanning" enabled by CONFIG_SCSI_SCAN_ASYNC. Without this enabled the modprobe of cxlflash module gets hung with following backtrace: Call Trace: __switch_to+0x2cc/0x470 __schedule+0x288/0xab0 schedule+0x40/0xc0 schedule_timeout+0x254/0x4f0

[PATCH] scsi: cxlflash: Select SCSI_SCAN_ASYNC

2018-02-18 Thread Vaibhav Jain
The cxlflash driver uses "Asynchronous SCSI scanning" enabled by CONFIG_SCSI_SCAN_ASYNC. Without this enabled the modprobe of cxlflash module gets hung with following backtrace: Call Trace: __switch_to+0x2cc/0x470 __schedule+0x288/0xab0 schedule+0x40/0xc0 schedule_timeout+0x254/0x4f0