From: Song Liu <liu.song.a23@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Tariq Toukan <tariqt@mellanox.com>,
Dmitry Safonov <0x7f454c46@gmail.com>,
open list <linux-kernel@vger.kernel.org>,
Maor Gottlieb <maorg@mellanox.com>,
kernel-team@fb.com
Subject: Re: WARNING and PANIC in irq_matrix_free
Date: Fri, 25 May 2018 13:10:50 -0700 [thread overview]
Message-ID: <CAPhsuW7PPRfPYfCtBMsOYdGJCkPKsVNU0501RFKdECvadhOu3w@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1805231049021.1598@nanos.tec.linutronix.de>
Hi,
We are seeing something probably related.
We run ethtool on a system with Broadcom NIC to increase number of
combined queues.
[root@ ~]# ethtool -l eth0
Channel parameters for eth0:
Pre-set maximums:
RX: 9
TX: 8
Other: 0
Combined: 17
Current hardware settings:
RX: 0
TX: 0
Other: 0
Combined: 8
[root@ ~]# ethtool -L eth0 combined 16
The last command PANIC the kernel easily (5 out of 5 in my tests).
I haven't got luck to catch much console output, the only line I got is:
[ 504.727865] WARNING: CPU: 10 PID: 0 at kernel/irq/matrix.c:371
irq_matrix_free+0x32/0xd0
The NIC we have is
Broadcom Limited BCM57302 NetXtreme-C 10Gb/25Gb Ethernet Controller
Thanks,
Song
On Wed, May 23, 2018 at 1:49 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Wed, 23 May 2018, Tariq Toukan wrote:
>> On 19/05/2018 2:20 PM, Thomas Gleixner wrote:
>> > On Fri, 18 May 2018, Dmitry Safonov wrote:
>> > > I'm not entirely sure that it's the same fault, but at least backtrace
>> > > looks resembling.
>> >
>> > Yes, it's similar, but not the same issue. I'll stare are the code ...
>> >
>> > Thanks,
>> >
>> > tglx
>> >
>>
>> We still see the issue in our daily regression runs.
>> I have your patch merged into my internal branch, it prints the following:
>>
>> [ 4898.226258] Trying to clear prev_vector: 0
>> [ 4898.226439] Trying to clear prev_vector: 0
>>
>> i.e. vector(0) is lower than FIRST_EXTERNAL_VECTOR.
>
> Could you please enable the vector and irq matrix trace points and capture
> the trace when this happens?
>
> Thanks,
>
> tglx
>
next prev parent reply other threads:[~2018-05-25 20:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-20 12:07 Tariq Toukan
2018-02-20 18:11 ` Thomas Gleixner
2018-02-20 18:18 ` Thomas Gleixner
2018-02-21 11:27 ` Tariq Toukan
2018-02-22 21:38 ` Thomas Gleixner
2018-02-25 9:50 ` Tariq Toukan
2018-05-18 22:41 ` Dmitry Safonov
2018-05-18 23:43 ` Dmitry Safonov
2018-05-19 11:20 ` Thomas Gleixner
2018-05-23 7:16 ` Tariq Toukan
2018-05-23 8:49 ` Thomas Gleixner
2018-05-25 20:10 ` Song Liu [this message]
2018-05-25 21:29 ` Song Liu
2018-05-28 10:53 ` Thomas Gleixner
2018-05-28 11:17 ` Tariq Toukan
2018-05-28 14:27 ` Thomas Gleixner
2018-05-28 18:36 ` Song Liu
2018-05-28 18:34 ` Song Liu
2018-05-28 20:09 ` Thomas Gleixner
[not found] ` <3F47F523-64C5-422B-B9B0-73B8D105CF71@fb.com>
2018-05-29 8:35 ` Thomas Gleixner
2018-05-29 16:54 ` Song Liu
2018-05-30 21:56 ` Thomas Gleixner
2018-06-04 7:56 ` Dou Liyang
2018-06-04 11:17 ` Thomas Gleixner
2018-06-04 11:59 ` Dou Liyang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPhsuW7PPRfPYfCtBMsOYdGJCkPKsVNU0501RFKdECvadhOu3w@mail.gmail.com \
--to=liu.song.a23@gmail.com \
--cc=0x7f454c46@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maorg@mellanox.com \
--cc=tariqt@mellanox.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®