Bug#1025870: libwlroots10: phosh crashes sometimes due to bug in wlroots (patch available)

2022-12-10 Thread Lukas Straub
Package: libwlroots10
Version: 0.15.1-3
Severity: normal
X-Debbugs-Cc: lukasstra...@web.de

Dear Maintainer,

I'm using Mobian phosh on a pinephone (non-pro). Sometimes (twice per week) 
when waking from
sleep, phosh crashes due to a bug in wlroots and brings down the whole session 
with it.

This bug has been solved upstream, there's a patch in wlroots 0.16 that can be 
backported
to 0.15 and fixes this issue.

It's the patch here:
https://gitlab.gnome.org/World/Phosh/phoc/-/issues/300#note_1595892

I tested wlroots 0.15.1-3 with this patch applied and that solved the issue for 
me.

Regards,
Lukas Straub

-- System Information:
Debian Release: bookworm/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: arm64 (aarch64)

Kernel: Linux 5.15-sunxi64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libwlroots10 depends on:
ii  libc62.36-5
ii  libdrm2  2.4.114-1
ii  libegl1  1.5.0-1
ii  libgbm1  22.2.4-1
ii  libgles2 1.5.0-1
ii  libinput10   1.22.0-1
ii  libpixman-1-00.42.2-1
ii  libseat1 0.7.0-5+b1
ii  libudev1 252.2-1
ii  libwayland-client0   1.21.0-1
ii  libwayland-server0   1.21.0-1
ii  libxcb-composite01.15-1
ii  libxcb-dri3-01.15-1
ii  libxcb-icccm40.4.1-1.1
ii  libxcb-present0  1.15-1
ii  libxcb-render-util0  0.3.9-1+b1
ii  libxcb-render0   1.15-1
ii  libxcb-res0  1.15-1
ii  libxcb-shm0  1.15-1
ii  libxcb-xfixes0   1.15-1
ii  libxcb-xinput0   1.15-1
ii  libxcb1  1.15-1
ii  libxkbcommon01.4.1-1

libwlroots10 recommends no packages.

libwlroots10 suggests no packages.

-- no debconf information



Bug#960271: Status on bug 960271 - 'BITS_PER_LONG' wrongly used

2020-05-22 Thread Lukas Straub
Hello Everyone,
When will this fix be released?

Regards,
Lukas Straub


pgpiQp_Q0hiTt.pgp
Description: OpenPGP digital signature


Bug#956633: libpango-1.0-0: After upgrading from 1.42.4-8 to 1.44.7-3: Wrong font rendering in geany

2020-04-13 Thread Lukas Straub
Package: libpango-1.0-0
Version: 1.44.7-3
Severity: normal

Dear Maintainer,

After upgrading libpangocairo-1.0-0 and libpango-1.0-0 from 1.44.7-3 to
1.42.4-8, fonts are rendered wrong in geany. It seems the cahracters are
too low, so for example underscores are invisible. I'll send some
screenshots by mail.


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.5.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libpango-1.0-0 depends on:
ii  fontconfig 2.13.1-2+b1
ii  libc6  2.30-4
ii  libfribidi01.0.8-2
ii  libglib2.0-0   2.64.1-1
ii  libharfbuzz0b  2.6.4-1
ii  libthai0   0.1.28-3

libpango-1.0-0 recommends no packages.

libpango-1.0-0 suggests no packages.

-- no debconf information



Bug#953114: linux-image-5.4.0-4-amd64: r8169 temporarely looses netwok connectivity

2020-03-04 Thread Lukas Straub
Package: src:linux
Version: 5.4.19-1
Severity: normal

Dear Maintainer,
Under network and/or cpu load, network connectivity is regularely lost for 
short amounts of time (~3 seconds).

This problems also happens with 
linux-image-5.5.0-rc5-amd64-unsigned_5.5~rc5-1~exp1_amd64.
This problem does not happen with linux-image-5.3.0-2-amd64.

