Bug#920764: login: Please add /dev/ttyLP0 /dev/ttyLP1 to securetty

2019-01-28 Thread Andrew Lunn
Source: shadow Version: 4.5 Severity: normal Dear Maintainer, I've install Debian on an Freescale Vybrid SoC, vf610. The Linux driver for its UARTs name the ttyLP0, ttyLP1. Please could you add these names to /etc/securetty so that root can login via these UARTs. -- System Information: Debian

Bug#892057: Fwd: Re: TS-x09 fails to boot when obtaining MAC

2018-03-26 Thread Andrew Lunn
On Tue, Mar 27, 2018 at 12:50:04AM +0200, Martin Michlmayr wrote: > The fix is in Linus' tree since v.16-rc5: > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=13a55372b64e00e564a08d785ca87bd9d454ba30 > > I don't see it in 4.9 stable or the stable queue. Will Greg

Bug#887873: linux-image-4.9.0-5-marvell: frequent "usercopy: kernel memory overwrite attempt detected" on QNAP NAS (ARM)

2018-03-09 Thread Andrew Lunn
> > Hi Menno > > > > Could you also try linux-image-4.14.0-3-marvell from sid? > > Can do. Should I just use the kernel packages from sid or update the whole > system to sid? Hi Menno The kernel packages should be sufficient. Andrew

Bug#887873: linux-image-4.9.0-5-marvell: frequent "usercopy: kernel memory overwrite attempt detected" on QNAP NAS (ARM)

2018-03-07 Thread Andrew Lunn
On Thu, Mar 08, 2018 at 09:49:29AM +1300, Menno Finlay-Smits wrote: > On Thu, 8 Mar 2018, at 02:36, Andrew Lunn wrote: > > > What else can I try? > > > > Do you have transparent huge pages enabled? > > > > ~$ cat /sys/kernel/mm/transparent_hugepage

Bug#887873: linux-image-4.9.0-5-marvell: frequent "usercopy: kernel memory overwrite attempt detected" on QNAP NAS (ARM)

2018-03-07 Thread Andrew Lunn
> What else can I try? Do you have transparent huge pages enabled? ~$ cat /sys/kernel/mm/transparent_hugepage/enabled [always] madvise never If so, could you disable it with: echo never > /sys/kernel/mm/transparent_hugepage/enabled and run your rsync command. Thanks Andrew

Bug#887873: linux-image-4.9.0-5-marvell: frequent "usercopy: kernel memory overwrite attempt detected" on QNAP NAS (ARM)

2018-03-07 Thread Andrew Lunn
> What else can I try? There doesn't appear to be a newer kernel in > proposed right now. Are you happy to apply patches, build a kernel, and test it? Thanks Andrew

Bug#887873: linux-image-4.9.0-5-marvell: frequent "usercopy: kernel memory overwrite attempt detected" on QNAP NAS (ARM)

