Processed: reassign 963868 to src:linux

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 963868 src:linux 5.7.6-1
Bug #963868 [linux-image-amd64] linux-image-amd64: 5.7.6 crash (maybe amdgpu 
and temperature related)
Bug reassigned from package 'linux-image-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/5.7.6+1.
Ignoring request to alter fixed versions of bug #963868 to the same values 
previously set
Bug #963868 [src:linux] linux-image-amd64: 5.7.6 crash (maybe amdgpu and 
temperature related)
Marked as found in versions linux/5.7.6-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
963868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963868
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#968110: linux-image-5.7.0-2-amd64: USB 3 storage device not detected

2020-08-08 Thread Jörg-Volker Peetz
Package: src:linux
Version: 5.7.10-1
Severity: normal

Dear Maintainer,

USB 3 storage devices (hdd and stick) are not detected. Nothing shows up in the
log files (messages, kern.log) and the command lsusb doesn't show the device.
The version 5.7.6-1 also doesn't work.

A USB 2 storage device and a USB mouse are detected and can be used.

Any ideas?
Regards,
Jörg.


** Model information
sys_vendor: Hewlett-Packard
product_name: HP ProBook 650 G1
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version:
bios_vendor: Hewlett-Packard
bios_version: L77 Ver. 01.21
board_vendor: Hewlett-Packard
board_name: 1993
board_version: KBC Version 16.39



Processed: bug 964181 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=208729

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> forwarded 964181 https://bugzilla.kernel.org/show_bug.cgi?id=208729
Bug #964181 [src:linux] linux-image-4.19.0-9-amd64: Unable to get battery status
Set Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=208729'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
964181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964181
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Bug#968109: linux-image-5.7.0-2-arm64: USB unusable on Raspberry Pi 4B 8GB

2020-08-08 Thread Ryutaroh Matsumoto
Package: src:linux
Version: 5.7.10-1
Severity: normal

Dear Maintainer,

I installed an SD card image from
https://raspi.debian.net/daily/raspi_4.img.xz
to Raspberry Pi 4B 8GB (board revision 1.4).

USB is unusable and "lsusb" shows nothing.
Relevant dmesg is as follows:


[3.198861] pci :01:00.0: enabling device ( -> 0002)
[8.663493] pci :01:00.0: xHCI HW not ready after 5 sec (HC bug?) status 
= 0x801
[8.663690] pci :01:00.0: quirk_usb_early_handoff+0x0/0x890 took 5336734 
usecs

[   12.265387] xhci_hcd :01:00.0: xHCI Host Controller
[   12.268816] mmc0: queuing unknown CIS tuple 0x80 (7 bytes)
[   12.278041] dwc2 fe98.usb: supply vusb_d not found, using dummy regulator
[   12.278134] dwc2 fe98.usb: supply vusb_a not found, using dummy regulator
[   12.282227] xhci_hcd :01:00.0: new USB bus registered, assigned bus 
number 1
[   22.320273] xhci_hcd :01:00.0: can't setup: -110
[   22.336521] xhci_hcd :01:00.0: USB bus 1 deregistered
[   22.353573] xhci_hcd :01:00.0: init :01:00.0 fail, -110


Best regards, Ryutaroh Matsumoto

