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