Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux


                    

Sponsored Ad

Reply
 
Thread Tools
Old 04-11-06, 11:49 AM   #1
rscharp
frosch01
 
Join Date: Apr 2006
Location: Stuttgart/Germany
Posts: 1
Default Kernel-Oops

Hi,

I tried the latest 2 drivers 8756 and 8178 on my Dell Inspiron i8000 Laptop. It uses a Geforce2-Go chipset. The resolution is 1600x1200.

The last driver working was 7676 at kernels 2.6.14 and 2.6.15. Now with 2.6.16 I am not able to compile the kernel module. With older Kernels the 7676 driver is working well.

During installation there occurs a warning that the installation expects to see the link /usr/lib/tls/libnvidia-tls.so.1 instead of /usr/lib/libnvidia-tls.so.1. The links refernce the files /usr/lib/tls/libnvidia-tls.so.1.0.8756 and /usr/lib/libnvidia-tls.so.1.0.8756. These two files are not identical. I tried to ignore the error since the rest of installation seems to be successful.

So I continued with loading the nvidia module which was fine. After trying to start X (by running X as root) the display hangs up and I see only a black screen. I am not able to switch back to text mode. The keyboard seems still to work.

After logging in remote I tried to run nvidia-bug-report.sh. But it hung up also so I had to abort it.

When I run dmseg I see the following:

Code:
nvidia: module license 'NVIDIA' taints kernel.
ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 11
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
NVRM: loading NVIDIA Linux x86 Kernel Module  1.0-8756  Wed Mar 29 14:26:26 PST 2006
ACPI: PCI Interrupt 0000:01:00.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11
NVRM: loading NVIDIA Linux x86 Kernel Module  1.0-8756  Wed Mar 29 14:26:26 PST 2006
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
Unable to handle kernel NULL pointer dereference at virtual address 00000104
 printing eip:
