1.0-5328 Oops with Fedora Core 1 and Vanilla 2.4.23

drees · 12-23-03, 02:27 AM

I'm getting an Oops when starting X with the 1.0-5328 drivers. I'm running Fedora Core 1 and a vanilla 2.4.23 kernel.

Code:

Unable to handle kernel paging request at virtual address f000e846
c0217263
*pde = 00000000
Oops: 0000
CPU:    0
EIP:    0010:[<c0217263>]    Tainted: P
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00013046
eax: f000e816   ebx: 00003246   ecx: 00000048   edx: 00000000
esi: 00000000   edi: d3fd3000   ebp: cc2fb780   esp: cc2fb750
ds: 0018   es: 0018   ss: 0018
Process X (pid: 3854, stackpage=cc2fb000)
Stack: d3532800 cc2fb7ac c010ec6c cacb0c00 00003116 d6ac0b7b 00000000 00000048
       cc2fb77c d6acfbbe d3ae3c00 00000000 cc2fb790 d6ada76d 00000000 00000048
       cc2fb7bc d6ad2d86 cacb0c00 00000000 00000048 d6cc2a80 d3d20000 d3532800
Call Trace:    [<c010ec6c>] [<d6ac0b7b>] [<d6acfbbe>] [<d6ada76d>] [<d6ad2d86>]
  [<d6cc2a80>] [<d6ad6657>] [<d6cc2a80>] [<d6adeae6>] [<d6abf985>] [<d6cc2a80>]
  [<d6cc332c>] [<d6cc3350>] [<d6cc3368>] [<d6cc32c0>] [<d6cc2a80>] [<d6cc32c0>]
  [<d6cc2a80>] [<d6adc4fc>] [<d6cc2a80>] [<d6cc332c>] [<d6cc3350>] [<d6cc3368>]
  [<d6cc2a80>] [<d6adf6a9>] [<d6cc2a80>] [<d6cc2a80>] [<d6b6a872>] [<d6c4dba1>]
  [<d6af7497>] [<d6acfbbe>] [<d6ada6b8>] [<d6c49ff1>] [<d6adc07b>] [<d6c49ff1>]
  [<d6c49ff1>] [<d6adc0cc>] [<d6c9ada0>] [<d6ba617b>] [<d6af2d78>] [<d6b0060d>]
  [<d6ba617b>] [<d6ba6961>] [<d6ad02ba>] [<d6ac17fb>] [<d6ac16d0>] [<d6ad0445>]
  [<d6adbc22>] [<d6cc2a80>] [<d6b6d4c7>] [<d6ba65df>] [<d6ac1035>] [<d6ba617b>]
  [<d6ba6961>] [<d6ba617b>] [<d6ba6961>] [<d6beef74>] [<d6b9f3f2>] [<d6b886d3>]
  [<d6adbc22>] [<d6cc2a80>] [<d6b8a321>] [<d6bb8e65>] [<d6ae0229>] [<d6b8a1e5>]
  [<d6ae2fa2>] [<d6adbc22>] [<d6cc2a80>] [<d6ace3db>] [<d6b8aa64>] [<d6b8a95b>]
  [<d6cc2a80>] [<d6abfb3f>] [<d6c5aa94>] [<d6adea91>] [<d6cc2a80>] [<d6abe843>]
  [<d6cc2a80>] [<c0112f34>] [<c013c98d>] [<c013cbb6>] [<d6abe5d5>] [<c0149cfd>]
  [<c010730f>]
Code: 8b 50 30 89 34 24 89 4c 24 04 8b 44 24 20 89 44 24 08 ff 52


>>EIP; c0217263 <pci_read_config_dword+23/50>   <=====

>>edi; d3fd3000 <_end+13c66294/14557314>
>>ebp; cc2fb780 <_end+bf8ea14/14557314>
>>esp; cc2fb750 <_end+bf8e9e4/14557314>

