Re: General protection fault with use_blk_mq=1.

2018-03-29 Thread Zephaniah E. Loss-Cutler-Hull
On 03/29/2018 02:12 AM, Zephaniah E. Loss-Cutler-Hull wrote: > On 03/28/2018 10:13 PM, Paolo Valente wrote: >> In addition, the outcome of your attempt without >> CONFIG_DEBUG_BLK_CGROUP would give us useful bisection information: >> - if no failure occurs, then the issue is

Re: General protection fault with use_blk_mq=1.

2018-03-29 Thread Zephaniah E. Loss-Cutler-Hull
On 03/28/2018 10:13 PM, Paolo Valente wrote: > > >> Il giorno 29 mar 2018, alle ore 05:22, Jens Axboe <ax...@kernel.dk> ha >> scritto: >> >> On 3/28/18 9:13 PM, Zephaniah E. Loss-Cutler-Hull wrote: >>> On 03/28/2018 06:02 PM, Jens Axboe wrote: >

Re: General protection fault with use_blk_mq=1.

2018-03-28 Thread Zephaniah E. Loss-Cutler-Hull
On 03/28/2018 06:02 PM, Jens Axboe wrote: > On 3/28/18 5:03 PM, Zephaniah E. Loss-Cutler-Hull wrote: >> I am not subscribed to any of the lists on the To list here, please CC >> me on any replies. >> >> I am encountering a fairly consistent crash anywhere from 15 minute

General protection fault with use_blk_mq=1.

2018-03-28 Thread Zephaniah E. Loss-Cutler-Hull
earlier kernels in this configuration. Looking through the code, I'd guess that this is dying inside blkg_rwstat_add, which calls percpu_counter_add_batch, which is what RIP is pointing at. Regards, Zephaniah E. Loss-Cutler-Hull.