Date: Sun, 20 May 2012 13:31:37 +0200 From: =?ISO-8859-1?Q?Fernando_Apestegu=EDa?= <fernando.apesteguia@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Radeon, DRM and crash on 9.0 Message-ID: <CAGwOe2YBqftON-7vN-Eb99hCGcXA-E-_3i48yiAOD8zBPNwndQ@mail.gmail.com> In-Reply-To: <4FB7F743.9020405@FreeBSD.org> References: <CAGwOe2a14UtKvuY4YoB4-W2cssUhjC1rqi3GQD_BffH9Sum52w@mail.gmail.com> <4FB7F743.9020405@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 19, 2012 at 9:40 PM, Andriy Gapon <avg@freebsd.org> wrote: > on 19/05/2012 17:52 Fernando Apestegu=EDa 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 =3D 0; apic id =3D 00 >> instruction pointer =A0 =A0 =3D 0x20:0xffffffff816480a3 >> stack pointer =A0 =A0 =A0 =A0 =A0 =3D 0x28:0xffffff804a5eb970 >> frame pointer =A0 =A0 =A0 =A0 =A0 =3D 0x28:0xffffff804a5eb990 >> code segment =A0 =A0 =A0 =A0 =A0 =A0=3D base 0x0, limit 0xfffff, type 0x= 1b >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D DPL 0, pres 1, long 1= , def32 0, gran 1 >> processor eflags =A0 =A0 =A0 =A0=3D interrupt enabled, IOPL =3D 3 >> current process =A0 =A0 =A0 =A0 =3D 2254 (Xorg) >> trap number =A0 =A0 =A0 =A0 =A0 =A0 =3D 28 >> panic: machine check trap >> cpuid =3D 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 deco= des the > above report: > HARDWARE ERROR. This is *NOT* a software problem! > Please contact your hardware vendor > CPU 0 4 northbridge > =A0Northbridge Watchdog error > =A0 =A0 =A0 bit57 =3D processor context corrupt > =A0 =A0 =A0 bit61 =3D error uncorrected > =A0bus error 'generic participation, request timed out > =A0 =A0 =A0 =A0 =A0 =A0 generic error mem transaction > =A0 =A0 =A0 =A0 =A0 =A0 generic access, level generic' > STATUS b200000000070f0f MCGSTATUS 4 > MCGCAP 105 APICID 0 SOCKETID 0 > CPUID Vendor AMD Family 15 Model 4 Thanks for the reply. I found some information about this specific error. It seems it could be caused by overheating (among other things), and it's true this laptop can become really hot at times. I'll have a look at it. Thanks! > >> core.txt.4 >> >> Fatal trap 28: machine check trap while in kernel mode >> cpuid =3D 0; apic id =3D 00 >> instruction pointer =A0 =A0 =3D 0x20:0xffffffff816462b6 >> stack pointer =A0 =A0 =A0 =A0 =A0 =3D 0x28:0xffffff804a5eb930 >> frame pointer =A0 =A0 =A0 =A0 =A0 =3D 0x28:0xffffff804a5eb940 >> code segment =A0 =A0 =A0 =A0 =A0 =A0=3D base 0x0, limit 0xfffff, type 0x= 1b >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=3D DPL 0, pres 1, long 1= , def32 0, gran 1 >> processor eflags =A0 =A0 =A0 =A0=3D interrupt enabled, IOPL =3D 3 >> current process =A0 =A0 =A0 =A0 =3D 2254 (Xorg) >> trap number =A0 =A0 =A0 =A0 =A0 =A0 =3D 28 >> panic: machine check trap >> cpuid =3D 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: <VIA 8385 host to PCI bridge> on hostb0 >> >> drm.ko is loaded and agp is included in kernel. >> >> AGP =A0for the card seems to be properly detected: >> >> dmesg | grep drm >> drm0: <ATI Radeon RV350 Mobility 9600 M10 NP> 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.or= g" >> > > > -- > Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAGwOe2YBqftON-7vN-Eb99hCGcXA-E-_3i48yiAOD8zBPNwndQ>