After reviewing previous communication again, I saw Andrew's message:
"I can reproduce it. But none of the kernel debug tools helped me get
any further. I think the next step is to explain the problem to
Russell King and see if he has any ideas."
Andrew, do you think you could report this issue t
Andrew,
As discussed previously (going back to 2017), there is an issue on
Kirkwood devices with 1 GB RAM. People see:
external abort on linefetch (0x814)
You were able to reproduce this issue in the end and suggested
to set CONFIG_VMSPLIT_3G
Two users confirmed that while this makes the ori
I'm adding Andrew Lunn in hope this can be tracked down. This relates
to Kirkwood machines with 1 GB of RAM. CONFIG_VMSPLIT_3G seems to
lead to network problems.
* Timo Jyrinki [2019-04-26 14:29]:
> ti 23. huhtik. 2019 klo 1.37 Matti Viljanen (matti.vilja...@kapsi.fi)
> kirjoitti:
> > I have a
ti 23. huhtik. 2019 klo 1.37 Matti Viljanen (matti.vilja...@kapsi.fi) kirjoitti:
> I have a Fujitsu Q703 aka. QNap TS-221, with 1GB of RAM and 6282 variant
> chip inside, and I have hit this behavior.
...
> it get an IP address but the LEDs blink normally - I think this is the
> same situation Timo
2018-07-22 09:54 GMT+03:00 Timo Jyrinki :
> "Network doesn't work". I'm not sure what's going on, but the
> installer isn't able to enable the network, even though the network
> device exists and can be configured. Cable is connected similarly to
> normal operation and lights are blinking (and obv
2018-07-04 21:48 GMT+03:00 Andrew Lunn :
>> 1) The config option change works, but some networking issues were
>> mentioned. Someone needs to figure out whether that's related.
>
> I would be interested in knowing what the network issues were? They
> might be a pointer to what is going wrong with
* Andrew Lunn [2018-07-04 20:48]:
> > 1) The config option change works, but some networking issues were
> > mentioned. Someone needs to figure out whether that's related.
>
> I would be interested in knowing what the network issues were? They
> might be a pointer to what is going wrong with hig
On Tue, Jul 03, 2018 at 11:27:32PM +0200, Martin Michlmayr wrote:
> * Damien [2018-07-03 22:33]:
> > Is there any plan to have this fixed kernel in Debian mainstream, or in a
> > dpkg ?
>
> I think we haven't quite established what the best course of action
> is:
>
> 1) The config option change
* Damien [2018-07-03 22:33]:
> Is there any plan to have this fixed kernel in Debian mainstream, or in a
> dpkg ?
I think we haven't quite established what the best course of action
is:
1) The config option change works, but some networking issues were
mentioned. Someone needs to figure out whe
Hi,
Is there any plan to have this fixed kernel in Debian mainstream, or in
a dpkg ?
I'm not skilled in such low level problematics, and I'm failing to have
serial console working.
--
Regards,
Damien Martins
On Sat, 2018-06-09 at 16:23 +0200, Andrew Lunn wrote:
> > Debian uses a Marvell specific kernel, so we don't need to worry
> about
> > the impact on other platforms.
>
> That i was not sure about. Are there any plans to merge all ARM v5
> kernels together?
Not AFAIK, marvell is the only armv5 fla
> With only 1G of physical RAM anything using the full 3G would be
> already so far into swapping hell that it seems like it would be pretty
> unusable. So maybe we can assert that it is unlikely that there is any
> real world usage that would be impacted by this change.
Hi Ian
That was what i wa
(adding debian-kernel, context: external aborts on qnap/marvell systems
with 1G of RAM, avoided with VMSPLIT_3G_OPT=y).
On Sat, 2018-06-02 at 21:31 +0200, Andrew Lunn wrote:
> On Sat, Jun 02, 2018 at 09:48:47PM +0300, Timo Jyrinki wrote:
> > 2018-06-02 18:55 GMT+03:00 Ian Campbell :
> > > You need
2018-06-05 20:25 GMT+03:00 Timo Jyrinki :
> more proper kernel zImage build with CONFIG_VMSPLIT_3G_OPT=y would be useful
...
> wget https://people.debian.org/~timo/qnap/zImage
It seems my native kernel build on the QNAP device finished last
night, so here's the zImage for it:
https://people.debia
On 02-06-18 21:31, Andrew Lunn wrote:
> On Sat, Jun 02, 2018 at 09:48:47PM +0300, Timo Jyrinki wrote:
>> 2018-06-02 18:55 GMT+03:00 Ian Campbell :
>>> You need to append a dtb and then encode in u-boot's uImage format.
>>> e.g.
>>>
>>>cat arch/arm/boot/zImage arch/arm/boot/dts/kirkwood-ts419-62
2018-06-02 22:31 GMT+03:00 Andrew Lunn :
>> kernel-kirkwood-ts219-6282-split3gopt from
...
>> I'm getting full 1GB RAM without the errors!
>
> Now, the question is, is this an O.K. workaround? Or do we need to
> figure out why highmem breaks on Kirkwood?
Fine by me, but I'm not really in position
On Sat, Jun 02, 2018 at 09:48:47PM +0300, Timo Jyrinki wrote:
> 2018-06-02 18:55 GMT+03:00 Ian Campbell :
> > You need to append a dtb and then encode in u-boot's uImage format.
> > e.g.
> >
> >cat arch/arm/boot/zImage arch/arm/boot/dts/kirkwood-ts419-6281.dtb > x
> >sudo mkimage -A arm -T
2018-06-02 18:55 GMT+03:00 Ian Campbell :
> You need to append a dtb and then encode in u-boot's uImage format.
> e.g.
>
>cat arch/arm/boot/zImage arch/arm/boot/dts/kirkwood-ts419-6281.dtb > x
>sudo mkimage -A arm -T kernel -O linux -C none -a 0x8000 -e 0x8000 -d x
> uImage
Thank you! Now
On Sat, 2018-06-02 at 16:55 +0100, Ian Campbell wrote:
> On Sat, 2018-06-02 at 15:36 +0300, Timo Jyrinki wrote:
> > 2018-05-28 19:00 GMT+03:00 Andrew Lunn :
> > > Could you try changing "Memory split" to "3G/1G user/kernel split
> > (for
> > > full 1G low memory)". You should then see that the lowm
On Sat, 2018-06-02 at 15:36 +0300, Timo Jyrinki wrote:
> 2018-05-28 19:00 GMT+03:00 Andrew Lunn :
> > Could you try changing "Memory split" to "3G/1G user/kernel split
> (for
> > full 1G low memory)". You should then see that the lowmem in the
> > Virtual kernel memory layout table goes from starti
2018-05-28 19:00 GMT+03:00 Andrew Lunn :
> Could you try changing "Memory split" to "3G/1G user/kernel split (for
> full 1G low memory)". You should then see that the lowmem in the
> Virtual kernel memory layout table goes from starting at 0xc000 to
> starting at 0xB000. I hope it will then
On Tue, 2018-05-29 at 13:51 +0200, Andrew Lunn wrote:
> On Tue, May 29, 2018 at 06:50:16AM +0100, Jonathan Medhurst wrote:
> > On Mon, 2018-05-28 at 18:00 +0200, Andrew Lunn wrote:
> > > Hi Rob
> > >
> > > Since my QNAP only has 512M, there is not too much
> > > experimentation i
> > > can do.
> >
On Tue, May 29, 2018 at 06:50:16AM +0100, Jonathan Medhurst wrote:
> On Mon, 2018-05-28 at 18:00 +0200, Andrew Lunn wrote:
> > Hi Rob
> >
> > Since my QNAP only has 512M, there is not too much experimentation i
> > can do.
> >
> > Could you try changing "Memory split" to "3G/1G user/kernel split (
On Mon, 2018-05-28 at 18:00 +0200, Andrew Lunn wrote:
> Hi Rob
>
> Since my QNAP only has 512M, there is not too much experimentation i
> can do.
>
> Could you try changing "Memory split" to "3G/1G user/kernel split (for
> full 1G low memory)".
Don't you mean change it to 2G/2G? That's what would
1On Sun, May 27, 2018 at 01:39:35PM +0200, RobJE Debian ARM wrote:
> On 24-05-18 14:30, Andrew Lunn wrote:
> > On Thu, May 24, 2018 at 12:40:06PM +0300, Timo Jyrinki wrote:
> >> 2018-04-25 14:16 GMT+03:00 Martin Michlmayr :
> >>> Timo Jyrinki is happy to run some tests. He's affected and has a
> >
On 24-05-18 14:30, Andrew Lunn wrote:
> On Thu, May 24, 2018 at 12:40:06PM +0300, Timo Jyrinki wrote:
>> 2018-04-25 14:16 GMT+03:00 Martin Michlmayr :
>>> Timo Jyrinki is happy to run some tests. He's affected and has a
>>> serial console. The bug is still there in the 4.9 kernel we're
>>> shippi
On Thu, May 24, 2018 at 12:40:06PM +0300, Timo Jyrinki wrote:
> 2018-04-25 14:16 GMT+03:00 Martin Michlmayr :
> > Timo Jyrinki is happy to run some tests. He's affected and has a
> > serial console. The bug is still there in the 4.9 kernel we're
> > shipping with Debian kernel.
> >
> > Andrew, wh
2018-04-25 14:16 GMT+03:00 Martin Michlmayr :
> Timo Jyrinki is happy to run some tests. He's affected and has a
> serial console. The bug is still there in the 4.9 kernel we're
> shipping with Debian kernel.
>
> Andrew, what information or access do you need so this can be tracked
> down?
Yeste
Quite a few Debian users on QNAP are affected by this "external abort
on linefetch" issue. Ian Campell raised this with Andrew Lunn
(upstream kernel) last year but Andrew couldn't reproduce it:
https://lists.debian.org/debian-arm/2017/07/msg00054.html
RobJE provided additional information but for
On 29-07-17 17:50, Andrew Lunn wrote:
> So i'm thinking this has to be related to bits of hardware i'm not
> using. I don't have anything on the PCIe bus, i don't have any USB
> devices plugged in, i don't use the mtd devices, etc.
>
> Could somebody who does have the issue describe their system?
On Sun, Jul 23, 2017 at 10:25:41AM +0100, Ian Campbell wrote:
> Hello kirkwood folks,
>
> We have been seeing reports on the Debian arm list about
> instability/errors running Debian Stretch (4.9 based) on
> various Kirkwood 6282 based QNAP systems. Errors are things like [0,
> actually one of the
Hi Andrew and list,
On 28-07-17 18:33, Andrew Lunn wrote:
> So far, i've not been able to reproduce this. I have 6282 based QNAP
> NAS box, with a single disk. Since this is a kernel hacking box, i
> tftpboot and don't use an initrd. I've been using the
> mvebu_v5_defconfig kernel configuration an
> Hello kirkwood folks,
>
> We have been seeing reports on the Debian arm list about
> instability/errors running Debian Stretch (4.9 based) on
> various Kirkwood 6282 based QNAP systems. Errors are things like [0,
> actually one of the earlier pre-4.9 reports, same symptoms as with 4.9
> though]:
On Wed, 2017-07-26 at 19:55 +0200, Andrew Lunn wrote:
> On Wed, Jul 26, 2017 at 05:18:05PM +0100, Ian Campbell wrote:
> > On Wed, 2017-07-26 at 17:22 +0200, Andrew Lunn wrote:
> > > I have a 6282 system i can try to reproduce this on. It will
> probably
> > > be a few days before i get around to it
On Wed, Jul 26, 2017 at 05:18:05PM +0100, Ian Campbell wrote:
> On Wed, 2017-07-26 at 17:22 +0200, Andrew Lunn wrote:
> > I have a 6282 system i can try to reproduce this on. It will probably
> > be a few days before i get around to it.
>
> Thanks!
>
> For some reason my original mail never made
On Wed, 2017-07-26 at 17:22 +0200, Andrew Lunn wrote:
> I have a 6282 system i can try to reproduce this on. It will probably
> be a few days before i get around to it.
Thanks!
For some reason my original mail never made it to debian-arm or linux-
arm-kernel, suspiciously the mail which I attache
On Sun, Jul 23, 2017 at 10:25:41AM +0100, Ian Campbell wrote:
> Hello kirkwood folks,
>
> We have been seeing reports on the Debian arm list about
> instability/errors running Debian Stretch (4.9 based) on
> various Kirkwood 6282 based QNAP systems. Errors are things like [0,
> actually one of the
37 matches
Mail list logo