Trace; c010ec6c <pci_conf1_read_config_dword+4c/50>
Trace; d6ac0b7b <[nvidia]os_pci_read_dword+17/1c>
Trace; d6acfbbe <[nvidia]_nv001370rm+2e/cc>
Trace; d6ada76d <[nvidia]_nv001241rm+11/18>
Trace; d6ad2d86 <[nvidia]_nv000171rm+22a/268>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6ad6657 <[nvidia]_nv001749rm+167/50c>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6adeae6 <[nvidia]rm_update_agp_config+e/14>
Trace; d6abf985 <[nvidia]nv_agp_init+66/df>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6cc332c <[nvidia]_nv000443rm+160/fd9eb4>
Trace; d6cc3350 <[nvidia]_nv000443rm+184/fd9eb4>
Trace; d6cc3368 <[nvidia]_nv000443rm+19c/fd9eb4>
Trace; d6cc32c0 <[nvidia]_nv000443rm+f4/fd9eb4>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6cc32c0 <[nvidia]_nv000443rm+f4/fd9eb4>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6adc4fc <[nvidia]_nv001274rm+7c/b8>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6cc332c <[nvidia]_nv000443rm+160/fd9eb4>
Trace; d6cc3350 <[nvidia]_nv000443rm+184/fd9eb4>
Trace; d6cc3368 <[nvidia]_nv000443rm+19c/fd9eb4>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6adf6a9 <[nvidia]_nv000899rm+7e9/f70>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6b6a872 <[nvidia]_nv006308rm+1e/28>
Trace; d6c4dba1 <[nvidia]_nv006300rm+d59/1038>
Trace; d6af7497 <[nvidia]_nv005199rm+17/a0>
Trace; d6acfbbe <[nvidia]_nv001370rm+2e/cc>
Trace; d6ada6b8 <[nvidia]_nv001212rm+10/14>
Trace; d6c49ff1 <[nvidia]_nv000406rm+4d1/17a0>
Trace; d6adc07b <[nvidia]_nv001016rm+3b/64>
Trace; d6c49ff1 <[nvidia]_nv000406rm+4d1/17a0>
Trace; d6c49ff1 <[nvidia]_nv000406rm+4d1/17a0>
Trace; d6adc0cc <[nvidia]_nv001228rm+28/78>
Trace; d6c9ada0 <[nvidia]_nv000797rm+0/3e>
Trace; d6ba617b <[nvidia]_nv001532rm+1f/28>
Trace; d6af2d78 <[nvidia]_nv004240rm+180/18c>
Trace; d6b0060d <[nvidia]_nv003333rm+10ed/1100>
Trace; d6ba617b <[nvidia]_nv001532rm+1f/28>
Trace; d6ba6961 <[nvidia]_nv003619rm+19/20>
Trace; d6ad02ba <[nvidia]_nv001344rm+22/6c>
Trace; d6ac17fb <[nvidia]_nv005593rm+13/34>
Trace; d6ac16d0 <[nvidia]_nv005594rm+14/58>
Trace; d6ad0445 <[nvidia]_nv001338rm+1d/24>
Trace; d6adbc22 <[nvidia]_nv001223rm+12/18>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6b6d4c7 <[nvidia]_nv003847rm+173/1b0>
Trace; d6ba65df <[nvidia]_nv001535rm+1f/28>
Trace; d6ac1035 <[nvidia]_nv005601rm+d/34>
Trace; d6ba617b <[nvidia]_nv001532rm+1f/28>
Trace; d6ba6961 <[nvidia]_nv003619rm+19/20>
Trace; d6ba617b <[nvidia]_nv001532rm+1f/28>
Trace; d6ba6961 <[nvidia]_nv003619rm+19/20>
Trace; d6beef74 <[nvidia]_nv001823rm+2c/38>
Trace; d6b9f3f2 <[nvidia]_nv002279rm+a2/b0>
Trace; d6b886d3 <[nvidia]_nv003832rm+117/12c>
Trace; d6adbc22 <[nvidia]_nv001223rm+12/18>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6b8a321 <[nvidia]_nv003785rm+5d/6c>
Trace; d6bb8e65 <[nvidia]_nv003612rm+1c5/1fc>
Trace; d6ae0229 <[nvidia]_nv006208rm+39/44>
Trace; d6b8a1e5 <[nvidia]_nv003831rm+65/a8>
Trace; d6ae2fa2 <[nvidia]_nv005643rm+96/c4>
Trace; d6adbc22 <[nvidia]_nv001223rm+12/18>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6ace3db <[nvidia]_nv001218rm+6b/78>
Trace; d6b8aa64 <[nvidia]_nv000012rm+0/58>
Trace; d6b8a95b <[nvidia]_nv003805rm+2a3/2bc>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6abfb3f <[nvidia]nv_start_rc_timer+73/7f>
Trace; d6c5aa94 <[nvidia].rodata.end+55a/3f886>
Trace; d6adea91 <[nvidia]rm_ioctl+19/20>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; d6abe843 <[nvidia]nv_kern_ioctl+26e/2b4>
Trace; d6cc2a80 <[nvidia]nv_linux_devices+0/580>
Trace; c0112f34 <mtrr_ioctl+3e4/570>
Trace; c013c98d <get_empty_filp+4d/120>
Trace; c013cbb6 <fput+c6/120>
Trace; d6abe5d5 <[nvidia]nv_kern_ioctl+0/2b4>
Trace; c0149cfd <sys_ioctl+bd/240>
Trace; c010730f <system_call+33/38>

