Bug 103101 - NVMe: setpci reset while running I/Os and issuing ioctl commands results in kernel kernel oops and system reset
Summary: NVMe: setpci reset while running I/Os and issuing ioctl commands results in k...
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86-64 Linux
: P1 high
Assignee: drivers_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-19 09:30 UTC by Nagarajkumar N
Modified: 2015-08-19 09:33 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.1.3
Subsystem:
Regression: No
Bisected commit-id:

Attachments
system log on kernel oops (8.64 KB, application/octet-stream)
2015-08-19 09:30 UTC, Nagarajkumar N 		Details
Add an attachment (proposed patch, testcase, etc.)

Description Nagarajkumar N 2015-08-19 09:30:36 UTC 
Created attachment 185191 [details]
system log on kernel oops

On NVMe device, while running  I/Os through vdbench tool and ioctl commands in a loop(NVME IDENTIFY) are running in parallel, issuing setpci reset causes kernel oops followed by system reset

system log file attached on kernel oops

sys parameters:

[root@localhost ~]# cat /sys/block/nvme0n1/size
3125627568
[root@localhost ~]# cat /sys/block/nvme0n1/queue/hw_sector_size
4096
[root@localhost ~]# cat /sys/block/nvme0n1/queue/logical_block_size
4096
[root@localhost ~]# cat /sys/block/nvme0n1/queue/max_segments
128
[root@localhost ~]# cat /sys/block/nvme0n1/queue/max_segment_size
65536


#lspci -vt
\-[0000:00]-+-00.0  Intel Corporation Haswell-E DMI2
             +-01.0-[03]----00.0  Hewlett-Packard Company Device 3239
             +-01.1-[0e]--
             +-02.0-[05]----00.0  LSI Logic / Symbios Logic SSS6200 PCI-Express Flash SSD
             +-02.1-[0f]--
             +-02.2-[04]--
             +-02.3-[10]--
             +-03.0-[08]--
             +-03.1-[11]--
             +-03.2-[0b]----00.0  Device 1bb1:0100   //NVMe device

setpci -s 0000:00:03.2 0xa0.l=0x308200d0

Number of CPU cores: 40

processor       : 39
vendor_id       : GenuineIntel
cpu family      : 6
model           : 63
model name      : Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz
stepping        : 2
microcode       : 0x2b
cpu MHz         : 2297.356
cache size      : 25600 KB
physical id     : 1
siblings        : 20
core id         : 12
cpu cores       : 10
apicid          : 57
initial apicid  : 57
fpu             : yes
fpu_exception   : yes
cpuid level     : 15
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm ida arat epb pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm xsaveopt cqm_llc cqm_occup_llc
bugs            :
bogomips        : 4604.88
clflush size    : 64
cache_alignment : 64
address sizes   : 46 bits physical, 48 bits virtual
power management:
Comment 1 Nagarajkumar N 2015-08-19 09:33:31 UTC 
vd bench parameters: 
sd=sd1,lun=/dev/nvme0n1,openflags=o_direct
wd=wd1,sd=sd1,xfersize=64k,rdpct=60
rd=run1,wd=wd1,iorate=max,elapsed=72h,interval=1,forthreads=128
Note You need to log in before you can comment on or make changes to this bug.