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

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

Bug#993948: kernel/amd64: system hang on HPE ProLiant BL460c Gen9

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

Contents

  Bug#993948: kernel/amd64: system hang on HPE ProLiant BL460c Gen9 YunQiang Su <wzssyqa@gmail.com> - 2021-09-08 15:00 +0200
    Bug#993948: kernel/amd64: system hang on HPE ProLiant BL460c Gen9 suyunqiang <wzssyqa@icloud.com> - 2021-09-09 05:50 +0200
    Bug#993948: kernel/amd64: system hang on HPE ProLiant BL460c Gen9 YunQiang Su <wzssyqa@gmail.com> - 2021-09-10 03:50 +0200
    Bug#993948: marked as done (kernel/amd64: system hang on HPE  ProLiant BL460c Gen9) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-09-26 00:10 +0200
    Bug#993948: kernel/amd64: system hang on HPE ProLiant BL460c Gen9 Yunqiang Su <wzssyqa@gmail.com> - 2021-10-21 10:50 +0200
      Bug#993948: kernel/amd64: system hang on HPE ProLiant BL460c Gen9 Claudio Kuenzler <ck@claudiokuenzler.com> - 2021-10-22 07:40 +0200
        Bug#993948: kernel/amd64: system hang on HPE ProLiant BL460c Gen9 YunQiang Su <wzssyqa@gmail.com> - 2021-10-22 08:00 +0200
          Bug#993948: kernel/amd64: system hang on HPE ProLiant BL460c Gen9 Claudio Kuenzler <ck@claudiokuenzler.com> - 2021-10-22 08:10 +0200
            Bug#993948: kernel/amd64: system hang on HPE ProLiant BL460c Gen9 YunQiang Su <wzssyqa@gmail.com> - 2021-10-22 16:40 +0200
              Bug#993948: kernel/amd64: system hang on HPE ProLiant BL460c Gen9 YunQiang Su <wzssyqa@gmail.com> - 2021-10-23 18:00 +0200

#72851 — Bug#993948: kernel/amd64: system hang on HPE ProLiant BL460c Gen9

Package: src:linux
Version: 5.10

After upgrade to bullseyes' kernel, the system always hang after about 10 min
with an error from IML log

An Unrecoverable System Error (NMI) has occurred (Service Information:
0x00000008, 0x89480000)

Kernel 5.14 from experimental also has this problem.
Kernel 4.19 works fine.
Fedora 34 seems to be working well.

--
YunQiang Su

[toc] | [next] | [standalone]

#72856

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

On Thu, 9 Sep 2021 11:11:45 +0800 Yunqiang Su <wzssyqa@gmail.com> wrote:
> 
> On Wed, 8 Sep 2021 20:53:27 +0800 YunQiang Su <wzssyqa@gmail.com> wrote:
> > Package: src:linux
> > Version: 5.10
> > 
> > After upgrade to bullseyes' kernel, the system always hang after about 10 min
> > with an error from IML log
> > 
> > An Unrecoverable System Error (NMI) has occurred (Service Information:
> > 0x00000008, 0x89480000)
> > 
> > Kernel 5.14 from experimental also has this problem.
> > Kernel 4.19 works fine.
> > Fedora 34 seems to be working well.
> 
> This is the output of dmesg and lspci from both Fedora 34 and Debian bullseye.
> Wish they are useful.
> 

The problem seems due to some problem of the driver/firmware of bnx2x.
Since If I purge firmware-bnx2x, the OS will not hang (although no network connection then).

I check md5sum of the firmware of Bullseye: they have the same value with Fedora ones.
Note: fedora ones is compressed by xz. I test them after decompress.

My hardware requires: bnx2x-e2-7.13.15.0.fw

> > 
> > --
> > YunQiang Su
> > 
> > 

[toc] | [prev] | [next] | [standalone]

#72874

