Tomi Leppänen wrote:

> Didn't make any difference. Here is dmesg now:
[...]
> [    0.144739] pci 0000:01:00.0: BAR 0: trying firmware assignment [mem 
> 0xd0000000-0xdfffffff pref]
> [    0.144764] pci 0000:01:00.0: BAR 0: [mem 0xd0000000-0xdfffffff pref] 
> conflicts with PCI Bus 0000:00 [mem 0x20000000-0xffefffff]
> [    0.144784] pci 0000:01:00.0: BAR 0: can't assign mem pref (size 
> 0x10000000)

Thanks, Tomi.  If you still have time to work on this, please report
it upstream to linux-...@vger.kernel.org (no subscription needed,
since the convention is to always reply-to-all there) and either cc us
or let us know the Message-ID so we can follow the resulting
discussion.

Upstream will probably want to know a few things (so it can be good to
use a few attachments):

 - which versions you have tested and what happened with each
 - "dmesg" output from a recent (ideally a mainline kernel or 3.1-rc4
   from experimental) right after boot, just like you sent here
 - "lspci -vvx" or even "lspci -vvxxx" output (see the lspci manpage
   for a warning about the latter)

Thanks and good luck,
Jonathan



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110921232928.GB23011@elie

Reply via email to