Re: [PATCH 0/2] genirq/affinity: try to make sure online CPU is assgined to irq vector

[Laurence Oberman]

On Tue, 2018-01-16 at 15:22 +0000, Don Brace wrote:
> > -----Original Message-----
> > From: Laurence Oberman [mailto:loberman@xxxxxxxxxx]
> > Sent: Tuesday, January 16, 2018 7:29 AM
> > To: Thomas Gleixner <tglx@xxxxxxxxxxxxx>; Ming Lei <ming.lei@redhat
> > .com>
> > Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Jens Axboe <axboe@xxxxxx
> > >;
> > linux-block@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; Mike
> > Snitzer
> > <snitzer@xxxxxxxxxx>; Don Brace <don.brace@xxxxxxxxxxxxx>
> > Subject: Re: [PATCH 0/2] genirq/affinity: try to make sure online
> > CPU is assgined
> > to irq vector
> > 
> > > > It is because of irq_create_affinity_masks().
> > > 
> > > That still does not answer the question. If the interrupt for a
> > > queue
> > > is
> > > assigned to an offline CPU, then the queue should not be used and
> > > never
> > > raise an interrupt. That's how managed interrupts have been
> > > designed.
> > > 
> > > Thanks,
> > > 
> > > ÂÂÂÂÂÂtglx
> > > 
> > > 
> > > 
> > > 
> > 
> > I captured a full boot log for this issue for Microsemi, I will
> > send it
> > to Don Brace.
> > I enabled all the HPSA debug and here is snippet
> > 
> > 
> > ..
> > ..
> > ..
> > Â 246.751135] INFO: task systemd-udevd:413 blocked for more than
> > 120
> > seconds.
> > [ÂÂ246.788008]ÂÂÂÂÂÂÂTainted: GÂÂÂÂÂÂÂÂÂÂIÂÂÂÂÂÂ4.15.0-rc4.noming+
> > #1
> > [ÂÂ246.822380] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs"
> > disables this message.
> > [ÂÂ246.865594] systemd-udevdÂÂÂDÂÂÂÂ0ÂÂÂ413ÂÂÂÂ411 0x80000004
> > [ÂÂ246.895519] Call Trace:
> > [ÂÂ246.909713]ÂÂ? __schedule+0x340/0xc20
> > [ÂÂ246.930236]ÂÂschedule+0x32/0x80
> > [ÂÂ246.947905]ÂÂschedule_timeout+0x23d/0x450
> > [ÂÂ246.970047]ÂÂ? find_held_lock+0x2d/0x90
> > [ÂÂ246.991774]ÂÂ? wait_for_completion_io+0x108/0x170
> > [ÂÂ247.018172]ÂÂio_schedule_timeout+0x19/0x40
> > [ÂÂ247.041208]ÂÂwait_for_completion_io+0x110/0x170
> > [ÂÂ247.067326]ÂÂ? wake_up_q+0x70/0x70
> > [ÂÂ247.086801]ÂÂhpsa_scsi_do_simple_cmd+0xc6/0x100 [hpsa]
> > [ÂÂ247.114315]ÂÂhpsa_scsi_do_simple_cmd_with_retry+0xb7/0x1c0
> > [hpsa]
> > [ÂÂ247.146629]ÂÂhpsa_scsi_do_inquiry+0x73/0xd0 [hpsa]
> > [ÂÂ247.174118]ÂÂhpsa_init_one+0x12cb/0x1a59 [hpsa]
> 
> This trace comes from internally generated discovery commands. No
> SCSI devices have
> been presented to the SML yet.
> 
> At this point we should be running on only one CPU. These commands
> are meant to use
> reply queue 0 which are tied to CPU 0. It's interesting that the
> patch helps.
> 
> However, I was wondering if you could inspect the iLo IML logs and
> send the
> AHS logs for inspection.
> 
> Thanks,
> Don Brace
> ESC - Smart Storage
> Microsemi Corporation


Hello Don

I took two other dl380 g7's and ran the same kernel and it hangs in the
identical place. Its absolutely consistent here.

I doubt all three have hardware issues.

Nothing is logged of interest in the IML.

Ming will have more to share on specifically why it helps.
I think he sent that along to you already.

Regards
Laurence