Yunqiang Su <wzssyqa@gmail.com> 于2021年9月9日周四 上午11:11写道：
>
>
> On Wed, 8 Sep 2021 20:53:27 +0800 YunQiang Su <wzssyqa@gmail.com> wrote:
> > Package: src:linux
> > Version: 5.10
> >
> > After upgrade to bullseyes' kernel, the system always hang after about 10 min
> > with an error from IML log
> >
> > An Unrecoverable System Error (NMI) has occurred (Service Information:
> > 0x00000008, 0x89480000)
> >
> > Kernel 5.14 from experimental also has this problem.
> > Kernel 4.19 works fine.
> > Fedora 34 seems to be working well.
>
> This is the output of dmesg and lspci from both Fedora 34 and Debian bullseye.
> Wish they are useful.
>

Finally, we find the problem:

https://github.com/torvalds/linux/commit/8343b1f8b97ac016150c8303f95b63b20b98edf8
https://github.com/torvalds/linux/commit/65161c35554f7135e6656b3df1ce2c500ca0bdcf

In the first patch:
   They thought `err' is not used at all, and removed it.
In the second patch:
   They add it back and a wrong value "-EINVAL" is given.

Better KPI got.

> >
> > --
> > YunQiang Su
> >
> >



-- 
YunQiang Su

[toc] | [prev] | [next] | [standalone]

#73065 — Bug#993948: marked as done (kernel/amd64: system hang on HPE ProLiant BL460c Gen9)

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

Your message dated Sat, 25 Sep 2021 22:02:07 +0000
with message-id <E1mUFkF-000BoG-Or@fasolo.debian.org>
and subject line Bug#993948: fixed in linux 5.10.46-5
has caused the Debian Bug report #993948,
regarding kernel/amd64: system hang on HPE ProLiant BL460c Gen9
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
993948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993948
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#73484

On Fri, 10 Sep 2021 09:40:41 +0800 YunQiang Su <wzssyqa@gmail.com> wrote:
> Yunqiang Su <wzssyqa@gmail.com> 于2021年9月9日周四 上午11:11写道：
> >
> >
> > On Wed, 8 Sep 2021 20:53:27 +0800 YunQiang Su <wzssyqa@gmail.com> wrote:
> > > Package: src:linux
> > > Version: 5.10
> > >
> > > After upgrade to bullseyes' kernel, the system always hang after about 10 min
> > > with an error from IML log
> > >
> > > An Unrecoverable System Error (NMI) has occurred (Service Information:
> > > 0x00000008, 0x89480000)
> > >
> > > Kernel 5.14 from experimental also has this problem.
> > > Kernel 4.19 works fine.
> > > Fedora 34 seems to be working well.
> >
> > This is the output of dmesg and lspci from both Fedora 34 and Debian bullseye.
> > Wish they are useful.
> >
> 
> Finally, we find the problem:
> 
> https://github.com/torvalds/linux/commit/8343b1f8b97ac016150c8303f95b63b20b98edf8
> https://github.com/torvalds/linux/commit/65161c35554f7135e6656b3df1ce2c500ca0bdcf
> 
> In the first patch:
>    They thought `err' is not used at all, and removed it.
> In the second patch:
>    They add it back and a wrong value "-EINVAL" is given.
> 
> Better KPI got.
> 

The NICs can be detected now, while the machine continue to hang…
4.19.y works fine, while 5.10, 5.14 cannot.

I think that we need more dig.

> > >
> > > --
> > > YunQiang Su
> > >
> > >
> 
> 
> 
> -- 
> YunQiang Su
> 
> 

[toc] | [prev] | [next] | [standalone]

#73494

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

Also look at the following links and compare. Might be related or even the
same as you are seeing:

https://www.claudiokuenzler.com/blog/1125/debian-11-bullseye-boot-freeze-kernel-panic-hp-proliant-dl380
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898336
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995773


On Thu, Oct 21, 2021 at 10:42 AM Yunqiang Su <wzssyqa@gmail.com> wrote:

