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

Newegg Daily Deals

Reply
 
Thread Tools
Old 09-16-10, 09:28 AM   #1
hansen
Registered User
 
Join Date: Feb 2009
Posts: 16
Default 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?
hansen is offline   Reply With Quote
Old 09-16-10, 03:08 PM   #2
Licaon
Registered User
 
Licaon's Avatar
 
Join Date: Nov 2004
Location: Between the keyboard and the chair.
Posts: 490
Default Re: 260.19.XX prints 'ioremap error'

Quote:
Originally Posted by hansen View Post
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 ?
Licaon is offline   Reply With Quote
Old 09-18-10, 07:40 PM   #3
hansen
Registered User
 
Join Date: Feb 2009
Posts: 16
Default Re: 260.19.XX prints 'ioremap error'

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
Attached Files
File Type: gz nvidia-bug-report.log.gz (38.8 KB, 62 views)
File Type: gz kernelconfig.gz (12.7 KB, 69 views)
hansen is offline   Reply With Quote
Old 09-23-10, 12:42 AM   #4
hansen
Registered User
 
Join Date: Feb 2009
Posts: 16
Default 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 is offline   Reply With Quote
Old 10-15-10, 12:23 PM   #5
hansen
Registered User
 
Join Date: Feb 2009
Posts: 16
Default 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 is offline   Reply With Quote
Old 10-15-10, 08:16 PM   #6
hansen
Registered User
 
Join Date: Feb 2009
Posts: 16
Default 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
hansen is offline   Reply With Quote
Reply


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 -5. The time now is 09:36 PM.


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