Re: Error assigning BAR 0 to hotplugged device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Jul 17, 2014 at 9:33 AM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
> On Thu, Jul 17, 2014 at 8:08 AM, Chuck Tuffli <ctuffli@xxxxxxxxx> wrote:
>> On Wed, Jul 16, 2014 at 7:15 PM, Yinghai Lu <yinghai@xxxxxxxxxx> wrote:
>>>> If the BIOS doesn't allocate enough memory mapped IO resources for
>>>> devices, it sounds like the kernel can't really fix this problem,
>>>> right?
>>>
>>> Yes. You need to fix BIOS at first.
>>>
>>> So it will be final products or just development prototype?
>>
>> This is a prototype development system I'm using to develop software.
>> Since a BIOS fix isn't likely to happen, are there existing features I
>> can use to work around this problem?
>
> You need have a scripts with kexec to reload kernel.
> 1. make sure that card is the slot 9b:15.0
> 2. boot system with kernel.
> 3. unload or unbind the drivers for devices under 80:03.0
> 4. use setpci to clear bridge io, mmio, mmio pref bars with 80:03.0
> 5. kexec load kernel and start kernel again.

Perfect. Thanks so much for your explanations and advice!

--chuck
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [DMA Engine]     [Linux Coverity]     [Linux USB]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Greybus]

  Powered by Linux