nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   260.19.XX prints 'ioremap error' (http://www.nvnews.net/vbulletin/showthread.php?t=155168)

hansen 09-16-10 08:28 AM

260.19.XX prints 'ioremap error'
 
When modprobing the 260.19.XX Nvidia kernel module, I get this:

Code:

Sep 16 15:04:13 [kernel] nvidia 0000:01:00.0: setting latency timer to 64
Sep 16 15:04:13 [kernel] vgaarb: device changed decodes: PCI:0000:01:00.0,olddecodes=none,decodes=none:owns=io+mem
Sep 16 15:04:13 [kernel] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  260.19.06  Mon Sep 13 04:29:19 PDT 2010
Sep 16 15:04:14 [kernel] ioremap error for 0x9f000-0xa0000, requested 0x10, got 0x0

Normal 2D seems to work fine now with 260.19.06, besides that I can't start/play ET anymore with this driver. It then quits right in the startup with Memory Access Error. Happens in both Xorg-Server 1.8.2 and 1.9.0, the running Linux kernel is 2.6.35.4 vanilla.

Anybody else seeing this error message?

Licaon 09-16-10 02:08 PM

Re: 260.19.XX prints 'ioremap error'
 
Quote:

Originally Posted by hansen (Post 2319132)
Normal 2D seems to work fine now with 260.19.06, besides that I can't start/play ET anymore with this driver. It then quits right in the startup with Memory Access Error. Happens in both Xorg-Server 1.8.2 and 1.9.0, the running Linux kernel is 2.6.35.4 vanilla.

Anybody else seeing this error message?

can you read http://www.nvnews.net/vbulletin/showthread.php?t=46678 and generate a good report with the debug info as instructed after the issue appears ?

hansen 09-18-10 06:40 PM

Re: 260.19.XX prints 'ioremap error'
 
2 Attachment(s)
I have to correct that this error message in dmesg does not show up till X is started.

I've generated the bug-report, and it looks like this error is about some reserved memory in my system. Just compare the memory regions:
Code:

*** /proc/iomem
*** ls: -r--r--r-- 1 root root 0 2010-09-19 01:21:46.873999998 +0200 /proc/iomem
00000000-0000ffff : reserved
00010000-0009efff : System RAM
0009f000-0009ffff : reserved
000a0000-000bffff : PCI Bus 0000:00
000c0000-000dffff : PCI Bus 0000:00
...

I can submit the kernel .config if you want that, too. But I don't think there'd be much to see...

Hopefully we're able to pin down this issue.

Bye, hansen

hansen 09-22-10 11:42 PM

Re: 260.19.XX prints 'ioremap error'
 
I tried again with new kernel 2.6.35.5 and nvidia-drivers 260.19.06, still the same error occurs.
Code:

ioremap error for 0x9f000-0xa0000, requested 0x10, got 0x0

hansen 10-15-10 11:23 AM

Re: 260.19.XX prints 'ioremap error'
 
Tested the new 260.19.12 driver version, there ain't error/warning in dmesg anymore.
But while loading 3d game (Enemy Territory) it still sort of segfaults with 'memory access error'...

hansen 10-15-10 07:16 PM

Re: 260.19.XX prints 'ioremap error'
 
This is the error message when starting ET:
Code:

Received signal 11, exiting...
X Error of failed request: GLXBadContext
  Major opcode of failed request: 134
  Minor opcode of failed request: 4
  Serial number of failed request: 295
X Error of failed request: BadWindow (invalid Window parameter)
  Major opcode of failed request: 4
  Minor opcode of failed request: 0
  Serial number of failed request: 296
Memory Access Error



All times are GMT -5. The time now is 02:41 PM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.