d1076baa
*pde = 00000000
Oops: 0000 [#1]
Modules linked in: nvidia lp ipv6 dm_mod rtc eth1394 psmouse parport_pc serio_raw parport yenta_socket snd_maestro3 snd_ac97_codec snd_ac97_bus rsrc_nonstatic pcmcia_core snd_pcm snd_timer snd_page_alloc snd soundcore i2c_core hw_random shpchp pci_hotplug i8xx_tco intel_agp agpgart ext3 jbd mbcache usbhid ide_cd cdrom ide_disk e100 mii ohci1394 ieee1394 uhci_hcd usbcore piix generic ide_core thermal processor fan
CPU:    0
EIP:    0060:[<d1076baa>]    Tainted: P      VLI
EFLAGS: 00013287   (2.6.16-1-686 #1)
EIP is at _nv004158rm+0x7da/0x188c [nvidia]
eax: 00000000   ebx: ca2d2c00   ecx: ce801800   edx: 00000000
esi: 00000000   edi: c95f5c15   ebp: c95f5c2c   esp: c95f5a94
ds: 007b   es: 007b   ss: 0068
Process Xorg (pid: 7487, threadinfo=c95f4000 task=cf604ab0)
Stack: <0>00000000 00000000 00000004 d1006f2a cfdc5400 ce866800 ce801800 d1006f2a
       ce86681c 0000002e c95f5adc d117cd57 0000000d 00000001 ce801800 cb888400
       cfdc5400 ce866800 cd453400 d117cc90 00000000 00000080 cfc38a00 00000000
Call Trace:
 [<d1006f2a>] _nv002668rm+0x26/0x2c [nvidia]
 [<d1006f2a>] _nv002668rm+0x26/0x2c [nvidia]
 [<d117cd57>] _nv005436rm+0x23/0x28 [nvidia]
 [<d117cc90>] _nv005438rm+0x28/0x44 [nvidia]
 [<d1017a4a>] _nv002534rm+0x1a/0x6c [nvidia]
 [<d117c394>] _nv005205rm+0x8c/0x98 [nvidia]
 [<d117c5ce>] _nv005247rm+0x6a/0x7c [nvidia]
 [<d110db3c>] _nv000419rm+0x24/0x28 [nvidia]
 [<d110db0f>] _nv000457rm+0x1f/0x28 [nvidia]
 [<d110734e>] _nv000417rm+0x4e/0x58 [nvidia]
 [<d117e549>] _nv005236rm+0x51/0x90 [nvidia]
 [<d117e2c1>] _nv005453rm+0x6d/0x78 [nvidia]
 [<d1006f2a>] _nv002668rm+0x26/0x2c [nvidia]
 [<d1006f58>] _nv002662rm+0x28/0x30 [nvidia]
 [<d1074b2d>] _nv004159rm+0x36d/0x12bc [nvidia]
 [<d1016262>] _nv002583rm+0x16/0x2c [nvidia]
 [<d1006da0>] _nv002673rm+0x38/0x50 [nvidia]
 [<d1080a40>] _nv001518rm+0x80/0x2dc [nvidia]
 [<d1080c5c>] _nv001518rm+0x29c/0x2dc [nvidia]
 [<d1124b3d>] _nv006192rm+0xed/0x190 [nvidia]
 [<d1124bd3>] _nv006192rm+0x183/0x190 [nvidia]
 [<d1106080>] _nv006834rm+0x20/0x70 [nvidia]
 [<d117dbfc>] _nv005462rm+0x1c4/0x1e8 [nvidia]
 [<d117dbed>] _nv005462rm+0x1b5/0x1e8 [nvidia]
 [<d117d6ec>] _nv005249rm+0x34/0x7c [nvidia]
 [<d117d768>] _nv005216rm+0x34/0x7c [nvidia]
 [<d117d79b>] _nv005216rm+0x67/0x7c [nvidia]
 [<d0ff362c>] _nv005371rm+0x40/0x48 [nvidia]
 [<d0ff3649>] _nv005356rm+0x15/0x1c [nvidia]
 [<d101924d>] _nv001817rm+0xe1/0x1c8 [nvidia]
 [<d1019259>] _nv001817rm+0xed/0x1c8 [nvidia]
 [<d101cb09>] _nv001788rm+0x91/0xb0 [nvidia]
 [<d101cb1e>] _nv001788rm+0xa6/0xb0 [nvidia]
 [<d1019c76>] _nv001823rm+0x242/0x3d8 [nvidia]
 [<d1019c66>] _nv001823rm+0x232/0x3d8 [nvidia]
 [<d1016406>] _nv002584rm+0x12/0x18 [nvidia]
 [<d101e1fd>] rm_init_adapter+0x59/0x80 [nvidia]
 [<d126b5a6>] nv_kern_open+0x1d3/0x26e [nvidia]
 [<d126c632>] nv_kern_isr+0x0/0x63 [nvidia]
 [<b014d488>] chrdev_open+0xe9/0x100
 [<b014d39f>] chrdev_open+0x0/0x100
 [<b0145d8d>] __dentry_open+0xb5/0x189
 [<b0145f18>] do_filp_open+0x2d/0x35
 [<b01589a1>] dput+0x1b/0x111
 [<b0146000>] do_sys_open+0x40/0xb1
 [<b0146089>] sys_open+0x13/0x17
 [<b0102935>] syscall_call+0x7/0xb
Code: a4 83 c4 fc 83 c4 f8 53 8b 45 08 50 e8 ec 6e 00 00 50 6a 18 8b 95 a0 fe ff ff 52 8b 42 18 ff d0 89 c6 83 c4 20 83 c4 f8 6a 00 56 <8b> 86 04 01 00 00 ff d0 8b 85 98 fe ff ff c1 e8 04 8a 44 28 ec
When I have a look at Xorg.0.log there seems to be only some minor configuration problems with invalit paths etc. So I have attached the xorg.conf to this posting.

Any ideas?
Attached Files
File Type: log Xorg.0.log (17.9 KB, 87 views)
rscharp is offline   Reply With Quote
Old 04-17-06, 08:09 PM   #2
netllama
NVIDIA Corporation
 
Join Date: Dec 2004
Posts: 8,763
Default Re: Kernel-Oops

Can you please generate and post an nvidia-bug-report.log against 1.0-8756?

Thanks,
Lonni
netllama is offline   Reply With Quote

Sponsored Ads - Guests Only

Old 05-23-06, 01:02 PM   #3
zander
NVIDIA Corporation
 
zander's Avatar
 
Join Date: Aug 2002
Posts: 3,573
Default Re: Kernel-Oops

@rscharp: does this problem still reproduce with 1.0-8762?
zander is offline   Reply With Quote
Old 05-31-06, 08:16 AM   #4
fugro-jason
Registered User
 
Join Date: May 2006
Posts: 1
Default Re: Kernel-Oops

I have been fighting most of the day with a similar problem
and then I saw the hint to try the latest latest driver (8762)
This fixed the problem for me

(geforce 6800xt dual opt270)
fugro-jason is offline   Reply With Quote
Reply




Shop Online


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump




All times are GMT -4. The time now is 01:26 PM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2010, Jelsoft Enterprises Ltd.
nV News - Copyright ©1998-2010. All rights reserved.