Bug#915333: git-annex: Illegal Instruction on armel (Fujitsu Q700 like QNAP TS-21x/TS-22x)

2019-04-07 Thread Darshaka Pathirana
Hey,

On Mon, 11 Mar 2019 12:05:55 +0200 Adrian Bunk  wrote:
> On Thu, Jan 31, 2019 at 08:12:17PM +0100, Bernhard Übelacker wrote:
> > Hello Everyone,
> > I own a qnap ts-119pII with a similar cpu.
> >
> > See attached file with several debugging attempts.

I took some time and wanted to reproduce and test this issue.

> > If I read [1] right, then the UXTH instruction is just supported
> > on ARMv6 or later.
>
> Looking at the code, the bug seems to be in
> https://sources.debian.org/src/ghc/8.4.4+dfsg1-2/debian/patches/llvm-arm-unknown-linux-gnueabi.patch/
>
> ARM1136JF-S is ARM11, which is ARMv6.
> arm9e would be correct here instead of arm1136jf-s.
>
> Due to the static-only nature of the ghc ecosystem the fix would then
> require a complete rebuild of all Haskell packages on armel, but with
> the buildds otherwise mostly idle now this should be finished within
> 2-3 days.

First I tried to reproduce the crash on one of our porterboxes[4]
`amdahl` (where I could not reproduce the bug, git-annex runs just
fine), but I only much later figured out that it run armv8l:

[4] https://db.debian.org/machines.cgi?host=amdahl

  dpat@amdahl ~ % export sessionid=913555
  dpat@amdahl ~ % schroot -b -c sid_armel-dchroot -n $sessionid
  I: 00check: Untarring chroot environment.  This might take a minute or two.
  I: 99porterbox-extra-sources: o To install build dependencies run
  I: 99porterbox-extra-sources:   dd-schroot-cmd -c 915333 apt-get update
  I: 99porterbox-extra-sources:   followed by build-dep/install as appropriate 
in the host system.
  I: 99porterbox-extra-sources: o If you started this session with schroot -b, 
please do not forget to run
  I: 99porterbox-extra-sources:   schroot --end-session -c 915333
  I: 99porterbox-extra-sources:   when you no longer need this environment.
  915333
  schroot -b -c sid_armel-dchroot -n $sessionid  9.08s user 5.17s system 126% 
cpu 11.293 total
  (sid_armel-dchroot)dpat@amdahl ~ % uname -a
  Linux amdahl 4.9.0-8-arm64 #1 SMP Debian 4.9.144-3.1 (2019-02-19) armv8l 
GNU/Linux

I also tried on `abel` but its a armv7l.

I then wanted to setup a qemu-arm environment but I am stuck finding out which
machine/cpu option would be correct. I found [1] and [2] which states that the 
CPU
"Feroceon 88FR131 rev 1 (v5l)" is a actually a Marvell Kirkwood 88F6281.
(Ok, [3] says that qnap ts-11x runs on Kirkwood system-on-chip (SoC) from 
Marvell).

[1] 
https://www.chainsawonatireswing.com/2012/01/07/find-out-which-cpu-your-synology-diskstation-uses/
[2] https://www.7-cpu.com/cpu/Kirkwood.html
[3] https://www.debian.org/releases/stable/armel/ch02s01.html.en (see 2.1.4)

So, is it possible to emulate a armv5 and if yes, how? Thanks.

Regards from the Debian BSP201904, Salzburg,
 - Darsha



signature.asc
Description: OpenPGP digital signature


Bug#961490: fwupd: version in stable too old, no updates possible

2020-06-29 Thread Darshaka Pathirana
Hi,

just wanted to let you know that I do *not* get the

  "Not compatible with org.freedesktop.fwupd version 1.2.5, requires >= 1.2.7"

output/error here:

  % sudo fwupdmgr refresh
  Fetching metadata https://cdn.fwupd.org/downloads/firmware.xml.gz
  Downloading… [***]
  Fetching signature https://cdn.fwupd.org/downloads/firmware.xml.gz.asc

  % sudo fwupdmgr get-updates 2>/dev/null | grep -e "has firmware updates" -e 
"^ID" -e "^Update Version"
  UEFI Device Firmware has firmware updates:
  ID:  com.lenovo.ThinkPadN20HT.firmware
  Update Version:  0.1.13
  ID:  com.lenovo.ThinkPadN20HT.firmware
  Update Version:  0.1.12
  ID:  com.lenovo.ThinkPadN20HT.firmware
  Update Version:  0.1.11
  ID:  com.lenovo.ThinkPadN20HT.firmware
  Update Version:  0.1.10

(Yes, I have a pending update).

FYI:

  Package: fwupd
  Version: 1.2.5-2

and:

  % sudo fwupdmgr --version
  client version: 1.2.5
  compile-time dependency versions
  gusb:   0.3.0
  efivar: 37
  daemon version: 1.2.5

20KF001GGE System Firmware (0.1.40) and UEFI Device Firmware
(184.70.3626) have been updated recently.


But my main reason for coming here is the fact that the (critical[1])
Firmware-Update for the Thunderbolt Controller[1][2] and the NVMe[2] is
not detected:

