public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gregory Fontenele <gregoryfontenele@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xorg crashes
Date: Tue, 5 Apr 2011 18:41:48 -0300	[thread overview]
Message-ID: <BANLkTik8JMrjf4kVnDpVS-e3okFbdcUYWA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=FFxGS-qQKxrs5PRAMmfxvtbs0Mg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2197 bytes --]

how it came out of that list?

On Tue, Apr 5, 2011 at 18:36, Mike Bean <beandaemon@gmail.com> wrote:

> Well, re-running emerge on the driver set had at least two effects. 1) The
> segfault address moved, and 2) the backtrace moved, 3) the error changed.
>
> My xlog: http://pastebin.com/zs5zvEBE
>
> My usefile: http://pastebin.com/vtvZsumP
>
> My xorg.conf: http://pastebin.com/qwyE5nsX
>
> Kinda wish I could stay and comb it, but if I don't get into traffic before
> rush hour, it'll tack a good 30-45 min onto my commute length.  Will have to
> go through it when I get home!
> <http://pastebin.com/zs5zvEBE>
> On Tue, Apr 5, 2011 at 2:19 PM, Jeremy McSpadden <deface@uberpenguin.net>wrote:
>
>> Can you paste our make.conf file ? and the output of " eselect profile
>> list " ?
>>
>> On Apr 5, 2011, at 3:15 PM, Mike Bean wrote:
>>
>> That, is an interesting question, because I HAVE been changing USE flags.
>> When the kernel was built it had a distinctly different use flag set.   Now
>> it's USE="mmx sse sse2 ssh X -gnome -kde -qt4 dbus jpeg lock session
>> startup-notification thunar udev -cdr -dvd alsa gtk"
>>
>> I might be giving myself away as a gentoo noob here, but I haven't
>> technically built anything.    When you say, "rebuild" are you referring to
>> basically the same process as emerge?   That's how I got my drivers and
>> xorg, but when I think of building something I always think of
>> configure/make/make install, and I want to be sure I'm not doing the wrong
>> thing because of a misunderstanding
>>
>> On Tue, Apr 5, 2011 at 1:20 PM, Volker Armin Hemmann <
>> volkerarmin@googlemail.com> wrote:
>>
>>> On Tuesday 05 April 2011 09:58:39 Mike Bean wrote:
>>> > Not sure what's going on, hopefully it's a configuration mistake of
>>> some
>>> > kind.   Sometimes it crashes, sometimes it's intermittent.  My xlog is
>>> at
>>> > http://pastebin.com/9jsJE8mw
>>> > Not really sure how to debug it, all advice is appreciated
>>>
>>> well, it is not a driver issue. Your server segfaults. Have you set
>>> strange
>>> flags? have you rebuild xorg-server and all the stuff it depends on with
>>> sane
>>> flags?
>>>
>>>
>>
>>
>


-- 
Atenciosamente,
Gregory Fontenele

[-- Attachment #2: Type: text/html, Size: 3703 bytes --]

  reply	other threads:[~2011-04-05 21:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 15:58 [gentoo-user] xorg crashes Mike Bean
2011-04-05 18:28 ` Mick
2011-04-05 18:55   ` Mike Bean
2011-04-05 19:20 ` Volker Armin Hemmann
2011-04-05 20:15   ` Mike Bean
2011-04-05 20:19     ` Jeremy McSpadden
2011-04-05 21:36       ` Mike Bean
2011-04-05 21:41         ` Gregory Fontenele [this message]
2011-04-05 22:33           ` Gregory Fontenele
2011-04-05 22:30         ` Jeremy McSpadden
2011-04-06  6:20     ` Yohan Pereira

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=BANLkTik8JMrjf4kVnDpVS-e3okFbdcUYWA@mail.gmail.com \
    --to=gregoryfontenele@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