From: Raffaele BELARDI <raffaele.belardi@st.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] swapping processor problem
Date: Wed, 16 Nov 2011 08:26:50 +0100 [thread overview]
Message-ID: <4EC365BA.5010501@st.com> (raw)
In-Reply-To: <CA+czFiB7QqBt1mh7N-xQqH-W3HCjCY0CtT_ip2Jgy09xGoCn4A@mail.gmail.com>
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?
next prev parent reply other threads:[~2011-11-16 7:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 7:33 [gentoo-user] swapping processor problem Raffaele BELARDI
2011-11-16 6:59 ` [gentoo-user] " Raffaele BELARDI
2011-11-16 7:11 ` [gentoo-user] " Michael Mol
2011-11-16 7:26 ` Raffaele BELARDI [this message]
2011-11-16 7:34 ` Dale
2011-11-16 8:08 ` Raffaele BELARDI
2011-11-16 8:23 ` Dale
2011-11-16 8:33 ` Raffaele BELARDI
2011-11-16 8:55 ` Dale
2011-11-16 9:31 ` James Broadhead
2011-11-16 9:51 ` Dale
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EC365BA.5010501@st.com \
--to=raffaele.belardi@st.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox