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
> > stretch NAS (arm
Your message dated Sun, 04 Mar 2018 21:26:24 +0100
with message-id <1675396.BpHO95W9OA@kjartansson>
and subject line Re: Bug#723042: QNAP still not booting
has caused the Debian Bug report #723042,
regarding [armel/kirkwood] Linux 3.10 fails to boot on QNAP
to be marked as done.
This means that yo
What about 4.15 from unstable? Is that working for you?
Which Kirkwood platform are you on?
--
Martin Michlmayr
http://www.cyrius.com/
On Sunday 4 March 2018 18:28:39 CET Martin Michlmayr wrote:
> * Christoph Egger [2014-08-22 21:32]:
> > FWIW it still doesn't boot. I'll buy a jtag adapter post-debconf so I
> > can get anything out of it that might b usefull
>
> This bug report is quite old.
>
> There are users running Debian j
* Christoph Egger [2018-03-04 20:19]:
> I have since then retired the QNAP
The bug is quite old and I'm not aware of any boot issues on the QNAP
TS-41x so I think it's best to close this report. Ok?
--
Martin Michlmayr
http://www.cyrius.com/
Your message dated Sun, 4 Mar 2018 20:05:10 +0100
with message-id <20180304190510.qorgn6cgj7kfl...@jirafa.cyrius.com>
and subject line Re: Bug#708849: linux-image-3.2.0-4-kirkwood: Pogoplug Series
4 support
has caused the Debian Bug report #708849,
regarding linux-image-3.2.0-4-kirkwood: Pogoplug
* Christoph Egger [2013-07-28 15:44]:
> I've upgraded the kernel on my QNAP to 3.9. Unfortunately, network
> is now stuck around 1 MBit/s and I'm seeing lots of error messages in
> syslog like the ones below:
>
> [ 203.642744] mv643xx_eth_port mv643xx_eth_port.0 eth0: received packet
> spanni
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
> > stretch NAS (arm
* Kamal Wickramanayake [2017-10-06 14:13]:
> I haven't submitted the changes to upstream. Appreciate if you release
> the package with a corrected kirkwood-t5325.dtb.
Can you please submit or get "bodhi" (or whoever wrote the patch) to
submit the patches upstream. This is how it would flow into
* Ben Hutchings [2013-07-28 21:31]:
> > FWIW:
> > http://lists.infradead.org/pipermail/linux-arm-kernel/2012-September/122873.html
>
> Those fixes were applied in 3.10 and then backported in 3.9.9 and
> 3.2.48.
Sounds like this bug can be closed?
--
Martin Michlmayr
http://www.cyrius.com/
Fix:
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=13a55372b64e00e564a08d785ca87bd9d454ba30
- Forwarded message from Andrew Lunn -
Date: Sun, 4 Mar 2018 19:17:41 +0100
From: Andrew Lunn
To: Martin Michlmayr
Cc: Gregory Clement ,
andriy.shevche...@linux.intel
Package: linux
Version: 4.9.65-3
Severity: important
A number of Debian users reported that Debian stretch doesn't boot on
their QNAP TS-x09 whereas jessie works fine, e.g.
https://forum.qnap.com/viewtopic.php?f=147&t=138368
https://lists.debian.org/debian-arm/2018/02/msg00070.html
Debian user "
Processing commands for cont...@bugs.debian.org:
> severity 887873 important
Bug #887873 [src:linux] linux-image-4.9.0-5-marvell: frequent "usercopy: kernel
memory overwrite attempt detected" on QNAP NAS (ARM)
Severity set to 'important' from 'critical'
> --
Stopping processing here.
Please cont
Your message dated Sun, 4 Mar 2018 18:31:09 +0100
with message-id <20180304173109.elqj4fqy22zj3...@jirafa.cyrius.com>
and subject line Re: Bug#797881: QNAP TS-219P II: qcontrol no longer works
after upgrading to linux-image-4.1.0-0.bpo.1-kirkwood
has caused the Debian Bug report #797881,
regarding
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
> stretch NAS (armel) causes the kernel to fail after ~20mins with a kernel
> memory overwrite attemp
* Christoph Egger [2014-08-22 21:32]:
> FWIW it still doesn't boot. I'll buy a jtag adapter post-debconf so I
> can get anything out of it that might b usefull
This bug report is quite old.
There are users running Debian jessie (3.16) and stretch (4.9)
successfully on QNAP TS-41x hardware.
Do y
Package: src:linux
Version: 4.9.82-1+deb9u3
Severity: important
Tags: ipv6
-- Package-specific info:
** Version:
Linux version 4.9.0-6-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0
20170516 (Debian 6.3.0-18+deb9u1) ) #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
** Command line:
BOOT_
Hi Debian:
I want to add bios information to you. I think it can help you to fix this
bug.
The bios information is from dmidecode.
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Handle 0x, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: 1.1.0
Release Da
Package: linux
Version: 4.9.82-1+deb9u2
Hi Debian:
I'm Chan Jui Huang. I always get the ACPI error, when I boot the
laptop. This is my dmeg:
[ 0.178535] ACPI Error: [_SB_.PCI0.RP05.PXSX] Namespace lookup
failure, AE_NOT_FOUND (20160831/dswload2-191)
[ 0.178553] ACPI Error: Method parse/executio
Hi there,
I usually build debian packages from their sources with the following
command line:
*debuild -i -I --no-sign --build=binary*
Is there a way to build only the *architecture independant binary packages
and the ones related to the host architecture (amd64)*? I'm looking for a
way to avoid
20 matches
Mail list logo
