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

2016-10-26 Thread Jaromír Doleček
In my case it crashed on the same device, Core i7-6xxxK/Xeon-D Memory Controller (Target Address, Thermal, RAS) ID 0x6fa8. The last pci line before the trap was for device immediatelly preceding that one. Thanks Paul for getting to the bottom of this. Jaromir 2016-10-25 7:02 GMT+02:00 Paul

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

2016-10-25 Thread Eric Haszlakiewicz
On October 25, 2016 1:02:35 AM EDT, Paul Goyette wrote: >OK, here's the problem... > >The device in question is Intel product code 6fa8 which has a product >name of (deliberately line-split to facilitate character counting) > > "Core i7-6xxxK/Xeon-D Memory Cont" >

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

2016-10-25 Thread Paul Goyette
On Tue, 25 Oct 2016, Paul Goyette wrote: 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

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

2016-10-25 Thread Paul Goyette
OK, here's the problem... The device in question is Intel product code 6fa8 which has a product name of (deliberately line-split to facilitate character counting) "Core i7-6xxxK/Xeon-D Memory Cont" "roller (Target Address, Thermal," " RAS)" That's a total of 65

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

2016-10-23 Thread Paul Goyette
On Sun, 23 Oct 2016, Jarom??r Dole?~Mek wrote: Here is the output from lspci/pcictl. Hmmm, nothing obvious there. Looks normal. I'd still be interested if you can reproduce this with a non-PCIVERBOSE kernel and manually/forced-load module. I'll try that DDB_COMMANDONENTER also - the

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

2016-10-23 Thread Jaromír Doleček
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 : > On Tue, 18 Oct 2016, Paul Goyette wrote: > >> Just as an added

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

2016-10-18 Thread Paul Goyette
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

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

2016-10-18 Thread William J. Coldwell
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

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

2016-10-18 Thread Paul Goyette
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

PCIVERBOSE causing kernel stack overflow during boot - why?

2016-10-17 Thread Jaromír Doleček
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?