Confirmed PCIe bug in Kernel 4.0 (Kirkwood)

This forum is for Marvell Kirkwood devices such as the GoFlex Home/Net, PogoPlug v1/v2, SheevaPlug, and ZyXEL devices.

Confirmed PCIe bug in Kernel 4.0 (Kirkwood)

Postby sakaki » Thu Apr 30, 2015 8:48 am

Hello,

if you have a PCIe device on your Kirkwood system, that has stopped working after an upgrade to kernel 4.0, you may like to know that there is a known bug in the current 4.0 kernel (which therefore affects e.g. linux-kirkwood-dt 4.0-1).

The bug was introduced by commit a0b5cd4, and has been addressed by this patch, which is working its way through the usual pipeline towards release.

For those interested, the patch comment reads:$this->bbcode_second_pass_code('', 'Commit a0b5cd4ac2d6 ("bus: mvebu-mbus: use automatic I/O
synchronization barriers") enabled the usage of automatic I/O
synchronization barriers by enabling bit WIN_CTRL_SYNCBARRIER in the
control registers of MBus windows, but on non io-coherent platforms
(orion5x, kirkwood and dove) the WIN_CTRL_SYNCBARRIER bit in
the window control register is either reserved (all windows except 6
and 7) or enables read-only protection (windows 6 and 7).')
Hope that saves somebody else the fun of doing a kernel bisect ^-^

Best,

sakaki
sakaki
 
Posts: 11
Joined: Sat Mar 28, 2015 1:53 pm

Re: Confirmed PCIe bug in Kernel 4.0 (Kirkwood)

Postby moonman » Thu Apr 30, 2015 3:35 pm

sakaki, thank you for figuring this one out. Will commit the patch shortly.
Pogoplug V4 | GoFlex Home | Raspberry Pi 4 4GB | CuBox-i4 Pro | ClearFog | BeagleBone Black | Odroid U2 | Odroid C1 | Odroid XU4
-----------------------------------------------------------------------------------------------------------------------
[armv5] Updated U-Boot | [armv5] NAND Rescue System
moonman
Developer
 
Posts: 3388
Joined: Sat Jan 15, 2011 3:36 am


Return to Marvell Kirkwood

Who is online

Users browsing this forum: No registered users and 29 guests