Re: Regression causes a hang on boot with a Comtrol PCI card

Jesse Hathaway
2019-03-14T20:57:22Z

> > 1302fcf0d03e (refs/bisect/bad) PCI: Configure *all* devices, not just
> > hot-added ones
> > 1c3c5eab1715 sched/core: Enable might_sleep() and smp_processor_id()
> > checks early
>
> How did you narrow it down to *two* commits, and do you have to revert
> both of them to avoid the hang? Usually a bisection identifies a
> single commit, and the two you mention aren't related.

Sorry I should have been more verbose in what the bisection process was, I
found the problem after attempting to upgrade from linux v3.16 to v4.9. When
v4.9 hung I tried the latest kernel, v5.0, which also hanged. I began a git
bisect, but found there was more than one bad commit. Here is my current
understanding:

- [x] v3.18 vanilla, 1302fcf0d03e committed, hangs
- [x] v3.18 with revert of 1302fcf0d03e, works
.
.
.
- [x] v4.12 vanilla, hangs
- [x] v4.12 with revert of 1302fcf0d03e, works

- [x] v4.13 vanilla, 1c3c5eab1715 committed, hangs
- [x] v4.13 with revert of 1302fcf0d03e, hangs
- [x] v4.13 with revert of 1c3c5eab1715, hangs
- [x] v4.13 with revert of 1302fcf0d03e & 1c3c5eab1715, works

- [x] v5.0 vanilla, hangs
- [x] v5.0 with revert of 1302fcf0d03e & 1c3c5eab1715, works

> Can you collect a complete dmesg log (with a working kernel) and
> output of "sudo lspci -vvxxx"? You can open a bug report at
> https://bugzilla.kernel.org, attach the logs there, and respond here
> with the URL.

Bug submitted along with the requested logs,
https://bugzilla.kernel.org/show_bug.cgi?id=202927

> Where does the hang happen? Is it when we configure the Comtrol card?

Hang occurs after PCI is initialized, snippet below, I have included the full
output in the bug report:

[ 10.561971] pci 0000:81:00.0: bridge window [mem 0xc8000000-0xc80fffff]
[ 10.569661] pci 0000:80:01.0: PCI bridge to [bus 81-82]
[ 10.575594] pci 0000:80:01.0: bridge window [mem 0xc8000000-0xc80fffff]
[ 10.583278] pci 0000:80:03.0: PCI bridge to [bus 83]
[ 10.589008] NET: Registered protocol family 2
[ 10.594254] tcp_listen_portaddr_hash hash table entries: 65536
(order: 8, 1048576 bytes)
[ 10.603671] TCP established hash table entries: 524288 (order: 10,
4194304 bytes)
[ 10.612729] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
[ 10.620446] TCP: Hash tables configured (established 524288 bind 65536)
[ 10.628124] UDP hash table entries: 65536 (order: 9, 2097152 bytes)
[ 10.635541] UDP-Lite hash table entries: 65536 (order: 9, 2097152 bytes)
[ 10.643669] NET: Registered protocol family 1

Please let me know if there is anything else I can provide, I am also happy to
test any patches, Jesse Hathaway