On Tue, May 10, 2011 at 01:20:30AM +0200, Andreas Beckmann wrote:
> Still testing with 2.6.32-2-amd64?
>
> Do you have binutils-gold installed? Which version? Purge it.
Looks like it's it. With old binutils, no oops.
> > Although, I noticed that mere modprobe does not cause the oops anymore, I
> > need to actually attempt to start X. Since the latter takes less effort
> > (just trying to boot normally), I did not notice when this changed. At
> > least with the current kernel in sid (2.6.38-2) the module can be loaded and
> > unloaded without any ill effects.
>
> Does Xorg.*.log* contain anything helpful after the crash?
I didn't check, would it still be useful now that we know it's something
that happens due to new binutils?
> How usable is the system after the Oops? Console? Ssh? ...
I needed SAK to get keyboard back, after that I could switch to console and
everything not related to X seemed to work fine. Of course, you shouldn't
trust a system after a crash so I didn't tarry long.
By the way, if you have no idea what the problem with gold could be, there
is no need to add a conflict. LD = ld.bfd does the same.
--
1KB // Microsoft corollary to Hanlon's razor:
// Never attribute to stupidity what can be
// adequately explained by malice.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