Code;  c0217263 <pci_read_config_dword+23/50>
00000000 <_EIP>:
Code;  c0217263 <pci_read_config_dword+23/50>   <=====
   0:   8b 50 30                  mov    0x30(%eax),%edx   <=====
Code;  c0217266 <pci_read_config_dword+26/50>
   3:   89 34 24                  mov    %esi,(%esp,1)
Code;  c0217269 <pci_read_config_dword+29/50>
   6:   89 4c 24 04               mov    %ecx,0x4(%esp,1)
Code;  c021726d <pci_read_config_dword+2d/50>
   a:   8b 44 24 20               mov    0x20(%esp,1),%eax
Code;  c0217271 <pci_read_config_dword+31/50>
   e:   89 44 24 08               mov    %eax,0x8(%esp,1)
Code;  c0217275 <pci_read_config_dword+35/50>
  12:   ff 52 00                  call   *0x0(%edx)

The patches at minion.de don't compile under 2.4 without commenting out line "typedef of irqreturn_t" in nv-linux.h. However, even after a successful compile, X fails to start up.

Back to the old stable version for me which worked OK.

bwkaz · 12-23-03, 08:59 AM

Looks like the same oops I'm getting on both 2.6.0 and 2.4.23 (vanilla also).

See if the patch here helps at all. If you're feeling lucky, at least. It doesn't hurt my hardware, but ... yeah.

Instructions are in that post.

drees · 12-24-03, 01:45 AM

Thanks for the input.

Here's what works and what doesn't work on my machine:

Duron 800
MSI KM2M Combo-L (Via KM266 chipset)
ASUS FX 5200 64MB

Fedora Core 1, Vanilla 2.4.23 kernel.

-5338
Oops when starting X. If I set NvAGP to 1 in XF86Config it appears to work OK, but this basically disabled AGP as I have agpgart compiled into the kernel. I didn't try setting NvAGP to 0, but I suspect this would also work. glxgears results in about 1300 fps. I'm using the Composite video out as the display device, and in X the display was pretty jittery. Overscan does NOT work.

-4496
Everything appears to load OK. However, running glxgears results in the X server crashing. TV-out slightly less jittery than -5338. Overscan does NOT work.

-4363
Everything appears to load OK. glxgears results in 2000 fps. TV-out very solid, very little jitter. Overscan WORKS!

The moral? The latest drivers aren't necessarily the best ones to use for your system.

12-23-03, 08:59 AM	#2
bwkaz Registered User Join Date: Sep 2002 Posts: 2,262	Looks like the same oops I'm getting on both 2.6.0 and 2.4.23 (vanilla also). See if the patch here helps at all. If you're feeling lucky, at least. It doesn't hurt my hardware, but ... yeah. Instructions are in that post. __________________ Registered Linux User #219692

12-24-03, 01:45 AM	#3
drees Registered User Join Date: Dec 2003 Posts: 13	Thanks for the input. Here's what works and what doesn't work on my machine: Duron 800 MSI KM2M Combo-L (Via KM266 chipset) ASUS FX 5200 64MB Fedora Core 1, Vanilla 2.4.23 kernel. -5338 Oops when starting X. If I set NvAGP to 1 in XF86Config it appears to work OK, but this basically disabled AGP as I have agpgart compiled into the kernel. I didn't try setting NvAGP to 0, but I suspect this would also work. glxgears results in about 1300 fps. I'm using the Composite video out as the display device, and in X the display was pretty jittery. Overscan does NOT work. -4496 Everything appears to load OK. However, running glxgears results in the X server crashing. TV-out slightly less jittery than -5338. Overscan does NOT work. -4363 Everything appears to load OK. glxgears results in 2000 fps. TV-out very solid, very little jitter. Overscan WORKS! The moral? The latest drivers aren't necessarily the best ones to use for your system.