Mar 04 15:51:39 tele-clu-03 kernel: [ cut here ]
Mar 04 15:51:39 tele-clu-03 kernel: NETDEV WATCHDOG: enp1s0 (r8169): transmit 
queue 0 timed out
Mar 04 15:51:39 tele-clu-03 kernel: WARNING: CPU: 0 PID: 1503 at 
net/sched/sch_generic.c:447 dev_watchdog+0x248/0x250
Mar 04 15:51:39 tele-clu-03 kernel: Modules linked in: tun sctp ppp_deflate 
bsd_comp ppp_async crc_ccitt ppp_generic slhc sch_htb cls_cgroup bridge stp llc 
ext4 crc16 mbcache jbd2 dm_thin_pool dm_persistent_data dm_bio_prison dm_bufio 
radeon nls_ascii nls_cp437 vfat fat kvm_amd ccp rng_core kvm efi_pstore ttm 
snd_hda_codec_realtek evdev snd_hda_codec_generic drm_kms_helper 
snd_hda_codec_hdmi ledtrig_audio snd_hda_intel snd_intel_nhlt snd_hda_codec drm 
irqbypass serio_raw snd_hda_core efivars pcspkr k10temp sp5100_tco snd_hwdep 
watchdog snd_pcm sg snd_timer snd i2c_algo_bit soundcore button acpi_cpufreq 
efivarfs ip_tables x_tables autofs4 btrfs xor zstd_decompress zstd_compress 
raid6_pq libcrc32c crc32c_generic dm_mod sd_mod uas usb_storage ahci libahci 
ohci_pci libata ohci_hcd ehci_pci ehci_hcd usbcore scsi_mod psmouse r8169 
realtek libphy i2c_piix4 usb_common
Mar 04 15:51:39 tele-clu-03 kernel: CPU: 0 PID: 1503 Comm: pidof Not tainted 
5.4.0-4-amd64 #1 Debian 5.4.19-1
Mar 04 15:51:39 tele-clu-03 kernel: Hardware name: FUJITSU FUTRO S700/D3003-B1, 
BIOS V4.6.4.1 R1.19.0 for D3003-B1x 07/03/2013
Mar 04 15:51:39 tele-clu-03 kernel: RIP: 0010:dev_watchdog+0x248/0x250
Mar 04 15:51:39 tele-clu-03 kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ef c6 05 58 
1d a8 00 01 e8 0d e4 fa ff 44 89 e1 4c 89 ee 48 c7 c7 f0 cc 52 85 48 89 c2 e8 
76 40 a0 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 41 57 41 56 49 89 d6 41 55
Mar 04 15:51:39 tele-clu-03 kernel: RSP: :a25280003e68 EFLAGS: 00010286
Mar 04 15:51:39 tele-clu-03 kernel: RAX:  RBX: 898fb6076e00 
RCX: 0006
Mar 04 15:51:39 tele-clu-03 kernel: RDX: 0007 RSI: 0082 
RDI: 898ff9817680
Mar 04 15:51:39 tele-clu-03 kernel: RBP: 898ff3f6245c R08: 0373 
R09: 0004
Mar 04 15:51:39 tele-clu-03 kernel: R10:  R11: 0001 
R12: 
Mar 04 15:51:39 tele-clu-03 kernel: R13: 898ff3f62000 R14: 898ff3f62480 
R15: 0001
Mar 04 15:51:39 tele-clu-03 kernel: FS:  7f50dcc40540() 
GS:898ff980() knlGS:
Mar 04 15:51:39 tele-clu-03 kernel: CS:  0010 DS:  ES:  CR0: 
80050033
Mar 04 15:51:39 tele-clu-03 kernel: CR2: 558bfde65018 CR3: 7650c000 
CR4: 06f0
Mar 04 15:51:39 tele-clu-03 kernel: Call Trace:
Mar 04 15:51:39 tele-clu-03 kernel:  
Mar 04 15:51:39 tele-clu-03 kernel:  ? pfifo_fast_enqueue+0x150/0x150
Mar 04 15:51:39 tele-clu-03 kernel:  call_timer_fn+0x2d/0x130
Mar 04 15:51:39 tele-clu-03 kernel:  __run_timers.part.0+0x16f/0x260
Mar 04 15:51:39 tele-clu-03 kernel:  ? timerqueue_add+0x96/0xb0
Mar 04 15:51:39 tele-clu-03 kernel:  ? enqueue_hrtimer+0x36/0x90
Mar 04 15:51:39 tele-clu-03 kernel:  run_timer_softirq+0x26/0x50
Mar 04 15:51:39 tele-clu-03 kernel:  __do_softirq+0xe6/0x2e9
Mar 04 15:51:39 tele-clu-03 kernel:  irq_exit+0xa6/0xb0
Mar 04 15:51:39 tele-clu-03 kernel:  smp_apic_timer_interrupt+0x76/0x130
Mar 04 15:51:39 tele-clu-03 kernel:  apic_timer_interrupt+0xf/0x20
Mar 04 15:51:39 tele-clu-03 kernel:  
Mar 04 15:51:39 tele-clu-03 kernel: RIP: 0033:0x7f50dcabd77a
Mar 04 15:51:39 tele-clu-03 kernel: Code: ff 0f 1f 80 00 00 00 00 0f b6 74 24 
13 48 39 cd 0f 85 e2 fe ff ff eb db 0f 1f 84 00 00 00 00 00 48 b9 ff ff ff ff 
ff ff ff 7f <48> 63 54 24 14 48 01 ca 48 39 c2 0f 82 14 ff ff ff 8b 4c 24 14 48
Mar 04 15:51:39 tele-clu-03 kernel: RSP: 002b:7ffd49e5db10 EFLAGS: 0246 
ORIG_RAX: ff13
Mar 04 15:51:39 tele-clu-03 kernel: RAX: 017f RBX:  
RCX: 7fff
Mar 04 15:51:39 tele-clu-03 kernel: RDX: 000a RSI:  
RDI: 558bfde5b2b6
Mar 04 15:51:39 tele-clu-03 kernel: RBP:  R08: 1999 
R09: 
Mar 04 15:51:39 tele-clu-03 kernel: R10: 7f50dcbecac0 R11: 7f50dcbed3c0 
R12: 
Mar 04 15:51:39 tele-clu-03 kernel: R13: 558bfde5b2b3 R14:  
R15: 000a
Mar 04 15:51:39 tele-clu-03 kernel: ---[ end trace c38142171e4748bf ]---


