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

["William J. Coldwell" <billc%netbsd.org@localhost>]

Off-topic: "BEAST" seems very appropriate naming.

--
Cryo:William J. Coldwell ARIN:WC25/AS7769 PGP:0xF97CC215/0x5E9944455
Warped, Inc. warped.com Founder/CTO 661-WARPED1 @warped @deadjournal
NetBSD netbsd.org/pkgsrc.org President,Project Security,Social Media

"Put on 3D glasses, otherwise you only see in 1½D.”  [self opinion];

On Oct 18, 2016, at 01:11, Paul Goyette <paul%whooppee.com@localhost> 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.



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

!DSPAM:58058f59188191671919093!

+------------------+--------------------------+------------------------+
| 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 |
+------------------+--------------------------+------------------------+