On Fri, 2023-09-15 at 13:42 -0700, Bart Van Assche wrote:
> On 9/15/23 12:33, <email address hidden> wrote:
> > The users loqs and leonshaw helped to narrow it down to this
> > commit:
> >
> >
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=624885209f31eb9985bf51abe204ecbffe2fdeea
>
> Damien, can you please take a look?
>
> Thanks,
>
> Bart.
>
I had a quick look at this and its not making sense. The only calls I
see are in the scan when the devices is added and in the re-scan.
It should not be consuming the scsi_eh thread unless some type of udev
events keeps happening.
Would be good to get some
cat /proc/<PID>/stack of the scsi_eh threads if they are constantly
consuming CPUY
I will try reproduce and try figure out what is going on here.
On Fri, 2023-09-15 at 13:42 -0700, Bart Van Assche wrote: /git.kernel. org/pub/ scm/linux/ kernel/ git/torvalds/ linux.git/ commit/ ?id=624885209f3 1eb9985bf51abe2 04ecbffe2fdeea
> On 9/15/23 12:33, <email address hidden> wrote:
> > The users loqs and leonshaw helped to narrow it down to this
> > commit:
> >
> >
> https:/
>
> Damien, can you please take a look?
>
> Thanks,
>
> Bart.
>
I had a quick look at this and its not making sense. The only calls I
see are in the scan when the devices is added and in the re-scan.
It should not be consuming the scsi_eh thread unless some type of udev
events keeps happening.
Would be good to get some
cat /proc/<PID>/stack of the scsi_eh threads if they are constantly
consuming CPUY
I will try reproduce and try figure out what is going on here.
Thanks
Laurence