2018-03-05 Thread Andrew Lunn
On Sun, Mar 04, 2018 at 09:41:15PM +0100, Andrew Lunn wrote: > On Sun, Mar 04, 2018 at 06:41:57PM +0100, Martin Michlmayr wrote: > > A Debian user reported the following issue on QNAP TS-119P II with > > 4.9.65: > > > > * Menno Finlay-Smits <in...@menno.io> [

Bug#887873: linux-image-4.9.0-5-marvell: frequent "usercopy: kernel memory overwrite attempt detected" on QNAP NAS (ARM)

2018-03-04 Thread Andrew Lunn
On Sun, Mar 04, 2018 at 06:41:57PM +0100, Martin Michlmayr wrote: > A Debian user reported the following issue on QNAP TS-119P II with > 4.9.65: > > * Menno Finlay-Smits [2018-01-21 23:08]: > > Rsyncing files between 2 HDDs on a QNAP 119p with a fresh, minimal install > > of > >

Bug#887873: linux-image-4.9.0-5-marvell: frequent "usercopy: kernel memory overwrite attempt detected" on QNAP NAS (ARM)

2018-03-04 Thread Andrew Lunn
On Sun, Mar 04, 2018 at 06:41:57PM +0100, Martin Michlmayr wrote: > A Debian user reported the following issue on QNAP TS-119P II with > 4.9.65: > > * Menno Finlay-Smits [2018-01-21 23:08]: > > Rsyncing files between 2 HDDs on a QNAP 119p with a fresh, minimal install > > of > >

Bug#860387: ostinato: .deb for python binding

2017-04-15 Thread Andrew Lunn
Package: ostinato Version: 0.8-1 Severity: wishlist Dear Maintainer, The Ostinator sources contain a python binding library. This allows the drone to be used directly from python scripts, rather than using the GUI. This is particularly useful for Continuous Integration setups. Currently, this

Bug#811351: additional request...

2016-01-21 Thread Andrew Lunn
> I can add more verbose comments to mainline kernel .dts on how to > enable serial port, and how to select between rs232/485. Andrew, do > you want me to resend the current patches, or can it be done with an > incremental patch? Either, but incremental is probably easiest. Andrew

Bug#811351: additional request...

2016-01-19 Thread Andrew Lunn
> As per the above discussion, would it be possible to have the patch > comment the code, rather than delete it, so that people with a need > for the serial port could activate it? Maybe also add a note in the > /usr/share/doc/ as to how to perform the activation. FYI The patches go into the

Bug#714959: linux-image-3.2.0-4-kirkwood mdraid array fails to assemble b/c drives are not yet ready (sata_mv)

2014-03-29 Thread Andrew Lunn
Having looked back at the initial mail, it looks like dmesg_error.txt and dmesg_after_patch.txt show approximately the same thing, or at least I'm not spotting the error. I think error is too strong a word. It is more a problem of just going too slow. Take a look at the time stamps. In the

Bug#714959: linux-image-3.2.0-4-kirkwood mdraid array fails to assemble b/c drives are not yet ready (sata_mv)

2014-03-26 Thread Andrew Lunn
On Wed, Mar 26, 2014 at 03:09:18PM +0100, Sebastian Hesselbarth wrote: On 03/26/2014 02:55 PM, Andrew Lunn wrote: * Martin Waschbuesch mar...@waschbuesch.de [2013-07-04 19:12]: Package: src:linux Version: 3.2.46-1 Severity: normal Tags: upstream patch Dear Maintainer, On my QNAP TS-412

Bug#714959: linux-image-3.2.0-4-kirkwood mdraid array fails to assemble b/c drives are not yet ready (sata_mv)

2014-03-26 Thread Andrew Lunn
* Martin Waschbuesch mar...@waschbuesch.de [2013-07-04 19:12]: Package: src:linux Version: 3.2.46-1 Severity: normal Tags: upstream patch Dear Maintainer, On my QNAP TS-412, after a clean install of Wheezy, the kernel fails to bring up all sata ports (using Marvell 88SX7042

Bug#714959: linux-image-3.2.0-4-kirkwood mdraid array fails to assemble b/c drives are not yet ready (sata_mv)

2014-03-26 Thread Andrew Lunn
+#defineQMV_SATA_INIT_DELAY_PHASE 5000 //milliseconds + + /* * module options */ @@ -4329,7 +4333,11 @@ struct ata_port *ap = host-ports[port]; void __iomem *port_mmio =

Bug#731345: flash-kernel: add support for DT based kernels on Sheeva Plug

2014-01-08 Thread Andrew Lunn
Hi Marc I've not tested it, but ethernet should work. Adding DT support to the ethernet driver took time, so during the transition, we instantiated ethernet using old style platform_driver. If it really does not work, it is a bug, which i will fix and get put into stable. Feel free to

Bug#731345: flash-kernel: add support for DT based kernels on Sheeva Plug

2014-01-08 Thread Andrew Lunn
Not quite, as 3.11 comes with DT for the sheeva plug, but that DT lacks ethernet support. Hi Marc I've not tested it, but ethernet should work. Adding DT support to the ethernet driver took time, so during the transition, we instantiated ethernet using old style platform_driver. If it really

Bug#549050: cupsd segfaults on SIGHUP

2009-10-28 Thread Andrew Lunn
Me two: londo:/var/log# zless kern.log* | grep cups Oct 25 06:56:46 londo kernel: cupsd[3772]: segfault at 2b24d0e8 ip b7d803e4 sp bf965320 error 4 in libcups.so.2[b7d71000+41000] Oct 28 06:40:20 londo kernel: cupsd[6838]: segfault at 2be440d8 ip b7e753e4 sp bfb13b50 error 4 in

Bug#445670: aiccu: Asked twice about configuration when updating package

2007-10-07 Thread Andrew Lunn
Package: aiccu Version: 20070115-6 Severity: wishlist When updating the aiccu package it always asks me twice what my tunnel broken is. It asks first during pre-configure and again during package configuration. -- System Information: Debian Release: lenny/sid APT prefers unstable APT

Bug#445671: aiccu: When promping for configuration, select the current tunnal broker as default

2007-10-07 Thread Andrew Lunn
Package: aiccu Version: 20070115-6 Severity: wishlist It would be nice if during configuration of aiccu it set the default tunnel broken to the currently configured setting. As you can see from the debconf information it knows i use SixXs, so it would be better to have that as the default

Bug#391714: tar: Man page: -l no longer means --one-file-system

2006-10-08 Thread Andrew Lunn
Package: tar Version: 1.15.91-2 Severity: normal The Debian man page for tar says: -l, --one-file-system stay in local file system when creating an archive Since version 1.15.91 this is no longer true. The use of -l has been dropped. See