> On Fri, 10 Sep 2021 09:40:41 +0800 YunQiang Su <wzssyqa@gmail.com> wrote:
> > Yunqiang Su <wzssyqa@gmail.com> 于2021年9月9日周四 上午11:11写道：
> > >
> > >
> > > On Wed, 8 Sep 2021 20:53:27 +0800 YunQiang Su <wzssyqa@gmail.com>
> wrote:
> > > > Package: src:linux
> > > > Version: 5.10
> > > >
> > > > After upgrade to bullseyes' kernel, the system always hang after
> about 10 min
> > > > with an error from IML log
> > > >
> > > > An Unrecoverable System Error (NMI) has occurred (Service
> Information:
> > > > 0x00000008, 0x89480000)
> > > >
> > > > Kernel 5.14 from experimental also has this problem.
> > > > Kernel 4.19 works fine.
> > > > Fedora 34 seems to be working well.
> > >
> > > This is the output of dmesg and lspci from both Fedora 34 and Debian
> bullseye.
> > > Wish they are useful.
> > >
> >
> > Finally, we find the problem:
> >
> >
> https://github.com/torvalds/linux/commit/8343b1f8b97ac016150c8303f95b63b20b98edf8
> >
> https://github.com/torvalds/linux/commit/65161c35554f7135e6656b3df1ce2c500ca0bdcf
> >
> > In the first patch:
> >    They thought `err' is not used at all, and removed it.
> > In the second patch:
> >    They add it back and a wrong value "-EINVAL" is given.
> >
> > Better KPI got.
> >
>
> The NICs can be detected now, while the machine continue to hang…
> 4.19.y works fine, while 5.10, 5.14 cannot.
>
> I think that we need more dig.
>
> > > >
> > > > --
> > > > YunQiang Su
> > > >
> > > >
> >
> >
> >
> > --
> > YunQiang Su
> >
> >
>
>

[toc] | [prev] | [next] | [standalone]

#73495

Claudio Kuenzler <ck@claudiokuenzler.com> 于2021年10月22日周五 下午1:18写道：
>
> Also look at the following links and compare. Might be related or even the same as you are seeing:
>
> https://www.claudiokuenzler.com/blog/1125/debian-11-bullseye-boot-freeze-kernel-panic-hp-proliant-dl380
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898336
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995773
>

I built kernel by myself (5.14.12), same version as the current debian sid one.
       in fact 5.14.14 is also tested.
It won't trigger this problem.
And I make sure that hpwdt module is loaded.

No idea why Debian's kernel cannot work.

>
> On Thu, Oct 21, 2021 at 10:42 AM Yunqiang Su <wzssyqa@gmail.com> wrote:
>>
>> On Fri, 10 Sep 2021 09:40:41 +0800 YunQiang Su <wzssyqa@gmail.com> wrote:
>> > Yunqiang Su <wzssyqa@gmail.com> 于2021年9月9日周四 上午11:11写道：
>> > >
>> > >
>> > > On Wed, 8 Sep 2021 20:53:27 +0800 YunQiang Su <wzssyqa@gmail.com> wrote:
>> > > > Package: src:linux
>> > > > Version: 5.10
>> > > >
>> > > > After upgrade to bullseyes' kernel, the system always hang after about 10 min
>> > > > with an error from IML log
>> > > >
>> > > > An Unrecoverable System Error (NMI) has occurred (Service Information:
>> > > > 0x00000008, 0x89480000)
>> > > >
>> > > > Kernel 5.14 from experimental also has this problem.
>> > > > Kernel 4.19 works fine.
>> > > > Fedora 34 seems to be working well.
>> > >
>> > > This is the output of dmesg and lspci from both Fedora 34 and Debian bullseye.
>> > > Wish they are useful.
>> > >
>> >
>> > Finally, we find the problem:
>> >
>> > https://github.com/torvalds/linux/commit/8343b1f8b97ac016150c8303f95b63b20b98edf8
>> > https://github.com/torvalds/linux/commit/65161c35554f7135e6656b3df1ce2c500ca0bdcf
>> >
>> > In the first patch:
>> >    They thought `err' is not used at all, and removed it.
>> > In the second patch:
>> >    They add it back and a wrong value "-EINVAL" is given.
>> >
>> > Better KPI got.
>> >
>>
>> The NICs can be detected now, while the machine continue to hang…
>> 4.19.y works fine, while 5.10, 5.14 cannot.
>>
>> I think that we need more dig.
>>
>> > > >
>> > > > --
>> > > > YunQiang Su
>> > > >
>> > > >
>> >
>> >
>> >
>> > --
>> > YunQiang Su
>> >
>> >
>>


