On 11/16/2011 08:11 AM, Michael Mol wrote: > Play with your BIOS settings. Look for things like legacy USB support. > Also, double-check that all the relevant USB drivers (UHCI, EHCI, > XHCI, HID, etc) are either built-into the kernel, or are loaded as > modules. Consider rebuilding your kernel. > > Just because one processor has a superset of the instructions of the > other doesn't mean there may not be other compatibilities. Some time > back, a thread on here discussed how to find out what -march=native > becomes, in terms of -march and a bunch of other parameters. I've > noticed parameters like cache line sizes and cache sizes, among a > couple others. I imagine a bungling of, e.g., cache line sizes could > break code that has heavy dependency on data locality and/or memory > models; it might have broken your USB drivers, for example. > > But, really, I think BIOS settings and driver presence are the more > likely culprit. >
I don't think it was a software issue because the same lock happened also booting from a live-CD. I ended up swapping the motherboards, now live-CD boots fine but I need a new kernel. The march=native thread looks interesting, do you remember the subject line so I can search it in the archives?
