From: Michael Mol <mikemol@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Gentoo segfaults on virtualbox-4.1.14 when running on AMD bulldozer
Date: Mon, 30 Apr 2012 15:22:19 -0400 [thread overview]
Message-ID: <CA+czFiA7RsM9ai2z_4Qr3NTU4LLPdW1e1ZmO3aTjQzoG71aGiQ@mail.gmail.com> (raw)
In-Reply-To: <4F9EE1EC.4010402@gentoo.org>
On Mon, Apr 30, 2012 at 3:03 PM, Markos Chandras <hwoarang@gentoo.org> wrote:
> On 04/30/2012 02:33 PM, Michael Mol wrote:
>> Neat. Random guess, but it could be a bug in Bulldozer's memory
>> controller or IOMMU. Try disabling IOMMU support in your kernel?
>>
>> On Apr 29, 2012 3:29 PM, "Markos Chandras" <hwoarang@gentoo.org
>> <mailto:hwoarang@gentoo.org>> wrote:
>>
>> On 04/28/2012 01:24 AM, Matthew Marlowe wrote:
>>> On Fri, Apr 27, 2012 at 3:54 PM, Markos Chandras
>> <hwoarang@gentoo.org <mailto:hwoarang@gentoo.org>> wrote:
>>>> On 04/27/2012 11:45 PM, Nikos Chantziaras wrote:
>>>>> On 27/04/12 22:35, Markos Chandras wrote:
>>>>>> I replaced my Phenom II cpu with a new 6-core AMD
>>>>>> bulldozer.
>> However, I
>>>>>> noticed that all of my Gentoo virtual machines throw
>>>>>> (compiler) segmentation faults when building or running any
>>>>>> application.
>>>>>
>>>
>>> I'm not familiar with virtualbox, but I've seen similar issues
>>> occur with vmware and the solution was to at least temporarily
>>> mask whatever new cpu flags the new hypervisor was passing to the
>>> guest. In vmware, one could limit the cpu flags to maintain
>>> compatibility with various cpu releases which was especially
>>> helpful in clusters.... Yes, your gentoo vms should have been
>>> fine ..but at least until you track down the issue, see if
>>> virtualbox has a similar feature?
>>>
>> Interestingly this seems to be caused when using my wireless card
>> to bridge the virtualbox interfaces onto. I can't reproduce (yet)
>> any segfaults when I use the onboard ethernet card. I have the
>> following wireless card (supported by the rtl8180 kernel module)
>>
>> 04:06.0 Ethernet controller: Belkin F5D7000 v7000 Wireless G
>> Desktop Card [Realtek RTL8185] (rev 20)
>>
>> -- Regards, Markos Chandras / Gentoo Linux Developer / Key ID:
>> B4AFF2C2
>>
> AMD IOMMU (Device Drivers -> Hardware IOMMU ) makes no difference. I
> will have to move the discussion to virtualbox forums/ML as this seems
> a driver or virtualbox problem. Bridge networking on that wireless
> card work flawlessly when using Windows 7 as host.
Report back when you find out the meat of the problem. I'm intensely curious.
--
:wq
next prev parent reply other threads:[~2012-04-30 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 19:35 [gentoo-user] Gentoo segfaults on virtualbox-4.1.14 when running on AMD bulldozer Markos Chandras
2012-04-27 22:30 ` [gentoo-user] " Markos Chandras
2012-04-27 22:45 ` Nikos Chantziaras
2012-04-27 22:54 ` Markos Chandras
2012-04-28 0:24 ` Matthew Marlowe
2012-04-28 8:25 ` Markos Chandras
2012-04-29 19:23 ` Markos Chandras
2012-04-30 13:33 ` Michael Mol
2012-04-30 19:03 ` Markos Chandras
2012-04-30 19:22 ` Michael Mol [this message]
2012-04-28 0:36 ` walt
2012-04-28 8:26 ` Markos Chandras
2012-05-01 17:39 ` [gentoo-user] " Alan McKinnon
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=CA+czFiA7RsM9ai2z_4Qr3NTU4LLPdW1e1ZmO3aTjQzoG71aGiQ@mail.gmail.com \
--to=mikemol@gmail.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