Re: Hard LOCKUP on 4.15-rc9 + 'blkmq/for-next' branch

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

 



On 1/22/18 4:31 PM, David Zarzycki wrote:
> Hello,
> 
> I previously reported a hang when building LLVM+clang on a block multi-queue device (NVMe _or_ loopback onto tmpfs with the ’none’ scheduler).
> 
> I’ve since updated the kernel to 4.15-rc9, merged the ‘blkmq/for-next’ branch, disabled nohz_full parameter (used for testing), and tried again. Both NVMe and loopback now lock up hard (ext4 if it matters). Here are the backtraces:
> 
> NVMe:      http://znu.io/IMG_0366.jpg
> Loopback:  http://znu.io/IMG_0367.jpg

I tried to reproduce this today using the exact recipe that you provide,
but it ran fine for hours. Similar setup, nvme on a dual socket box
with 48 threads.

> What should I try next to help debug this?

This one looks different than the other one. Are you sure your hw
is sane? I'd probably try and enable lockdep debugging etc and
see if you catch anything.

-- 
Jens Axboe




[Index of Archives]     [Linux RAID]     [Linux SCSI]     [Linux ATA RAID]     [IDE]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Device Mapper]

  Powered by Linux