-- Package-specific info:
** Kernel log: boot messages should be attached

** Model information
sys_vendor: FUJITSU
product_name: FUTRO S700
product_version:
chassis_vendor: FUJITSU
chassis_version:
bios_vendor: FUJITSU // American Megatrends Inc.
bios_version: 

Bug#953111: pacemaker: post-start got lost

2020-03-04 Thread Lukas Straub
Package: pacemaker
Version: 2.0.3-3
Severity: normal

Dear Maintainer,
I have a master-slave resource which relies on the post-start notification to 
start replication
to the slave. This works well, but every now and then the post-start 
notification isn't sent.

Note the line
 Discarding attempt to perform action notify on colo_test in state S_INTEGRATION
below.

Mar 04 16:28:50 tele-clu-03 python[8351]: (colo_test) DEBUG: notify called: 
action: pre-start, master_uname: tele-clu-03, start_uname: tele-clu-02, 
stop_uname: tele-clu-01, shutdown_guest: False
Mar 04 16:28:50 tele-clu-03 pacemaker-controld[538]:  notice: Result of notify 
operation for colo_test on tele-clu-03: 0 (ok)
Mar 04 16:28:50 tele-clu-03 pacemaker-controld[538]:  notice: Initiating start 
operation colo_test_start_0 on tele-clu-02
Mar 04 16:28:54 tele-clu-03 corosync[481]:   [KNET  ] rx: host: 1 link: 0 is up
Mar 04 16:28:54 tele-clu-03 corosync[481]:   [KNET  ] host: host: 1 (passive) 
best link: 0 (pri: 0)
Mar 04 16:28:54 tele-clu-03 corosync[481]:   [TOTEM ] A new membership (1.1cc0) 
was formed. Members joined: 1
Mar 04 16:28:54 tele-clu-03 corosync[481]:   [CPG   ] downlist left_list: 0 
received
Mar 04 16:28:54 tele-clu-03 corosync[481]:   [CPG   ] downlist left_list: 0 
received
Mar 04 16:28:54 tele-clu-03 corosync[481]:   [CPG   ] downlist left_list: 0 
received
Mar 04 16:28:55 tele-clu-03 corosync[481]:   [QUORUM] Members[3]: 1 2 3
Mar 04 16:28:55 tele-clu-03 corosync[481]:   [MAIN  ] Completed service 
synchronization, ready to provide service.
Mar 04 16:28:55 tele-clu-03 pacemaker-controld[538]:  notice: Node tele-clu-01 
state is now member
Mar 04 16:28:55 tele-clu-03 pacemakerd[532]:  notice: Node tele-clu-01 state is 
now member
Mar 04 16:28:55 tele-clu-03 pacemaker-based[533]:  notice: Node tele-clu-01 
state is now member
Mar 04 16:28:55 tele-clu-03 pacemaker-attrd[536]:  notice: Node tele-clu-01 
state is now member
Mar 04 16:28:55 tele-clu-03 pacemaker-attrd[536]:  notice: Setting 
#attrd-protocol[tele-clu-01]: (unset) -> 2
Mar 04 16:28:55 tele-clu-03 pacemaker-fenced[534]:  notice: Node tele-clu-01 
state is now member
Mar 04 16:28:55 tele-clu-03 pacemaker-controld[538]:  notice: Transition 12 
aborted: Peer Halt
Mar 04 16:28:55 tele-clu-03 pacemaker-controld[538]:  notice: Initiating notify 
operation colo_test_post_notify_start_0 locally on tele-clu-03
Mar 04 16:28:55 tele-clu-03 pacemaker-controld[538]:  notice: Discarding 
attempt to perform action notify on colo_test in state S_INTEGRATION 
(shutdown=false)
Mar 04 16:28:55 tele-clu-03 pacemaker-controld[538]:  notice: Initiating notify 
operation colo_test_post_notify_start_0 on tele-clu-02
Mar 04 16:28:55 tele-clu-03 pacemaker-controld[538]:  notice: Transition 12 
(Complete=22, Pending=0, Fired=0, Skipped=1, Incomplete=1, 
Source=/var/lib/pacemaker/pengine/pe-warn-93.bz2): Stopped
Mar 04 16:28:57 tele-clu-03 pacemaker-schedulerd[537]:  notice: Watchdog will 
be used via SBD if fencing is required and stonith-watchdog-timeout is nonzero
Mar 04 16:28:57 tele-clu-03 pacemaker-schedulerd[537]:  notice: Calculated 
transition 13, saving inputs in /var/lib/pacemaker/pengine/pe-input-1569.bz2
Mar 04 16:28:57 tele-clu-03 pacemaker-controld[538]:  notice: Initiating 
monitor operation colo_test_monitor_0 on tele-clu-01
Mar 04 16:28:57 tele-clu-03 pacemaker-controld[538]:  notice: Initiating 
monitor operation colo_test_monitor_1 on tele-clu-02
Mar 04 16:28:58 tele-clu-03 pacemaker-controld[538]:  notice: Initiating 
monitor operation colo_small_test_monitor_0 on tele-clu-01
Mar 04 16:28:58 tele-clu-03 pacemaker-controld[538]:  notice: Transition 13 
(Complete=3, Pending=0, Fired=0, Skipped=0, Incomplete=0, 
Source=/var/lib/pacemaker/pengine/pe-input-1569.bz2): Complete
Mar 04 16:28:58 tele-clu-03 pacemaker-controld[538]:  notice: State transition 
S_TRANSITION_ENGINE -> S_IDLE
Mar 04 16:29:08 tele-clu-03 pacemaker-controld[538]:  notice: High CPU load 
detected: 2.75

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.3.0-2-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pacemaker depends on:
ii  corosync   3.0.2-1+b1
ii  dbus   1.12.16-2
ii  init-system-helpers1.57
ii  libc6  2.29-10
ii  libcfg73.0.2-1+b1
ii  libcib27   2.0.3-3
ii  libcmap4   3.0.2-1+b1
ii  libcorosync-common43.0.2-1+b1
ii  libcrmcluster292.0.3-3
ii  libcrmcommon34 2.0.3-3
ii  libcrmservice282.0.3-3
ii  libglib2.0-0   2.62.5-1
ii  libgnutls303.6.12-2
ii  liblrmd28  2.0.3-3
ii  libpacemaker1

