Re: Radeon KMS regression still present in 2.6.33-rc6
Am Samstag 30 Januar 2010 18:43:52 schrieb Linus Torvalds:
> On Sat, 30 Jan 2010, Kevin Winchester wrote:
> > I took a picture of the crash details:
> >
> > http://picasaweb.google.ca/kjwinchester/LinuxKernelPanic#5432580230065271
> > 634
> >
> > In case it helps, here is the gdb listing for the problem address:
> >
> > (gdb) l *(radeon_agp_init+0x1d)
> > 0x811c1592 is in radeon_agp_init
> > (drivers/gpu/drm/radeon/radeon_agp.c:136). 131 uint32_t
> > agp_status;
> > 132 int default_mode;
> > 133 bool is_v3;
> > 134 int ret;
> > 135
> > 136 if (rdev->ddev->agp->agp_info.aper_size < 32) {
> > 137 dev_warn(rdev->dev, "AGP aperture to small (%dM) "
> > 138 "need at least 32M, disabling AGP\n",
> > 139 rdev->ddev->agp->agp_info.aper_size);
> > 140 return -EINVAL;
> >
> > Is there any other info I can provide?
>
> In your crash 'rdev->ddev->agp' is NULL. The instruction decode is:
>
>e: 55 push %rbp
>f: 48 89 e5mov%rsp,%rbp
> 12: 41 56 push %r14
> 14: 41 55 push %r13
> 16: 41 54 push %r12
> 18: 53 push %rbx
> 19: 48 89 fbmov%rdi,%rbx
> 1c: 48 83 ec 40 sub$0x40,%rsp
> 20: 48 8b 7f 08 mov0x8(%rdi),%rdi
> 24: 48 8b 87 20 03 00 00mov0x320(%rdi),%rax
> 2b:*4c 8b 60 28 mov0x28(%rax),%r12 <-- trapping
> instruction 2f: 49 83 fc 1f cmp$0x1f,%r12
> 33: 77 2e ja 0x63
> 35: 48 8b 3bmov(%rbx),%rdi
> 38: 48 8b 5f 10 mov0x10(%rdi),%rbx
>
> so it's that lod of "agp_info.aper_size" that fails (you can see how it's
> trying to compare with 31, it comes from that "agp_info.aper_size < 32"
> thing.
>
> Did that DRM init happen before AGP init or something?
>
> Linus
This is caused by commit 42590a75019a50012f25a962246498dead42843
Fix is already posted:
http://marc.info/?l=linux-kernel&m=126428141429200&w=2
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Bug #14938] Unable to handle kernel paging request in radeon_fence_signaled
Am Dienstag 29 Dezember 2009 16:10:01 schrieb Rafael J. Wysocki: > This message has been generated automatically as a part of a report > of recent regressions. > > The following bug entry is on the current list of known regressions > from 2.6.32. Please verify if it still should be listed and let me know > (either way). > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=14938 > Subject : Unable to handle kernel paging request in radeon_fence_signaled > Submitter : Grant Wilson > Date : 2009-12-27 13:40 (3 days old) > References: http://marc.info/?l=linux-kernel&m=126192123104047&w=4 This should be the same as http://bugzilla.kernel.org/show_bug.cgi?id=14910. -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: radeon KMS causes GART Table Walk Errors (was: K8 ECC error with linux-2.6.32)
Am Freitag 18 Dezember 2009 15:44:35 schrieb Jerome Glisse: > On Fri, Dec 18, 2009 at 02:47:00PM +0100, Johannes Hirte wrote: > > Am Mittwoch 16 Dezember 2009 20:31:48 schrieb Johannes Hirte: > > > Am Mittwoch 16 Dezember 2009 19:41:48 schrieb Jerome Glisse: > > > > On Wed, Dec 16, 2009 at 03:58:30PM +0100, Johannes Hirte wrote: > > > > > Am Mittwoch 16 Dezember 2009 08:14:43 schrieb Borislav Petkov: > > > > > > On Tue, Dec 15, 2009 at 11:00:46PM +0100, Johannes Hirte wrote: > > > > > > > This patch (as the BIOS option) will only disable the error > > > > > > > reports. The error itself will still occur, right? So necessary > > > > > > > to find out why the radeon driver trigger this error. > > > > > > > > > > > > Because the graphics driver does aperture accesses with no > > > > > > matching GART translation, and the hw generates mchecks for > > > > > > that. The whole story on GART table walk errors is in section > > > > > > "13.10.1 GART Table Walk Error Reporting" in the document here: > > > > > > http://support.amd.com/us/Processor_TechDocs/32559.pdf > > > > > > > > > > > > I can't say for sure about your BIOS, but if it is done as > > > > > > described in the abovementioned section, the BIOS option should > > > > > > disable logging of the error, which implies reporting too. > > > > > > > > > > > > The patch is still needed for machines that do not have that BIOS > > > > > > option. > > > > > > > > > > Disabling in BIOS doesn't made any difference. The errors were > > > > > still reported. Your patch disabled it. But I think this will make > > > > > work harder for driver developers as they won't get this error > > > > > anymore. Could this be made changeable on runtime/boottime? > > > > > > > > > > I've added drm people to CC as they're responsible for this error. > > > > > > > > > > > > > > > regards, > > > > > Johannes > > > > > > > > More context would be usefull. Are you using KMS ? If so is your > > > > userspace KMS capable ? Does this GART error happen all the time or > > > > only after sometimes or when doing somethings specific ? > > > > > > Yes I'm using KMS when this error occours. > > > Hardware: > > > - Tyan Tiger K8W S8875 (AMD8151 Northbridge) > > > - Radeon HD3650 AGP (RV635) > > > > > > Software: > > > - linux-2.6.32 > > > - libdrm-2.4.16 > > > - mesa-7.7_rc2 > > > - xf86-video-ati- (latest git everytime) > > > - KDE-4.3.4 with compositing enabled (OpenGL) > > > > > > The errors occours after a while of normal desktop work. I haven't > > > tested without KMS or compisiting. Will do this as well. > > > > It's KMS related but not to compositing. Without KMS the errors don't > > occur. I found at least two log entries where the error occurred on > > initializing KMS. It happens reliable after a while working with X. > > > > regards, > > Johannes > > Can you give me the full reference of your motherboard ? > > Cheers, > Jerome > Hm, it seems to be fixed somewhere whithin 2.6.33. I was working with 2.6.33-rc1-00225-gc9f937e more than a day without any errors or screen corruptions, where as with 2.6.32 this happens usually within minutes after login on X. Haven't bisected yet, but will do so. regards, Johannes -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Oops:] radeon KMS in 2.6.33-rc1-00154-gf7b84a6
Am Montag 21 Dezember 2009 22:42:36 schrieb Felipe Balbi: > Hi, > > On Mon, Dec 21, 2009 at 10:38:53PM +0100, ext Johannes Hirte wrote: > >When loading the radeon module with modeset=1, the kernel oopses: > > [snip] > > >Dec 21 21:58:14 datengrab firmware.sh[2542]: Cannot find firmware file > >'radeon/R600_rlc.bin' > > does it have something to do with the missing firmware file ?? Yes, I've tested with the firmware binary from http://people.freedesktop.org/~agd5f/radeon_ucode/ now and it works. It seems a fallback path is missing if no firmware is found. regards, Johannes -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Oops:] radeon KMS in 2.6.33-rc1-00154-gf7b84a6
When loading the radeon module with modeset=1, the kernel oopses: Dec 21 21:58:14 datengrab kernel: [drm] Loading RV635 Microcode Dec 21 21:58:14 datengrab kernel: platform radeon_cp.0: firmware: requesting radeon/RV635_pfp.bin Dec 21 21:58:14 datengrab kernel: platform radeon_cp.0: firmware: requesting radeon/RV635_me.bin Dec 21 21:58:14 datengrab kernel: platform radeon_cp.0: firmware: requesting radeon/R600_rlc.bin Dec 21 21:58:14 datengrab kernel: r600_cp: Failed to load firmware "radeon/R600_rlc.bin" Dec 21 21:58:14 datengrab kernel: [drm:r600_startup] *ERROR* Failed to load firmware! Dec 21 21:58:14 datengrab kernel: radeon :01:00.0: 880119451e00 unpin not necessary Dec 21 21:58:14 datengrab kernel: BUG: unable to handle kernel NULL pointer dereference at 0048 Dec 21 21:58:14 datengrab kernel: IP: [] ttm_bo_reserve+0x18/0xe7 [ttm] Dec 21 21:58:14 datengrab kernel: PGD 0 Dec 21 21:58:14 datengrab kernel: Oops: [#1] SMP Dec 21 21:58:14 datengrab kernel: last sysfs file: /sys/devices/platform/radeon_cp.0/firmware/radeon_cp.0/loading Dec 21 21:58:14 datengrab kernel: CPU 0 Dec 21 21:58:14 datengrab kernel: Pid: 2524, comm: work_for_cpu Not tainted 2.6.33-rc1 #1 TYAN Tiger K8W Dual AMD Opteron, S2875/To Be Filled By O.E.M. Dec 21 21:58:14 datengrab kernel: RIP: 0010:[] [] ttm_bo_reserve+0x18/0xe7 [ttm] Dec 21 21:58:14 datengrab kernel: RSP: 0018:880119731db0 EFLAGS: 00010282 Dec 21 21:58:14 datengrab kernel: RAX: 880119451e80 RBX: 0048 RCX: Dec 21 21:58:14 datengrab kernel: RDX: RSI: 0001 RDI: 0048 Dec 21 21:58:14 datengrab kernel: RBP: R08: R09: 817361c0 Dec 21 21:58:14 datengrab kernel: R10: 8801196f4bd8 R11: a023dda6 R12: 88011fb74001 Dec 21 21:58:14 datengrab kernel: R13: R14: a0247700 R15: 8801196f4bd8 Dec 21 21:58:14 datengrab kernel: FS: 7f4aa0f83700() GS:88002820() knlGS: Dec 21 21:58:14 datengrab kernel: CS: 0010 DS: ES: CR0: 8005003b Dec 21 21:58:14 datengrab kernel: CR2: 0048 CR3: 0161c000 CR4: 06f0 Dec 21 21:58:14 datengrab kernel: DR0: DR1: DR2: Dec 21 21:58:14 datengrab kernel: DR3: DR6: 0ff0 DR7: 0400 Dec 21 21:58:14 datengrab kernel: Process work_for_cpu (pid: 2524, threadinfo 88011973, task 88011b2bf6c0) Dec 21 21:58:14 datengrab kernel: Stack: Dec 21 21:58:14 datengrab kernel: 880119473000 880119601180 880119473000 Dec 21 21:58:14 datengrab kernel: <0> 88011fb74000 0020 a02477e0 a021da29 Dec 21 21:58:14 datengrab kernel: <0> 880119473000 8801196f4800 88011fb74000 a0220ac9 Dec 21 21:58:14 datengrab kernel: Call Trace: Dec 21 21:58:14 datengrab kernel: [] ? r600_suspend+0x49/0xa7 [radeon] Dec 21 21:58:14 datengrab kernel: [] ? r600_init+0x1e3/0x27d [radeon] Dec 21 21:58:14 datengrab kernel: [] ? radeon_device_init+0x24e/0x2cd [radeon] Dec 21 21:58:14 datengrab kernel: [] ? radeon_driver_load_kms+0xb2/0x12c [radeon] Dec 21 21:58:14 datengrab kernel: [] ? drm_get_dev+0x341/0x450 [drm] Dec 21 21:58:14 datengrab kernel: [] ? do_work_for_cpu+0x0/0x1b Dec 21 21:58:14 datengrab kernel: [] ? local_pci_probe+0x12/0x16 Dec 21 21:58:14 datengrab kernel: [] ? do_work_for_cpu+0xb/0x1b Dec 21 21:58:14 datengrab kernel: [] ? kthread+0x75/0x7d Dec 21 21:58:14 datengrab kernel: [] ? kernel_thread_helper+0x4/0x10 Dec 21 21:58:14 datengrab kernel: [] ? kthread+0x0/0x7d Dec 21 21:58:14 datengrab kernel: [] ? kernel_thread_helper+0x0/0x10 Dec 21 21:58:14 datengrab kernel: Code: 00 00 31 c0 48 83 c4 28 5b 5d 41 5c 41 5d 41 5e 41 5f c3 41 56 41 88 ce 41 55 41 88 d5 41 54 41 88 f4 55 53 48 89 fb 48 83 ec 10 <48> 8b 2f 44 89 44 24 08 48 8d bd 88 00 00 00 e8 39 09 18 e1 44 Dec 21 21:58:14 datengrab kernel: RIP [] ttm_bo_reserve+0x18/0xe7 [ttm] Dec 21 21:58:14 datengrab kernel: RSP Dec 21 21:58:14 datengrab kernel: CR2: 0048 Dec 21 21:58:14 datengrab kernel: ---[ end trace b76801f20af7b25e ]--- Dec 21 21:58:14 datengrab firmware.sh[2542]: Cannot find firmware file 'radeon/R600_rlc.bin' regards, Johannes -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[stable] Regression in 2.6.32.2: radeon KMS hangs system
With 2.6.32.2 the system hangs completely with black screen when modprobing
radeon with modeset=1. I was able to connect via ssh, but after entering the
password nothing happend. I didn't got a prompt. Only SysRq worked. I've
tracked it down to the following patch:
>From 500b758725314ab1b5316eb0caa5b0fa26740e6b Mon Sep 17 00:00:00 2001
From: Alex Deucher
Date: Wed, 2 Dec 2009 11:46:52 -0500
Subject: drm/radeon/kms: handle vblanks properly with dpms on
From: Alex Deucher
commit 500b758725314ab1b5316eb0caa5b0fa26740e6b upstream.
avivo chips
Copied from pre-avivo code.
Signed-off-by: Alex Deucher
Signed-off-by: Dave Airlie
Signed-off-by: Greg Kroah-Hartman
---
drivers/gpu/drm/radeon/atombios_crtc.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
--- a/drivers/gpu/drm/radeon/atombios_crtc.c
+++ b/drivers/gpu/drm/radeon/atombios_crtc.c
@@ -241,6 +241,7 @@ void atombios_crtc_dpms(struct drm_crtc
{
struct drm_device *dev = crtc->dev;
struct radeon_device *rdev = dev->dev_private;
+ struct radeon_crtc *radeon_crtc = to_radeon_crtc(crtc);
switch (mode) {
case DRM_MODE_DPMS_ON:
@@ -248,20 +249,19 @@ void atombios_crtc_dpms(struct drm_crtc
if (ASIC_IS_DCE3(rdev))
atombios_enable_crtc_memreq(crtc, 1);
atombios_blank_crtc(crtc, 0);
+ drm_vblank_post_modeset(dev, radeon_crtc->crtc_id);
+ radeon_crtc_load_lut(crtc);
break;
case DRM_MODE_DPMS_STANDBY:
case DRM_MODE_DPMS_SUSPEND:
case DRM_MODE_DPMS_OFF:
+ drm_vblank_pre_modeset(dev, radeon_crtc->crtc_id);
atombios_blank_crtc(crtc, 1);
if (ASIC_IS_DCE3(rdev))
atombios_enable_crtc_memreq(crtc, 0);
atombios_enable_crtc(crtc, 0);
break;
}
-
- if (mode != DRM_MODE_DPMS_OFF) {
- radeon_crtc_load_lut(crtc);
- }
}
static void
After reverting this patch, modesetting works again. It's a Radeon HD3650 AGP
(RV635) on a Tyan Tiger K8W S2875ANRF (AMD 8151 AGP tunnel). Display is an
Acer X223W connected on DVI.
regards,
Johannes
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
--
___
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: radeon KMS causes GART Table Walk Errors (was: K8 ECC error with linux-2.6.32)
Am Freitag 18 Dezember 2009 15:44:35 schrieb Jerome Glisse: > On Fri, Dec 18, 2009 at 02:47:00PM +0100, Johannes Hirte wrote: > > Am Mittwoch 16 Dezember 2009 20:31:48 schrieb Johannes Hirte: > > > Am Mittwoch 16 Dezember 2009 19:41:48 schrieb Jerome Glisse: > > > > On Wed, Dec 16, 2009 at 03:58:30PM +0100, Johannes Hirte wrote: > > > > > Am Mittwoch 16 Dezember 2009 08:14:43 schrieb Borislav Petkov: > > > > > > On Tue, Dec 15, 2009 at 11:00:46PM +0100, Johannes Hirte wrote: > > > > > > > This patch (as the BIOS option) will only disable the error > > > > > > > reports. The error itself will still occur, right? So necessary > > > > > > > to find out why the radeon driver trigger this error. > > > > > > > > > > > > Because the graphics driver does aperture accesses with no > > > > > > matching GART translation, and the hw generates mchecks for > > > > > > that. The whole story on GART table walk errors is in section > > > > > > "13.10.1 GART Table Walk Error Reporting" in the document here: > > > > > > http://support.amd.com/us/Processor_TechDocs/32559.pdf > > > > > > > > > > > > I can't say for sure about your BIOS, but if it is done as > > > > > > described in the abovementioned section, the BIOS option should > > > > > > disable logging of the error, which implies reporting too. > > > > > > > > > > > > The patch is still needed for machines that do not have that BIOS > > > > > > option. > > > > > > > > > > Disabling in BIOS doesn't made any difference. The errors were > > > > > still reported. Your patch disabled it. But I think this will make > > > > > work harder for driver developers as they won't get this error > > > > > anymore. Could this be made changeable on runtime/boottime? > > > > > > > > > > I've added drm people to CC as they're responsible for this error. > > > > > > > > > > > > > > > regards, > > > > > Johannes > > > > > > > > More context would be usefull. Are you using KMS ? If so is your > > > > userspace KMS capable ? Does this GART error happen all the time or > > > > only after sometimes or when doing somethings specific ? > > > > > > Yes I'm using KMS when this error occours. > > > Hardware: > > > - Tyan Tiger K8W S8875 (AMD8151 Northbridge) > > > - Radeon HD3650 AGP (RV635) > > > > > > Software: > > > - linux-2.6.32 > > > - libdrm-2.4.16 > > > - mesa-7.7_rc2 > > > - xf86-video-ati- (latest git everytime) > > > - KDE-4.3.4 with compositing enabled (OpenGL) > > > > > > The errors occours after a while of normal desktop work. I haven't > > > tested without KMS or compisiting. Will do this as well. > > > > It's KMS related but not to compositing. Without KMS the errors don't > > occur. I found at least two log entries where the error occurred on > > initializing KMS. It happens reliable after a while working with X. > > > > regards, > > Johannes > > Can you give me the full reference of your motherboard ? > > Cheers, > Jerome > Tyan Tiger K8W (S2875ANRF) http://tyan.com/product_board_detail.aspx?pid=103 regards, Johannes -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: radeon KMS causes GART Table Walk Errors (was: K8 ECC error with linux-2.6.32)
Am Mittwoch 16 Dezember 2009 20:31:48 schrieb Johannes Hirte: > Am Mittwoch 16 Dezember 2009 19:41:48 schrieb Jerome Glisse: > > On Wed, Dec 16, 2009 at 03:58:30PM +0100, Johannes Hirte wrote: > > > Am Mittwoch 16 Dezember 2009 08:14:43 schrieb Borislav Petkov: > > > > On Tue, Dec 15, 2009 at 11:00:46PM +0100, Johannes Hirte wrote: > > > > > This patch (as the BIOS option) will only disable the error > > > > > reports. The error itself will still occur, right? So necessary to > > > > > find out why the radeon driver trigger this error. > > > > > > > > Because the graphics driver does aperture accesses with no > > > > matching GART translation, and the hw generates mchecks for > > > > that. The whole story on GART table walk errors is in section > > > > "13.10.1 GART Table Walk Error Reporting" in the document here: > > > > http://support.amd.com/us/Processor_TechDocs/32559.pdf > > > > > > > > I can't say for sure about your BIOS, but if it is done as described > > > > in the abovementioned section, the BIOS option should disable logging > > > > of the error, which implies reporting too. > > > > > > > > The patch is still needed for machines that do not have that BIOS > > > > option. > > > > > > Disabling in BIOS doesn't made any difference. The errors were still > > > reported. Your patch disabled it. But I think this will make work > > > harder for driver developers as they won't get this error anymore. > > > Could this be made changeable on runtime/boottime? > > > > > > I've added drm people to CC as they're responsible for this error. > > > > > > > > > regards, > > > Johannes > > > > More context would be usefull. Are you using KMS ? If so is your > > userspace KMS capable ? Does this GART error happen all the time or only > > after sometimes or when doing somethings specific ? > > Yes I'm using KMS when this error occours. > Hardware: > - Tyan Tiger K8W S8875 (AMD8151 Northbridge) > - Radeon HD3650 AGP (RV635) > > Software: > - linux-2.6.32 > - libdrm-2.4.16 > - mesa-7.7_rc2 > - xf86-video-ati- (latest git everytime) > - KDE-4.3.4 with compositing enabled (OpenGL) > > The errors occours after a while of normal desktop work. I haven't tested > without KMS or compisiting. Will do this as well. It's KMS related but not to compositing. Without KMS the errors don't occur. I found at least two log entries where the error occurred on initializing KMS. It happens reliable after a while working with X. regards, Johannes -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: radeon KMS causes GART Table Walk Errors (was: K8 ECC error with linux-2.6.32)
Am Mittwoch 16 Dezember 2009 19:41:48 schrieb Jerome Glisse: > On Wed, Dec 16, 2009 at 03:58:30PM +0100, Johannes Hirte wrote: > > Am Mittwoch 16 Dezember 2009 08:14:43 schrieb Borislav Petkov: > > > On Tue, Dec 15, 2009 at 11:00:46PM +0100, Johannes Hirte wrote: > > > > This patch (as the BIOS option) will only disable the error reports. > > > > The error itself will still occur, right? So necessary to find out > > > > why the radeon driver trigger this error. > > > > > > Because the graphics driver does aperture accesses with no > > > matching GART translation, and the hw generates mchecks for > > > that. The whole story on GART table walk errors is in section > > > "13.10.1 GART Table Walk Error Reporting" in the document here: > > > http://support.amd.com/us/Processor_TechDocs/32559.pdf > > > > > > I can't say for sure about your BIOS, but if it is done as described in > > > the abovementioned section, the BIOS option should disable logging of > > > the error, which implies reporting too. > > > > > > The patch is still needed for machines that do not have that BIOS > > > option. > > > > Disabling in BIOS doesn't made any difference. The errors were still > > reported. Your patch disabled it. But I think this will make work harder > > for driver developers as they won't get this error anymore. Could this be > > made changeable on runtime/boottime? > > > > I've added drm people to CC as they're responsible for this error. > > > > > > regards, > > Johannes > > More context would be usefull. Are you using KMS ? If so is your userspace > KMS capable ? Does this GART error happen all the time or only after > sometimes or when doing somethings specific ? Yes I'm using KMS when this error occours. Hardware: - Tyan Tiger K8W S8875 (AMD8151 Northbridge) - Radeon HD3650 AGP (RV635) Software: - linux-2.6.32 - libdrm-2.4.16 - mesa-7.7_rc2 - xf86-video-ati- (latest git everytime) - KDE-4.3.4 with compositing enabled (OpenGL) The errors occours after a while of normal desktop work. I haven't tested without KMS or compisiting. Will do this as well. regards, Johannes -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
radeon KMS causes GART Table Walk Errors (was: K8 ECC error with linux-2.6.32)
Am Mittwoch 16 Dezember 2009 08:14:43 schrieb Borislav Petkov: > On Tue, Dec 15, 2009 at 11:00:46PM +0100, Johannes Hirte wrote: > > This patch (as the BIOS option) will only disable the error reports. The > > error itself will still occur, right? So necessary to find out why the > > radeon driver trigger this error. > > Because the graphics driver does aperture accesses with no > matching GART translation, and the hw generates mchecks for > that. The whole story on GART table walk errors is in section > "13.10.1 GART Table Walk Error Reporting" in the document here: > http://support.amd.com/us/Processor_TechDocs/32559.pdf > > I can't say for sure about your BIOS, but if it is done as described in > the abovementioned section, the BIOS option should disable logging of > the error, which implies reporting too. > > The patch is still needed for machines that do not have that BIOS > option. Disabling in BIOS doesn't made any difference. The errors were still reported. Your patch disabled it. But I think this will make work harder for driver developers as they won't get this error anymore. Could this be made changeable on runtime/boottime? I've added drm people to CC as they're responsible for this error. regards, Johannes -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[OOPS] Radeon KMS with 2.6.32 and agp not compiled in
When the agp driver is not compiled in but is build as module, the kernel oopes on modprobing radeon with modeset=1. Dec 7 22:08:53 datengrab kernel: BUG: unable to handle kernel NULL pointer dereference at 0074 Dec 7 22:08:53 datengrab kernel: IP: [] radeon_agp_init+0x18/0x23c [radeon] Dec 7 22:08:53 datengrab kernel: PGD 0 Dec 7 22:08:53 datengrab kernel: Oops: [#1] SMP Dec 7 22:08:53 datengrab kernel: last sysfs file: /sys/module/agpgart/initstate Dec 7 22:08:53 datengrab kernel: CPU 0 Dec 7 22:08:53 datengrab kernel: Modules linked in: radeon(+) ttm drm_kms_helper drm i2c_algo_bit snd_seq_midi snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss snd_mixer_oss aes_x86_64 aes_generic xts gf128mul dm_crypt snd_emu10k1 snd_rawmidi snd_ac97_codec ac97_bus snd_pcm snd_seq_device snd_timer snd_page_alloc snd_util_mem snd_hwdep ohci_hcd i2c_amd8111 uhci_hcd sg snd amd64_agp sata_sil k8temp agpgart i2c_amd756 sr_mod hwmon Dec 7 22:08:53 datengrab kernel: Pid: 2531, comm: work_for_cpu Not tainted 2.6.32 #2 To Be Filled By O.E.M. Dec 7 22:08:53 datengrab kernel: RIP: 0010:[] [] radeon_agp_init+0x18/0x23c [radeon] Dec 7 22:08:53 datengrab kernel: RSP: 0018:8801172c3d80 EFLAGS: 00010282 Dec 7 22:08:53 datengrab kernel: RAX: RBX: 88011841 RCX: 88011fb97800 Dec 7 22:08:53 datengrab kernel: RDX: c000 RSI: RDI: 88011e43d800 Dec 7 22:08:53 datengrab kernel: RBP: R08: a0238201 R09: 8801172c3d90 Dec 7 22:08:53 datengrab kernel: R10: 81589940 R11: 0400 R12: 88011fb97800 Dec 7 22:08:53 datengrab kernel: R13: 0020 R14: a0243240 R15: 88011e43dbc0 Dec 7 22:08:53 datengrab kernel: FS: 7f0e85a7f700() GS:88002820() knlGS: Dec 7 22:08:53 datengrab kernel: CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b Dec 7 22:08:53 datengrab kernel: CR2: 0074 CR3: 01001000 CR4: 06f0 Dec 7 22:08:53 datengrab kernel: DR0: DR1: DR2: Dec 7 22:08:53 datengrab kernel: DR3: DR6: 0ff0 DR7: 0400 Dec 7 22:08:53 datengrab kernel: Process work_for_cpu (pid: 2531, threadinfo 8801172c2000, task 8801188d2280) Dec 7 22:08:53 datengrab kernel: Stack: Dec 7 22:08:53 datengrab kernel: 88011e43dbc0 813436f0 88010008 8801172c3df0 Dec 7 22:08:53 datengrab kernel: <0> 8801172c3db0 0246 88011841 880118410144 Dec 7 22:08:53 datengrab kernel: <0> 0282 88011841 88011fb97800 Dec 7 22:08:53 datengrab kernel: Call Trace: Dec 7 22:08:53 datengrab kernel: [] ? printk+0x40/0x48 Dec 7 22:08:53 datengrab kernel: [] ? r600_mc_init+0xf0/0x251 [radeon] Dec 7 22:08:53 datengrab kernel: [] ? r600_init+0x154/0x2b7 [radeon] Dec 7 22:08:53 datengrab kernel: [] ? radeon_device_init+0x1fe/0x276 [radeon] Dec 7 22:08:53 datengrab kernel: [] ? radeon_driver_load_kms+0xb2/0xec [radeon] Dec 7 22:08:53 datengrab kernel: [] ? drm_get_dev+0x322/0x42e [drm] Dec 7 22:08:53 datengrab kernel: [] ? do_work_for_cpu+0x0/0x1b Dec 7 22:08:53 datengrab kernel: [] ? local_pci_probe+0x12/0x16 Dec 7 22:08:53 datengrab kernel: [] ? do_work_for_cpu+0xb/0x1b Dec 7 22:08:53 datengrab kernel: [] ? kthread+0x75/0x7d Dec 7 22:08:53 datengrab kernel: [] ? child_rip+0xa/0x20 Dec 7 22:08:53 datengrab kernel: [] ? kthread+0x0/0x7d Dec 7 22:08:53 datengrab kernel: [] ? child_rip+0x0/0x20 Dec 7 22:08:53 datengrab kernel: Code: 48 85 c0 74 0c 83 78 74 00 74 06 5a e9 c3 5e fa ff 58 c3 41 55 41 54 55 53 48 89 fb 48 83 ec 48 48 8b 7f 08 48 8b 87 48 03 00 00 <83> 78 74 00 75 1d e8 38 5e fa ff 85 c0 89 c5 74 12 89 c2 48 c7 Dec 7 22:08:53 datengrab kernel: RIP [] radeon_agp_init+0x18/0x23c [radeon] Dec 7 22:08:53 datengrab kernel: RSP Dec 7 22:08:53 datengrab kernel: CR2: 0074 Dec 7 22:08:53 datengrab kernel: ---[ end trace b9e94e547b237285 ]--- -- Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