-- Package-specific info:
** Version:
Linux version 5.7.0-2-arm64 (debian-kernel@lists.debian.org) (gcc version 9.3.0 
(Debian 9.3.0-15), GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 
5.7.10-1 (2020-07-26)

** Command line:
video=HDMI-A-1:3840x2160M@30,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48
 dma.dmachans=0x71f5 bcm2709.boardrev=0xd03114 bcm2709.serial=0x488d2af3 
bcm2709.uart_clock=4800 bcm2709.disk_led_gpio=42 
bcm2709.disk_led_active_low=0 smsc95xx.macaddr=DC:A6:32:BB:99:D9 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  console=tty0 
console=ttyS1,115200 root=/dev/mmcblk1p2 rw elevator=deadline fsck.repair=yes 
net.ifnames=0  rootwait

** Tainted: C (1024)
 * staging driver was loaded

** Kernel log:
Unable to read kernel log; any relevant messages should be attached

** Model information
Device Tree model: Raspberry Pi 4 Model B Rev 1.4

** Loaded modules:
nls_ascii
nls_cp437
vfat
fat
hci_uart
btqca
btrtl
btbcm
btsdio
btintel
bcm2835_v4l2(C)
bluetooth
brcmfmac
brcmutil
videobuf2_vmalloc
videobuf2_memops
snd_bcm2835(C)
videobuf2_v4l2
jitterentropy_rng
videobuf2_common
snd_pcm
drbg
snd_timer
videodev
snd
ansi_cprng
cpufreq_dt
cfg80211
mc
soundcore
ecdh_generic
ecc
rfkill
raspberrypi_cpufreq
bcm2835_wdt
bcm2711_thermal
pwm_bcm2835
iproc_rng200
vchiq(C)
rng_core
leds_gpio
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
btrfs
blake2b_generic
xor
xor_neon
zstd_decompress
zstd_compress
raid6_pq
libcrc32c
crc32c_generic
bfq
broadcom
bcm_phy_lib
xhci_pci
dwc2
xhci_hcd
udc_core
mdio_bcm_unimac
usbcore
genet
sdhci_iproc
of_mdio
sdhci_pltfm
i2c_bcm2835
fixed_phy
libphy
sdhci
gpio_regulator
usb_common
phy_generic

** Network interface configuration:
*** /etc/network/interfaces:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

*** /etc/network/interfaces.d/eth0:
auto eth0

# TODO: switch back to iptables-persistent once it re-enters testing
iface eth0 inet dhcp
# We don't currently support setup of firewalls here.
#   pre-up iptables-restore < /etc/iptables/rules.v4 || true
#   pre-up ip6tables-restore < /etc/iptables/rules.v6 || ture

*** /etc/network/interfaces.d/wlan0:
auto wlan0

# TODO: switch back to iptables-persistent once it re-enters testing
iface wlan0 inet dhcp
# We don't currently support setup of firewalls here.
#   pre-up iptables-restore < /etc/iptables/rules.v4 || true
#   pre-up ip6tables-restore < /etc/iptables/rules.v6 || ture

** Network status:
*** IP interfaces and addresses:
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: eth0:  mtu 1500 qdisc mq state DOWN group 
default qlen 1000
link/ether dc:a6:32:bb:99:d9 brd ff:ff:ff:ff:ff:ff
3: wlan0:  mtu 1500 qdisc pfifo_fast state UP 
group default qlen 1000
link/ether dc:a6:32:bb:99:da brd ff:ff:ff:ff:ff:ff
inet 192.168.1.84/24 brd 192.168.1.255 scope global dynamic wlan0
   valid_lft 42924sec preferred_lft 42924sec
inet6 2400:4050:2ba1:ac00:dea6:32ff:febb:99da/64 scope global dynamic 
mngtmpaddr 
   valid_lft 14071sec preferred_lft 12271sec
inet6 fe80::dea6:32ff:febb:99da/64 scope link 
   valid_lft forever preferred_lft forever

*** Device statistics:
Inter-|   Receive|  Transmit
 face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo:   0   0000 0  0 00  
 0000 0   0  0
  eth0:   0   0000 0  0 0

Bug#968107: POSIX locks not working on fuse fileystems for thunderbird

2020-08-08 Thread Ángel
Package: src:linux
Version: 4.19.132-1
Severity: normal

After updating an i386 system from stretch to buster, it was found that
thunderbird no longer works, instead showing every time the message:
> Thunderbird is already running, but is not responding. To open a new
window, you must first close the existing Thunderbird process, or
restart your system.


strace showed that it is finally shown after thunderbird loops a number
of times on: 

 openat(AT_FDCWD, "<$HOME>/.thunderbird/Profiles//.parentlock", 
O_WRONLY|O_CREAT|O_TRUNC, 0666) = 7
 fcntl64(7, F_GETLK, {l_type=F_UNLCK, l_whence=SEEK_SET, l_start=0, l_len=0, 
l_pid=3085726144}) = 0
 fcntl64(7, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 
-1 EACCES
 close(7)= 0

this is part of nsProfileLock::Lock() at source file nsProfileLock.cpp


The issue is, another instance of thunderbird was *NOT* running. The
issue manifesting itself every time, even just after booting, also after
removing the exiting .parentlock.

Manually doing these operations from a separate test program worked,
though, so it's not that POSIX locks (even on that same file)
*sometimes* work.

Finally, it was determined that the error only happened if the profile
was in a fuse filesystem, as tested on exFAT and ntfs-3g. Even more
intriguing, on sshfs the old profile doesn't work but a new one does?!

Downgrading thunderbird from 1:68.9.0-1~deb9u1 to 1:68.8.0-1~deb9u1 made
no difference, as didn't downgrading libfuse from 2.9.9-1+deb10u1 to
2.9.7-1+deb9u2. However, going back from 4.19.0-10-686-pae to the old
stretch kernel 4.9.0-12-686-pae makes thunderbird work again. Going
forwards to 5.6.0-0.bpo.2-686-pae, it still fails.

Thus, it seems that some change in the new kernel makes POSIX locks not
work on a fuse filesystem (and fail with EACCES, as opposed to e.g.
EOPNOTSUPP) but only under certain conditions that seem to be triggered
by thunderbird but not by a simpler program.
Interestingly, firefox (which would supposedly use the same profile
locking code) did not show any issue on that same system.

Also, the number of file locks was not limited (this is only the second
F_WRLCK in the process, anyway):
file locks  (-x) unlimited


-- Package-specific info:
** Version:
Linux version 4.19.0-10-686-pae (debian-kernel@lists.debian.org) (gcc
version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.132-1 (2020-07-24)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-686-pae root=UUID= ro quiet

** Not tainted


** Model information

** Loaded modules:
netlink_diag
speedstep_lib
cpufreq_userspace
cpufreq_powersave
cpufreq_conservative
rfkill
binfmt_misc
fuse
snd_intel8x0
snd_ac97_codec
ac97_bus
snd_pcm
joydev
snd_timer
snd
iTCO_wdt
soundcore
intel_powerclamp
iTCO_vendor_support
sg
pcspkr
serio_raw
rng_core
evdev
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
crypto_simd
cryptd
aes_i586
hid_generic
usbhid
hid
sd_mod
ata_generic
nouveau
psmouse
ata_piix
mxm_wmi
wmi
video
i2c_algo_bit
libata
ttm
drm_kms_helper
uhci_hcd
ehci_pci
i2c_i801
ehci_hcd
drm
scsi_mod
usbcore
8139too
8139cp
lpc_ich
mfd_core
mii
usb_common
thermal
fan
floppy
button


-- System Information:
Debian Release: 10.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 4.19.0-10-686-pae (SMP w/2 CPU cores)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-4.19.0-10-686-pae depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.133+deb10u1
ii  kmod26-1
ii  linux-base  4.6

Versions of packages linux-image-4.19.0-10-686-pae recommends:
ii  apparmor 2.13.2-10
ii  firmware-linux-free  3.4

Versions of packages linux-image-4.19.0-10-686-pae suggests:
pn  debian-kernel-handbook  
ii  grub-pc 2.02+dfsg1-20+deb10u2
pn  linux-doc-4.19  

Versions of packages linux-image-4.19.0-10-686-pae is related to:
pn  firmware-amd-graphics 
pn  firmware-atheros  
pn  firmware-bnx2 
pn  firmware-bnx2x
pn  firmware-brcm80211
pn  firmware-cavium   
pn  firmware-intel-sound  
pn  firmware-intelwimax   
pn  firmware-ipw2x00  
pn  firmware-ivtv 
pn  firmware-iwlwifi  
pn  firmware-libertas 
pn  firmware-linux-nonfree
pn  firmware-misc-nonfree 
pn  firmware-myricom  
pn  firmware-netxen   
pn  firmware-qlogic   
pn  firmware-realtek  
pn  firmware-samsung  
pn  firmware-siano
pn  firmware-ti-connectivity  
pn  xen-hypervisor

-- no debconf information



Bug#964181: linux-image-4.19.0-9-amd64: Unable to get battery status

2020-08-08 Thread Tino Schmidt

As I feel no one can help me I took this to upstream:
https://bugzilla.kernel.org/show_bug.cgi?id=208729



Bug#968099: ethtool: please upgrade to v5.8 to support forcing master or slave mode

2020-08-08 Thread Jonas Smedegaard
Package: ethtool
Version: 1:5.4-1
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Linux 5.7 introduced support for forcing master or slave mode for
ethernet devices.

This is helpful for debugging issues like Bug#911560, #845128, #927397
suspectedly involving badly calibrated ethernet PHYs.

Interacting with theese new features require ethtool 5.8 or newer.

Therefore, please upgrade ethtool to 5.8.

 - Jonas

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEn+Ppw2aRpp/1PMaELHwxRsGgASEFAl8uqhYACgkQLHwxRsGg
ASGSyg//cpQFH7EhWMLig8tFxmPI1FPjb7eQS1H60re19zC5lP+3Mru866WwkGmd
EGxWRddS4Q/Tr2LB819QE1THIm5iM9AKK8ieSF/dh/wSjllZjAywJIo7B5h+0SX1
+0MzYLZtTYG7VpHXDZwUbZKB/Ii8ikluq6Uu3PiEGNJwQyypGxY+OfnGjaDId/qh
VakUHzY5ec54iFiVTzJJx81DCA8j344Ly/UZ2q3BWTRct3Gc2oIllrayKuOI0htH
hYVIn4Q+tdB6LeatVD1nozKavp9I6jx2d2dlGV9rUWIO+lgCh4RIBjJZtW9CQyyp
mmvJw75bzS0l13UWc1jW38+KbRoFjLpU49iuFyRkt3zmK0BMl2dmyTrGvv6Iju98
9f+HffekycgQw27DA2UohpQhuC4QpD46Phxcx46C9xV71WaDF9Qoxm14veRGU6xA
mX+A6B02Uexfgnn8mZEuqJBFClsDUILAnBFRmRudPvjoa6voHEBm8Ex2XhsnJJfo
dZseAU4vADhRXc6/S4+eNw1szz9EoXwKTLsLerL+PBwwrSrzJeB45RQz7IEzbM5L
8bi/HDT6XIm63xWt/vOtMNVU51E/C5ftETo8uPq+FKPWbYRrBLm7qu9Gw5bRsCz/
6c3BCOT3TX78ZzlDkQBfPsnxUlm3QFoT0b1MXSuP/6cBjKsenuw=
=/Wc+
-END PGP SIGNATURE-