Bug#951532: libinput: Touchpad behavour changed

2020-02-21 Thread Lukas Straub
On Fri, 21 Feb 2020 17:58:57 +0200
Timo Aaltonen  wrote:

> On 21.2.2020 17.16, Lukas Straub wrote:
> > On Wed, 19 Feb 2020 16:10:26 +0200
> > Timo Aaltonen  wrote:
> >
> >> On 17.2.2020 22.33, Lukas Straub wrote:
> >>> Source: libinput
> >>> Version: 1.15.1-1
> >>> Severity: normal
> >>>
> >>> Dear Maintainer,
> >>> Since Version 1.15.1-1 the behavour of the Touchpad changed. I have a 
> >>> "unified" Touchpad i.e. no physical seperate buttons, the whole touchpad 
> >>> is pressed down.
> >>> -It's now impossible to do a middle or right-click and drag (It will 
> >>> always send left-click)
> >>> -If I have my finger on the touch area first, I can do left-click and 
> >>> drag. If the mouse button is pressed first, it's impossible to drag (the 
> >>> pointer stays where it is).
> >>>
> >>> These problems go away if I downgrade to libinput-bin 1.14.3-1.
> >>
> >> Test 1.15.1-2 which was uploaded today.
> >>
> >>
> >
> > Hmm, I just updated to 1.15.2-1 and it is impossible to drag again.
>
> So it didn't work the first time either?
>
> I guess it needs libevdev 1.9.0-rc1...
>
>

No,
1.15.1-1 had the Problems described above.
1.15.1-2 everything worked again.
1.15.2-1 drag (if the mouse button is pressed first) stopped working again.

Regards,
Lukas Straub



Bug#951532: libinput: Touchpad behavour changed

2020-02-21 Thread Lukas Straub
On Wed, 19 Feb 2020 16:10:26 +0200
Timo Aaltonen  wrote:

