<div dir="ltr"><div>How about this? It seems at least related.<br><br><a href="https://github.com/alterapraxisptyltd/openatom/issues/1">https://github.com/alterapraxisptyltd/openatom/issues/1</a><br><br></div>Quote:<br>[linux] Infinite loop in pci_get_rom_size()<br><div class="">
<div class="">
<div class="">
<p>This is one of those issues that you find when putting
supposedly stable code through unusual situations. I did expect any
function in linux that is not part of radeon.ko to not be rock solid.
Turns out that's not really the case.</p>
<p>If we have a PCIR structure with a zero size length, the loop
iterating through those structure does not advance. It simply does
"image += readw(pds + 16) * 512;", but if that field is zero we're back
analyzing the same structure on the next loop. The way to get out of
this loop is to set bit 7 of the type field. That's what 'last_image'
does. If that bit is not set, with the above, that's an infinite loop. </p>
<p>Luckily, it doesn't crash the kernel, but it hangs any driver that
calls the function under said circumstances. No more modprobe -r or
unbinding. Reboot is needed. No idea why a firmware blob here is treated
as trusted input.</p>
</div>
</div>
</div><br><br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-01-15 0:14 GMT-03:00 Federico <span dir="ltr"><<a href="mailto:federicotg@gmail.com" target="_blank">federicotg@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Also just tried *enabling* the IGP and keeping PEG as the primary graphics. Video output stayed on the discrete card output and the same stack trace happened when booting without nomodeset. So now I'm back to setting it as disabled as it had been before.<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-01-14 23:59 GMT-03:00 Federico <span dir="ltr"><<a href="mailto:federicotg@gmail.com" target="_blank">federicotg@gmail.com</a>></span>:<div><div class="h5"><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>AFAIK this BIOS requires me to disable IGP to even use the discrete graphics. At least that's the first thing I had to do when I first installed the card and every time I wanted to change the monitor connection.<br></div>Here's how "disabled" it is:<br><br><a href="https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1386973/+attachment/4298792/+files/20150114_234953.png" target="_blank">https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1386973/+attachment/4298792/+files/20150114_234953.png</a><br><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-01-14 23:46 GMT-03:00 Michel Dänzer <span dir="ltr"><<a href="mailto:michel@daenzer.net" target="_blank">michel@daenzer.net</a>></span>:<div><div><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 15.01.2015 11:10, Federico wrote:<br>
> Here's the 3.18 32-bits 60 lines per screen stack trace. Always using<br>
> softlockup_panic=1.<br>
><br>
> Quite similar, but slightly different. Hopefully, useful.<br>
><br>
> <a href="https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1386973/+attachment/4298769/+files/20150114_230142.png" target="_blank">https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1386973/+attachment/4298769/+files/20150114_230142.png</a><br>
<br>
</span>Looks like it hangs while reading the video BIOS ROM.<br>
<br>
If the integrated GPU is still enabled in the system BIOS setup, does<br>
disabling it avoid the problem?<br>
<div><div><br>
<br>
--<br>
Earthling Michel Dänzer | <a href="http://www.amd.com" target="_blank">http://www.amd.com</a><br>
Libre software enthusiast | Mesa and X developer<br>
</div></div></blockquote></div></div></div><br></div>
</blockquote></div></div></div><br></div>
</blockquote></div><br></div>