Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

2019-07-29 Thread Stefan Langanke
Hello, the links in Marco's email are leading to the right changes in upstream kernel that lead to the problem. I have the same issue debugged this on my TS-109. The so called fix at [1] does not do the trick. There is an uncaught NULL pointer exception, that seems to be thrown, if the

Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

2019-07-10 Thread Marco Genise
I just tested experimental, same issue there with linux-image-5.0.0-trunk-marvell (5.0.2-1~exp1). After digging around I assume this problem is related to changes in drivers/net/ethernet/marvell/mvmdio.c in Version 4.12, which extended the number of possible clock sources, see [1]. Just a

Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

2019-07-10 Thread Marco Genise
Also affects linux-image-4.19.0-5-marvell 4.19.37-5 (buster) on QNAP TS-109.

Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

2019-05-10 Thread Martin Michlmayr
Unfortuantely I'm not aware of any changes. I just saw a message from Marcus Better from January that the problem is in 4.19, so I assume it's still there. Can one of you please try the latest kernel in stretch-backports (or even 5.0.2 in experimental). If the problem is there, please show the

Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

2019-05-09 Thread Martin Michlmayr
* Martin Michlmayr [2019-01-22 11:45]: > Ralf, have you been able to find out more about this issue? Ralf, is this issue still there? > If not, it might be worth copying Andrew Lunn who is > the kernel upstream expert for Orion. > > * Ralf Hemberger [2018-10-02 21:48]: > > Hello, > > > > >

Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

2019-01-22 Thread Martin Michlmayr
Ralf, have you been able to find out more about this issue? If not, it might be worth copying Andrew Lunn who is the kernel upstream expert for Orion. * Ralf Hemberger [2018-10-02 21:48]: > Hello, > > > I can try this weekend whether removing systemd makes a difference. > > > Installing

Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

2019-01-13 Thread Marcus Better
Also affects linux-image-4.19.0-1-marvell 4.19.12-1 (buster) on QNAP TS-209.

Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

2018-10-02 Thread Ralf Hemberger
Hello, > I can try this weekend whether removing systemd makes a difference. > Installing sysvinit-core made no difference. I tried the older backports-kernels and the problem exists already with linux-image-4.12.0-0.bpo.2-marvell_4.12.13-1~bpo9+1_armel.deb.

Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

2018-09-26 Thread Ralf Hemberger
Another difference is that the buffalo linkstation is based on device tree. I can try this weekend whether removing systemd makes a difference. Am Mi., 26. Sep. 2018 um 01:09 Uhr schrieb Roger Shimizu < rogershim...@gmail.com>: > On Mon, Sep 24, 2018 at 8:36 PM, Martin Michlmayr wrote: > >

Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

2018-09-25 Thread Roger Shimizu
On Mon, Sep 24, 2018 at 8:36 PM, Martin Michlmayr wrote: > [copied Roger and Ian] > > * Ralf Hemberger [2018-09-13 00:56]: >> I ugraded the kernel to the stretch-backports version with apt. >> After reboot the kernel couldn't find the PHY [41.082447], >> subsequently followed a kernel oops /

Bug#908712: linux-image-4.17.0-0.bpo.3-marvell: stretch-backports kernel 4.17 breaks QNAP TS-209

2018-09-24 Thread Martin Michlmayr
[copied Roger and Ian] * Ralf Hemberger [2018-09-13 00:56]: > I ugraded the kernel to the stretch-backports version with apt. > After reboot the kernel couldn't find the PHY [41.082447], > subsequently followed a kernel oops / crash, systemd-udevd crashes. > [ 23.578592] serial8250.1: ttyS1