On Mon, Mar 09, 2009 at 11:50:27PM +0100, Julien BLACHE wrote: >reassign 518750 libpci3 1:3.1.2-1 >thanks > >Filippo Giunchedi <fili...@debian.org> wrote: > >Hi Anibal, > >See the bug log for the details, summary below. > >>mmap(NULL, 1048576, PROT_READ|PROT_WRITE, MAP_SHARED, 4, 0xd0100004) = -1 >>EINVAL (Invalid argument) > >This is a mmap call issued by pommed, with the address taken verbatim >from libpci. > >As you can see in the lspci output, the address is actually >0xd010000*0*; the 4 we see here is probably the flag indicating a 64bit >BAR that is not cleared by libpci. > >libpci3 from Lenny does pass 0xd0100000 as expected. It looks like a >subtle bug in libpci; can you investigate this issue and confirm? > >Thanks, > >JB. > >-- > Julien BLACHE - Debian & GNU/Linux Developer - <jbla...@debian.org> > > Public key available on <http://www.jblache.org> - KeyID: F5D6 5169 > GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169
Hello Martin, This bug report is available at http://bugs.debian.org/518750 This bug is not present in version 3.0.3 (Lenny), it's in 3.1.2 as explained above by Julien. Anibal -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