-- 
YunQiang Su

[toc] | [prev] | [next] | [standalone]

#73496

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

The fact that a later Kernel versions work fine _could_ be because of a
hpwdt commit after 5.10:
https://github.com/torvalds/linux/commit/acc195bd2cc48445ea35d00036d8c0afcc4fcc9c#diff-994ee4b010b5c6222ad7a20e160f733401f46894b36fa3e1fb6ffbb48bedb817
I have not tested sid or a newer Kernel on our HP machines though.
If you've compiled your own Kernel and this one works (did your do a
multiple reboot test?), maybe there's a difference in the Kernel "config"?

What happens if you disable the hpwdt module as mentioned in the other bug
reports? Does Bullseye with 5.10 and experimental with 5.14 work in this
case?

[toc] | [prev] | [next] | [standalone]

#73500

Claudio Kuenzler <ck@claudiokuenzler.com> 于2021年10月22日周五 下午2:03写道：
>
> The fact that a later Kernel versions work fine _could_ be because of a hpwdt commit after 5.10: https://github.com/torvalds/linux/commit/acc195bd2cc48445ea35d00036d8c0afcc4fcc9c#diff-994ee4b010b5c6222ad7a20e160f733401f46894b36fa3e1fb6ffbb48bedb817
> I have not tested sid or a newer Kernel on our HP machines though.
> If you've compiled your own Kernel and this one works (did your do a multiple reboot test?), maybe there's a difference in the Kernel "config"?
>
> What happens if you disable the hpwdt module as mentioned in the other bug reports? Does Bullseye with 5.10 and experimental with 5.14 work in this case?

I test upstream linux and debian-linux with the same config.
All of the upstream config works fine, while debian-linux has this problem.
I guess it is due to one patch by Debian.

-- 
YunQiang Su

[toc] | [prev] | [next] | [standalone]

#73517

YunQiang Su <wzssyqa@gmail.com> 于2021年10月22日周五 下午10:36写道：
>
> Claudio Kuenzler <ck@claudiokuenzler.com> 于2021年10月22日周五 下午2:03写道：
> >
> > The fact that a later Kernel versions work fine _could_ be because of a hpwdt commit after 5.10: https://github.com/torvalds/linux/commit/acc195bd2cc48445ea35d00036d8c0afcc4fcc9c#diff-994ee4b010b5c6222ad7a20e160f733401f46894b36fa3e1fb6ffbb48bedb817
> > I have not tested sid or a newer Kernel on our HP machines though.
> > If you've compiled your own Kernel and this one works (did your do a multiple reboot test?), maybe there's a difference in the Kernel "config"?
> >
> > What happens if you disable the hpwdt module as mentioned in the other bug reports? Does Bullseye with 5.10 and experimental with 5.14 work in this case?
>
> I test upstream linux and debian-linux with the same config.
> All of the upstream config works fine, while debian-linux has this problem.
> I guess it is due to one patch by Debian.
>

I find the real problem: it is due to intel_iommu by default.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934309

> --
> YunQiang Su



-- 
YunQiang Su

[toc] | [prev] | [standalone]

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

csiph-web