> On 17.2.2020 22.33, Lukas Straub wrote:
> > Source: libinput
> > Version: 1.15.1-1
> > Severity: normal
> >
> > Dear Maintainer,
> > Since Version 1.15.1-1 the behavour of the Touchpad changed. I have a 
> > "unified" Touchpad i.e. no physical seperate buttons, the whole touchpad is 
> > pressed down.
> > -It's now impossible to do a middle or right-click and drag (It will always 
> > send left-click)
> > -If I have my finger on the touch area first, I can do left-click and drag. 
> > If the mouse button is pressed first, it's impossible to drag (the pointer 
> > stays where it is).
> >
> > These problems go away if I downgrade to libinput-bin 1.14.3-1.
>
> Test 1.15.1-2 which was uploaded today.
>
>

Hmm, I just updated to 1.15.2-1 and it is impossible to drag again.

Regards,
Lukas Straub



Bug#951532: libinput: Touchpad behavour changed

2020-02-19 Thread Lukas Straub
On Wed, 19 Feb 2020 16:10:26 +0200
Timo Aaltonen  wrote:

> On 17.2.2020 22.33, Lukas Straub wrote:
> > Source: libinput
> > Version: 1.15.1-1
> > Severity: normal
> >
> > Dear Maintainer,
> > Since Version 1.15.1-1 the behavour of the Touchpad changed. I have a 
> > "unified" Touchpad i.e. no physical seperate buttons, the whole touchpad is 
> > pressed down.
> > -It's now impossible to do a middle or right-click and drag (It will always 
> > send left-click)
> > -If I have my finger on the touch area first, I can do left-click and drag. 
> > If the mouse button is pressed first, it's impossible to drag (the pointer 
> > stays where it is).
> >
> > These problems go away if I downgrade to libinput-bin 1.14.3-1.
>
> Test 1.15.1-2 which was uploaded today.
>
>

Yep, It works now. Thanks.



Bug#951532: libinput: Touchpad behavour changed

2020-02-17 Thread Lukas Straub
Source: libinput
Version: 1.15.1-1
Severity: normal

Dear Maintainer,
Since Version 1.15.1-1 the behavour of the Touchpad changed. I have a "unified" 
Touchpad i.e. no physical seperate buttons, the whole touchpad is pressed down.
-It's now impossible to do a middle or right-click and drag (It will always 
send left-click)
-If I have my finger on the touch area first, I can do left-click and drag. If 
the mouse button is pressed first, it's impossible to drag (the pointer stays 
where it is). 

These problems go away if I downgrade to libinput-bin 1.14.3-1.

Regards,
Lukas Straub

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.4.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Bug#920607: Fw: Bug#920607: Debian Buster installer on qnap ts-21x / Fujitsu Q700 : /dev/mtdblock* missing

2019-02-09 Thread Lukas Straub
On Sat, 2 Feb 2019 16:30:46 +0100
Uwe Kleine-König  wrote:

