View Single Post
Old 01-18-07, 06:47 AM   #7
Registered User
Join Date: Jan 2007
Posts: 11
Default Re: kernel page fault on modprobe of 9746's nvidia.ko

Originally Posted by netllama
I was using the latest Fedora Core 6 kernel, which is based off of 2.6.18.x. You can get its source & configuration here:
I just tried a vanilla kernel.

Just after I compiled the 9746 drivers it worked fine. Then I restarted and modprobe-d the nvidia module. This, contrary to the newer kernel, did work.

However, when I started Xorg, it hangs. I ssh-d into the machine and found this in dmesg:

Unable to handle kernel paging request at ffffffff6d723638 RIP: 
PGD 203027 PUD 0 
Oops: 0010 [1] PREEMPT SMP 
CPU 0 
Modules linked in: stir4200 usbhid parport_pc nvidia parport uhci_hcd ohci_hcd eth1394 bcraid
Pid: 9956, comm: Xorg Tainted: P #1
RIP: 0010:[<ffffffff6d723638>]  [<ffffffff6d723638>]
RSP: 0018:ffff81007f1bbba0  EFLAGS: 00010202
RAX: ffff810037868000 RBX: ffff810037868000 RCX: ffff810037489110
RDX: ffff810037489110 RSI: ffff810037489110 RDI: ffffffff8886c200
RBP: ffff8100384ca8c0 R08: ffff810037489110 R09: 0000000000000001
R10: 0000000000000000 R11: ffffffff80492204 R12: ffff810037489110
R13: ffff810037489110 R14: 0000000000000001 R15: 0000000000000000
FS:  00002b686123fae0(0000) GS:ffffffff806c6000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffff6d723638 CR3: 000000007ed45000 CR4: 00000000000006e0
Process Xorg (pid: 9956, threadinfo ffff81007f1ba000, task ffff81007f331180)
Stack:  ffffffff8813ae60 ffff810037489110 ffffffff8838f0a2 00000000bfef0020
 ffff810037458800 0000000000000000 00000000bfef0100 0000000000000000
 ffff81003c917400 ffff81003d05b000 ffffffff88112ece 00000000bfef0100
Call Trace:
 [<ffffffff8813ae60>] :nvidia:_nv003253rm+0x34/0x3a
 [<ffffffff8838f0a2>] :nvidia:_nv004835rm+0x74/0xd8
 [<ffffffff88112ece>] :nvidia:_nv002598rm+0x6e/0x94
 [<ffffffff88112cdb>] :nvidia:_nv002595rm+0xcd/0xee
 [<ffffffff882a1742>] :nvidia:_nv009103rm+0x8c/0xae
 [<ffffffff8811dfee>] :nvidia:_nv002597rm+0x1da/0x2d2
 [<ffffffff804922bf>] pci_conf1_read+0xbb/0xc6
 [<ffffffff8811dd2d>] :nvidia:_nv002600rm+0xef/0x1d6
 [<ffffffff8811da06>] :nvidia:_nv002603rm+0x42/0x27a
 [<ffffffff88143883>] :nvidia:rm_set_interrupts+0x11f/0x136
 [<ffffffff8844834e>] :nvidia:os_acquire_sema+0x5f/0x77
 [<ffffffff88119592>] :nvidia:_nv004373rm+0x70/0xaa
 [<ffffffff88146461>] :nvidia:_nv002552rm+0x1a9/0x63a
 [<ffffffff88143b4d>] :nvidia:rm_ioctl+0x9/0xe
 [<ffffffff884450da>] :nvidia:nv_kern_ioctl+0x35a/0x3eb
 [<ffffffff884451aa>] :nvidia:nv_kern_unlocked_ioctl+0x1c/0x23
 [<ffffffff8024152d>] do_ioctl+0x21/0x6b
 [<ffffffff8022fa49>] vfs_ioctl+0x252/0x26b
 [<ffffffff8022fa83>] __up_write+0x21/0x10d
 [<ffffffff8024bf49>] sys_ioctl+0x3c/0x5c
 [<ffffffff8025d452>] system_call+0x7e/0x83

Code:  Bad RIP value.
RIP  [<ffffffff6d723638>]
 RSP <ffff81007f1bbba0>
CR2: ffffffff6d723638
It seems like about the same problem. This time the invalid isn't ffffffff6d723538 but ffffffff6d723638.

I attached the .config of the kernel I used.
Attached Files
File Type: txt config- (36.7 KB, 103 views)
baswesterbaan is offline   Reply With Quote