From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1QKVxj-0003r2-TW for garchives@archives.gentoo.org; Thu, 12 May 2011 13:29:57 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9FD851C0C7; Thu, 12 May 2011 13:27:47 +0000 (UTC) Received: from mail-yi0-f53.google.com (mail-yi0-f53.google.com [209.85.218.53]) by pigeon.gentoo.org (Postfix) with ESMTP id 60A461C0C7 for ; Thu, 12 May 2011 13:27:47 +0000 (UTC) Received: by yia25 with SMTP id 25so677109yia.40 for ; Thu, 12 May 2011 06:27:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=HatalPw8sX1KyGLarSQO00PiZ7zKSM6AwVm3YLDzOro=; b=d+3FQ65/I8BUy4+ZuaIrpmlYpU4lYVAD1aXgDysHfDcbRIFikmNXDm/2ro1jbpZ8JM zOxrUSeZooev7W2n6U3+MKwALx56znNY5PJzPYoS0GhqUBgbBKQpUqL1hN/2MLo55269 jn/HcA5qboDZIxi01/jYj9d7NYBu5DxPCM2GA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=YE46PQhaQwdAKSZltGRo9oipwtLC3LTNBFV7SR+oH/53PlgQDyW1Ae49kRNMHn1gVu 8wQBLMUEwyDIegZauZwko2mfsSm+moYcFRR2Q/3U9LBEeCfzkQFrz/w3f97QHpLsfv2d 3WqfJ7dFRoMR77LwmXaogwUsNNoxWGPZNs18c= Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.100.86.1 with SMTP id j1mr125239anb.10.1305206866807; Thu, 12 May 2011 06:27:46 -0700 (PDT) Received: by 10.100.94.7 with HTTP; Thu, 12 May 2011 06:27:46 -0700 (PDT) In-Reply-To: <4DCB9FD9.501@gmail.com> References: <20110512031741.GB2974@solfire> <4DCB9FD9.501@gmail.com> Date: Thu, 12 May 2011 15:27:46 +0200 Message-ID: Subject: Re: [gentoo-user] Update nvidia-drivers From: Xiangru Chen To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=0016368e21e9a78b9f04a3142733 X-Archives-Salt: X-Archives-Hash: e90187f22a7c5b2e21b2ee8f7268a9e2 --0016368e21e9a78b9f04a3142733 Content-Type: text/plain; charset=ISO-8859-1 Hi, I'm using nvidia-drivers-270.41.03 and got those too. "ioremap error for 0xbf7ef000-0xbf7f0000, requested 0x10, got 0x0" Regards -- Xiangru Chen On Thu, May 12, 2011 at 10:52 AM, Dale wrote: > meino.cramer@gmx.de wrote: > >> Hi, >> >> this morning there was an update to nvidia-drivers-270.41.06. >> >> After running dmesg I found this: >> >> ioremap error for 0x9a000-0x9b000, requested 0x10, got 0x0 >> ioremap error for 0xcfe90000-0xcfe91000, requested 0x10, got 0x0 >> >> I dont know, whether this is related to that update... >> >> In the context of the output of dmesg it looks like: >> >> nvidia 0000:08:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24 >> nvidia 0000:08:00.0: setting latency timer to 64 >> vgaarb: device changed decodes: >> PCI:0000:08:00.0,olddecodes=io+mem,decodes=none:owns=io+mem >> NVRM: loading NVIDIA UNIX x86_64 Kernel Module 270.41.06 Mon Apr 18 >> 14:53:56 PDT 2011 >> microcode: CPU0: patch_level=0x10000bf >> microcode: CPU1: patch_level=0x10000bf >> microcode: CPU2: patch_level=0x10000bf >> microcode: CPU3: patch_level=0x10000bf >> microcode: CPU4: patch_level=0x10000bf >> microcode: CPU5: patch_level=0x10000bf >> microcode: Microcode Update Driver: v2.00, >> Peter Oruba >> EXT4-fs (sda11): re-mounted. Opts: (null) >> EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: >> (null) >> EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: >> (null) >> EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: >> (null) >> EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: >> (null) >> EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: >> (null) >> EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: >> (null) >> EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: >> (null) >> EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: >> (null) >> sky2 0000:05:00.0: eth1: enabling interface >> sky2 0000:05:00.0: eth1: Link is up at 100 Mbps, full duplex, flow >> control both >> sky2 0000:05:00.0: eth1: Link is up at 100 Mbps, full duplex, flow >> control both >> Adding 6291452k swap on /dev/sda2. Priority:-1 extents:1 >> across:6291452k >> ioremap error for 0x9a000-0x9b000, requested 0x10, got 0x0 >> ioremap error for 0xcfe90000-0xcfe91000, requested 0x10, got 0x0 >> >> >> Is this something to care of? And if "yes" -- what do I have to fix >> where ? >> >> Thank you very much for any help! :) >> >> Best regards >> mcc >> >> >> > > I get one of those in mine too. > > root@fireball / # dmesg | grep ioremap > [ 31.812410] ioremap error for 0xbfcf3000-0xbfcf4000, requested 0x10, got > 0x0 > root@fireball / # > > I'm using nvidia-drivers-260.19.44 so at least one of those applies to a > different series. You are not completely alone here. Let's hope it is not > a serious problem or even a problem at all. The rest of dmesg looks normal > to me. > > Dale > > :-) :-) > > --0016368e21e9a78b9f04a3142733 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,

