Re: PCIVERBOSE causing kernel stack overflow during boot - why?

[Paul Goyette <paul%whooppee.com@localhost>]

As I mentioned earlier, I also have an "unusual" pcibus.  On my machine 
it is bus 255, and has a whole bunch of unsupported devices, similar to 
what your pcictl shows.

So, I just built a GENERIC+PCIVERBOSE+DDB_COMMANDONETER kernel from HEAD 
and tried to boot it.  sure enough, it's broken!  In my case I got a 
"stack overflow" panic.  I set command_on_enter to "bt;c" and I got a 
backtrace, but the c(ontinue) did not dump or reboot due to not having a 
working keyboard at this point.  Here's the relevant portion of the 
backtrace:

	...
	ssp_init()
	pci_aprint_devinfo_fancy()
	pri_print() + 0x4c
	config_found()
	...

I'll have a deeper look...


On Sun, 23 Oct 2016, Jaromír DoleÄ~Mek wrote:

> Here is the output from lspci/pcictl.
>
> I'll try that DDB_COMMANDONENTER also - the machine is remote though,
> so I'll send it later when I get it.
>
> Thanks.
>
> Jaromir
>
> 2016-10-19 7:23 GMT+02:00 Paul Goyette <paul%whooppee.com@localhost>:
> > On Tue, 18 Oct 2016, Paul Goyette wrote:
> >
> > > Just as an added experiment, can you try to boot the non-PCIVERBOSE
> > > kernel, and at the boot prompt enter
> > >
> > >         load pciverbose
> > >
> > > before actually booting?
> > >
> > > As far as getting a back-trace, you could set DDB_COMMANDONENTER="bt" in
> > > your config file ....
> > >
> > > The dmesg looks interesting, especially with that strange pci9 bus.  My
> > > machine has a similar "management devices" pci bus.
> >
> >
> > Also, if you have installed pkgsrc/sysutils/pciutils it would be useful to
> > get the output from
> >
> >         lspci -tvnn
> >
> > Otherwise, please provide output from following two commands:
> >
> >         pcictl pci0 list -N
> >         pcictl pci0 list -n
> >
> >
> >
> > > On Mon, 17 Oct 2016, Jaromír DoleÄ~Mek wrote:
> > >
> > > > Hi,
> > > >
> > > > I've got an amd64 system which panics with 'stack overflow detected'
> > > > on boot, somewhere halfway through probing pci9 bus, when booted with
> > > > kernel with PCIVERBOSE. Same kernel config without PCIVERBOSE boots
> > > > fine. dmesg without PCIVERBOSE is attached.
> > > >
> > > > Any idea what might be causing this?
> > > >
> > > > I've had cursory look at pci code, it doesn't seem as if anything
> > > > would be allocating extra space there. Maybe some interaction with
> > > > dev_verbose module code? Unfortunately can't get backtrace as this
> > > > happens before the keyboard is probed and attached.
> > > >
> > > > Jaromir
> > >
> > > +------------------+--------------------------+------------------------+
> > > | Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:      |
> > > | (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com   |
> > > | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
> > > +------------------+--------------------------+------------------------+
> >
> >
> > +------------------+--------------------------+------------------------+
> > | Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:      |
> > | (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com   |
> > | Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
> > +------------------+--------------------------+------------------------+
>
>
> !DSPAM:580ce657154322062083821!

+------------------+--------------------------+------------------------+
| Paul Goyette     | PGP Key fingerprint:     | E-mail addresses:      |
| (Retired)        | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com   |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
+------------------+--------------------------+------------------------+