> Control: tag -1 + pending
> 
> On Wed, Jan 30, 2019 at 09:42:32PM +0100, Uwe Kleine-König wrote:  
> > Maybe adding spi-orion to
> > debian/installer/modules/armel-marvell/mtd-modules is the right fix
> > here, but I don't understand enough about the generation of udebs to
> > judge if this is right.
> 
> After getting some feedback off-list I committed this to linux.git
> (https://deb.li/i78Aj).
> 
> Best regards
> Uwe
>   

Cool, Can a new Installer be build with this fix?

Regards,
Lukas Straub



Bug#920641: Acknowledgement (cifs: Reading files from samba share with "smb encrypt = mandatory" hangs Applications)

2019-02-04 Thread Lukas Straub
Control: fixed -1 4.19.16-1

This seems to be fixed in linux 4.19.16-1. At least I could not
reproduce it there.



Bug#920641: cifs: Reading files from samba share with "smb encrypt = mandatory" hangs Applications

2019-01-27 Thread Lukas Straub
Source: linux
Version: 4.19.0-1-amd64
Severity: important

Dear Maintainer,
Reading from a cifs share "smb encrypt = mandatory" hangs the Application, 
however ls and writing files works without porblem.
I dont have these Problems with linux 4.18.0-3.

Steps to reproduce:

1. Setup an samba server with a share similar to the following:
[data]  
smb encrypt = mandatory
path = /mnt/data
available = yes
read only = no
inherit permissions = yes
mangled names = no

2. Mount from the client:
$ mount -t cifs ///data /mnt/nas

3. Read something:
cat /mnt/nas/somefile.txt

The cat then hangs instead of displaying the file.

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled



Bug#920607: Debian Buster installer on qnap ts-21x / Fujitsu Q700 : /dev/mtdblock* missing

2019-01-27 Thread Lukas Straub
Package: linux
Version: 4.19.12-1

Hello Everyone,
I tried the latest Buster Installer on my Fujitsu Q700 (rebranded
qnap ts-21x) and Everything works except that /dev/mtdblock* devices
are missing so flashing the kernel and initrd fails.

Regards,
Lukas Straub
[0.00] Booting Linux on physical CPU 0x0
[0.00] Linux version 4.19.0-1-marvell (debian-ker...@lists.debian.org) 
(gcc version 8.2.0 (Debian 8.2.0-12)) #1 Debian 4.19.12-1 (2018-12-22)
[0.00] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), 
cr=0005397f
[0.00] CPU: VIVT data cache, VIVT instruction cache
[0.00] OF: fdt: Machine model: QNAP TS219 family
[0.00] Memory policy: Data cache writeback
[0.00] On node 0 totalpages: 131072
[0.00]   Normal zone: 1024 pages used for memmap
[0.00]   Normal zone: 0 pages reserved
[0.00]   Normal zone: 131072 pages, LIFO batch:31
[0.00] random: get_random_bytes called from start_kernel+0x78/0x4ac 
with crng_init=0
[0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[0.00] pcpu-alloc: [0] 0
[0.00] Built 1 zonelists, mobility grouping on.  Total pages: 130048
[0.00] Kernel command line: console=ttyS0,115200 root=/dev/ram 
initrd=0xa0,0x90 ramdisk=32768
[0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[0.00] Memory: 504484K/524288K available (3943K kernel code, 342K 
rwdata, 1032K rodata, 304K init, 218K bss, 19804K reserved, 0K cma-reserved, 0K 
highmem)
[0.00] Virtual kernel memory layout:
[0.00] vector  : 0x - 0x1000   (   4 kB)
[0.00] fixmap  : 0xffc0 - 0xfff0   (3072 kB)
[0.00] vmalloc : 0xe080 - 0xff80   ( 496 MB)
[0.00] lowmem  : 0xc000 - 0xe000   ( 512 MB)
[0.00] pkmap   : 0xbfe0 - 0xc000   (   2 MB)
[0.00] modules : 0xbf00 - 0xbfe0   (  14 MB)
[0.00]   .text : 0x(ptrval) - 0x(ptrval)   (3945 kB)
[0.00]   .init : 0x(ptrval) - 0x(ptrval)   ( 304 kB)
[0.00]   .data : 0x(ptrval) - 0x(ptrval)   ( 343 kB)
[0.00].bss : 0x(ptrval) - 0x(ptrval)   ( 219 kB)
[0.00] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[0.00] ftrace: allocating 18837 entries in 37 pages
[0.00] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[0.00] clocksource: orion_clocksource: mask: 0x max_cycles: 
0x, max_idle_ns: 9556302233 ns
[0.08] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 
10737418237ns
[0.38] Switching to timer-based delay loop, resolution 5ns
[0.000128] Calibrating delay loop (skipped), value calculated using timer 
frequency.. 400.00 BogoMIPS (lpj=80)
[0.000150] pid_max: default: 32768 minimum: 301
[0.000420] Security Framework initialized
[0.000438] Yama: disabled by default; enable with sysctl kernel.yama.*
[0.000542] AppArmor: AppArmor initialized
[0.000673] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.000693] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[0.001652] CPU: Testing write buffer coherency: ok
[0.002622] Setting up static identity map for 0x8200 - 0x823c
[0.002856] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[0.004650] devtmpfs: initialized
[0.007845] VFP support v0.3: not present
[0.007994] clocksource: jiffies: mask: 0x max_cycles: 0x, 
max_idle_ns: 764504178510 ns
[0.008019] futex hash table entries: 256 (order: -1, 3072 bytes)
[0.008382] pinctrl core: initialized pinctrl subsystem
[0.009458] NET: Registered protocol family 16
[0.009839] DMA: preallocated 256 KiB pool for atomic coherent allocations
[0.010448] audit: initializing netlink subsys (disabled)
[0.011192] cpuidle: using governor ladder
[0.011208] cpuidle: using governor menu
[0.011538] Feroceon L2: Enabling L2
[0.011580] Feroceon L2: Cache support initialised.
[0.011809] [Firmware Info]: 
/ocp@f100/ethernet-controller@72000/ethernet0-port@0: local-mac-address is 
not set
[0.015587] No ATAGs?
[0.016074] audit: type=2000 audit(0.008:1): state=initialized 
audit_enabled=0 res=1
[0.019974] clocksource: Switched to clocksource orion_clocksource
[0.041981] VFS: Disk quotas dquot_6.6.0
[0.042070] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[0.042509] AppArmor: AppArmor Filesystem Enabled
[0.043616] NET: Registered protocol family 2
[0.044345] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 
bytes)
[0.044374] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[0.044426] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[0.044476] TCP: Hash tables configured (established 4096 bind 4096

Bug#915333: Status

2018-12-29 Thread Lukas Straub
Hello Everyone,
Any status on this?

Regards,
Lukas Straub



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

2018-12-02 Thread Lukas Straub
Package: git-annex
Version: 7.20181121-1
Severity: important

Dear Maintainer,
I wanted to use git-annex on this machine (Fujitsu Q700 NAS), but it Crashes 
with 
"Illegal Instruction". I don't have these problems with other Packages or with 
the 
upstream build of git-annex.

Many Thanks for Maintaining the Debian Package.

Regards,
Lukas Straub


/proc/cpuinfo:
processor   : 0
model name  : Feroceon 88FR131 rev 1 (v5l)
BogoMIPS: 400.00
Features: swp half thumb fastmult edsp 
CPU implementer : 0x56
CPU architecture: 5TE
CPU variant : 0x2
CPU part: 0x131
CPU revision: 1

Hardware: Marvell Kirkwood (Flattened Device Tree)
Revision: 
Serial  : 

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: armel (armv5tel)

Kernel: Linux 4.18.0-0.bpo.1-marvell
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git-annex depends on:
ii  curl7.62.0-1
ii  git 1:2.19.2-1
ii  libatomic1  8.2.0-9
ii  libc6   2.27-8
ii  libffi6 3.2.1-9
ii  libgmp102:6.1.2+dfsg-3
ii  libmagic1   1:5.34-2
ii  libsqlite3-03.25.3-2
ii  libxml2 2.9.4+dfsg1-7+b2
ii  netbase 5.5
ii  openssh-client  1:7.9p1-4
ii  rsync   3.1.2-2.2
ii  zlib1g  1:1.2.11.dfsg-1

Versions of packages git-annex recommends:
ii  aria2  1.34.0-3
ii  bind9-host 1:9.11.5+dfsg-1
ii  git-remote-gcrypt  1.1-1
ii  gnupg  2.2.11-1
ii  lsof   4.89+dfsg-0.1
ii  nocache1.0-1

Versions of packages git-annex suggests:
pn  adb 
pn  bup 
pn  libnss-mdns 
pn  magic-wormhole  
pn  tahoe-lafs  
ii  tor 0.3.4.9-5
pn  uftp
pn  xdot
pn  youtube-dl  

-- no debconf information



Bug#899107: linux-image-4.16.0-1-amd64: Sometimes Black Screen on Boot

2018-05-19 Thread Lukas Straub
Package: src:linux
Version: 4.16.5-1
Severity: important

Dear Maintainer,
Since upgrading to 4.16.5-1, sometimes the screen stays black on Boot and I see 
the following in the Kernel log (via ssh):
[   18.235309] BUG: unable to handle kernel NULL pointer dereference at 

[   18.235320] IP:   (null)
[   18.235324] PGD 0 P4D 0 
[   18.235329] Oops: 0010 [#1] SMP PTI
[   18.235333] Modules linked in: iTCO_wdt iTCO_vendor_support dell_wmi 
wmi_bmof sparse_keymap coretemp kvm_intel dell_rbtn dell_laptop dell_smbios 
dell_wmi_descriptor dcdbas dell_smm_hwmon kvm irqbypass joydev pcspkr serio_raw 
arc4 pcmcia evdev i915(+) iwl3945 iwlegacy snd_hda_codec_idt 
snd_hda_codec_generic lpc_ich mac80211 snd_hda_intel yenta_socket cfg80211 
snd_hda_codec pcmcia_rsrc drm_kms_helper snd_hda_core pcmcia_core rfkill 
snd_hwdep drm snd_pcm snd_timer i2c_algo_bit snd soundcore shpchp wmi battery 
button video ac acpi_cpufreq parport_pc ppdev lp parport ip_tables x_tables 
autofs4 ext4 crc16 mbcache jbd2 fscrypto btrfs zstd_decompress zstd_compress 
xxhash ecb crypto_simd glue_helper cryptd aes_x86_64 xts algif_skcipher af_alg 
dm_crypt dm_mod raid10 raid456 async_raid6_recov async_memcpy async_pq
[   18.235414]  async_xor async_tx xor raid6_pq libcrc32c crc32c_generic raid1 
raid0 multipath linear md_mod uas usb_storage sg hid_generic usbhid hid sr_mod 
cdrom sd_mod ata_generic psmouse i2c_i801 ahci ata_piix libahci firewire_ohci 
firewire_core crc_itu_t libata tg3 scsi_mod libphy thermal ehci_pci uhci_hcd 
ehci_hcd usbcore usb_common
[   18.235454] CPU: 1 PID: 454 Comm: systemd-udevd Not tainted 4.16.0-1-amd64 
#1 Debian 4.16.5-1
[   18.235458] Hardware name: Dell Inc. Latitude D630   
/0KU184, BIOS A19 06/04/2013
[   18.235463] RIP: 0010:  (null)
[   18.235466] RSP: 0018:b7ba40acf9e0 EFLAGS: 00010287
[   18.235470] RAX:  RBX: 97ac5467 RCX: 0032
[   18.235474] RDX: c0c54380 RSI: b7ba40acfa04 RDI: 97ac5574a000
[   18.235478] RBP: 97ac54670338 R08: 97ac57eeb8e0 R09: c0c3df38
[   18.235481] R10: e1bb44564780 R11: 005f R12: 97ac54670368
[   18.235485] R13: c0c3df38 R14: c0c3df30 R15: 97ac5574a000
[   18.235490] FS:  7fe3b8e008c0() GS:97ac5fd0() 
knlGS:
[   18.235494] CS:  0010 DS:  ES:  CR0: 80050033
[   18.235498] CR2:  CR3: 00011889 CR4: 06e0
[   18.235501] Call Trace:
[   18.235581]  ? intel_modeset_setup_hw_state+0x31c/0xfc0 [i915]
[   18.235612]  ? drm_modeset_lock+0x6f/0xf0 [drm]
[   18.235654]  ? __intel_display_resume+0x1e/0xc0 [i915]
[   18.235695]  ? intel_display_resume+0xe1/0x110 [i915]
[   18.235737]  ? intel_lid_notify+0xbc/0xc0 [i915]
[   18.235744]  ? notifier_call_chain+0x47/0x70
[   18.235749]  ? blocking_notifier_call_chain+0x3e/0x60
[   18.235754]  ? acpi_lid_notify_state+0x94/0x200 [button]
[   18.235759]  ? acpi_lid_update_state+0x49/0x70 [button]
[   18.235763]  ? acpi_lid_input_open+0x65/0x90 [button]
[   18.235768]  ? input_open_device+0x73/0xa0
[   18.235774]  ? evdev_open+0x186/0x1d0 [evdev]
[   18.235779]  ? chrdev_open+0xc4/0x1d0
[   18.235783]  ? cdev_put.part.1+0x20/0x20
[   18.235787]  ? do_dentry_open+0x1b3/0x2d0
[   18.235792]  ? path_openat+0x661/0x1660
[   18.235797]  ? vsnprintf+0xf2/0x4b0
[   18.235801]  ? snprintf+0x45/0x70
[   18.235805]  ? do_filp_open+0x9b/0x110
[   18.235809]  ? __check_object_size+0xa7/0x1a0
[   18.235813]  ? do_sys_open+0x1bd/0x250
[   18.235817]  ? do_sys_open+0x1bd/0x250
[   18.235822]  ? do_syscall_64+0x6c/0x130
[   18.235826]  ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[   18.235830] Code:  Bad RIP value.
[   18.235838] RIP:   (null) RSP: b7ba40acf9e0
[   18.235841] CR2: 
[   18.235858] ---[ end trace e29515312d175fa6 ]---


-- Package-specific info:
** Version:
Linux version 4.16.0-1-amd64 (debian-ker...@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-17)) #1 SMP Debian 4.16.5-1 (2018-04-29)

** Command line:
BOOT_IMAGE=/vmlinuz-4.16.0-1-amd64 root=/dev/mapper/luklap--new-root ro 
video=SVIDEO-1:d quiet init=/sbin/e4rat-preload

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

sys_vendor: Dell Inc.
product_name: Latitude D630   
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: A19
board_vendor: Dell Inc.
board_name: 0KU184
board_version: 

** Loaded modules:
kvdo(O)
uds(O)
bluetooth
drbg
ansi_cprng
ecdh_generic
pci_stub
vboxpci(O)
vboxnetadp(O)
vboxnetflt(O)
msr
vboxdrv(O)
zram
zsmalloc
iptable_filter
bridge
stp
llc
fuse
iTCO_wdt
iTCO_vendor_support
dell_wmi
sparse_keymap
wmi_bmof
dell_rbtn
dell_laptop
dell_smbios
dell_wmi_descriptor
dcdbas
dell_smm_hwmon
coretemp
kvm_intel
kvm
arc4
irqbypass
iwl3945
evdev
joydev
serio_raw
iwlegacy
i915
pcmcia
pcspkr
snd_hda_codec_idt
snd_hda_codec_generic
snd_hda_intel

Bug#898318: linux-image-amd64: dm-integrity Module not avivable

2018-05-10 Thread Lukas Straub
Package: linux-image-amd64
Version: 4.16+93
Severity: wishlist

Dear Maintainer,
I wanted to try dm-integrity with integritysetup (allready part of 
cryptsetup-bin), but the Module is not avivable in any kernel packages. Could 
you please add the Module to the package/build?

-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.16.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-image-amd64 depends on:
ii  linux-image-4.16.0-1-amd64  4.16.5-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information