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/zs5zvEBEMy usefile: http://pastebin.com/vtvZsumPMy xorg.conf: http://pastebin.com/qwyE5nsXKinda 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!
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:well, it is not a driver issue. Your server segfaults. Have you set strangeOn 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
flags? have you rebuild xorg-server and all the stuff it depends on with sane
flags?