[1] https://pcsupport.lenovo.com/fi/en/solutions/ht508988
[2] https://fwupd.org/lvfs/devices/com.lenovo.ThinkPadN20TF.firmware
[3] https://fwupd.org/lvfs/devices/com.lenovo.PM981.512GB_1TB.firmware

  % sudo fwupdmgr get-devices | grep -v Serial
  ThinkPad X280 Thunderbolt Controller
DeviceId: a4ff56667c8863bbfec8c52b6aa02b51a98a8fb2
Guid: 4808eca4-fd4a-50e6-9e8d-bfd813f063da <- 
TBT-01091704-native
Summary:  Unmatched performance for high-speed I/O
Plugin:   thunderbolt
Flags:internal|updatable|registered
Vendor:   Lenovo
VendorId: TBT:0x0109
Version:  12.00
Icon: computer
Created:  2020-06-29

  20KF001GGE System Firmware
DeviceId: 5a566863d357fb728a620cdf235632fb9bc99f5f
Guid: 508f7539-1ad6-48b9-8680-38377535009d
Plugin:   uefi
Flags:
internal|updatable|require-ac|supported|registered|needs-reboot
Version:  0.1.40
VersionLowest:0.0.1
Icon: computer
Created:  2020-06-29

  UEFI Device Firmware
DeviceId: 093ef0be8328a2c4ed2fe55cd36aae3171b92ade
Guid: 6d28cd9f-7bcd-4fb9-9f10-0372e2962fc4
Plugin:   uefi
Flags:
internal|updatable|require-ac|supported|registered|needs-reboot
Version:  184.70.3626
VersionLowest:0.0.1
Icon: audio-card
Created:  2020-06-29

  UEFI Device Firmware
DeviceId: ca368aebcf7da847029e9f2520ec55fb7a036b31
Guid: 3f4a527b-6588-45b8-b2d3-dc61189b63cb
Plugin:   uefi
Flags:
internal|updatable|require-ac|supported|registered|needs-reboot
Version:  0.1.4
VersionLowest:0.1.4
Icon: audio-card
Created:  2020-06-29

  SAMSUNG MZVLB512HAJQ-000L7
DeviceId: e11623b2caa18fee292058a5c09ca4e6152f7ecf
Guid: 47335265-a509-51f7-841e-1c94911af66b <- 
NVME\VEN_144D&DEV_A808
Guid: 8fd4ca73-d0ae-52e8-8977-461435c6f4cf <- NVME\VEN_144D
Guid: 79d6cfae-a5a2-5936-9248-5aebd23480f7 <- SAMSUNG 
MZVLB512HAJQ-000L7
Summary:  NVM Express Solid State Drive
Plugin:   nvme
Flags:
internal|updatable|require-ac|supported|registered|needs-reboot
Vendor:   Samsung Electronics Co Ltd
VendorId: NVME:0x144D
Version:  3L2QEXA7
Icon: drive-harddisk
Created:  2020-06-29

  ST2000LM007-1R8174
DeviceId: 8b2e996216566cd71a3ec9c03bce8a9827a277e0
Guid: fe3873a5-8d96-5cd6-ae8e-aec49f11ed82 <- 
IDE\ST2000LM007-1R8174__EB01
Guid: a3cbe2af-31fd-5848-a7f9-44a95fa5f44d <- 
IDE\0ST2000LM007-1R8174__
Guid: 0f5e4f1e-1732-52a1-88d9-118952f0ffb3 <- 
ST2000LM007-1R8174
Summary:  ATA Drive
Plugin:   ata
Flags:updatable|require-ac|registered|needs-reboot
Version:  EB01
Icon: drive-harddisk
Created:  2020-06-29

  % sudo fwupdmgr get-updates 1>/dev/null
  No upgrades for 20KF001GGE System Firmware, current is 0.1.40: 0.1.30=older, 
0.1.29=older, 0.1.28=older, 

Bug#847287: roundcube: Roundcube 1.2.2: Remote command execution via malicious email composing

2016-12-08 Thread Darshaka Pathirana
On Wed, 07 Dec 2016 12:16:14 +0100 Vincent Bernat
 wrote:
>  ❦  7 décembre 2016 12:08 +0100, Guilhem Moulin  :
>
> >> Is the tag for debian/1.1.5+dfsg.1-1_bpo8+1? The diff for it is pretty
> >> big.
> >
> > 1.1.5+dfsg.1-1_bpo8+1 is the current version from jessie-backports (since
> > April 29).  The diff between 1.1.5+dfsg.1-1_bpo8+1 and 1.1.5+dfsg.1-1_bpo8+2
> > is merely the upstream fix
> >
> > 
> > https://anonscm.debian.org/cgit/pkg-roundcube/roundcube.git/diff/?id=debian/1.1.5%2bdfsg.1-1_bpo8%2b2&id2=debian/1.1.5%2bdfsg.1-1_bpo8%2b1
> 
> I deleted the tag on my side, fetched it again and the diff is now
> OK. I'll upload in the next hour.

Wow. That was quick! Thanks to you all.

What about wheezy / wheezy-backports? Are these packages affected too?

Regards,
 - Darsha



signature.asc
Description: OpenPGP digital signature