From owner-freebsd-hackers@FreeBSD.ORG Sat May 19 19:40:54 2012 Return-Path: Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C11E0106566B for ; Sat, 19 May 2012 19:40:54 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 290F18FC0C for ; Sat, 19 May 2012 19:40:53 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id WAA05199; Sat, 19 May 2012 22:40:52 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1SVpWF-000Bwo-MN; Sat, 19 May 2012 22:40:51 +0300 Message-ID: <4FB7F743.9020405@FreeBSD.org> Date: Sat, 19 May 2012 22:40:51 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120503 Thunderbird/12.0.1 MIME-Version: 1.0 To: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= References: In-Reply-To: X-Enigmail-Version: 1.5pre Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: FreeBSD Hackers Subject: Re: Radeon, DRM and crash on 9.0 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 19 May 2012 19:40:54 -0000 on 19/05/2012 17:52 Fernando Apesteguía said the following: > Hi, > > I'm having some system crashes from time to time. I had this before > but until recently I couldn't set my system so I could get crash > dumps. > > My video card is a ATI Mobility Radeon 9700. I'm running FreeBSD > 9.0-RELEASE for amd64. These are excerpts from two crash dumps text > files: > > core.txt.3: > > Fatal trap 28: machine check trap while in kernel mode > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xffffffff816480a3 > stack pointer = 0x28:0xffffff804a5eb970 > frame pointer = 0x28:0xffffff804a5eb990 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, IOPL = 3 > current process = 2254 (Xorg) > trap number = 28 > panic: machine check trap > cpuid = 0 > KDB: stack backtrace: > #0 0xffffffff80869abe at kdb_backtrace+0x5e > #1 0xffffffff80833fb7 at panic+0x187 > #2 0xffffffff80b18b80 at trap_fatal+0x290 > #3 0xffffffff80b190c0 at trap+0x110 > #4 0xffffffff80b0396f at calltrap+0x8 > #5 0xffffffff816a305b at drm_ioctl+0x31b > #6 0xffffffff8075597b at devfs_ioctl_f+0x7b > #7 0xffffffff8087afb1 at kern_ioctl+0x111 > #8 0xffffffff8087b1df at sys_ioctl+0xef > #9 0xffffffff80b18480 at amd64_syscall+0x450 > #10 0xffffffff80b03c57 at Xfast_syscall+0xf7 > > > Unread portion of the kernel message buffer: > MCA: Bank 4, Status 0xb200000000070f0f > MCA: Global Cap 0x0000000000000105, Status 0x0000000000000004 > MCA: Vendor "AuthenticAMD", ID 0xf4a, APIC ID 0 > MCA: CPU 0 UNCOR PCC BUSLG ??? ERR Other timed out Did you notice that you were getting the machine check exceptions? You might want to google for this term. Anyway, there is sysutils/mcelog port and this is how mcelog utility decodes the above report: HARDWARE ERROR. This is *NOT* a software problem! Please contact your hardware vendor CPU 0 4 northbridge Northbridge Watchdog error bit57 = processor context corrupt bit61 = error uncorrected bus error 'generic participation, request timed out generic error mem transaction generic access, level generic' STATUS b200000000070f0f MCGSTATUS 4 MCGCAP 105 APICID 0 SOCKETID 0 CPUID Vendor AMD Family 15 Model 4 > core.txt.4 > > Fatal trap 28: machine check trap while in kernel mode > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xffffffff816462b6 > stack pointer = 0x28:0xffffff804a5eb930 > frame pointer = 0x28:0xffffff804a5eb940 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = interrupt enabled, IOPL = 3 > current process = 2254 (Xorg) > trap number = 28 > panic: machine check trap > cpuid = 0 > KDB: stack backtrace: > #0 0xffffffff80869abe at kdb_backtrace+0x5e > #1 0xffffffff80833fb7 at panic+0x187 > #2 0xffffffff80b18b80 at trap_fatal+0x290 > #3 0xffffffff80b190c0 at trap+0x110 > #4 0xffffffff80b0396f at calltrap+0x8 > #5 0xffffffff8164f3cc at radeon_cp_indirect+0x24c > #6 0xffffffff816a305b at drm_ioctl+0x31b > #7 0xffffffff8075597b at devfs_ioctl_f+0x7b > #8 0xffffffff8087afb1 at kern_ioctl+0x111 > #9 0xffffffff8087b1df at sys_ioctl+0xef > #10 0xffffffff80b18480 at amd64_syscall+0x450 > #11 0xffffffff80b03c57 at Xfast_syscall+0xf7 > > dmesg | grep agp > agp0: on hostb0 > > drm.ko is loaded and agp is included in kernel. > > AGP for the card seems to be properly detected: > > dmesg | grep drm > drm0: on vgapci0 > info: [drm] AGP at 0xe0000000 256MB > info: [drm] Initialized radeon 1.31.0 20080613 > info: [drm] Setting GART location based on new memory map > info: [drm] Loading R300 Microcode > info: [drm] Num pipes: 1 > > grep -i "Direct rendering" /var/log/Xorg.0.log > (II) RADEON(0): Direct rendering enabled > > The crash is not easily reproducible but seems to be more likely to > occur the more activity there is in the screen (like when scrolling a > window quite fast). > > Any help is appreciated. > > Thanks in advance. > _______________________________________________ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org" > -- Andriy Gapon