i810 1.7.4 driver lockups

Alan Hourihane alanh at fairlite.demon.co.uk
Thu Feb 1 09:46:01 PST 2007 

Thomas Hellstrom will be able to comment further, but I think you may
need an updated agpgart module which may not have made 2.6.19.

You can get the latest from

git://anongit.freedesktop.org/git/mesa/linux-agp-compat

Alan.

On Thu, 2007-02-01 at 14:04 -0330, Roderick Greening wrote:
> I went back trough my logs, and I located this in /var/log/messages:
> 
> Feb  1 11:26:59 prometheus BUG: unable to handle kernel NULL pointer 
> dereference at virtual address 00000029
> Feb  1 11:26:59 prometheus printing eip:
> Feb  1 11:26:59 prometheus f9080503
> Feb  1 11:26:59 prometheus *pde = 00000000
> Feb  1 11:26:59 prometheus Oops: 0002 [#1]
> Feb  1 11:26:59 prometheus PREEMPT SMP
> Feb  1 11:26:59 prometheus Modules linked in: i915 drm snd_rtctimer 
> snd_pcm_oss snd_mixer_oss snd_seq_oss snd_seq_midi_event snd_seq 
> snd_usb_audio snd_usb_lib snd_rawmidi snd_seq_device snd_hwdep video thermal 
> processor fan button battery ac sbs i2c_ec acerhk usbhid ipw3945(F) 
> ieee80211 ieee80211_crypt yenta_socket rsrc_nonstatic r8169 firmware_class 
> pcmcia_core snd_hda_intel snd_hda_codec psmouse snd_pcm snd_timer snd pcspkr 
> i2c_i801 intel_agp agpgart soundcore snd_page_alloc
> Feb  1 11:26:59 prometheus CPU:    1
> Feb  1 11:26:59 prometheus EIP:    0060:[<f9080503>]    Tainted: GF     VLI
> Feb  1 11:26:59 prometheus EFLAGS: 00210246   (2.6.19-gentoo-r5 #1)
> Feb  1 11:26:59 prometheus EIP is at drm_agp_bind_ttm+0x83/0xb0 [drm]
> Feb  1 11:26:59 prometheus eax: 00000001   ebx: f5ae21c0   ecx: 00000000   
> edx: 0000e000
> Feb  1 11:26:59 prometheus esi: 00000000   edi: c223ebe0   ebp: 00000000   
> esp: f74bdd78
> Feb  1 11:26:59 prometheus ds: 007b   es: 007b   ss: 0068
> Feb  1 11:26:59 prometheus Process glxgears (pid: 10103, ti=f74bc000 
> task=f760a560 task.ti=f74bc000)
> Feb  1 11:26:59 prometheus Stack: f9084301 00000001 0000e000 00000000 
> 00000100 f51539c0 f5ae21c0 f90843a9
> Feb  1 11:26:59 prometheus f731b0c0 f71d0800 0000e000 00000000 f71d0c98 
> 00000000 f71d081c f731b0c0
> Feb  1 11:26:59 prometheus f71d0800 f9086621 00000000 f9081d38 f713b8c0 
> 03000000 f731b0c0 00000000
> Feb  1 11:26:59 prometheus Call Trace:
> Feb  1 11:26:59 prometheus [<f9084301>] drm_set_caching+0xa1/0xf0 [drm]
> Feb  1 11:26:59 prometheus [<f90843a9>] drm_bind_ttm+0x59/0x1f0 [drm]
> Feb  1 11:26:59 prometheus [<f9086621>] drm_bo_move_buffer+0xc1/0x190 [drm]
> Feb  1 11:26:59 prometheus [<f9081d38>] drm_ht_find_item+0x8/0x20 [drm]
> Feb  1 11:26:59 prometheus [<f9086976>] 
> drm_buffer_object_validate+0x286/0x2e0 [drm]
> Feb  1 11:26:59 prometheus [<f9085dee>] drm_lookup_buffer_object+0x1e/0x90 
> [drm]
> Feb  1 11:26:59 prometheus [<f9087497>] drm_bo_ioctl+0x837/0x870 [drm]
> Feb  1 11:26:59 prometheus [<c011bab0>] default_wake_function+0x0/0x10
> Feb  1 11:26:59 prometheus [<f9086c60>] drm_bo_ioctl+0x0/0x870 [drm]
> Feb  1 11:26:59 prometheus [<f907b12e>] drm_ioctl+0xae/0x210 [drm]
> Feb  1 11:26:59 prometheus [<c030fdaa>] schedule+0x32a/0x910
> Feb  1 11:26:59 prometheus [<c030fddc>] schedule+0x35c/0x910
> Feb  1 11:26:59 prometheus [<f9086c60>] drm_bo_ioctl+0x0/0x870 [drm]
> Feb  1 11:26:59 prometheus [<c0177a48>] do_ioctl+0x78/0x90
> Feb  1 11:26:59 prometheus [<c0177abc>] vfs_ioctl+0x5c/0x2b0
> Feb  1 11:26:59 prometheus [<c0177d82>] sys_ioctl+0x72/0x90
> Feb  1 11:26:59 prometheus [<c01032c1>] sysenter_past_esp+0x56/0x79
> Feb  1 11:26:59 prometheus =======================
> Feb  1 11:26:59 prometheus Code: f9 89 44 24 04 c7 04 24 30 9f 08 f9 e8 47 
> 2d 0a c7 89 d8 8b 74 24 10 8b 5c 24 0c 8b 7c 24 14 8b 6c 24 18 83 c4 1c c3 
> 90 89 43 08 <c6> 46 29 01
> 8b 47 10 eb b4 8d 74 26 00 b8 53 80 08 f9 89 44 24
> Feb  1 11:26:59 prometheus EIP: [<f9080503>] drm_agp_bind_ttm+0x83/0xb0 
> [drm] SS:ESP 0068:f74bdd78
> 
> I assume this will help someone determine where the problem lies.
> 
> Thanks for any assistance on this one.
> 
> 
> >From: Alan Hourihane <alanh at fairlite.demon.co.uk>
> >To: Roderick Greening <roderick_greening at hotmail.com>
> >CC: xorg at lists.freedesktop.org
> >Subject: Re: i810 1.7.4 driver lockups
> >Date: Thu, 01 Feb 2007 17:04:49 +0000
> >MIME-Version: 1.0
> >Received: from anchor-post-35.mail.demon.net ([194.217.242.85]) by 
> >bay0-mc10-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); Thu, 
> >1 Feb 2007 09:05:26 -0800
> >Received: from fairlite.demon.co.uk ([80.176.228.186] 
> >helo=[192.168.0.50])by anchor-post-35.mail.demon.net with esmtp (Exim 
> >4.42)id 1HCfMo-0009mT-Hk; Thu, 01 Feb 2007 17:05:00 +0000
> >X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlK3oXsmRrh6gU=
> >References: <BAY116-F3A6D0085E41F1301C587184A40 at phx.gbl>
> >X-Mailer: Evolution 2.8.2.1 Return-Path: alanh at fairlite.demon.co.uk
> >X-OriginalArrivalTime: 01 Feb 2007 17:05:27.0483 (UTC) 
> >FILETIME=[2BBB18B0:01C74623]
> >
> >With that option you are using the older i915_dri.so 3D driver. But if
> >you take it out you use the new i915tex_dri.so.
> >
> >It may be that your kernel module is causing problems, in which case
> >looking at the output from 'dmesg' will be valuable information when the
> >lockup occurs.
> >
> >Alan.
> >
> >On Thu, 2007-02-01 at 13:19 -0330, Roderick Greening wrote:
> > > Ok, added option and restarted. 3D apps no longer crash.
> > >
> > > Is there a point in which I should be able to turn this option off or is
> > > this something that will need to be left in place indefinately for my 
> >video
> > > card?
> > >
> > >
> > > >From: Alan Hourihane <alanh at fairlite.demon.co.uk>
> > > >To: Roderick Greening <roderick_greening at hotmail.com>
> > > >CC: xorg at lists.freedesktop.org
> > > >Subject: Re: i810 1.7.4 driver lockups
> > > >Date: Thu, 01 Feb 2007 16:43:00 +0000
> > > >MIME-Version: 1.0
> > > >Received: from anchor-post-30.mail.demon.net ([194.217.242.88]) by
> > > >bay0-mc2-f9.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444); 
> >Thu, 1
> > > >Feb 2007 08:43:38 -0800
> > > >Received: from fairlite.demon.co.uk ([80.176.228.186]
> > > >helo=[192.168.0.50])by anchor-post-30.mail.demon.net with esmtp (Exim
> > > >4.42)id 1HCf1Z-0005w7-1R; Thu, 01 Feb 2007 16:43:09 +0000
> > > >X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlK3oXsmRrh6gU=
> > > >References: <BAY116-F163BDB9192B2CD622063384A40 at phx.gbl>
> > > >X-Mailer: Evolution 2.8.2.1 Return-Path: alanh at fairlite.demon.co.uk
> > > >X-OriginalArrivalTime: 01 Feb 2007 16:43:39.0203 (UTC)
> > > >FILETIME=[1FEF6930:01C74620]
> > > >
> > > >The option didn't exist in 1.7.2
> > > >
> > > >Alan.
> > > >
> > > >On Thu, 2007-02-01 at 12:51 -0330, Roderick Greening wrote:
> > > > > I haven't tried that, but I will. It was working without this option
> > > >with
> > > > > xorg 7.2, Mesa 6.5.2 and vid driver 1.7.2 though.
> > > > >
> > > > >
> > > > > >From: Alan Hourihane <alanh at fairlite.demon.co.uk>
> > > > > >To: Roderick Greening <roderick_greening at hotmail.com>
> > > > > >CC: xorg at lists.freedesktop.org
> > > > > >Subject: Re: i810 1.7.4 driver lockups
> > > > > >Date: Thu, 01 Feb 2007 16:02:12 +0000
> > > > > >MIME-Version: 1.0
> > > > > >Received: from anchor-post-35.mail.demon.net ([194.217.242.85]) by
> > > > > >bay0-mc5-f6.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444);
> > > >Thu, 1
> > > > > >Feb 2007 08:03:18 -0800
> > > > > >Received: from fairlite.demon.co.uk ([80.176.228.186]
> > > > > >helo=[192.168.0.50])by anchor-post-35.mail.demon.net with esmtp 
> >(Exim
> > > > > >4.42)id 1HCeO6-000Km3-Ga; Thu, 01 Feb 2007 16:02:17 +0000
> > > > > >X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlK3oXsmRrh6gU=
> > > > > >References: <BAY116-F136A5EC599E707E20D0E0784A40 at phx.gbl>
> > > > > >X-Mailer: Evolution 2.8.2.1 Return-Path: alanh at fairlite.demon.co.uk
> > > > > >X-OriginalArrivalTime: 01 Feb 2007 16:03:18.0698 (UTC)
> > > > > >FILETIME=[7D33A8A0:01C7461A]
> > > > > >
> > > > > >On Thu, 2007-02-01 at 12:04 -0330, Roderick Greening wrote:
> > > > > > > I recently tried using xf86-video-i810 version 1.7.4 (previous
> > > >working
> > > > > >was
> > > > > > > 1.7.2).
> > > > > > >
> > > > > > > I have a gentoo linux setup, with xorg 7.1. The driver version 
> >for
> > > >1.7.2
> > > > > >was
> > > > > > > fine. Upon attempting to use 1.7.4 with any accelerated app, it
> > > >locks up
> > > > > >the
> > > > > > > display. This was with Mesa 6.5.1
> > > > > > >
> > > > > > > I then tried upgrading to xorg 7.2 and Mesa 6.5.2. Again driver
> > > >1.7.2
> > > > > >works
> > > > > > > fine, but 1.7.4 locks up when running any acceletated apps.
> > > > > > >
> > > > > > > My system is an Acer 9410 laptop with Intel 950 chipset (video 
> >card
> > > >is a
> > > > > > > 945).
> > > > > > >
> > > > > > > Any suggestions on what I can try to see 1) why the driver is
> > > >locking up
> > > > > >the
> > > > > > > display and 2) how I can fix this?
> > > > > > >
> > > > > > > Is there anyone out there who has a similar configuration and 
> >has
> > > >this
> > > > > > > driver working?
> > > > > >
> > > > > >Does using the option "Legacy3D" make a difference ?
> > > > > >
> > > > > >Alan.
> > > > > >
> > > > >
> > > > >
> > > >
> > >
> > >
> >
> 
>

More information about the xorg mailing list