| 1 |
Hi, |
| 2 |
|
| 3 |
I'm using nvidia-drivers-270.41.03 and got those too. |
| 4 |
|
| 5 |
"ioremap error for 0xbf7ef000-0xbf7f0000, requested 0x10, got 0x0" |
| 6 |
|
| 7 |
Regards |
| 8 |
|
| 9 |
-- |
| 10 |
Xiangru Chen |
| 11 |
|
| 12 |
|
| 13 |
On Thu, May 12, 2011 at 10:52 AM, Dale <rdalek1967@×××××.com> wrote: |
| 14 |
|
| 15 |
> meino.cramer@×××.de wrote: |
| 16 |
> |
| 17 |
>> Hi, |
| 18 |
>> |
| 19 |
>> this morning there was an update to nvidia-drivers-270.41.06. |
| 20 |
>> |
| 21 |
>> After running dmesg I found this: |
| 22 |
>> |
| 23 |
>> ioremap error for 0x9a000-0x9b000, requested 0x10, got 0x0 |
| 24 |
>> ioremap error for 0xcfe90000-0xcfe91000, requested 0x10, got 0x0 |
| 25 |
>> |
| 26 |
>> I dont know, whether this is related to that update... |
| 27 |
>> |
| 28 |
>> In the context of the output of dmesg it looks like: |
| 29 |
>> |
| 30 |
>> nvidia 0000:08:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24 |
| 31 |
>> nvidia 0000:08:00.0: setting latency timer to 64 |
| 32 |
>> vgaarb: device changed decodes: |
| 33 |
>> PCI:0000:08:00.0,olddecodes=io+mem,decodes=none:owns=io+mem |
| 34 |
>> NVRM: loading NVIDIA UNIX x86_64 Kernel Module 270.41.06 Mon Apr 18 |
| 35 |
>> 14:53:56 PDT 2011 |
| 36 |
>> microcode: CPU0: patch_level=0x10000bf |
| 37 |
>> microcode: CPU1: patch_level=0x10000bf |
| 38 |
>> microcode: CPU2: patch_level=0x10000bf |
| 39 |
>> microcode: CPU3: patch_level=0x10000bf |
| 40 |
>> microcode: CPU4: patch_level=0x10000bf |
| 41 |
>> microcode: CPU5: patch_level=0x10000bf |
| 42 |
>> microcode: Microcode Update Driver: v2.00<tigran@×××××××××××××××××.uk>, |
| 43 |
>> Peter Oruba |
| 44 |
>> EXT4-fs (sda11): re-mounted. Opts: (null) |
| 45 |
>> EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: |
| 46 |
>> (null) |
| 47 |
>> EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: |
| 48 |
>> (null) |
| 49 |
>> EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: |
| 50 |
>> (null) |
| 51 |
>> EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: |
| 52 |
>> (null) |
| 53 |
>> EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: |
| 54 |
>> (null) |
| 55 |
>> EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: |
| 56 |
>> (null) |
| 57 |
>> EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: |
| 58 |
>> (null) |
| 59 |
>> EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: |
| 60 |
>> (null) |
| 61 |
>> sky2 0000:05:00.0: eth1: enabling interface |
| 62 |
>> sky2 0000:05:00.0: eth1: Link is up at 100 Mbps, full duplex, flow |
| 63 |
>> control both |
| 64 |
>> sky2 0000:05:00.0: eth1: Link is up at 100 Mbps, full duplex, flow |
| 65 |
>> control both |
| 66 |
>> Adding 6291452k swap on /dev/sda2. Priority:-1 extents:1 |
| 67 |
>> across:6291452k |
| 68 |
>> ioremap error for 0x9a000-0x9b000, requested 0x10, got 0x0 |
| 69 |
>> ioremap error for 0xcfe90000-0xcfe91000, requested 0x10, got 0x0 |
| 70 |
>> |
| 71 |
>> |
| 72 |
>> Is this something to care of? And if "yes" -- what do I have to fix |
| 73 |
>> where ? |
| 74 |
>> |
| 75 |
>> Thank you very much for any help! :) |
| 76 |
>> |
| 77 |
>> Best regards |
| 78 |
>> mcc |
| 79 |
>> |
| 80 |
>> |
| 81 |
>> |
| 82 |
> |
| 83 |
> I get one of those in mine too. |
| 84 |
> |
| 85 |
> root@fireball / # dmesg | grep ioremap |
| 86 |
> [ 31.812410] ioremap error for 0xbfcf3000-0xbfcf4000, requested 0x10, got |
| 87 |
> 0x0 |
| 88 |
> root@fireball / # |
| 89 |
> |
| 90 |
> I'm using nvidia-drivers-260.19.44 so at least one of those applies to a |
| 91 |
> different series. You are not completely alone here. Let's hope it is not |
| 92 |
> a serious problem or even a problem at all. The rest of dmesg looks normal |
| 93 |
> to me. |
| 94 |
> |
| 95 |
> Dale |
| 96 |
> |
| 97 |
> :-) :-) |
| 98 |
> |
| 99 |
> |
Archives