Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #60835 > unrolled thread

Bug#897893: Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver

Started byBen Hutchings <ben@decadent.org.uk>
First post2018-05-04 16:20 +0200
Last post2018-05-04 16:40 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#897893: Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver Ben Hutchings <ben@decadent.org.uk> - 2018-05-04 16:20 +0200
    Bug#897893: Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver Eugene Budanov <budanov@restream.rt.ru> - 2018-05-04 16:40 +0200

#60835 — Bug#897893: Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver

FromBen Hutchings <ben@decadent.org.uk>
Date2018-05-04 16:20 +0200
SubjectBug#897893: Strange kernel panics on linux-image-4.9.0-6-amd64 with mlx4_en driver
Message-ID<vLJIZ-lX-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo

On Fri, 2018-05-04 at 15:35 +0300, Eugene Budanov wrote:
> Package: linux-image-4.9.0-6-amd64
> Version: 4.9.82-1+deb9u3
> 
> Hi!
> 
> Here's a short problem description.
> 
> We have some Supermicro servers with the same configuration for all
> machines (hardware, kernels, packages, etc). A month ago, or maybe a
> bit later, all of these machines began crashing into kernel panic. I
> can't find any pattern of failure at all. But it happens very often.
> Some machines may drop into kernel panic a couple times a day! But
> usually machines crash about every 3 to 6 days. All of these machines
> have intensive network and i/o operations.
> 
> I saved dmesg log from one of these machines after the crash (see the
> attachment).
> 
> As far as I see, every machine probably has problems with mlx4_en or
> GRO. Also I see list_add double add => list_del corruption. Can I do
> anything to get more detailed logs? What additional information do
> you need for better problem diagnostics?

The WARNING messages show that there are out-of-tree modules (i.e. not
part of the kernel package) loaded.  What are those?

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug

[toc] | [next] | [standalone]


#60836

FromEugene Budanov <budanov@restream.rt.ru>
Date2018-05-04 16:40 +0200
Message-ID<vLK2l-u1-3@gated-at.bofh.it>
In reply to#60835

[Multipart message — attachments visible in raw view] — view raw

Hi!

This is only one driver, mpt2sas downloaded from LSI site version 22.00 instead 13.0 from Debian package. Because from beggining we think that is was a problems in RAID controller. But this hypothesis turned out as erroneous. On other machines we use mpt2sas in-kernel driver only. No 3rd party drivers.

---
С уважением,
Буданов Евгений.
Системный администратор
Компания «Рестрим»

On 4 мая 2018 г., 17:08 +0300, Ben Hutchings <ben@decadent.org.uk>, wrote:
> Control: tag -1 moreinfo
>
> On Fri, 2018-05-04 at 15:35 +0300, Eugene Budanov wrote:
> > Package: linux-image-4.9.0-6-amd64
> > Version: 4.9.82-1+deb9u3
> >
> > Hi!
> >
> > Here's a short problem description.
> >
> > We have some Supermicro servers with the same configuration for all
> > machines (hardware, kernels, packages, etc). A month ago, or maybe a
> > bit later, all of these machines began crashing into kernel panic. I
> > can't find any pattern of failure at all. But it happens very often.
> > Some machines may drop into kernel panic a couple times a day! But
> > usually machines crash about every 3 to 6 days. All of these machines
> > have intensive network and i/o operations.
> >
> > I saved dmesg log from one of these machines after the crash (see the
> > attachment).
> >
> > As far as I see, every machine probably has problems with mlx4_en or
> > GRO. Also I see list_add double add => list_del corruption. Can I do
> > anything to get more detailed logs? What additional information do
> > you need for better problem diagnostics?
>
> The WARNING messages show that there are out-of-tree modules (i.e. not
> part of the kernel package) loaded. What are those?
>
> Ben.
>
> --
> Ben Hutchings
> Every program is either trivial or else contains at least one bug
>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web