We verified the exact same device worked with the previous cpu in the
same mb/bios combination same os/kernel combination, only identified
change for us was a ivy bridge vs a sandy bridge in the same
mb/bios/boardfirmware.
And in this case only one device driver/pci board was using the given
Legacy INTx is shared amongst multiple devices. Since it is a level sensitive
simulation of the interrupt line, it only takes one device (or driver) to
forget to clear the interrupt, and then it stuck and won't work for any of the
devices using it.
If you're working with one particular device
I know from some data I have seen that between the Intel Sandy Bridge
and Intel Ivy Bridge the same motherboards stopped delivering INTx
reliably (int lost under load around 1x every 30 days, driver and
firmware has no method to recover from failure) We had to transition
to using MSI on some PCI
I don't personally know of any PCI drivers that use polling instead of
interrupts, since that would really mean the hardware is broke.
Basically all you need to do is create a timer, and have it's callback set to
your driver routine that can check the device status registers to determine if
I don't personally know of any PCI drivers that use polling instead of
interrupts, since that would really mean the hardware is broke.
Basically all you need to do is create a timer, and have it's callback set to
your driver routine that can check the device status registers to determine if
Legacy INTx is shared amongst multiple devices. Since it is a level sensitive
simulation of the interrupt line, it only takes one device (or driver) to
forget to clear the interrupt, and then it stuck and won't work for any of the
devices using it.
If you're working with one particular device
We verified the exact same device worked with the previous cpu in the
same mb/bios combination same os/kernel combination, only identified
change for us was a ivy bridge vs a sandy bridge in the same
mb/bios/boardfirmware.
And in this case only one device driver/pci board was using the given
I know from some data I have seen that between the Intel Sandy Bridge
and Intel Ivy Bridge the same motherboards stopped delivering INTx
reliably (int lost under load around 1x every 30 days, driver and
firmware has no method to recover from failure) We had to transition
to using MSI on some PCI
On Mon, Mar 2, 2015 at 4:02 PM, McKay, Luke wrote:
> It doesn't appear that your device supports MSI. If it did lspci -v should
> list the MSI capability and whether or not it is enabled.
>
> i.e. Something like...
> Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
>
> Without a
On Mon, Mar 2, 2015 at 4:02 PM, McKay, Luke luke.mc...@aeroflex.com wrote:
It doesn't appear that your device supports MSI. If it did lspci -v should
list the MSI capability and whether or not it is enabled.
i.e. Something like...
Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
It doesn't appear that your device supports MSI. If it did lspci -v should
list the MSI capability and whether or not it is enabled.
i.e. Something like...
Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
Without a listing that shows the capability is present, there is nothing to
It doesn't appear that your device supports MSI. If it did lspci -v should
list the MSI capability and whether or not it is enabled.
i.e. Something like...
Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
Without a listing that shows the capability is present, there is nothing to
2015-02-12 16:48 GMT+02:00 Stephen Hemminger :
> On Wed, 11 Feb 2015 18:19:00 +
> Andrey Utkin wrote:
>
>> Is it true that _every_ PCI or PCI Express device supporting MSI is
>> indicated by some mention of MSI in "lspci -v", and if there's no such
>> mention, it surely doesn't support MSI?
On Wed, 11 Feb 2015 18:19:00 +
Andrey Utkin wrote:
> Is it true that _every_ PCI or PCI Express device supporting MSI is
> indicated by some mention of MSI in "lspci -v", and if there's no such
> mention, it surely doesn't support MSI?
>
Look at kernel source (drivers/pci/msi.c) function
On Wed, 11 Feb 2015 18:19:00 +
Andrey Utkin andrey.krieger.ut...@gmail.com wrote:
Is it true that _every_ PCI or PCI Express device supporting MSI is
indicated by some mention of MSI in lspci -v, and if there's no such
mention, it surely doesn't support MSI?
Look at kernel source
2015-02-12 16:48 GMT+02:00 Stephen Hemminger step...@networkplumber.org:
On Wed, 11 Feb 2015 18:19:00 +
Andrey Utkin andrey.krieger.ut...@gmail.com wrote:
Is it true that _every_ PCI or PCI Express device supporting MSI is
indicated by some mention of MSI in lspci -v, and if there's no
Is it true that _every_ PCI or PCI Express device supporting MSI is
indicated by some mention of MSI in "lspci -v", and if there's no such
mention, it surely doesn't support MSI?
--
Andrey Utkin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
Is it true that _every_ PCI or PCI Express device supporting MSI is
indicated by some mention of MSI in lspci -v, and if there's no such
mention, it surely doesn't support MSI?
--
Andrey Utkin
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
18 matches
Mail list logo