I'm using nvidia-drivers-270.41.03 and got those too.
"ioremap error for 0xbf7ef000-0xbf7f0000, requested 0x10, got 0x0&quo= t;

Regards

--
Xiangru Chen


On Thu, May 12, 2011 at 10:52 AM, Dale <rdalek1967@gmail.com> wrote:
meino.cramer@gmx.de wrote:
Hi,

this morning there was an update to nvidia-drivers-270.41.06.

After running dmesg I found this:

=A0 =A0 ioremap error for 0x9a000-0x9b000, requested 0x10, got 0x0
=A0 =A0 ioremap error for 0xcfe90000-0xcfe91000, requested 0x10, got 0x0
I dont know, whether this is related to that update...

In the context of the output of dmesg it looks like:

=A0 =A0 nvidia 0000:08:00.0: PCI INT A -> =A0GSI 24 (level, low) -> = =A0IRQ 24
=A0 =A0 nvidia 0000:08:00.0: setting latency timer to 64
=A0 =A0 vgaarb: device changed decodes: PCI:0000:08:00.0,olddecodes=3Dio+m= em,decodes=3Dnone:owns=3Dio+mem
=A0 =A0 NVRM: loading NVIDIA UNIX x86_64 Kernel Module =A0270.41.06 =A0Mon= Apr 18 14:53:56 PDT 2011
=A0 =A0 microcode: CPU0: patch_level=3D0x10000bf
=A0 =A0 microcode: CPU1: patch_level=3D0x10000bf
=A0 =A0 microcode: CPU2: patch_level=3D0x10000bf
=A0 =A0 microcode: CPU3: patch_level=3D0x10000bf
=A0 =A0 microcode: CPU4: patch_level=3D0x10000bf
=A0 =A0 microcode: CPU5: patch_level=3D0x10000bf
=A0 =A0 microcode: Microcode Update Driver: v2.00<tigran@aivazian.fsnet.co.uk= >, Peter Oruba
=A0 =A0 EXT4-fs (sda11): re-mounted. Opts: (null)
=A0 =A0 EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (= null)
=A0 =A0 EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (= null)
=A0 =A0 EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: (= null)
=A0 =A0 EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: (= null)
=A0 =A0 EXT4-fs (sda9): mounted filesystem with ordered data mode. Opts: (= null)
=A0 =A0 EXT4-fs (sda10): mounted filesystem with ordered data mode. Opts: = (null)
=A0 =A0 EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (= null)
=A0 =A0 EXT4-fs (sda12): mounted filesystem with ordered data mode. Opts: = (null)
=A0 =A0 sky2 0000:05:00.0: eth1: enabling interface
=A0 =A0 sky2 0000:05:00.0: eth1: Link is up at 100 Mbps, full duplex, flow= control both
=A0 =A0 sky2 0000:05:00.0: eth1: Link is up at 100 Mbps, full duplex, flow= control both
=A0 =A0 Adding 6291452k swap on /dev/sda2. =A0Priority:-1 extents:1 across= :6291452k
=A0 =A0 ioremap error for 0x9a000-0x9b000, requested 0x10, got 0x0
=A0 =A0 ioremap error for 0xcfe90000-0xcfe91000, requested 0x10, got 0x0

Is this something to care of? And if "yes" -- what do I have to f= ix
where ?

Thank you very much for any help! :)

Best regards
mcc

=A0

I get one of those in mine too.

root@fireball / # dmesg | grep ioremap
[ =A0 31.812410] ioremap error for 0xbfcf3000-0xbfcf4000, requested 0x10, g= ot 0x0
root@fireball / #

I'm using nvidia-drivers-260.19.44 so at least one of those applies to = a different series. =A0You are not completely alone here. =A0Let's hope= it is not a serious problem or even a problem at all. The rest of dmesg lo= oks normal to me.

Dale

:-) =A0:-)


--0016368e21e9a78b9f04a3142733--