From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1MBTgb-0004zo-9g for garchives@archives.gentoo.org; Tue, 02 Jun 2009 13:05:49 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id C9E88E0394; Tue, 2 Jun 2009 13:05:47 +0000 (UTC) Received: from mail-ew0-f213.google.com (mail-ew0-f213.google.com [209.85.219.213]) by pigeon.gentoo.org (Postfix) with ESMTP id 8B1CCE0394 for ; Tue, 2 Jun 2009 13:05:47 +0000 (UTC) Received: by ewy9 with SMTP id 9so7883048ewy.34 for ; Tue, 02 Jun 2009 06:05:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=4OJuMdSPmT8hgotMoeRDCIPQQ5JZBHfDRvvbWMNqMAo=; b=BXA0VT7CVtGeYU0ovsqcMKqZP0qLDmOsuHhZ2j/LevI4O6xYa/fvdzue5WIGsU8kHi zpvOtCC4+csqA+4rYoDB1tQaMpQoXmAgMLgP52W4yPt97n+rj/B+iSDgzpODuNyYBFr0 HuGNZUB5R8dgXdAjZpIA5GpXPJc6C01DR6ySs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:subject:date:user-agent:references:in-reply-to:mime-version :content-type:content-transfer-encoding:message-id; b=Ei6Zaj2nsMm0j+/ANvafrAdX77kvMnCvfJ7XD4pp+AjjD5dTzu018Sv8crpP5iuRAi 43LalK6bww9joS/mOnPOxpfxv/XUi2MkIAAlmic3CvziirMgnudKHYhd/f0gLK2zQep6 TVi5sFps8/azVXnYJitk1fJGo+5J8kvfIps78= Received: by 10.210.77.2 with SMTP id z2mr1140591eba.69.1243947946836; Tue, 02 Jun 2009 06:05:46 -0700 (PDT) Received: from energy.localnet (energy.heim10.tu-clausthal.de [139.174.197.94]) by mx.google.com with ESMTPS id 21sm10835053ewy.114.2009.06.02.06.05.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Tue, 02 Jun 2009 06:05:46 -0700 (PDT) From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Kernel Oops! with new xorg Date: Tue, 2 Jun 2009 15:05:39 +0200 User-Agent: KMail/1.11.90 (Linux/2.6.29.4r4; KDE/4.2.87; x86_64; ; ) References: <358eca8f0906020256g44b6e05dgadcdef6e3997ca37@mail.gmail.com> <200906021216.52800.volkerarmin@googlemail.com> <358eca8f0906020407i79f76afdjaf1e547e44275d02@mail.gmail.com> In-Reply-To: <358eca8f0906020407i79f76afdjaf1e547e44275d02@mail.gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <200906021505.40863.volkerarmin@googlemail.com> X-Archives-Salt: 31a00825-6ae4-4cc4-9bb0-4e7f6f6076da X-Archives-Hash: 5ab7a7e9a9acb5f1c18aa5f2c56e3ae6 On Dienstag 02 Juni 2009, Mick wrote: > 2009/6/2 Volker Armin Hemmann : > > On Dienstag 02 Juni 2009, Mick wrote: > >> This what I am currently running: > >> > >> x11-base/xorg-server-1.5.3-r6 > >> > >> x11-base/xorg-x11-7.2 > >> > >> Is there anything I can do to fix this? > > > > for starters, more informations. Driver versions used. Xorg.0.log before > > crash, maybe dmesg before crash (you know, for hardware stuff), does the > > crash happen with an unpatched kernel too? etc pp. > > I am running the following drivers: > > x11-drivers/xf86-input-evdev-2.1.3 (hal -debug) > x11-drivers/xf86-input-keyboard-1.3.2 (-debug) > x11-drivers/xf86-input-mouse-1.4.0 (-debug) > x11-drivers/xf86-input-synaptics-1.0.0 (hal -debug) > x11-drivers/xf86-video-ati-6.12.1-r1 (-debug) > > Also, these are my mtrr settings in the kernel (not sure if they are > correct): > > CONFIG_MTRR=y > CONFIG_MTRR_SANITIZER=y > CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1 > CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=4 > they are ok - I would reduce spare nr default to '1' because that is all that is needed. But they should not cause a crash. > I am not sure I understand the question about unpatching the kernel - > do you mean vanilla upstream kernel? (I've always used > gentoo-sources). yes, I mean that. Try the vanilla upstream kernel - because if you hit the crash with vanilla kernel, you can start pestering lkml and/or dri-devel and/or radeon devs mailing list. As long as you are using the patched kernel it is a gentoo problem. If you hit it with vanilla too it is a more global linux problem ;)