Re: AMD boot freeze bisected tob126b4703afa4010b161784a43650337676dd03b

[Bjorn Helgaas]

On Tue, Nov 02, 2010 at 06:03:35PM +0100, Borislav Petkov wrote:
> I am testing 37-rc1 on a quad-socket MCM system (48 cores) and it
> freezes during boot with the messages below:
> ... 
> 
> Bisecting the kernel gave the following results and reverting
> b126b4703afa4010b161784a43650337676dd03b does really fix booting. Let me
> know what info you'd need/patches tested for debugging this.

Thanks very much for testing this.  Can you collect the complete
dmesg please?  We need the information about the host bridge
windows and the device that we assigned resources to, and the
snippet you included doesn't have that.

If you're able to boot Windows and collect an Everest report
(http://lavalys.com), that would be a great bonus.  The goal
is to allocate things the same way Windows does, but obviously
I failed somewhere.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/