Bug#1072063: linux-image-6.8.11-amd64: one of the external monitors randomly blank for 2-3 seconds with 6.8 kernels

[Vincent Lefevre]

Package: src:linux
Version: 6.8.11-1
Severity: important

I have 2 external monitors with my Dell Precision 5570 laptop, connected
via the Thunderbolt WD22TB4 dock. With the linux-image-6.8.9-amd64 kernel,
then with linux-image-6.8.11-amd64, one of these monitors (not always the
same one) randomly gets blank, several times a day. When I downgraded to
the 6.7.12 kernel before the upgrade to 6.8.11, the problem disappeared.
So this is really an issue with the 6.8 kernels.

The issue seems to be the same as
  https://github.com/pop-os/pop/issues/3261
(specific to a 6.8 kernel, randomly blank for a few seconds).

With almost the same hardware, but apparently a more serious problem:
https://lore.kernel.org/lkml/ecc8bd98-0dac-4f17-abb3-ebc8b10fd...@leemhuis.info/T/
which mentions

  https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/10637

but this is actually unrelated (there was a firmware bug, but
I already have the fixed version "Fixed the issue where a black
screen is displayed intermittently when the external monitor is
connected to the Dell Dock WD19, WD19TB, and WD22TB4.- Improved
the display compatibility of WD19, WD22, and HD22 series dock
between systems and monitors."). I new firmware has been available
for several days, but I haven't upgraded yet.

I can also see various issues reported about 6.8 and dual monitor
setup.

-- Package-specific info:
** Version:
Linux version 6.8.11-amd64 (debian-kernel@lists.debian.org) 
(x86_64-linux-gnu-gcc-13 (Debian 13.2.0-25) 13.2.0, GNU ld (GNU Binutils for 
Debian) 2.42) #1 SMP PREEMPT_DYNAMIC Debian 6.8.11-1 (2024-05-26)

** Command line:
BOOT_IMAGE=/vmlinuz-6.8.11-amd64 root=/dev/mapper/qaa--vg-root ro quiet

** Tainted: W (512)
 * kernel issued warning

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

** Model information
sys_vendor: Dell Inc.
product_name: Precision 5570
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 1.21.0
board_vendor: Dell Inc.
board_name: 01Y4G1
board_version: A00

** Loaded modules:
mptcp_diag
xsk_diag
tcp_diag
udp_diag
raw_diag
inet_diag
unix_diag
af_packet_diag
netlink_diag
uinput
ctr
ccm
snd_seq_dummy
rfcomm
snd_hrtimer
snd_seq
snd_seq_device
cmac
algif_hash
algif_skcipher
af_alg
snd_hda_codec_hdmi
bnep
qrtr
binfmt_misc
snd_sof_pci_intel_tgl
snd_sof_intel_hda_common
soundwire_intel
soundwire_generic_allocation
snd_sof_intel_hda_mlink
soundwire_cadence
snd_sof_intel_hda
snd_sof_pci
snd_sof_xtensa_dsp
snd_sof
snd_sof_utils
snd_soc_hdac_hda
snd_hda_ext_core
intel_uncore_frequency
snd_ctl_led
intel_uncore_frequency_common
snd_soc_acpi_intel_match
x86_pkg_temp_thermal
snd_hda_codec_realtek
snd_soc_acpi
intel_powerclamp
snd_soc_core
snd_hda_codec_generic
coretemp
btusb
kvm_intel
snd_compress
btrtl
snd_pcm_dmaengine
btintel
soundwire_bus
btbcm
btmtk
iwlmvm
snd_hda_intel
kvm
bluetooth
snd_intel_dspcfg
snd_intel_sdw_acpi
mac80211
snd_hda_codec
uvcvideo
irqbypass
snd_hda_core
videobuf2_vmalloc
uvc
snd_hwdep
nls_ascii
dell_rbtn
videobuf2_memops
sha3_generic
rapl
snd_pcm
hid_sensor_als
nls_cp437
snd_timer
videobuf2_v4l2
dell_laptop
jitterentropy_rng
joydev
intel_cstate
hid_sensor_trigger
iTCO_wdt
dell_wmi
intel_pmc_bxt
libarc4
mei_pxp
mei_wdt
iwlwifi
mei_hdcp
videodev
ledtrig_audio
dell_smbios
hid_sensor_iio_common
snd
intel_uncore
iTCO_vendor_support
dell_wmi_sysman
intel_rapl_msr
pcspkr
vfat
processor_thermal_device_pci
dell_wmi_ddv
drbg
processor_thermal_device
dcdbas
industrialio_triggered_buffer
ansi_cprng
fat
cfg80211
dell_smm_hwmon
ecdh_generic
firmware_attributes_class
dell_wmi_descriptor
videobuf2_common
wmi_bmof
processor_thermal_wt_hint
kfifo_buf
soundcore
watchdog
mei_me
ecc
mc
processor_thermal_rfim
ucsi_acpi
industrialio
mei
processor_thermal_rapl
typec_ucsi
rfkill
intel_rapl_common
processor_thermal_wt_req
typec
processor_thermal_power_floor
igen6_edac
roles
intel_pmc_core
processor_thermal_mbox
apple_mfi_fastcharge
int3403_thermal
intel_vsec
int3400_thermal
int340x_thermal_zone
pmt_telemetry
acpi_thermal_rel
acpi_tad
intel_hid
pmt_class
sparse_keymap
acpi_pad
ac
serio_raw
hid_multitouch
evdev
msr
parport_pc
ppdev
lp
parport
loop
configfs
efi_pstore
nfnetlink
efivarfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
r8153_ecm
cdc_ether
usbnet
r8152
mii
hid_apple
usbhid
dm_crypt
dm_mod
hid_sensor_custom
hid_sensor_hub
intel_ishtp_hid
nvme
nvme_core
t10_pi
crc64_rocksoft_generic
crc64_rocksoft
crc_t10dif
crct10dif_generic
crc64
i915
nouveau
ahci
libahci
libata
scsi_mod
scsi_common
drm_gpuvm
mxm_wmi
drm_exec
gpu_sched
drm_buddy
i2c_algo_bit
crct10dif_pclmul
crct10dif_common
drm_display_helper
crc32_pclmul
hid_generic
crc32c_intel
cec
drm_ttm_helper
ghash_clmulni_intel
xhci_pci
rc_core
i2c_hid_acpi
ttm
sha512_ssse3
rtsx_pci_sdmmc
i2c_hid
xhci_hcd
sha512_generic
mmc_core
intel_lpss_pci
drm_kms_helper
hid
usbcore
sha256_ssse3
intel_ish_ipc
video
i2c_i801
intel_lpss
thunderbolt
drm
sha1_ssse3
psmouse
intel_ishtp
i2c_smbus
idma64

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Vincent Lefevre]

Control: tags -1 unreproducible - fixed-upstream
Control: close -1

On 2022-11-09 17:16:06 +0100, Vincent Lefevre wrote:
> I've tried a couple of cold boots, but this did not reproduce the
> issue. Perhaps the bug is rare with my laptop and more common with
> some other hardware.

AFAIK, I've never had the issue again.

On 2024-04-25 17:39:16 +, Debian Bug Tracking System wrote:
> > # remote status report for #1023192 (http://bugs.debian.org/1023192)
> > # Bug title: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: 
> > Reading Intel version command failed (-110)
> > #  * http://bugzilla.kernel.org/show_bug.cgi?id=215167
> > #  * remote status changed: NEW -> RESOLVED
> > #  * remote resolution changed: (?) -> OBSOLETE
> > #  * closed upstream
> > tags 1023192 + fixed-upstream

No, the bug was closed as OBSOLETE, with the following comment:

"This bug report has become unintelligible. 

Please file a new one if you're still affected.

Make sure you have verified kernel 6.6.13 or 6.7.1 with the latest firmware."

So I'm retagging and closing the bug (I was the reporter, and no other
users got affected).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1017720: nfs-common: No such file or directory

[Vincent Lefevre]

On 2024-04-09 14:09:43 +0200, Vincent Lefevre wrote:
> Some additional information: created only once, but data may be
> appended (on the creator's side, the file is created for writing,
> and data are written occasionally, and at some point, the file is
> closed). The error with "open" may occur even several hours after
> the last time data were written to the file.

This is actually reproducible with a read-only directory.
I've attached a Perl script to reproduce the issue, just
based on "stat".

The conditions seem to be:
  * The directory and the files need to be recent enough: I can't
reproduce the issue with an old directory, even if I add many
new files into it.
  * Concurrent "stat": with the attached script, the issue is
reproducible with 2 threads or more, but not with a single
thread.

Example of errors:

./dir-stat: can't stat . (x 2)
./dir-stat: can't stat 775 (x 148)
./dir-stat: can't stat 772 (x 1)
./dir-stat: can't stat 415 (x 1)
./dir-stat: can't stat 716 (x 1)
./dir-stat: can't stat 453 (x 1)
./dir-stat: can't stat 9 (x 1)
./dir-stat: can't stat 201 (x 1)
./dir-stat: can't stat 981 (x 1)
./dir-stat: can't stat 660 (x 1)
./dir-stat: can't stat 120 (x 1)
./dir-stat: can't stat 127 (x 1)
./dir-stat: can't stat 663 (x 1)

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
#!/usr/bin/env perl

# Create a directory with several hundreds of files, for instance with
#   mkdir test && cd test && touch `seq 999`
# then run this Perl script with the directory name in argument.

use strict;
use threads;

my $maxthreads = 2;
my $nthreads = 0;

@ARGV == 1 or die "Usage: $0 \n";
my $dir = $ARGV[0];
-d $dir or die "$0: $dir is not a directory\n";

sub thr ($) {
  my $file = $_[0];
  my $err = 0;
  until (stat "$dir/$file")
{
  $err++;
  sleep 0.25;
}
  warn "$0: can't stat $file (x $err)\n" if $err;
}

sub join_threads () {
  my @thr;
  sleep 0.25 until @thr = threads->list(threads::joinable);
  foreach my $thr (@thr)
{ $thr->join(); }
  $nthreads -= @thr;
}

opendir DIR, $dir or die "$0: opendir failed ($!)\n";
while (my $file = readdir DIR)
  {
$nthreads < $maxthreads or join_threads;
$nthreads++ < $maxthreads or die "$0: internal error\n";
threads->create(\, $file);
  }
closedir DIR or die "$0: closedir failed ($!)\n";
join_threads while $nthreads;

Bug#1017720: nfs-common: No such file or directory

[Vincent Lefevre]

On 2024-04-04 14:56:47 +0200, Vincent Lefevre wrote:
> On 2023-11-29 16:19:02 +0100, Vincent Lefevre wrote:
> > I have the same kind of issue at my lab with one of my programs:
> > a readdir lists the file, but then a stat sometimes gives a
> > "No such file or directory" error. Some clients are more affected
> > that others.
> 
> And sometimes, the "stat" succeeds as expected, but the "open" that
> follows gives a "No such file or directory" error.
> 
> Also note that in my case, the file under this filename is unique:
> it is created only once (never deleted then recreated).

Some additional information: created only once, but data may be
appended (on the creator's side, the file is created for writing,
and data are written occasionally, and at some point, the file is
closed). The error with "open" may occur even several hours after
the last time data were written to the file.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1017720: nfs-common: No such file or directory

[Vincent Lefevre]

On 2023-11-29 16:19:02 +0100, Vincent Lefevre wrote:
> I have the same kind of issue at my lab with one of my programs:
> a readdir lists the file, but then a stat sometimes gives a
> "No such file or directory" error. Some clients are more affected
> that others.

And sometimes, the "stat" succeeds as expected, but the "open" that
follows gives a "No such file or directory" error.

Also note that in my case, the file under this filename is unique:
it is created only once (never deleted then recreated).

> The clients are Debian 11.8 machines (also nfs-common 1:1.3.4-6;
> 5.10.0-26-amd64 kernel).

Still the same problem with a Debian 12.5 machine (nfs-common 1:2.6.2-4;
6.1.0-18-amd64 (6.1.76-1) kernel) on the client side.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1059936: Tracked down `behavior of -n is non-portable`

[Vincent Lefevre]

Control: reassign -1 klibc-utils
Control: forcemerge 1055694 -1

Note: Bug 1055694 was initially described as a different bug, but
it was retitled on January 9 (to match the change in coreutils),
so that it became the same bug as 1059936. Hence the merge.

On 2024-01-15 05:09:10 +, Alexander Huynh wrote:
> I believe the offending line is in the `klibc` package, after some tracing: 
> https://salsa.debian.org/kernel-team/klibc/-/blob/2078f63fe594652d42e19060b05aa03966fbd8a5/debian/initramfs-tools/hooks/klibc-utils#L31

Yes, this is mentioned in the merge request at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1055694#43

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1059936: initramfs-tools: update-initramfs yields "cp: warning: behavior of -n is non-portable and may change in future"

[Vincent Lefevre]

Package: initramfs-tools
Version: 0.142
Severity: normal

I get the following warnings with coreutils 9.4-3:

Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.5.0-5-amd64
[...]
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
cp: warning: behavior of -n is non-portable and may change in future; use 
--update=none instead
[...]

-- Package-specific info:
-- initramfs sizes
-rw-r--r-- 1 root root 62M 2023-12-19 03:08:02 /boot/initrd.img-6.1.0-16-amd64
-rw-r--r-- 1 root root 66M 2024-01-03 22:25:04 /boot/initrd.img-6.5.0-5-amd64
-- /proc/cmdline
BOOT_IMAGE=/vmlinuz-6.5.0-5-amd64 root=/dev/mapper/qaa--vg-root ro quiet

-- resume
RESUME=/dev/mapper/qaa--vg-swap_1
-- /proc/filesystems
ext3
ext2
ext4
fuseblk
vfat

-- lsmod
Module  Size  Used by
tls   151552  0
nfnetlink  20480  1
rfcomm102400  4
ctr12288  1
ccm20480  3
snd_seq_dummy  12288  0
snd_hrtimer12288  1
snd_seq   114688  7 snd_seq_dummy
snd_seq_device 16384  1 snd_seq
cmac   12288  3
algif_hash 12288  1
algif_skcipher 12288  1
af_alg 36864  6 algif_hash,algif_skcipher
snd_hda_codec_hdmi 90112  1
qrtr   57344  4
bnep   36864  2
binfmt_misc28672  1
dell_rbtn  20480  0
snd_sof_pci_intel_tgl12288  0
snd_sof_intel_hda_common   204800  1 snd_sof_pci_intel_tgl
soundwire_intel61440  1 snd_sof_intel_hda_common
soundwire_generic_allocation12288  1 soundwire_intel
snd_sof_intel_hda_mlink40960  2 soundwire_intel,snd_sof_intel_hda_common
soundwire_cadence  45056  1 soundwire_intel
snd_sof_intel_hda  24576  1 snd_sof_intel_hda_common
intel_uncore_frequency12288  0
snd_sof_pci24576  2 snd_sof_intel_hda_common,snd_sof_pci_intel_tgl
intel_uncore_frequency_common16384  1 intel_uncore_frequency
snd_sof_xtensa_dsp 16384  1 snd_sof_intel_hda_common
x86_pkg_temp_thermal16384  0
btusb  81920  0
snd_sof   356352  3 
snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_hda
intel_powerclamp   16384  0
btrtl  28672  1 btusb
snd_sof_utils  16384  1 snd_sof
coretemp   16384  0
snd_soc_hdac_hda   24576  1 snd_sof_intel_hda_common
btbcm  24576  1 btusb
snd_hda_ext_core   36864  4 
snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_sof_intel_hda_mlink,snd_sof_intel_hda
iwlmvm589824  0
snd_ctl_led24576  0
btintel57344  1 btusb
snd_soc_acpi_intel_match90112  2 
snd_sof_intel_hda_common,snd_sof_pci_intel_tgl
btmtk  12288  1 btusb
kvm_intel 413696  0
snd_hda_codec_realtek   192512  1
snd_soc_acpi   12288  2 
snd_soc_acpi_intel_match,snd_sof_intel_hda_common
snd_hda_codec_generic   114688  1 snd_hda_codec_realtek
bluetooth1134592  34 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
snd_soc_core  421888  4 
soundwire_intel,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hda
mac80211 1392640  1 iwlmvm
snd_compress   28672  1 snd_soc_core
kvm  1359872  1 kvm_intel
soundwire_bus 114688  3 
soundwire_intel,soundwire_generic_allocation,soundwire_cadence
libarc412288  1 mac80211
snd_hda_intel  61440  1
snd_intel_dspcfg   32768  3 snd_hda_intel,snd_sof,snd_sof_intel_hda_common
snd_intel_sdw_acpi 16384  2 snd_sof_intel_hda_common,snd_intel_dspcfg
sha3_generic   16384  1
dell_laptop32768  0
snd_hda_codec 225280  6 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_sof_intel_hda
jitterentropy_rng  20480  1
uvcvideo  147456  0
irqbypass  12288  1 kvm
ledtrig_audio  12288  3 snd_ctl_led,snd_hda_codec_generic,dell_laptop
iwlwifi   544768  1 iwlmvm
joydev 24576  0
hid_sensor_als 16384  1
videobuf2_vmalloc  20480  1 uvcvideo
rapl   20480  0
snd_hda_core  147456  9 
snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hda,snd_sof_intel_hda
uvc12288  1 uvcvideo
drbg   49152  1
dell_wmi   16384  0
hid_sensor_trigger 20480  2 hid_sensor_als
mei_hdcp   28672  0
mei_wdt12288  0
mei_pxp16384  0
nls_ascii  12288  1
intel_cstate   20480  0
snd_hwdep  20480  1 snd_hda_codec
videobuf2_memops   16384  1 videobuf2_vmalloc
intel_rapl_msr   

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

[Vincent Lefevre]

On 2023-12-19 14:32:31 +0100, Diederik de Haas wrote:
> If you manually create those links from the above "+Link:" lines,
> would that fix the issues?

I've added only the ga107 symlinks (since this is what is needed
for my machine) with

for i in acr nvdec sec2
do
  mkdir /usr/lib/firmware/nvidia/ga107/$i &&
  cd /usr/lib/firmware/nvidia/ga107/$i &&
  ln -s ../../ga102/$i/* .
done

and this fixes all the issues: the "Possible missing firmware" messages
(for ga107), the kernel crashes that were mentioned in the journalctl
output, and the black screen issue.

Thank you,

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1040910: Nvidia firmware missing on Testing

[Vincent Lefevre]

On 2023-07-12 11:30:22 +0200, Mauro Sacchetto wrote:
> Package: firmware-misc-nonfree
> Version: 20230515-3
> 
> My machine (with Cinnamon) has Nvidia GTX 670.
> On Testing, after the last upgrades I receive:
> 
> root@debian:~# update-initramfs -u
> update-initramfs: Generating /boot/initrd.img-6.3.0-1-amd64
> W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin 
> for module nouveau
[...]
> 
> Some drivers missing?

*firmware*, not drivers.

I reported

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058991

last night. My GPU (GA107GLM) is affected, and the kernel is unusable.

You can see whether the kernel on your machine attempts to load
such a firmware with

  journalctl -b -g 'firmware: failed to load'

(this is the command for the current boot).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

[Vincent Lefevre]

Another piece of information: this is a regression.

With the 6.1.0-16-amd64 kernel from stable, "journalctl -b -g ga107"
gives

Dec 19 04:57:07 qaa kernel: nouveau :01:00.0: NVIDIA GA107 (b77000a1)
Dec 19 04:57:07 qaa kernel: nouveau :01:00.0: firmware: failed to load 
nvidia/ga107/nvdec/scrubber.bin (-2)
Dec 19 04:57:07 qaa kernel: nouveau :01:00.0: firmware: failed to load 
nvidia/ga107/nvdec/scrubber.bin (-2)

and I don't have any issue with the machine.

With the 6.5.0-5-amd64 kernel, "journalctl -b -1 -g ga107" gives

Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: NVIDIA GA107 (b77000a1)
Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: firmware: failed to load 
nvidia/ga107/acr/ucode_ahesasc.bin (-2)
Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: firmware: failed to load 
nvidia/ga107/acr/ucode_ahesasc.bin (-2)
Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: firmware: direct-loading 
firmware nvidia/ga107/gr/NET_img.bin
Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: firmware: direct-loading 
firmware nvidia/ga107/gr/fecs_bl.bin
Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: firmware: direct-loading 
firmware nvidia/ga107/gr/fecs_sig.bin
Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: firmware: direct-loading 
firmware nvidia/ga107/gr/gpccs_bl.bin
Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: firmware: direct-loading 
firmware nvidia/ga107/gr/gpccs_sig.bin
Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: firmware: failed to load 
nvidia/ga107/sec2/sig.bin (-2)
Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: firmware: failed to load 
nvidia/ga107/sec2/sig.bin (-2)
Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: firmware: failed to load 
nvidia/ga107/nvdec/scrubber.bin (-2)
Dec 19 04:21:16 qaa kernel: nouveau :01:00.0: firmware: failed to load 
nvidia/ga107/nvdec/scrubber.bin (-2)

and I get the crashes, and as soon as I log out or after
"xset dpms force off" is run, the screen remains black.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

[Vincent Lefevre]

On 2023-12-19 04:32:02 +0100, Vincent Lefevre wrote:
> firmware-misc-nonfree triggers the following warnings:
> 
> update-initramfs: Generating /boot/initrd.img-6.5.0-5-amd64
[...]
> W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin 
> for module nouveau
[...]
> while https://forums.debian.net/viewtopic.php?t=155793 says that
> the solution is to install firmware-misc-nonfree!

I would add that even the section "Firmware missing from Debian" in
https://wiki.debian.org/Firmware does not apply because, for instance
for the above firmware, there's no "acr" directory in nvidia/ga107:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/nvidia/ga107
contains only a "gr" directory.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1058991: firmware-misc-nonfree: Possible missing firmware for module nouveau, kernel crash in nouveau

[Vincent Lefevre]

Package: firmware-misc-nonfree
Version: 20230625-1
Severity: grave
Justification: renders package unusable

firmware-misc-nonfree triggers the following warnings:

update-initramfs: Generating /boot/initrd.img-6.5.0-5-amd64
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153b-2.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-3.fw for module 
r8152
W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for module 
r8152
W: Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for module i915
W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin 
for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/hs_bl_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/desc.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/hs_bl_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/desc.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/hs_bl_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/desc.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/hs_bl_sig.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/sig.bin for module 
nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/image.bin for 
module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/desc.bin for 
module nouveau

while https://forums.debian.net/viewtopic.php?t=155793 says that
the solution is to install firmware-misc-nonfree!

And I get in the journalctl output:

Dec 19 04:02:54 qaa kernel: [ cut here ]
Dec 19 04:02:54 qaa kernel: nouveau :01:00.0: timeout
Dec 19 04:02:54 qaa kernel: WARNING: CPU: 7 PID: 1347 at 
drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1792 
gf100_gr_init_ctxctl_ext+0x555/0x570 [nouveau]
Dec 19 04:02:54 qaa kernel: Modules linked in: cmac algif_hash algif_skcipher 
af_alg snd_hda_codec_hdmi qrtr bnep binfmt_misc snd_sof_pci_intel_tgl 
snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation 
snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci 
snd_sof_xtensa_dsp intel_uncore_frequency snd_sof intel_uncore_frequency_common 
snd_sof_utils snd_soc_hdac_hda x86_pkg_temp_thermal snd_hda_ext_core 
intel_powerclamp snd_soc_acpi_intel_match btusb snd_soc_acpi coretemp 
snd_ctl_led btrtl snd_soc_core iwlmvm snd_hda_codec_realtek btbcm snd_compress 
btintel 

Bug#1055694: klibc-utils: Patch to fix cp warning

[Vincent Lefevre]

Hi,

On 2023-12-07 10:43:23 +0100, Mario Izquierdo (mariodebian) wrote:
> I found a small typo in initramfs-tools klibc-utils script:
> 
> # diff -ur klibc-utils /usr/share/initramfs-tools/hooks/klibc-utils
> --- klibc-utils   2023-12-07 10:35:52.738502916 +0100
> +++ /usr/share/initramfs-tools/hooks/klibc-utils  2023-12-07 
> 10:36:02.686695427 +0100
> @@ -27,7 +27,7 @@
>   ;;
>   *)
>   # Don't install commands that already exist in /bin or /sbin
> - if ! [ -e "${DESTDIR}/sbin/$command" ]; then
> + if ! [ -e "${DESTDIR}/bin/$command" ]; then
>   cp -pnL "$src" "${DESTDIR}/bin"
>   fi
>   ;;

But the code doesn't match the comment ("in /bin or /sbin").
What is actually expected?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1017720: nfs-common: No such file or directory

[Vincent Lefevre]

On 2022-08-19 13:16:47 +, Jason Breitman wrote:
> Package: nfs-common
> Version: 1:1.3.4-6
> Severity: important
> 
> Kernel: 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux
> 
> -- Description
> After updating and or creating new files on our file server via rsync, we 
> see many files report the error message below from NFSv4 clients since 
> upgrading from Debian 10.8 to Debian 11.4.
> Clearing the dentry cache resolves the issue right away.
> I am not sure that nfs-common is the package to blame, but listed it 
> based on the bug submission recommendations. 
> 
> -- Test
> ls -l /mnt/dir/someOtherDir/* | grep '?'
> 
> -- Error message
> ls: cannot access 'filename': No such file or directory
> -? ? ???? filename

I have the same kind of issue at my lab with one of my programs:
a readdir lists the file, but then a stat sometimes gives a
"No such file or directory" error. Some clients are more affected
that others.

The clients are Debian 11.8 machines (also nfs-common 1:1.3.4-6;
5.10.0-26-amd64 kernel).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1055931: apt ignores bullseye-backports

[Vincent Lefevre]

Hi Nis,

On 2023-11-16 17:31:13 +0100, Nis Martensen wrote:
> On 14.11.2023 15.17, Vincent Lefevre wrote:
> >> Checking for newer versions at madison and 
> >> https://ftp-master.debian.org/new.html
> >>
> >> Your version (6.1.55-1) of linux-image-6.1.0-13-amd64 appears to be out of 
> >> date.
> >> The following newer release(s) are available in the Debian archive:
> >>   bullseye-backports (backports-policy): 6.1.55+1~bpo11+1
> 
> > So I'm wondering where this information comes from.
> 
> I can find "6.1.55+1~bpo11+1" in https://ftp-master.debian.org/new.822
> so it must come from there.

Thanks. I had first looked at

  https://ftp-master.debian.org/new.html

(as output by reportbug), and it doesn't appear on this page
(I searched for both "linux" and "6.1.55"). Note that clicking
on "Click to toggle all/binary-NEW packages" does not make this
kernel appear either.

FYI, I later looked at https://ftp-master.debian.org/new.822 too
(as I could see it in the strace output), but only searched for
linux-image there, explaining that I didn't find it either (it
actually appears as linux-signed-amd64).

At the bottom of the new.html page:
"You can also look at the RFC822 version."

But why are the contents different? (linux-signed-amd64 appears
only in the RFC822 version.)

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1055945: linux-image-6.1.0-13-amd64: touchpad buttons sometimes stop working for several seconds/minutes

[Vincent Lefevre]

Package: src:linux
Version: 6.1.55-1
Severity: important

The touchpad buttons of my new laptop sometimes stop working for
several seconds or minutes (typically from 25" to 6'20"). The time
between two consecutive issues also varies and can be very short,
such as 30 seconds.

The device in question is: VEN_04F3:00 04F3:311C

This is visible even with evtest: when I click on any of the soft
buttons, I normally get an event like

Event: time 1698773368.142943, type 1 (EV_KEY), code 272 (BTN_LEFT), value 0

(note: always BTN_LEFT, even though this can be button 1, 2 or 3 at
a higher level). But when the problem occurs, I do not get such an
event.

Moving the mouse pointer is always possible, i.e. the issue concerns
only the buttons.

The only suspicious messages in the logs I could see are in the
X server logs

(EE) event14 - VEN_04F3:00 04F3:311C Touchpad: kernel bug: Touch jump detected 
and discarded.
See 
https://wayland.freedesktop.org/libinput/doc/1.22.1/touchpad-jumping-cursors.html
 for details

(nothing suspicious in the journalctl output). Note that libinput
stops emitting such messages after some number, so that it is not
possible to know whether this "Touch jump detected and discarded"
issue occurs at the same time as the button issue.

Additional info:

$ xinput list-props 13
Device 'VEN_04F3:00 04F3:311C Touchpad':
Device Enabled (190):   1
Coordinate Transformation Matrix (192): 1.00, 0.00, 0.00, 
0.00, 1.00, 0.00, 0.00, 0.00, 1.00
libinput Tapping Enabled (353): 0
libinput Tapping Enabled Default (354): 0
libinput Tapping Drag Enabled (355):1
libinput Tapping Drag Enabled Default (356):1
libinput Tapping Drag Lock Enabled (357):   0
libinput Tapping Drag Lock Enabled Default (358):   0
libinput Tapping Button Mapping Enabled (359):  1, 0
libinput Tapping Button Mapping Default (360):  1, 0
libinput Natural Scrolling Enabled (332):   0
libinput Natural Scrolling Enabled Default (333):   0
libinput Disable While Typing Enabled (361):1
libinput Disable While Typing Enabled Default (362):1
libinput Scroll Methods Available (334):1, 1, 0
libinput Scroll Method Enabled (335):   1, 0, 0
libinput Scroll Method Enabled Default (336):   1, 0, 0
libinput Click Methods Available (363): 1, 1
libinput Click Method Enabled (364):1, 0
libinput Click Method Enabled Default (365):1, 0
libinput Middle Emulation Enabled (366):0
libinput Middle Emulation Enabled Default (367):0
libinput Accel Speed (341): 0.00
libinput Accel Speed Default (342): 0.00
libinput Accel Profiles Available (343):1, 1
libinput Accel Profile Enabled (344):   1, 0
libinput Accel Profile Enabled Default (345):   1, 0
libinput Left Handed Enabled (346): 0
libinput Left Handed Enabled Default (347): 0
libinput Send Events Modes Available (313): 1, 1
libinput Send Events Mode Enabled (314):0, 0
libinput Send Events Mode Enabled Default (315):0, 0
Device Node (316):  "/dev/input/event14"
Device Product ID (317):1267, 12572
libinput Drag Lock Buttons (348):   
libinput Horizontal Scroll Enabled (349):   1
libinput Scrolling Pixel Distance (350):15
libinput Scrolling Pixel Distance Default (351):15
libinput High Resolution Wheel Scroll Enabled (352):1

The X input drivers:

$ dpkg -l | grep xserver-xorg-input
ii  xserver-xorg-input-all  1:7.7+23
 amd64X.Org X server -- input driver metapackage
ii  xserver-xorg-input-libinput 1.2.1-1+b1  
 amd64X.Org X server -- libinput input driver
ii  xserver-xorg-input-wacom1.1.0-1 
 amd64X.Org X server -- Wacom input driver


-- Package-specific info:
** Version:
Linux version 6.1.0-13-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP 
PREEMPT_DYNAMIC Debian 6.1.55-1 (2023-09-29)

** Command line:
BOOT_IMAGE=/vmlinuz-6.1.0-13-amd64 root=/dev/mapper/qaa--vg-root ro quiet

** Not tainted

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

** Model information
sys_vendor: Dell Inc.
product_name: Precision 5570
product_version: 
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: 1.18.0
board_vendor: Dell Inc.
board_name: 01Y4G1
board_version: A00

** Loaded modules:
netlink_diag
tls
ctr
ccm
snd_seq_dummy
snd_hrtimer
snd_seq
snd_seq_device
snd_hda_codec_hdmi
qrtr
bnep
binfmt_misc
nls_ascii
nls_cp437
vfat
fat
snd_sof_pci_intel_tgl

Bug#1055931: apt ignores bullseye-backports

[Vincent Lefevre]

Cc'ing Reportbug Maintainers.

On 2023-11-14 14:51:18 +0100, Vincent Lefevre wrote:
> Going back to what reportbug says, it still outputs
> 
> [...]
> Getting status for linux-image-6.1.0-13-amd64...
> Verifying package integrity...
> Checking for newer versions at madison and 
> https://ftp-master.debian.org/new.html
> 
> Your version (6.1.55-1) of linux-image-6.1.0-13-amd64 appears to be out of 
> date.
> The following newer release(s) are available in the Debian archive:
>   bullseye-backports (backports-policy): 6.1.55+1~bpo11+1
> Please try to verify if the bug you are about to report is already addressed 
> by these releases.  Do you still want to file a report [y|N|q|?]? 
> 
> So I've looked at https://ftp-master.debian.org/new.html with Firefox
> and "linux-image" doesn't appear anywhere. So the information comes
> from madison.
> 
> $ apt-cache madison linux-image-6.1.0-13-amd64
> linux-image-6.1.0-13-amd64 |   6.1.55-1 | https://ftp.debian.org/debian 
> stable/main amd64 Packages
> linux-signed-amd64 |   6.1.55+1 | https://ftp.debian.org/debian stable/main 
> Sources
> 
> No mentions of 6.1.55+1~bpo11+1, so this is more and more confusing.

After removing bullseye-backports from my sources lists and doing
"apt update", I've tried

  strace -o str.out -f -s 99 reportbug linux-image-6.1.0-13-amd64

but in the strace output, the string "bpo11" appears in 2 places only:

[...] manpages-de (<< 4.17.0-2~bpo11+1), manpages-fr (<< 4.17.0-2~bpo11+1) [...]

(thus unrelated to this issue) and in the message

193537 write(1, "  bullseye-backports (backports-policy): 6.1.55+1~bpo11+1\n", 
58) = 58

So I'm wondering where this information comes from.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1055931: apt ignores bullseye-backports

[Vincent Lefevre]

On 2023-11-14 13:45:21 +0100, Vincent Lefevre wrote:
> But "apt show -a linux-image-6.1.0-13-amd64" just gives the 6.1.55-1
> version (no 6.1.55+1~bpo11+1 version), and
> 
>   apt install -t bullseye-backports linux-image-6.1.0-13-amd64
> 
> also thinks that 6.1.55-1 is the version to be installed.

This may be specific to the kernel image. The following is rather
confusing:

$ apt install -s -t bullseye-backports 
linux-image-6.1.0-13-amd64/bullseye-backports
NOTE: This is only a simulation!
  apt needs root privileges for real execution.
  Keep also in mind that locking is deactivated,
  so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package linux-image-6.1.0-13-amd64 is not available, but is referred to by 
another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  linux-image-6.1.0-13-amd64-unsigned

E: Release 'bullseye-backports' for 'linux-image-6.1.0-13-amd64' was not found
$ apt install -s -t bullseye-backports 
linux-image-6.1.0-13-amd64-unsigned/bullseye-backports
NOTE: This is only a simulation!
  apt needs root privileges for real execution.
  Keep also in mind that locking is deactivated,
  so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package linux-image-6.1.0-13-amd64-unsigned is not available, but is referred 
to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  linux-image-6.1.0-13-amd64

E: Release 'bullseye-backports' for 'linux-image-6.1.0-13-amd64-unsigned' was 
not found

Going back to what reportbug says, it still outputs

[...]
Getting status for linux-image-6.1.0-13-amd64...
Verifying package integrity...
Checking for newer versions at madison and 
https://ftp-master.debian.org/new.html

Your version (6.1.55-1) of linux-image-6.1.0-13-amd64 appears to be out of date.
The following newer release(s) are available in the Debian archive:
  bullseye-backports (backports-policy): 6.1.55+1~bpo11+1
Please try to verify if the bug you are about to report is already addressed by 
these releases.  Do you still want to file a report [y|N|q|?]? 

So I've looked at https://ftp-master.debian.org/new.html with Firefox
and "linux-image" doesn't appear anywhere. So the information comes
from madison.

$ apt-cache madison linux-image-6.1.0-13-amd64
linux-image-6.1.0-13-amd64 |   6.1.55-1 | https://ftp.debian.org/debian 
stable/main amd64 Packages
linux-signed-amd64 |   6.1.55+1 | https://ftp.debian.org/debian stable/main 
Sources

No mentions of 6.1.55+1~bpo11+1, so this is more and more confusing.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#939079: nouveau: screen dimensions and resolution are wrong

[Vincent Lefevre]

Control: found -1 6.1.55-1

On 2019-09-01 04:11:15 +0200, Vincent Lefevre wrote:
> With the nouveau driver, I get:
> 
> $ xdpyinfo
> [...]
> screen #0:
>   dimensions:3200x1800 pixels (846x476 millimeters)
>   resolution:96x96 dots per inch
> [...]
> 
> which is wrong!

After installing Debian 12 (bookworm) on a new laptop, without the
nvidia driver, I can see the same issue.

screen #0:
  dimensions:3840x2400 pixels (1016x635 millimeters)
  resolution:96x96 dots per inch

For such a laptop, the dimensions and resulting resolution are
obviously wrong.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#970557: Closing this bug (BTS maintenance for src:linux bugs)

[Vincent Lefevre]

Hi,

On 2023-09-22 17:10:37 +0200, car...@debian.org wrote:
> This bug was filed for a very old kernel or the bug is old itself
> without resolution.
> 
> If you can reproduce it with
> 
> - the current version in unstable/testing
> - the latest kernel from backports
[...]

Just a note to say that the machine on which I got this crash
no longer exists.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1051844: initramfs-tools-core: the man pages have U+2010 HYPHEN characters instead of U+002D HYPHEN-MINUS

[Vincent Lefevre]

Package: initramfs-tools-core
Version: 0.142
Severity: minor

In the initramfs-tools(7) man page:

   Both /usr/share/initramfs‐tools/scripts and /etc/initramfs‐
   tools/scripts contains the following subdirectories.

where the dashes are U+2010 HYPHEN. This is incorrect and breaks
copy-paste. The character should be U+002D HYPHEN-MINUS.

Ditto in some other places in this man page and other man pages
from initramfs-tools-core.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'stable-security'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
merged-usr: no
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.4.0-4-amd64 (SMP w/12 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages initramfs-tools-core depends on:
ii  coreutils9.1-1
ii  cpio 2.13+dfsg-7.1
ii  e2fsprogs1.47.0-2+b1
ii  klibc-utils  2.0.13-1
ii  kmod 30+20230601-1
ii  logsave  1.47.0-2+b1
ii  udev 254.1-3

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.36.1-3.1
ii  zstd 1.5.5+dfsg2-1

Versions of packages initramfs-tools-core suggests:
ii  bash-completion  1:2.11-7

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1040178: Kernel modules will not build, missing asm/orc_header.h

[Vincent Lefevre]

On 2023-07-04 16:13:56 +0200, Andreas Beckmann wrote:
> This needs to be fixed before linux 6.3.0-2-* can migrate to testing,
> otherwise it will break dkms module building for everyone still having
> linux-headers-6.3.0-1-* installed (which is probably for the currently
> running kernel).

On one of my machines, the upgrade was fine, but this is because the
NVIDIA kernel module wasn't rebuilt for the 6.3.0-1 kernel (despite
I have autoinstall_all_kernels="1" in /etc/dkms/framework.conf). So
I suppose that this bug would affect the machine only if the NVIDIA
packages are upgraded.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#945140: linux-image-5.3.0-2-amd64: system occasionally hangs for several minutes

[Vincent Lefevre]

On 2019-11-20 19:06:25 +0100, Vincent Lefevre wrote:
> On 2019-11-20 12:52:09 +0100, Vincent Lefevre wrote:
> > Package: src:linux
> > Version: 5.3.9-2
> > Severity: important
> > 
> > Since yesterday, the system occasionally hangs for several minutes.
> > When this happens, I can observe in the journalctl output:
> > 
> > Nov 19 02:28:43 zira rtkit-daemon[752]: The canary thread is apparently 
> > starving. Taking action.
> [...]
> 
> Note sure whether this is a bug related to rtkit-daemon. I've found
> the possible culprit (which also explains that I had no problems
> before): xpdf takes several GB, even though the PDF file is rather
> simple (26 slides, no images...). The consequence is that the machine
> is swapping. I suspect a memory leak, possibly when the PDF file is
> reloaded (I've been writing slides, thus with many reloads...).

This was the probable cause (which I reported as bug 945188,
fixed in 2021).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#904770: about bugs in the nouveau driver

[Vincent Lefevre]

Note concerning these bugs in the nouveau driver: I haven't done
any report since a long time because I do not use the nouveau
driver any longer since upstream doesn't care to look at my bug
reports (even though some of them are completely reproducible)
and some of these bugs make nouveau unusable in practice. For
some time, I had an test machine that still had nouveau, but
this old machine is no longer there due to a disk failure.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Vincent Lefevre]

Hi Salvatore,

On 2022-11-05 09:40:20 +0100, Salvatore Bonaccorso wrote:
> Reading through the reports and
> https://bugzilla.kernel.org/show_bug.cgi?id=215167 I wonder if you can
> more easily reproduce your issue with doing cold boot of the machine
> or reboot it. I'm asking because it looks that for some people a
> workaround was to increase the sleeping time in btusb_qca_cmd_timeout().

I've tried a couple of cold boots, but this did not reproduce the
issue. Perhaps the bug is rare with my laptop and more common with
some other hardware.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Vincent Lefevre]

Control: tags -1 upstream

Hi Salvatore,

On 2022-11-01 08:05:28 +0100, Salvatore Bonaccorso wrote:
> What happens if you downgrade firmware-iwlwifi to 20210818-1?

Actually, I cannot reproduce the failure with the new kernel, even
with the current firmware-iwlwifi.

I don't know what happened, but there could be random failures with
recent kernels, as other users got exactly the same error:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859592

(bug reported in 2020-01) and

  https://bbs.archlinux.org/viewtopic.php?id=271459

(thread started in 2021-11).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Vincent Lefevre]

On 2022-10-31 13:09:31 +0100, Vincent Lefevre wrote:
> Package: src:linux
> Version: 6.0.5-1
> Severity: grave
> Justification: renders package unusable
> 
> (Setting to grave because Bluetooth is a major component.)
> 
> Bluetooth no longer works at all.

Bluetooth works again after downgrading the kernel to 6.0.3-1.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1023192: linux-image-6.0.0-2-amd64: Bluetooth no longer works: hci0: Reading Intel version command failed (-110)

[Vincent Lefevre]

Package: src:linux
Version: 6.0.5-1
Severity: grave
Justification: renders package unusable

(Setting to grave because Bluetooth is a major component.)

Bluetooth no longer works at all.

zira:~> journalctl -b -g bluetooth
Oct 31 12:55:16 zira kernel: Bluetooth: Core ver 2.22
Oct 31 12:55:16 zira kernel: NET: Registered PF_BLUETOOTH protocol family
Oct 31 12:55:16 zira kernel: Bluetooth: HCI device and connection manager 
initialized
Oct 31 12:55:16 zira kernel: Bluetooth: HCI socket layer initialized
Oct 31 12:55:16 zira kernel: Bluetooth: L2CAP socket layer initialized
Oct 31 12:55:16 zira kernel: Bluetooth: SCO socket layer initialized
Oct 31 12:55:17 zira systemd[1]: Starting Bluetooth service...
Oct 31 12:55:17 zira systemd[795]: ConfigurationDirectory 'bluetooth' already 
exists but the mode is different. (File system: 755 ConfigurationDirectoryMode: 
555)
Oct 31 12:55:17 zira bluetoothd[795]: Bluetooth daemon 5.65
Oct 31 12:55:17 zira systemd[1]: Started Bluetooth service.
Oct 31 12:55:17 zira systemd[1]: Reached target Bluetooth Support.
Oct 31 12:55:17 zira bluetoothd[795]: Bluetooth management interface 1.22 
initialized
Oct 31 12:55:17 zira dbus-daemon[801]: [system] Activating via systemd: service 
name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' 
requested by ':1.2' (uid=0 pid=795 comm="/usr/libexec/bluetooth/bluetoothd")
Oct 31 12:55:17 zira kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Oct 31 12:55:17 zira kernel: Bluetooth: BNEP filters: protocol multicast
Oct 31 12:55:17 zira kernel: Bluetooth: BNEP socket layer initialized
Oct 31 12:55:17 zira NetworkManager[950]:   [1667217317.6273] Loaded 
device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/1.40.2/libnm-device-plugin-bluetooth.so)
Oct 31 12:55:19 zira kernel: Bluetooth: hci0: Reading Intel version command 
failed (-110)
Oct 31 12:55:19 zira kernel: Bluetooth: hci0: command 0xfc05 tx timeout

With the 6.0.3-1 kernel version, I got:

Oct 31 11:17:59 zira kernel: Bluetooth: Core ver 2.22
Oct 31 11:17:59 zira kernel: NET: Registered PF_BLUETOOTH protocol family
Oct 31 11:17:59 zira kernel: Bluetooth: HCI device and connection manager 
initialized
Oct 31 11:17:59 zira kernel: Bluetooth: HCI socket layer initialized
Oct 31 11:17:59 zira kernel: Bluetooth: L2CAP socket layer initialized
Oct 31 11:17:59 zira kernel: Bluetooth: SCO socket layer initialized
Oct 31 11:17:59 zira kernel: Bluetooth: hci0: Legacy ROM 2.5 revision 8.0 build 
2 week 3 2013
Oct 31 11:17:59 zira kernel: bluetooth hci0: firmware: direct-loading firmware 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Oct 31 11:17:59 zira kernel: Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Oct 31 11:17:59 zira systemd[1]: Starting Bluetooth service...
[...]

So it appears that the 6.0.5-1 kernel version can't load the firmware.

-- Package-specific info:
** Version:
Linux version 6.0.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-12 (Debian 
12.2.0-7) 12.2.0, GNU ld (GNU Binutils for Debian) 2.39) #1 SMP PREEMPT_DYNAMIC 
Debian 6.0.5-1 (2022-10-28)

** Command line:
BOOT_IMAGE=/vmlinuz-6.0.0-2-amd64 root=/dev/mapper/crypt--lvm-root ro quiet 
systemd.swap=no

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

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

** Model information
sys_vendor: Hewlett-Packard
product_name: HP ZBook 15 G2
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version: 
bios_vendor: Hewlett-Packard
bios_version: M70 Ver. 01.08
board_vendor: Hewlett-Packard
board_name: 2253
board_version: KBC Version 03.10

** Loaded modules:
qrtr
ipt_REJECT
nf_reject_ipv4
xt_multiport
nft_compat
cpufreq_conservative
cpufreq_userspace
cpufreq_ondemand
cpufreq_powersave
bnep
nf_tables
libcrc32c
nfnetlink
nvidia_drm(POE)
drm_kms_helper
btusb
intel_rapl_msr
intel_rapl_common
iwlmvm
nvidia_modeset(POE)
btrtl
btbcm
btintel
btmtk
snd_ctl_led
mac80211
snd_hda_codec_realtek
bluetooth
snd_hda_codec_generic
snd_hda_codec_hdmi
ledtrig_audio
x86_pkg_temp_thermal
snd_hda_intel
intel_powerclamp
snd_intel_dspcfg
snd_intel_sdw_acpi
coretemp
libarc4
snd_hda_codec
uvcvideo
jitterentropy_rng
rapl
nvidia(POE)
iwlwifi
mei_wdt
snd_hda_core
intel_cstate
videobuf2_vmalloc
videobuf2_memops
binfmt_misc
mei_hdcp
snd_hwdep
videobuf2_v4l2
sha512_ssse3
intel_uncore
sha512_generic
cfg80211
videobuf2_common
snd_pcm
drbg
hp_wmi
videodev
joydev
ansi_cprng
platform_profile
pcspkr
snd_timer
iTCO_wdt
sparse_keymap
intel_pmc_bxt
serio_raw
mxm_wmi
ecdh_generic
iTCO_vendor_support
snd
wmi_bmof
at24
hp_accel
ipmi_devintf
watchdog
mc
rfkill
ecc
apple_mfi_fastcharge
evdev
lis3lv02d
ipmi_msghandler
soundcore
mei_me
tpm_infineon
ac
mei
sg
button
parport_pc
ppdev
drm
lp
parport
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
sd_mod
t10_pi

Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory

[Vincent Lefevre]

On 2022-07-04 10:00:04 +0200, Vincent Lefevre wrote:
> On 2022-07-04 15:01:13 +1000, Konomi Kitten wrote:
> > When update-initramfs runs I receive the following message:
> > 
> > depmod: WARNING: could not open modules.builtin.modinfo at
> > /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or
> > directory
> 
> I also got such a warning on two of my machines. It seems to
> be triggered when upgrading kmod (which provides depmod) to
> 30+20220630-1.

And downgrading to kmod 29-1+b1 makes this warning disappear.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory

[Vincent Lefevre]

On 2022-07-04 15:01:13 +1000, Konomi Kitten wrote:
> When update-initramfs runs I receive the following message:
> 
> depmod: WARNING: could not open modules.builtin.modinfo at
> /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or
> directory

I also got such a warning on two of my machines. It seems to
be triggered when upgrading kmod (which provides depmod) to
30+20220630-1.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#782323: linux-image-3.16.0-4-amd64: setting net.ipv6.conf.all.accept_ra to 0 has no effect, thus does not protect against SLAAC attacks

[Vincent Lefevre]

Hi,

On 2022-06-01 00:35:03 +0200, Diederik de Haas wrote:
> This bug was filed against kernel version 3.16 and the chance that
> an upstream kernel developer will devote time to it is ~ 0%, so I'm
> closing this bug.
> 
> If you can reproduce it with
> 
> - the current version in unstable/testing
> - the latest kernel from backports
> 
> please reopen the bug, see https://www.debian.org/Bugs/server-control
> for details.

I cannot test (at least at the moment), but after some search, I may
have an explanation of the issue (this would not be a kernel bug and
the switch to systemd may have fixed it). There's an upstream related
kernel bug

  https://bugzilla.kernel.org/show_bug.cgi?id=11655
  "/proc/sys/net/ipv6/conf/all/* controls don't work"

regarded as invalid, because the user was changing the settings
manually, and it is said that *.all.* variables must be set before
the device is created so that they are taken into account.

Now, in my case, I wasn't setting the variable manually, but via
the /etc/sysctl.conf file. So everything depends on when this file
is read. I've looked at old boot log files, and it was apparently
read via the /etc/init.d/procps script, which could be run rather
late, sometimes after the network was set up! So this was definitely
wrong.

Now, with systemd, there is documentation at

  https://www.freedesktop.org/software/systemd/man/sysctl.d.html

which says in particular:

  The settings configured with sysctl.d files will be applied early
  on boot. The network interface-specific options will also be
  applied individually for each network interface as it shows up in
  the system. (More specifically, net.ipv4.conf.*, net.ipv6.conf.*,
  net.ipv4.neigh.* and net.ipv6.neigh.*).

So, if I understand correctly, the settings are now read much earlier,
and normally before the network interfaces show up. Thus everything
should now be fine.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#1010209: linux-image-5.17.0-1-amd64: sr0 and sr1 I/O errors in the journalctl logs when running Wine

[Vincent Lefevre]

Package: src:linux
Version: 5.17.3-1
Severity: normal

While looking at the journalctl logs, I've noticed the following errors
that have been regularly occurring since March 1:

Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#7 FAILED Result: 
hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#7 Sense Key : Not Ready 
[current] 
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#7 Add. Sense: Medium not 
present - tray closed
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#7 CDB: Read(10) 28 00 00 
00 00 00 00 00 08 00
Apr 26 15:22:01 cventin kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) 
flags 0x80700 phys_seg 4 prio class 0
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#8 unaligned transfer
Apr 26 15:22:01 cventin kernel: I/O error, dev sr0, sector 0 op 0x0:(READ) 
flags 0x0 phys_seg 1 prio class 0
Apr 26 15:22:01 cventin kernel: Buffer I/O error on dev sr0, logical block 0, 
async page read
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#9 unaligned transfer
Apr 26 15:22:01 cventin kernel: I/O error, dev sr0, sector 1 op 0x0:(READ) 
flags 0x0 phys_seg 1 prio class 0
Apr 26 15:22:01 cventin kernel: Buffer I/O error on dev sr0, logical block 1, 
async page read
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#10 unaligned transfer
Apr 26 15:22:01 cventin kernel: I/O error, dev sr0, sector 2 op 0x0:(READ) 
flags 0x0 phys_seg 1 prio class 0
Apr 26 15:22:01 cventin kernel: Buffer I/O error on dev sr0, logical block 2, 
async page read
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#11 unaligned transfer
Apr 26 15:22:01 cventin kernel: I/O error, dev sr0, sector 3 op 0x0:(READ) 
flags 0x0 phys_seg 1 prio class 0
Apr 26 15:22:01 cventin kernel: Buffer I/O error on dev sr0, logical block 3, 
async page read
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#12 unaligned transfer
Apr 26 15:22:01 cventin kernel: I/O error, dev sr0, sector 4 op 0x0:(READ) 
flags 0x0 phys_seg 1 prio class 0
Apr 26 15:22:01 cventin kernel: Buffer I/O error on dev sr0, logical block 4, 
async page read
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#13 unaligned transfer
Apr 26 15:22:01 cventin kernel: I/O error, dev sr0, sector 5 op 0x0:(READ) 
flags 0x0 phys_seg 1 prio class 0
Apr 26 15:22:01 cventin kernel: Buffer I/O error on dev sr0, logical block 5, 
async page read
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#14 unaligned transfer
Apr 26 15:22:01 cventin kernel: I/O error, dev sr0, sector 6 op 0x0:(READ) 
flags 0x0 phys_seg 1 prio class 0
Apr 26 15:22:01 cventin kernel: Buffer I/O error on dev sr0, logical block 6, 
async page read
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#15 unaligned transfer
Apr 26 15:22:01 cventin kernel: I/O error, dev sr0, sector 7 op 0x0:(READ) 
flags 0x0 phys_seg 1 prio class 0
Apr 26 15:22:01 cventin kernel: Buffer I/O error on dev sr0, logical block 7, 
async page read
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#12 FAILED Result: 
hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#12 Sense Key : Not Ready 
[deferred] 
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#12 Add. Sense: Medium not 
present - tray closed
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#12 CDB: Read(10) 28 00 00 
00 00 00 00 00 08 00
Apr 26 15:22:02 cventin kernel: I/O error, dev sr1, sector 0 op 0x0:(READ) 
flags 0x80700 phys_seg 4 prio class 0
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#13 unaligned transfer
Apr 26 15:22:02 cventin kernel: Buffer I/O error on dev sr1, logical block 0, 
async page read
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#14 unaligned transfer
Apr 26 15:22:02 cventin kernel: Buffer I/O error on dev sr1, logical block 1, 
async page read
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#15 unaligned transfer
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#19 unaligned transfer
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#20 unaligned transfer
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#21 unaligned transfer
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#22 unaligned transfer
Apr 26 15:22:02 cventin kernel: sr 3:0:0:0: [sr1] tag#23 unaligned transfer

After a search for such errors on the web, I've eventually got

  
https://forum.endeavouros.com/t/dvd-drive-constantly-throw-errors-on-idle-state/6241/15

where it was found that this occurs when running Wine. Indeed,
I use Wine to test GNU MPFR, and I can reproduce the issue by
just running "wine blah" (where blah.exe doesn't exist).

-- Package-specific info:
** Version:
Linux version 5.17.0-1-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 
11.2.0-20) 11.2.0, GNU ld (GNU Binutils for Debian) 2.38) #1 SMP PREEMPT Debian 
5.17.3-1 (2022-04-18)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.17.0-1-amd64 
root=UUID=4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0 ro quiet

** Tainted: POE (12289)
 * proprietary 

Bug#1000870: nvidia: module verification failed: signature and/or required key missing - tainting kernel

[Vincent Lefevre]

Package: src:linux
Version: 5.15.5-1
Severity: normal

I can find in the journalctl logs:

  cventin kernel: nvidia: module verification failed: signature and/or required 
key missing - tainting kernel

It seems that this has occurred since the legacy nvidia driver is used
(*nvidia-legacy-390xx-*).

The same issue has been confirmed in Ubuntu:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805099

and according to the comments, this is a bug.

-- Package-specific info:
** Version:
Linux version 5.15.0-2-amd64 (debian-kernel@lists.debian.org) (gcc-11 (Debian 
11.2.0-12) 11.2.0, GNU ld (GNU Binutils for Debian) 2.37) #1 SMP Debian 
5.15.5-1 (2021-11-26)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-5.15.0-2-amd64 
root=UUID=4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0 ro quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

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

** Model information
sys_vendor: Dell Inc.
product_name: Precision Tower 7810
product_version: 01
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: A07
board_vendor: Dell Inc.
board_name: 0GWHMW
board_version: A00

** Loaded modules:
nvidia_uvm(POE)
snd_seq_dummy
snd_hrtimer
snd_seq
snd_seq_device
cpufreq_ondemand
cpufreq_conservative
cpufreq_userspace
cpufreq_powersave
intel_rapl_msr
intel_rapl_common
sb_edac
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
kvm
irqbypass
ghash_clmulni_intel
aesni_intel
crypto_simd
cryptd
dell_smbios
snd_hda_codec_realtek
dell_wmi_descriptor
rfkill
mei_wdt
video
snd_hda_codec_generic
dcdbas
rapl
snd_hda_codec_hdmi
ledtrig_audio
intel_cstate
dell_smm_hwmon
snd_hda_intel
snd_intel_dspcfg
snd_intel_sdw_acpi
intel_uncore
snd_hda_codec
iTCO_wdt
intel_wmi_thunderbolt
intel_pmc_bxt
pcspkr
iTCO_vendor_support
watchdog
snd_hda_core
snd_hwdep
snd_pcm
snd_timer
sg
snd
mei_me
mei
soundcore
evdev
nvidia_drm(POE)
drm_kms_helper
cec
rc_core
nvidia_modeset(POE)
nvidia(POE)
binfmt_misc
ipmi_devintf
ipmi_msghandler
parport_pc
drm
ppdev
lp
parport
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
sd_mod
t10_pi
crc_t10dif
crct10dif_generic
hid_generic
usbhid
hid
sr_mod
cdrom
ahci
xhci_pci
libahci
ata_generic
ehci_pci
crct10dif_pclmul
xhci_hcd
crct10dif_common
libata
crc32_pclmul
ehci_hcd
crc32c_intel
e1000e
usbcore
scsi_mod
i2c_i801
lpc_ich
ptp
i2c_smbus
pps_core
usb_common
scsi_common
wmi
button

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 
DMI2 [8086:2f00] (rev 02)
Subsystem: Dell Xeon E7 v3/Xeon E5 v3/Core i7 DMI2 [1028:0618]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI 
Express Root Port 1 [8086:2f02] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:01.1 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI 
Express Root Port 1 [8086:2f03] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:02.0 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI 
Express Root Port 2 [8086:2f04] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.0 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI 
Express Root Port 3 [8086:2f08] (rev 02) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.1 PCI bridge [0604]: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI 
Express Root Port 3 [8086:2f09] (rev 02) (prog-if 

Bug#757356: Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c

[Vincent Lefevre]

On 2021-07-21 18:28:44 -0400, Daniel Lin wrote:
> Yes, I haven't used a machine with hid_apple in many years, but the
> patch sign-off is OK with me.

Thanks. For the reference of my patch submission a few days ago:

  https://www.spinics.net/lists/linux-input/msg74111.html

  https://lore.kernel.org/patchwork/project/lkml/list/?series=509091

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#757356: Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c

[Vincent Lefevre]

On 2021-06-02 17:24:38 +0200, Salvatore Bonaccorso wrote:
> Hi Vincent,
> 
> On Wed, May 26, 2021 at 12:02:12PM +0200, Vincent Lefevre wrote:
[...]
> > I forgot that there was
> > 
> >   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757356#35
> > 
> > from Daniel Lin, with a patch, in 2017. I've looked at this patch
> > (but have not tried it), and it adds an additional EV_MSC event
> > when hidinput_apple_event() has to generate an EV_KEY event. So
> > I confirm that should solve this issue and I'm adding the patch
> > tag (I don't know whether the patch needs an update, though).
> 
> Can you, time permitting, starting from there (and needed refreshes)
> try to confirm if the patch solves the issue on top of 5.10.40?

I could build and test the patched kernel, and I confirm that the
new patch at

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757356#75

solves the issue for me.

> If so, next step would be to propose the change/report the bug at
> least, to upstream, get_maintainers.pl would suggest to report it
> to:
> 
> Jiri Kosina  (maintainer:HID CORE LAYER)
> Benjamin Tissoires  (maintainer:HID CORE LAYER)
> linux-in...@vger.kernel.org (open list:HID CORE LAYER)
> linux-ker...@vger.kernel.org (open list)

Since Daniel Lin (Cc'ed for any comment) is the author of the
original patch, I suppose that the patch should have:

Co-developed-by: Daniel Lin 
Signed-off-by: Daniel Lin 
Co-developed-by: Vincent Lefevre 
Signed-off-by: Vincent Lefevre 

as described at
  https://www.kernel.org/doc/html/latest/process/submitting-patches.html

if this is OK for him.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#757356: Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c

[Vincent Lefevre]

On 2021-06-02 17:24:38 +0200, Salvatore Bonaccorso wrote:
> Can you, time permitting, starting from there (and needed refreshes)
> try to confirm if the patch solves the issue on top of 5.10.40?

First, the patch did not apply correctly on top of 5.10.46 (currently
in unstable). So I've updated it and attached this new version. (I'm not
sure that the change concerning REL_HWHEEL is needed, but in any case,
it may be safer and it shouldn't hurt, thanks to the "type == EV_KEY"
test.)

Then I couldn't test it because the kernel build fails:

[...]
  CC  fs/locks.o
  CC  fs/binfmt_script.o
  CC  fs/binfmt_elf.o
  CC  fs/compat_binfmt_elf.o
  CC  fs/posix_acl.o
  CC  fs/coredump.o
  CC  fs/drop_caches.o
  CC  fs/fhandle.o
  CC  fs/dcookies.o
  CC [M]  fs/binfmt_misc.o
  CC [M]  fs/mbcache.o
  AR  fs/built-in.a
make[2]: *** [debian/rules:7: build-arch] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
make[1]: *** [scripts/Makefile.package:77: deb-pkg] Error 2
make: *** [Makefile:1573: deb-pkg] Error 2

I don't know whether this matters, but the /usr/src/linux-source-5.10.tar.xz
archive is not extracted properly by tar, with directories having
incorrect timestamps. I've reported a bug for this:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991275

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
--- a/drivers/hid/hid-apple.c   2021-06-23 12:42:55.0 +
+++ b/drivers/hid/hid-apple.c   2021-07-19 13:15:39.478215724 +
@@ -187,6 +187,15 @@
return NULL;
 }
 
+static void input_event_with_scancode(struct input_dev *input,
+   __u8 type, __u16 code, unsigned int hid, __s32 value)
+{
+   if (type == EV_KEY &&
+   (!test_bit(code, input->key)) == value)
+   input_event(input, EV_MSC, MSC_SCAN, hid);
+   input_event(input, type, code, value);
+}
+
 static int hidinput_apple_event(struct hid_device *hid, struct input_dev 
*input,
struct hid_usage *usage, __s32 value)
 {
@@ -199,7 +208,8 @@
 
if (usage->code == fn_keycode) {
asc->fn_on = !!value;
-   input_event(input, usage->type, KEY_FN, value);
+   input_event_with_scancode(input, usage->type, KEY_FN,
+   usage->hid, value);
return 1;
}
 
@@ -240,7 +250,8 @@
code = do_translate ? trans->to : trans->from;
}
 
-   input_event(input, usage->type, code, value);
+   input_event_with_scancode(input, usage->type, code,
+   usage->hid, value);
return 1;
}
 
@@ -258,8 +269,8 @@
clear_bit(usage->code,
asc->pressed_numlock);
 
-   input_event(input, usage->type, trans->to,
-   value);
+   input_event_with_scancode(input, usage->type,
+   trans->to, usage->hid, value);
}
 
return 1;
@@ -270,7 +281,8 @@
if (hid->country == HID_COUNTRY_INTERNATIONAL_ISO) {
trans = apple_find_translation(apple_iso_keyboard, 
usage->code);
if (trans) {
-   input_event(input, usage->type, trans->to, 
value);
+   input_event_with_scancode(input, usage->type,
+   trans->to, usage->hid, value);
return 1;
}
}
@@ -279,7 +291,8 @@
if (swap_opt_cmd) {
trans = apple_find_translation(swapped_option_cmd_keys, 
usage->code);
if (trans) {
-   input_event(input, usage->type, trans->to, value);
+   input_event_with_scancode(input, usage->type,
+   trans->to, usage->hid, value);
return 1;
}
}
@@ -287,7 +300,8 @@
if (swap_fn_leftctrl) {
trans = apple_find_translation(swapped_fn_leftctrl_keys, 
usage->code);
if (trans) {
-   input_event(input, usage->type, trans->to, value);
+   input_event_with_scancode(input, usage->type,
+   trans->to, usage->hid, value);
return 1;
}
}
@@ -306,8 +320,8 @@
 
if ((asc->quirks & APPLE_INVERT_HWHEEL) &&
usage->code == REL_HWHEEL) {
-   

Bug#757356: Apple keyboard: Scan code event (EV_MSC) not generated when the EV_KEY event is generated by hid-apple.c

[Vincent Lefevre]

Control: retitle -1 Apple keyboard: Scan code event (EV_MSC) not generated when 
the EV_KEY event is generated by hid-apple.c
Control: tags -1 patch

On 2021-05-26 10:39:11 +0200, Vincent Lefevre wrote:
> And the cursor keys. Actually, all the keys corresponding to
> 
> static const struct applespi_key_translation applespi_fn_codes[] = {
> { KEY_BACKSPACE, KEY_DELETE },
> { KEY_ENTER,KEY_INSERT },
> { KEY_F1,   KEY_BRIGHTNESSDOWN, APPLE_FLAG_FKEY },
> { KEY_F2,   KEY_BRIGHTNESSUP,   APPLE_FLAG_FKEY },
> { KEY_F3,   KEY_SCALE,  APPLE_FLAG_FKEY },
> { KEY_F4,   KEY_DASHBOARD,  APPLE_FLAG_FKEY },
> { KEY_F5,   KEY_KBDILLUMDOWN,   APPLE_FLAG_FKEY },
> { KEY_F6,   KEY_KBDILLUMUP, APPLE_FLAG_FKEY },
> { KEY_F7,   KEY_PREVIOUSSONG,   APPLE_FLAG_FKEY },
> { KEY_F8,   KEY_PLAYPAUSE,  APPLE_FLAG_FKEY },
> { KEY_F9,   KEY_NEXTSONG,   APPLE_FLAG_FKEY },
> { KEY_F10,  KEY_MUTE,   APPLE_FLAG_FKEY },
> { KEY_F11,  KEY_VOLUMEDOWN, APPLE_FLAG_FKEY },
> { KEY_F12,  KEY_VOLUMEUP,   APPLE_FLAG_FKEY },
> { KEY_RIGHT,KEY_END },
> { KEY_LEFT, KEY_HOME },
> { KEY_DOWN, KEY_PAGEDOWN },
> { KEY_UP,   KEY_PAGEUP },
> { }
> };
> 
> in drivers/input/keyboard/applespi.c.
> 
> Just in case, in /etc/modprobe.d/hid_apple.conf, I have
> 
> options hid_apple fnmode=2
> options hid_apple iso_layout=0

But since I'm using hid_apple, I should have taken
drivers/hid/hid-apple.c, which has the same kind of code:

static const struct apple_key_translation apple_fn_keys[] = {
{ KEY_BACKSPACE, KEY_DELETE },
{ KEY_ENTER,KEY_INSERT },
{ KEY_F1,   KEY_BRIGHTNESSDOWN, APPLE_FLAG_FKEY },
{ KEY_F2,   KEY_BRIGHTNESSUP,   APPLE_FLAG_FKEY },
{ KEY_F3,   KEY_SCALE,  APPLE_FLAG_FKEY },
{ KEY_F4,   KEY_DASHBOARD,  APPLE_FLAG_FKEY },
{ KEY_F5,   KEY_KBDILLUMDOWN,   APPLE_FLAG_FKEY },
{ KEY_F6,   KEY_KBDILLUMUP, APPLE_FLAG_FKEY },
{ KEY_F7,   KEY_PREVIOUSSONG,   APPLE_FLAG_FKEY },
{ KEY_F8,   KEY_PLAYPAUSE,  APPLE_FLAG_FKEY },
{ KEY_F9,   KEY_NEXTSONG,   APPLE_FLAG_FKEY },
{ KEY_F10,  KEY_MUTE,   APPLE_FLAG_FKEY },
{ KEY_F11,  KEY_VOLUMEDOWN, APPLE_FLAG_FKEY },
{ KEY_F12,  KEY_VOLUMEUP,   APPLE_FLAG_FKEY },
{ KEY_UP,   KEY_PAGEUP },
{ KEY_DOWN, KEY_PAGEDOWN },
{ KEY_LEFT, KEY_HOME },
{ KEY_RIGHT,KEY_END },
{ }
};

In the conditions from hidinput_apple_event(), the only ones that
should match according to my settings are

if (usage->code == fn_keycode) {

and

if (fnmode) {

and these are the keys (when trans is true, for fnmode) for which I do
not get a scan code event. Said otherwise, if hidinput_apple_event()
returns 1, I do not get a scan code event. There are input_event()
calls, but I suppose that they will just generate an EV_KEY event,
and EV_MSC is the one that is missing.

Note: in hid-apple.c, apple_event() calls hidinput_apple_event(), and
one has

static struct hid_driver apple_driver = {
[...]
.event = apple_event,
[...]
};
module_hid_driver(apple_driver);

I forgot that there was

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757356#35

from Daniel Lin, with a patch, in 2017. I've looked at this patch
(but have not tried it), and it adds an additional EV_MSC event
when hidinput_apple_event() has to generate an EV_KEY event. So
I confirm that should solve this issue and I'm adding the patch
tag (I don't know whether the patch needs an update, though).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#757356: Scan code event not generated for some keys of the Apple keyboard: those in applespi_fn_codes

[Vincent Lefevre]

Control: retitle -1 Scan code event not generated for some keys of the Apple 
keyboard: those in applespi_fn_codes

On 2021-05-26 09:52:16 +0200, Vincent Lefevre wrote:
> No MSC_SCAN line for F1 to F12.
[...]
> Same issue for the Enter and Backspace keys:
[...]

And the cursor keys. Actually, all the keys corresponding to

static const struct applespi_key_translation applespi_fn_codes[] = {
{ KEY_BACKSPACE, KEY_DELETE },
{ KEY_ENTER,KEY_INSERT },
{ KEY_F1,   KEY_BRIGHTNESSDOWN, APPLE_FLAG_FKEY },
{ KEY_F2,   KEY_BRIGHTNESSUP,   APPLE_FLAG_FKEY },
{ KEY_F3,   KEY_SCALE,  APPLE_FLAG_FKEY },
{ KEY_F4,   KEY_DASHBOARD,  APPLE_FLAG_FKEY },
{ KEY_F5,   KEY_KBDILLUMDOWN,   APPLE_FLAG_FKEY },
{ KEY_F6,   KEY_KBDILLUMUP, APPLE_FLAG_FKEY },
{ KEY_F7,   KEY_PREVIOUSSONG,   APPLE_FLAG_FKEY },
{ KEY_F8,   KEY_PLAYPAUSE,  APPLE_FLAG_FKEY },
{ KEY_F9,   KEY_NEXTSONG,   APPLE_FLAG_FKEY },
{ KEY_F10,  KEY_MUTE,   APPLE_FLAG_FKEY },
{ KEY_F11,  KEY_VOLUMEDOWN, APPLE_FLAG_FKEY },
{ KEY_F12,  KEY_VOLUMEUP,   APPLE_FLAG_FKEY },
{ KEY_RIGHT,KEY_END },
{ KEY_LEFT, KEY_HOME },
{ KEY_DOWN, KEY_PAGEDOWN },
{ KEY_UP,   KEY_PAGEUP },
{ }
};

in drivers/input/keyboard/applespi.c.

Just in case, in /etc/modprobe.d/hid_apple.conf, I have

options hid_apple fnmode=2
options hid_apple iso_layout=0

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#757356: Scan codes still not generated for F1 to F12, Enter and Backspace

[Vincent Lefevre]

Control: reopen -1
Control: found -1 5.10.38-1

On 2021-04-28 18:39:44 +0200, j...@debian.org wrote:
> This bug was filed for a very old kernel. If you can reproduce it with
> - the current version in unstable/testing
> - the latest kernel from buster.backports
> please reopen the bug, see https://www.debian.org/Bugs/server-control

Bug still reproducible with linux-image-5.10.0-7-amd64 5.10.38-1.

# evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:  AT Translated Set 2 keyboard
/dev/input/event1:  Video Bus
/dev/input/event2:  PS/2 Generic Mouse
/dev/input/event3:  Apple, Inc Apple Keyboard
/dev/input/event4:  Apple, Inc Apple Keyboard
/dev/input/event5:  PixArt USB Optical Mouse
[...]
Select the device event number [0-24]: 3
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x5ac product 0x221 version 0x111
Input device name: "Apple, Inc Apple Keyboard"
[...]
Testing ... (interrupt to exit)
Event: time 1622014586.354418, type 1 (EV_KEY), code 28 (KEY_ENTER), value 0
Event: time 1622014586.354418, -- SYN_REPORT 
Event: time 1622014588.314431, type 1 (EV_KEY), code 59 (KEY_F1), value 1
Event: time 1622014588.314431, -- SYN_REPORT 
éEvent: time 1622014588.402405, type 1 (EV_KEY), code 59 (KEY_F1), value 0
Event: time 1622014588.402405, -- SYN_REPORT 
Event: time 1622014591.010396, type 1 (EV_KEY), code 60 (KEY_F2), value 1
Event: time 1622014591.010396, -- SYN_REPORT 
èEvent: time 1622014591.130400, type 1 (EV_KEY), code 60 (KEY_F2), value 0
Event: time 1622014591.130400, -- SYN_REPORT 
Event: time 1622014593.266402, type 1 (EV_KEY), code 61 (KEY_F3), value 1
Event: time 1622014593.266402, -- SYN_REPORT 
êEvent: time 1622014593.418425, type 1 (EV_KEY), code 61 (KEY_F3), value 0
Event: time 1622014593.418425, -- SYN_REPORT 
Event: time 1622014594.258377, type 1 (EV_KEY), code 62 (KEY_F4), value 1
Event: time 1622014594.258377, -- SYN_REPORT 
ëEvent: time 1622014594.410386, type 1 (EV_KEY), code 62 (KEY_F4), value 0
Event: time 1622014594.410386, -- SYN_REPORT 
Event: time 1622014595.186424, type 1 (EV_KEY), code 63 (KEY_F5), value 1
Event: time 1622014595.186424, -- SYN_REPORT 
âEvent: time 1622014595.306297, type 1 (EV_KEY), code 63 (KEY_F5), value 0
Event: time 1622014595.306297, -- SYN_REPORT 
Event: time 1622014595.898361, type 1 (EV_KEY), code 64 (KEY_F6), value 1
Event: time 1622014595.898361, -- SYN_REPORT 
îEvent: time 1622014596.018362, type 1 (EV_KEY), code 64 (KEY_F6), value 0
Event: time 1622014596.018362, -- SYN_REPORT 
Event: time 1622014596.546417, type 1 (EV_KEY), code 65 (KEY_F7), value 1
Event: time 1622014596.546417, -- SYN_REPORT 
ôEvent: time 1622014596.666411, type 1 (EV_KEY), code 65 (KEY_F7), value 0
Event: time 1622014596.666411, -- SYN_REPORT 
Event: time 1622014597.130399, type 1 (EV_KEY), code 66 (KEY_F8), value 1
Event: time 1622014597.130399, -- SYN_REPORT 
ûEvent: time 1622014597.234394, type 1 (EV_KEY), code 66 (KEY_F8), value 0
Event: time 1622014597.234394, -- SYN_REPORT 
Event: time 1622014597.714254, type 1 (EV_KEY), code 67 (KEY_F9), value 1
Event: time 1622014597.714254, -- SYN_REPORT 
àEvent: time 1622014597.842254, type 1 (EV_KEY), code 67 (KEY_F9), value 0
Event: time 1622014597.842254, -- SYN_REPORT 
Event: time 1622014598.354389, type 1 (EV_KEY), code 68 (KEY_F10), value 1
Event: time 1622014598.354389, -- SYN_REPORT 
ùEvent: time 1622014598.458419, type 1 (EV_KEY), code 68 (KEY_F10), value 0
Event: time 1622014598.458419, -- SYN_REPORT 
Event: time 1622014598.962403, type 1 (EV_KEY), code 87 (KEY_F11), value 1
Event: time 1622014598.962403, -- SYN_REPORT 
ïEvent: time 1622014599.058405, type 1 (EV_KEY), code 87 (KEY_F11), value 0
Event: time 1622014599.058405, -- SYN_REPORT 
Event: time 1622014599.826412, type 1 (EV_KEY), code 88 (KEY_F12), value 1
Event: time 1622014599.826412, -- SYN_REPORT 
çEvent: time 1622014599.938401, type 1 (EV_KEY), code 88 (KEY_F12), value 0
Event: time 1622014599.938401, -- SYN_REPORT 
Event: time 1622014601.242407, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70068
Event: time 1622014601.242407, type 1 (EV_KEY), code 110 (KEY_INSERT), value 1
Event: time 1622014601.242407, -- SYN_REPORT 
^[[2~Event: time 1622014601.378309, type 4 (EV_MSC), code 4 (MSC_SCAN), value 
70068
Event: time 1622014601.378309, type 1 (EV_KEY), code 110 

Bug#988539: linux-image-5.10.0-6-amd64: umount of a USB stick froze the system

[Vincent Lefevre]

Package: src:linux
Version: 5.10.28-1
Severity: important

I copied a big file (> 3 GB) on a USB stick and did "umount" on the
device, and after a few dozens of seconds, the system got completely
frozen (the clock stopped, I couldn't move the mouse pointer, and
the keyboard wasn't reacting either) and the fan was making a lot of
noise. I had to switch off the machine.

After rebooting, I could see in the logs:

May 15 10:41:45 zira kernel: scsi 6:0:0:0: Direct-Access Generic  Flash 
Disk   8.07 PQ: 0 ANSI: 4
May 15 10:41:45 zira kernel: sd 6:0:0:0: Attached scsi generic sg2 type 0
May 15 10:41:45 zira kernel: sd 6:0:0:0: [sdb] 3072 512-byte logical 
blocks: (15.7 GB/14.6 GiB)
May 15 10:41:45 zira kernel: sd 6:0:0:0: [sdb] Write Protect is off
May 15 10:41:45 zira kernel: sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
May 15 10:41:45 zira kernel: sd 6:0:0:0: [sdb] Write cache: disabled, read 
cache: enabled, doesn't support DPO or FUA
May 15 10:41:45 zira kernel:  sdb: sdb1
May 15 10:41:45 zira kernel: sd 6:0:0:0: [sdb] Attached SCSI removable disk
May 15 10:42:12 zira kernel: FAT-fs (sdb1): Volume was not properly unmounted. 
Some data may be corrupt. Please run fsck.

This was *before* I had mounted the volume and done the copy.

I don't know wheter whether the corrupt FS was related to the freeze,
but this shouldn't be a reason to freeze the system.

-- Package-specific info:
** Version:
Linux version 5.10.0-6-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.28-1 (2021-04-09)

** Command line:
BOOT_IMAGE=/vmlinuz-5.10.0-6-amd64 root=/dev/mapper/zira--vg-root ro quiet 
systemd.swap=no

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

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

** Model information
sys_vendor: Hewlett-Packard
product_name: HP ZBook 15 G2
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version: 
bios_vendor: Hewlett-Packard
bios_version: M70 Ver. 01.08
board_vendor: Hewlett-Packard
board_name: 2253
board_version: KBC Version 03.10

** Loaded modules:
nls_ascii
nls_cp437
vfat
fat
uas
usb_storage
ctr
ccm
rfcomm
cmac
algif_hash
algif_skcipher
af_alg
bnep
cpufreq_conservative
cpufreq_ondemand
cpufreq_userspace
cpufreq_powersave
intel_rapl_msr
intel_rapl_common
x86_pkg_temp_thermal
intel_powerclamp
snd_hda_codec_realtek
btusb
binfmt_misc
coretemp
btrtl
iwlmvm
btbcm
snd_hda_codec_generic
btintel
mei_wdt
snd_hda_codec_hdmi
rapl
ledtrig_audio
mac80211
bluetooth
snd_hda_intel
snd_intel_dspcfg
soundwire_intel
soundwire_generic_allocation
snd_soc_core
libarc4
snd_compress
soundwire_cadence
intel_cstate
snd_hda_codec
jitterentropy_rng
iwlwifi
uvcvideo
videobuf2_vmalloc
snd_hda_core
videobuf2_memops
videobuf2_v4l2
snd_hwdep
soundwire_bus
videobuf2_common
drbg
snd_pcm
cfg80211
videodev
ansi_cprng
intel_uncore
joydev
mc
snd_timer
iTCO_wdt
hp_wmi
intel_pmc_bxt
mei_me
tpm_infineon
serio_raw
wmi_bmof
sparse_keymap
ecdh_generic
iTCO_vendor_support
snd
at24
ecc
pcspkr
sg
watchdog
rfkill
mxm_wmi
mei
soundcore
evdev
tpm_tis
tpm_tis_core
tpm
hp_accel
lis3lv02d
rng_core
hp_wireless
ac
button
nvidia_drm(POE)
drm_kms_helper
cec
nvidia_modeset(POE)
nvidia(POE)
ipmi_devintf
ipmi_msghandler
parport_pc
ppdev
lp
drm
parport
fuse
configfs
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
sd_mod
sr_mod
t10_pi
cdrom
crc_t10dif
crct10dif_generic
crct10dif_pclmul
crct10dif_common
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
rtsx_pci_sdmmc
mmc_core
ahci
libahci
aesni_intel
xhci_pci
libaes
crypto_simd
libata
xhci_hcd
ehci_pci
cryptd
glue_helper
ehci_hcd
e1000e
psmouse
scsi_mod
usbcore
rtsx_pci
i2c_i801
lpc_ich
i2c_smbus
ptp
pps_core
usb_common
battery
video
wmi

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor DRAM Controller [8086:0c04] (rev 06)
Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core 
Processor DRAM Controller [103c:2253]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: ie31200_edac

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
Family USB xHCI [8086:8c31] (rev 04) 

Bug#809149: Closing this bug (BTS maintenance for src:linux bugs)

[Vincent Lefevre]

On 2021-05-09 07:21:07 -0700, car...@debian.org wrote:
> This bug was filed for a very old kernel or the bug is old itself
> without resolution.

I confirm that the bug is obsolete. (I'm not sure I could ever
reproduce it.)

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#792778: nouveau: screen sometimes remains blank after "xset dpms force off"

[Vincent Lefevre]

On 2021-05-08 21:30:11 +0200, Salvatore Bonaccorso wrote:
> So this was more recent. I guess still present as well on a recent
> kernel?

I don't know, as nouveau became completely unusable for me and
I'm currently using the NVIDIA driver:

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-nouveau/-/issues/534

> Did you got a chance to report it upstream and got some feedback?

No, but in general, there is no useful feedback from upstream
(no attempt to fix bugs).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99

[Vincent Lefevre]

FYI, other users got the same error:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848395
  https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1568772
  https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1624435
  https://bugs.gentoo.org/578138

In Debian bug 848395: as said by the alsactl(1) man page:

init tries to initialize all devices to a default state.
If device is not known, error code 99 is returned.

I can see 2 possibilities:

1. For some reason, the device is not always initialized by the
   kernel.

2. There is a race condition: alsactl is run too soon, while the
   device has not been initialized yet by the kernel.

(2) would explain why this isn't always reproducible.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#946437: systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument

[Vincent Lefevre]

Control: found -1 5.10.24-1

On 2021-05-08 14:53:13 +0200, Salvatore Bonaccorso wrote:
> Vincent, is this still something you are able to reproduce with a
> recent kernel? If not, should we close the bug? If yes, any more
> insights since the last report?

I still get the error in the logs due to the F13 key.
Last tested with:

Linux version 5.10.0-5-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP 
Debian 5.10.24-1 (2021-03-19)

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99

[Vincent Lefevre]

On 2021-05-08 14:54:58 +0200, Salvatore Bonaccorso wrote:
> Is this still something you are able to reproduce and have more
> insights since then? If you are not able to reproduce it anymore,
> should we otherwise close the issue?

zira:~> journalctl | grep 'failed with exit code 99'
May 18 14:40:58 zira systemd-udevd[461]: controlC1: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with 
exit code 99.
May 18 14:43:03 zira systemd-udevd[488]: controlC1: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with 
exit code 99.
Sep 17 14:44:13 zira systemd-udevd[452]: controlC1: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with 
exit code 99.
Sep 18 11:22:05 zira systemd-udevd[464]: controlC0: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with 
exit code 99.
Sep 24 10:54:58 zira systemd-udevd[452]: controlC1: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with 
exit code 99.
Sep 24 11:01:26 zira systemd-udevd[432]: controlC1: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with 
exit code 99.
Sep 24 11:07:31 zira systemd-udevd[456]: controlC1: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with 
exit code 99.
Sep 24 11:09:43 zira systemd-udevd[444]: controlC1: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with 
exit code 99.
Sep 24 11:29:22 zira systemd-udevd[449]: controlC1: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with 
exit code 99.
Sep 24 11:30:50 zira systemd-udevd[450]: controlC1: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with 
exit code 99.
Oct 18 23:19:30 zira systemd-udevd[462]: controlC0: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with 
exit code 99.
Oct 18 23:20:28 zira systemd-udevd[450]: controlC0: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with 
exit code 99.
Oct 29 02:51:50 zira systemd-udevd[452]: controlC0: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with 
exit code 99.
Nov 30 02:44:43 zira systemd-udevd[451]: controlC1: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with 
exit code 99.
Jan 04 21:21:29 zira systemd-udevd[458]: controlC0: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with 
exit code 99.
Jan 22 19:54:32 zira systemd-udevd[468]: controlC0: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with 
exit code 99.

So this failure hasn't occurred for a few months, but this was already
the case between 2020-05-18 and 2020-09-17. Thus there may still be
some possibility that it occurs again in a few weeks.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#922873: linux-image-4.19.0-3-amd64: nouveau "PGRAPH TLB flush idle timeout fail" errors, machine unresponsive via ssh

[Vincent Lefevre]

Control: tags -1 - fixed-upstream

Removing the fixed-upstream tags to avoid confusion since the bug
is still open upstream and I've never heard of any fix.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#922873: linux-image-4.19.0-3-amd64: nouveau "PGRAPH TLB flush idle timeout fail" errors, machine unresponsive via ssh

[Vincent Lefevre]

On 2021-05-02 13:42:28 +0200, Salvatore Bonaccorso wrote:
> Can you still reproduce the issue in buster with newest 4.19.y kernel?
> Can you reproduce the issue with unstable's or buster-backports
> kernel?

Not this issue, but I got other crashes since. The latest one:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970557

i.e. with 5.8.10-1 in September 2020. I had no longer any issue
until the machine crashed again (I assume) in December, but
I don't have a physical access to it currently.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#710509: linux-image-3.8-2-amd64: Click with the middle button of the DualPoint Stick doesn't always have an immediate effect

[Vincent Lefevre]

On 2013-05-31 15:27:11 +0200, Vincent Lefevre wrote:
> A click with the middle button of the DualPoint Stick (above the
> touchpad) on my Dell Latitude E6400 doesn't always have an immediate
> effect: I sometimes need to press a key to see the effect (pasted
> data). This problem is recent.
> 
> I could reproduce it several times, only in Emacs. But I doubt that's
> an Emacs problem, because when a USB mouse is attached, I never have
> any problem with the middle button (I don't think Emacs can notice a
> difference between a mouse and the DualPoint Stick buttons).

Not sure, but this could actually be an issue with the X server.
I no longer have this machine, but I can reproduce a similar problem,
also specific to the middle button associated with the pointstick,
on another laptop, where there is no issue at the input event level
(as seen with the input-events utility), only for the X event.
The bug report is the following one:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977996

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#970557: kernel crash in nouveau

[Vincent Lefevre]

Control: found -1 5.8.10-1

On 2020-09-18 18:07:35 +0200, Vincent Lefevre wrote:
> Package: src:linux
> Version: 5.8.7-1
> Severity: important
> 
> A short time after updating the kernel and rebooted, the kernel
> crashed in nouveau while I wasn't using the machine (I only had
> an ssh session).

Ditto with linux-image-5.8.0-2-amd64 5.8.10-1, except that I don't
have any log message about the crash. The machine suddenly rebooted.

This is apparently the same bug I had in the past:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929308

In each time, the crash occurs just after a reboot that follows
a kernel upgrade. I have the impression that the nouveau driver
doesn't properly reset the video card (since the card keeps data
from the previous boot), and there might be some inconsistency
due to the kernel upgrade. Otherwise I wonder why this seems to
occur *only* after kernel upgrades.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#970557: linux-image-5.8.0-1-amd64: kernel crash in nouveau

[Vincent Lefevre]

Package: src:linux
Version: 5.8.7-1
Severity: important

A short time after updating the kernel and rebooted, the kernel
crashed in nouveau while I wasn't using the machine (I only had
an ssh session).

Sep 18 17:56:26 ypig kernel: [ 1445.181686] [ cut here ]
Sep 18 17:56:26 ypig kernel: [ 1445.181755] WARNING: CPU: 1 PID: 0 at 
drivers/gpu/drm/nouveau/nvkm/subdev/mc/base.c:72 nvkm_mc_intr+0x14d/0x170 
[nouveau]
Sep 18 17:56:26 ypig kernel: [ 1445.181756] Modules linked in: bnep bluetooth 
jitterentropy_rng drbg aes_generic crypto_simd cryptd glue_helper ansi_cprng 
ecdh_generic ecc libaes cpufreq_powersave cpufreq_conservative 
cpufreq_userspace binfmt_misc nfsd auth_rpcgss nfs_acl nfs lockd grace fscache 
sunrpc smsc47b397 loop firewire_sbp2 nft_counter ip6_tables nft_compat 
nf_tables x_tables nfnetlink snd_hda_codec_realtek snd_hda_codec_generic 
ledtrig_audio snd_hda_intel nouveau intel_powerclamp coretemp mxm_wmi 
snd_intel_dspcfg video snd_hda_codec kvm_intel ttm kvm snd_hda_core 
drm_kms_helper irqbypass cec hp_wmi snd_hwdep sparse_keymap snd_pcm rfkill drm 
intel_cstate evdev snd_timer intel_uncore i2c_algo_bit snd serio_raw button 
iTCO_wdt intel_pmc_bxt wmi_bmof soundcore sg iTCO_vendor_support watchdog 
i7core_edac acpi_cpufreq ext4 crc16 mbcache jbd2 crc32c_generic hid_generic 
usbhid hid sd_mod t10_pi crc_t10dif crct10dif_generic sr_mod cdrom 
crct10dif_common ahci mptsas libahci mptscsih mptbase libata scsi_transport_sas
Sep 18 17:56:26 ypig kernel: [ 1445.181790]  firewire_ohci scsi_mod 
firewire_core psmouse ehci_pci uhci_hcd crc_itu_t crc32c_intel ehci_hcd tg3 
usbcore lpc_ich libphy ptp pps_core usb_common wmi floppy
Sep 18 17:56:26 ypig kernel: [ 1445.181800] CPU: 1 PID: 0 Comm: swapper/1 
Tainted: G  I   5.8.0-1-amd64 #1 Debian 5.8.7-1
Sep 18 17:56:26 ypig kernel: [ 1445.181801] Hardware name: Hewlett-Packard HP 
Z800 Workstation/0AECh, BIOS 786G5 v01.17 08/19/2009
Sep 18 17:56:26 ypig kernel: [ 1445.181842] RIP: 0010:nvkm_mc_intr+0x14d/0x170 
[nouveau]
Sep 18 17:56:26 ypig kernel: [ 1445.181844] Code: 44 24 18 65 48 2b 04 25 28 00 
00 00 75 2b 48 83 c4 20 5b 5d 41 5c 41 5d 41 5e 41 5f c3 41 8b 47 40 85 c0 74 
ba e9 34 97 0a 00 <0f> 0b 45 31 e4 c6 44 24 0f 00 e9 00 ff ff ff e8 bf bf 77 f2 
66 66
Sep 18 17:56:26 ypig kernel: [ 1445.181845] RSP: 0018:be65c3250ee8 EFLAGS: 
00010046
Sep 18 17:56:26 ypig kernel: [ 1445.181846] RAX:  RBX: 
95ed5fcefd00 RCX: 0018
Sep 18 17:56:26 ypig kernel: [ 1445.181847] RDX: 00ff RSI: 
be65c3250f47 RDI: be65d1000100
Sep 18 17:56:26 ypig kernel: [ 1445.181848] RBP: 95eb45d89c00 R08: 
be65c3250ff8 R09: 
Sep 18 17:56:26 ypig kernel: [ 1445.181849] R10:  R11: 
 R12: 
Sep 18 17:56:26 ypig kernel: [ 1445.181850] R13:  R14: 
be65c3250fac R15: 95f00f84b4e0
Sep 18 17:56:26 ypig kernel: [ 1445.181851] FS:  () 
GS:95ed63c4() knlGS:
Sep 18 17:56:26 ypig kernel: [ 1445.181852] CS:  0010 DS:  ES:  CR0: 
80050033
Sep 18 17:56:26 ypig kernel: [ 1445.181853] CR2: 7fa6714218b0 CR3: 
96a0a000 CR4: 06e0
Sep 18 17:56:26 ypig kernel: [ 1445.181854] Call Trace:
Sep 18 17:56:26 ypig kernel: [ 1445.181858]  
Sep 18 17:56:26 ypig kernel: [ 1445.181902]  nvkm_pci_intr+0x4d/0x90 [nouveau]
Sep 18 17:56:26 ypig kernel: [ 1445.181908]  
__handle_irq_event_percpu+0x48/0x190
Sep 18 17:56:26 ypig kernel: [ 1445.181910]  handle_irq_event+0x5d/0xbb
Sep 18 17:56:26 ypig kernel: [ 1445.181912]  handle_edge_irq+0x9c/0x280
Sep 18 17:56:26 ypig kernel: [ 1445.181916]  asm_call_on_stack+0x12/0x20
Sep 18 17:56:26 ypig kernel: [ 1445.181917]  
Sep 18 17:56:26 ypig kernel: [ 1445.181919]  common_interrupt+0xb5/0x150
Sep 18 17:56:26 ypig kernel: [ 1445.181921]  asm_common_interrupt+0x1e/0x40
Sep 18 17:56:26 ypig kernel: [ 1445.181925] RIP: 
0010:cpuidle_enter_state+0xb3/0x3f0
Sep 18 17:56:26 ypig kernel: [ 1445.181927] Code: 65 8b 3d 90 87 fb 4c e8 8b 32 
a6 ff 49 89 c7 66 66 66 66 90 31 ff e8 3c 3d a6 ff 80 7c 24 0f 00 0f 85 d4 01 
00 00 fb 66 66 90 <66> 66 90 45 85 e4 0f 88 e0 01 00 00 49 63 d4 4c 2b 7c 24 10 
48 8d
Sep 18 17:56:26 ypig kernel: [ 1445.181927] RSP: 0018:be65c31abe78 EFLAGS: 
0246
Sep 18 17:56:26 ypig kernel: [ 1445.181929] RAX: 95ed63c6bf40 RBX: 
de62bfc7f800 RCX: 001f
Sep 18 17:56:26 ypig kernel: [ 1445.181929] RDX:  RSI: 
3877f6f2 RDI: 
Sep 18 17:56:26 ypig kernel: [ 1445.181930] RBP: b3cc79c0 R08: 
01507655682b R09: 0151d95e40fc
Sep 18 17:56:26 ypig kernel: [ 1445.181931] R10: 0046 R11: 
003c R12: 0004
Sep 18 17:56:26 ypig kernel: [ 1445.181932] R13: de62bfc7f800 R14: 
0004 R15: 01507655682b
Sep 18 17:56:26 ypig kernel: [ 1445.181935]  ? cpuidle_enter_state+0xa4/0x3f0
Sep 

Bug#970503: linux-image-5.8.0-1-amd64: using swap makes the machine hang

[Vincent Lefevre]

On 2020-09-18 10:23:01 +0200, Vincent Lefevre wrote:
> https://github.com/openzfs/zfs/issues/8552 suggests a drive firmware
> bug (which could explain the absence of errors with smartctl and
> badblocks), but in this case the kernel might have a way to avoid it.
> 
> Also I'm wondering why this issue occurs *only* with swap. This could
> mean that the problem is on the kernel side (at least partly).

As suggested by the above URL and also by
http://www.howtoeverything.net/linux/hardware/ubuntu-freeze-issue-after-ssd-upgrade
(which also mentions freeze issues with swap) I've set
libata.force=noncq, which made the error disappear. The error
no longer occurs after reboot without this kernel parameter.

Still wondering whether this is a general issue with SSD and
something can be done in the kernel.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#970503: linux-image-5.8.0-1-amd64: using swap makes the machine hang

[Vincent Lefevre]

There is the same issue with the 4.19.132-1 Linux kernel from stable.

I've done more tests, and from a VT shortly after the boot,
"memhog 15320M" was fine, but "memhog 15350M" gave errors in
the console after some time, same as in the dmesg output below.

[  406.347520] ata1.00: exception Emask 0x0 SAct 0x400 SErr 0x4 action 
0x6 frozen
[  406.364822] ata1: SError: { CommWake }
[  406.374357] ata1.00: failed command: READ FPDMA QUEUED
[  406.384633] ata1.00: cmd 60/08:d0:00:09:f5/00:00:1d:00:00/40 tag 26 ncq dma 
4096 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 
(timeout)
[  406.421074] ata1.00: status: { DRDY }
[  406.433787] ata1: hard resetting link
[  406.747063] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[  406.787976] ata1.00: configured for UDMA/133
[  406.798082] ata1.00: device reported invalid CHS sector 0
[  406.798089] sd 0:0:0:0: [sda] tag#26 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE cmd_age=30s
[  406.798091] sd 0:0:0:0: [sda] tag#26 Sense Key : Illegal Request [current]
[  406.798094] sd 0:0:0:0: [sda] tag#26 Add. Sense: Unaligned write command
[  406.798097] sd 0:0:0:0: [sda] tag#26 CDB: Read(10) 28 00 1d f5 09 00 00 00 
08 00
[  406.798099] blk_update_request: I/O error, dev sda, sector 502597888 op 
0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  406.826011] ata1: EH complete
[  484.340739] INFO: task kworker/dying:5 blocked for more than 120 seconds.
[  484.354535]   Tainted: P   OE 5.8.0-1-amd64 #1 Debian 5.8.7-1
[  484.368881] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[  484.399712] kworker/dying   D0 5  2 0x80004000
[...]

So it appears that this could be a hardware issue, but I did a short
and a long self-test with smartctl and I did not get any error. And
badblocks gave no errors either.

Comments from https://github.com/openzfs/zfs/issues/10094 suggest that
it may not necessarily be (uniquely) a hardware issue. Note: I do not
use zfs, I've found this with a search for the error messages[*] on the
web, and this one is similar.

[*] In particular the "Sense: Unaligned write command"

https://github.com/openzfs/zfs/issues/8552 suggests a drive firmware
bug (which could explain the absence of errors with smartctl and
badblocks), but in this case the kernel might have a way to avoid it.

Also I'm wondering why this issue occurs *only* with swap. This could
mean that the problem is on the kernel side (at least partly).

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#970503: linux-image-5.8.0-1-amd64: using swap makes the machine hang

[Vincent Lefevre]

Package: src:linux
Version: 5.8.7-1
Severity: important

When swap is used (even a little), the machine hangs. A manual
power-off is needed.

To reproduce on my machine, which has 16 GB RAM and 20 GB swap:

$ memhog 15G

(command from the numactl package), e.g. just after the boot.

The machine still answers to ping, and if the command is run from
a VT (Linux console), I can still see things I type on the keyboard,
but I can't do anything else. Trying to interrupt the command with
Ctrl-C or Ctrl-\ has no effect. If I run the command from X, the
whole interface is frozen, e.g. the mouse pointer can no longer
move.

I initially found this issue with MPFR, using a little more than
15 GB. After 10 minutes, the interface was still completely frozen.

Note that nothing could be written in the logs.

-- Package-specific info:
** Version:
Linux version 5.8.0-1-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 
(2020-09-05)

** Command line:
BOOT_IMAGE=/vmlinuz-5.8.0-1-amd64 root=/dev/mapper/zira--vg-root ro quiet

** Tainted: POE (12289)
 * proprietary module was loaded
 * externally-built ("out-of-tree") module was loaded
 * unsigned module was loaded

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

** Model information
sys_vendor: Hewlett-Packard
product_name: HP ZBook 15 G2
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version: 
bios_vendor: Hewlett-Packard
bios_version: M70 Ver. 01.08
board_vendor: Hewlett-Packard
board_name: 2253
board_version: KBC Version 03.10

** Loaded modules:
uinput
rfcomm
ipt_REJECT
nf_reject_ipv4
xt_multiport
nft_compat
nft_counter
nf_tables
nfnetlink
cmac
algif_hash
algif_skcipher
af_alg
bnep
cpufreq_conservative
cpufreq_userspace
cpufreq_powersave
intel_rapl_msr
intel_rapl_common
iwlmvm
mac80211
mei_wdt
btusb
btrtl
snd_hda_codec_realtek
btbcm
binfmt_misc
snd_hda_codec_generic
btintel
libarc4
x86_pkg_temp_thermal
bluetooth
snd_hda_codec_hdmi
ledtrig_audio
intel_powerclamp
iwlwifi
coretemp
snd_hda_intel
uvcvideo
snd_intel_dspcfg
rapl
videobuf2_vmalloc
jitterentropy_rng
videobuf2_memops
intel_cstate
snd_hda_codec
joydev
videobuf2_v4l2
hp_wmi
intel_uncore
pcspkr
sparse_keymap
cfg80211
snd_hda_core
videobuf2_common
serio_raw
mxm_wmi
wmi_bmof
drbg
at24
snd_hwdep
videodev
snd_pcm
ansi_cprng
snd_timer
sg
tpm_infineon
iTCO_wdt
snd
intel_pmc_bxt
ecdh_generic
mei_me
ecc
iTCO_vendor_support
watchdog
mc
rfkill
apple_mfi_fastcharge
mei
soundcore
evdev
tpm_tis
tpm_tis_core
tpm
hp_accel
lis3lv02d
rng_core
hp_wireless
button
ac
nvidia_drm(POE)
drm_kms_helper
cec
nvidia_modeset(POE)
nvidia(POE)
ipmi_devintf
ipmi_msghandler
parport_pc
ppdev
drm
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
sd_mod
sr_mod
cdrom
t10_pi
crc_t10dif
crct10dif_generic
hid_apple
hid_generic
usbhid
hid
crct10dif_pclmul
crct10dif_common
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
rtsx_pci_sdmmc
mmc_core
ahci
aesni_intel
xhci_pci
libahci
xhci_hcd
libata
libaes
crypto_simd
cryptd
glue_helper
ehci_pci
ehci_hcd
psmouse
scsi_mod
rtsx_pci
e1000e
usbcore
i2c_i801
lpc_ich
i2c_smbus
ptp
pps_core
usb_common
battery
video
wmi

** 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 pfifo_fast state UP 
group default qlen 1000
link/ether 30:8d:99:25:ad:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute 
eth0
   valid_lft 86268sec preferred_lft 86268sec
inet6 fe80::b735:e72d:ac2d:f50/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever
3: wlp61s0:  mtu 1500 qdisc noqueue state 
DOWN group default qlen 1000
link/ether cc:3d:82:a9:e3:ea brd ff:ff:ff:ff:ff:ff

*** Device statistics:
Inter-|   Receive|  Transmit
 face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo:   36248 411000 0  0 036248 
411000 0   0  0
  eth0:  9903821110000 0  0 2   205014 
922000 0   0  0
wlp61s0:   0   0000 0  0 00 
  0000 0   0  0

*** Protocol statistics:
Ip:
Forwarding: 2
1041 total packets received
1 with invalid addresses
0 forwarded
0 incoming packets discarded
1026 incoming packets delivered
1069 requests sent out
20 outgoing packets dropped
547 dropped because of missing route
18 reassemblies 

Bug#970235: initramfs-tools-core: typo in /etc/initramfs-tools/initramfs.conf

[Vincent Lefevre]

Package: initramfs-tools-core
Version: 0.138
Severity: minor

In the latest upgrade, the following comment was added:

# FSTYPE: ...
#
# The filesytem type(s) to support, or "auto" to use the current root
# filesystem type

In "The filesytem type(s)", replace "filesytem" by "filesystem".

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=POSIX, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages initramfs-tools-core depends on:
ii  coreutils8.32-3
ii  cpio 2.13+dfsg-3
ii  e2fsprogs1.45.6-1
ii  klibc-utils  2.0.8-1
ii  kmod 27+20200310-2
ii  logsave  1.45.6-1
ii  udev 246.4-1

Versions of packages initramfs-tools-core recommends:
ii  busybox  1:1.30.1-6
ii  pigz 2.4-1+b1

Versions of packages initramfs-tools-core suggests:
ii  bash-completion  1:2.11-2

-- no debconf information

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

[Vincent Lefevre]

On 2020-09-08 13:59:07 +0200, Bastian Blank wrote:
> Control: tag -1 moreinfo
> Control: severity -1 important
> 
> On Tue, Sep 08, 2020 at 01:36:45PM +0200, Vincent Lefevre wrote:
> > This version fails to load kernel modules (no issues with previous
> > Linux kernels provided by Debian). As a consequence, X does not work.
> 
> > ** Loaded modules:
> > rfcomm
> > ipt_REJECT
> 
> Your system have a lot of loaded modules.  Please provide the real error
> message.

OK, I thought that the dmesg outout should contain it.
According to journalctl:

Sep 08 13:31:20 zira systemd-modules-load[408]: Error running install command 
'modprobe nvidia-modeset ; modprobe -i nvidia-legacy-390xx-drm ' for module 
nvidia_drm: retcode 1
Sep 08 13:31:20 zira systemd-modules-load[408]: Failed to insert module 
'nvidia_drm': Invalid argument

Indeed, /var/log/apt/term.log contains:

Setting up linux-headers-5.8.0-1-amd64 (5.8.7-1) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 5.8.0-1-amd64:
[...]
{ unset ARCH; env NV_VERBOSE=1 make -j8 modules KERNEL_UNAME=5.8.0-1-amd64; } 
>> /var/lib/dkms/nvidia-legacy-390xx/390.138/build/make.log 2>&1
(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.0-1-amd64 (x86_64)
Consult /var/lib/dkms/nvidia-legacy-390xx/390.138/build/make.log for more 
information.
.
Setting up linux-headers-amd64 (5.8.7-1) ...
Setting up linux-image-amd64 (5.8.7-1) ...
Log ended: 2020-09-08  13:23:01

(note that this error was not forwarded to aptitude).

and /var/lib/dkms/nvidia-legacy-390xx/390.138/build/make.log contains:

[...]
FATAL: modpost: GPL-incompatible module nvidia-uvm.ko uses GPL-only symbol 
'radix_tree_preloads'
make[3]: *** 
[/usr/src/linux-headers-5.8.0-1-common/scripts/Makefile.modpost:111: 
/var/lib/dkms/nvidia-legacy-390xx/390.138/build/Module.symvers] Error 1
make[2]: *** [/usr/src/linux-headers-5.8.0-1-common/Makefile:1681: modules] 
Error 2
make[2]: Leaving directory '/usr/src/linux-headers-5.8.0-1-amd64'
make[1]: *** [Makefile:185: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.8.0-1-common'
make: *** [Makefile:81: modules] Error 2

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#969889: linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work

[Vincent Lefevre]

Package: src:linux
Version: 5.8.7-1
Severity: grave
Justification: renders package unusable

This version fails to load kernel modules (no issues with previous
Linux kernels provided by Debian). As a consequence, X does not work.

I've attached the dmesg output.

-- Package-specific info:
** Version:
Linux version 5.8.0-1-amd64 (debian-kernel@lists.debian.org) (gcc-10 (Debian 
10.2.0-6) 10.2.0, GNU ld (GNU Binutils for Debian) 2.35) #1 SMP Debian 5.8.7-1 
(2020-09-05)

** Command line:
BOOT_IMAGE=/vmlinuz-5.8.0-1-amd64 root=/dev/mapper/zira--vg-root ro quiet

** Not tainted

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

** Model information
sys_vendor: Hewlett-Packard
product_name: HP ZBook 15 G2
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version: 
bios_vendor: Hewlett-Packard
bios_version: M70 Ver. 01.08
board_vendor: Hewlett-Packard
board_name: 2253
board_version: KBC Version 03.10

** Loaded modules:
rfcomm
ipt_REJECT
nf_reject_ipv4
xt_multiport
nft_compat
nft_counter
nf_tables
nfnetlink
cmac
algif_hash
algif_skcipher
af_alg
cpufreq_conservative
cpufreq_userspace
cpufreq_powersave
bnep
btusb
btrtl
btbcm
iwlmvm
btintel
bluetooth
intel_rapl_msr
mac80211
libarc4
mei_wdt
intel_rapl_common
snd_hda_codec_realtek
jitterentropy_rng
binfmt_misc
iwlwifi
snd_hda_codec_generic
drbg
ledtrig_audio
x86_pkg_temp_thermal
snd_hda_codec_hdmi
ansi_cprng
intel_powerclamp
cfg80211
coretemp
ecdh_generic
hp_wmi
ecc
snd_hda_intel
sparse_keymap
rapl
snd_intel_dspcfg
uvcvideo
intel_cstate
snd_hda_codec
intel_uncore
videobuf2_vmalloc
videobuf2_memops
snd_hda_core
videobuf2_v4l2
videobuf2_common
iTCO_wdt
joydev
snd_hwdep
intel_pmc_bxt
videodev
snd_pcm
pcspkr
iTCO_vendor_support
serio_raw
mxm_wmi
wmi_bmof
mei_me
snd_timer
tpm_infineon
watchdog
sg
mc
rfkill
apple_mfi_fastcharge
at24
snd
mei
soundcore
evdev
tpm_tis
tpm_tis_core
tpm
hp_accel
lis3lv02d
hp_wireless
rng_core
ac
button
parport_pc
ppdev
drm
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
sd_mod
sr_mod
cdrom
t10_pi
crc_t10dif
crct10dif_generic
hid_apple
hid_generic
usbhid
hid
crct10dif_pclmul
crct10dif_common
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
rtsx_pci_sdmmc
mmc_core
ahci
libahci
libata
aesni_intel
xhci_pci
libaes
crypto_simd
xhci_hcd
cryptd
glue_helper
psmouse
ehci_pci
ehci_hcd
e1000e
i2c_i801
scsi_mod
i2c_smbus
usbcore
rtsx_pci
lpc_ich
ptp
pps_core
usb_common
battery
video
wmi

** 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 pfifo_fast state UP 
group default qlen 1000
link/ether 30:8d:99:25:ad:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute 
eth0
   valid_lft 86221sec preferred_lft 86221sec
inet6 fe80::b735:e72d:ac2d:f50/64 scope link noprefixroute 
   valid_lft forever preferred_lft forever
3: wlp61s0:  mtu 1500 qdisc noqueue state 
DOWN group default qlen 1000
link/ether cc:3d:82:a9:e3:ea brd ff:ff:ff:ff:ff:ff

*** Device statistics:
Inter-|   Receive|  Transmit
 face |bytespackets errs drop fifo frame compressed multicast|bytes
packets errs drop fifo colls carrier compressed
lo:   31682 360000 0  0 031682 
360000 0   0  0
  eth0:  9841141134000 0  0 4   217083 
945000 0   0  0
wlp61s0:   0   0000 0  0 00 
  0000 0   0  0

*** Protocol statistics:
Ip:
Forwarding: 2
1036 total packets received
1 with invalid addresses
0 forwarded
0 incoming packets discarded
1008 incoming packets delivered
1077 requests sent out
20 outgoing packets dropped
548 dropped because of missing route
2 reassemblies required
1 packets reassembled ok
Icmp:
46 ICMP messages received
0 input ICMP message failed
ICMP input histogram:
destination unreachable: 46
64 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
destination unreachable: 64
IcmpMsg:
InType3: 46
OutType3: 64
Tcp:
28 active connection openings
5 passive connection openings
9 failed connection attempts
2 connection resets received
0 connections established
648 segments received
721 segments sent out
9 segments retransmitted
0 bad segments received
31 resets sent
Udp:
412 packets received
40 packets to unknown port received
0 packet receive errors
463 packets sent
0 receive buffer errors
 

Bug#959170: linux: at boot: Process '/usr/sbin/alsactl ... restore 0' failed with exit code 99

[Vincent Lefevre]

Source: linux
Version: 5.6.7-1
Severity: minor

With the 5.6.0-1-amd64 Linux kernel at least, I get the following
error at boot (shown by journalctl):

Apr 30 11:57:16 zira systemd-udevd[489]: controlC0: Process '/usr/sbin/alsactl 
-E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 0' failed with 
exit code 99.

This apparently comes from /lib/systemd/system/alsa-restore.service,
which has:

ExecStart=-/usr/sbin/alsactl -E HOME=/run/alsa -E 
XDG_RUNTIME_DIR=/run/alsa/runtime restore

It seems that the first time I got a similar error was in October:

Oct 22 10:07:58 zira systemd-udevd[500]: Process '/usr/sbin/alsactl -E 
HOME=/run/alsa restore 1' failed with exit code 99.

Then in November:

Nov 10 02:40:42 zira systemd-udevd[513]: Process '/usr/sbin/alsactl -E 
HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit 
code 99.

/etc/alsa/conf.d contains:

lrwxrwxrwx 1 root root  44 2020-02-29 17:15:54 10-rate-lav.conf -> 
/usr/share/alsa/alsa.conf.d/10-rate-lav.conf
lrwxrwxrwx 1 root root  46 2020-02-29 17:15:54 10-samplerate.conf -> 
/usr/share/alsa/alsa.conf.d/10-samplerate.conf
lrwxrwxrwx 1 root root  45 2020-02-29 17:15:54 10-speexrate.conf -> 
/usr/share/alsa/alsa.conf.d/10-speexrate.conf
lrwxrwxrwx 1 root root  48 2020-02-29 17:15:54 50-arcam-av-ctl.conf -> 
/usr/share/alsa/alsa.conf.d/50-arcam-av-ctl.conf
lrwxrwxrwx 1 root root  40 2020-02-29 17:15:54 50-jack.conf -> 
/usr/share/alsa/alsa.conf.d/50-jack.conf
lrwxrwxrwx 1 root root  39 2020-02-29 17:15:54 50-oss.conf -> 
/usr/share/alsa/alsa.conf.d/50-oss.conf
lrwxrwxrwx 1 root root  46 2020-02-29 17:15:54 50-pulseaudio.conf -> 
/usr/share/alsa/alsa.conf.d/50-pulseaudio.conf
lrwxrwxrwx 1 root root  47 2020-02-29 17:15:54 60-a52-encoder.conf -> 
/usr/share/alsa/alsa.conf.d/60-a52-encoder.conf
lrwxrwxrwx 1 root root  41 2020-02-29 17:15:54 60-upmix.conf -> 
/usr/share/alsa/alsa.conf.d/60-upmix.conf
lrwxrwxrwx 1 root root  44 2020-02-29 17:15:54 60-vdownmix.conf -> 
/usr/share/alsa/alsa.conf.d/60-vdownmix.conf
lrwxrwxrwx 1 root root  46 2020-02-29 17:15:54 98-usb-stream.conf -> 
/usr/share/alsa/alsa.conf.d/98-usb-stream.conf
lrwxrwxrwx 1 root root  38 2020-02-06 03:06:41 99-pulse.conf -> 
/usr/share/alsa/alsa.conf.d/pulse.conf
-rw-r--r-- 1 root root 201 2018-11-03 00:35:24 
99-pulseaudio-default.conf.example

(I haven't changed anything there.)

-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

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

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#956383: linux-image-5.5.0-1-amd64: artifacts on screen / nouveau_exa_upload_to_screen:380 - falling back to memcpy ignores tiling

[Vincent Lefevre]

On 2020-04-10 16:08:26 +0200, Vincent Lefevre wrote:
> I get artifacts on screen when using xpdf or Firefox. I took a photo
> for the first one; see attached file. This may be related to the
> upgrade to the 5.5.13-2 kernel yesterday, as this problem never
> occurred before, IIRC.

I would add that this occurs randomly, and I haven't found a way to
reproduce the problem.

I'm going to reboot in order to see if this occurs again.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#930527: linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information

[Vincent Lefevre]

Hi,

On 2020-03-30 09:06:15 +0200, Ivo De Decker wrote:
> On Sun, Mar 29, 2020 at 09:43:42PM +0200, Vincent Lefevre wrote:
> > I don't think so, except the use of the nouveau driver, of course.
> > But there were no issues for years. I think that problems started
> > to occur after some kernel upgrade. Now, I haven't had any problem
> > since December, I think.
> 
> Do you think the problem is gone with the kernel you are running now?

I don't know. I don't use this machine often, except remotely
(via ssh). But problems with the nouveau driver were common
(and a crash could occur in the nouveau driver even when using
the machine remotely only), and I haven't seen any issue recently,
even the last few times I logged in physically.

> What version is that?

linux-image-5.4.0-4-amd64 5.4.19-1

ypig:~> uname -a
Linux ypig 5.4.0-4-amd64 #1 SMP Debian 5.4.19-1 (2020-02-13) x86_64 GNU/Linux

> > > Also, I don't think this bug is really 'grave'. Even if private
> > > information remains on the screen, the user can see that, and
> > > take action to avoid it.
> > 
> > Not if one logs out remotely.
> 
> What do you mean by that?

I sometimes log in physically, but go away without logging out first
(there are sometimes a good reason, e.g. if some computation program
hasn't finished yet and I had not started it in "screen"). I can
later log in via ssh and kill the X session.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#930527: linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information

[Vincent Lefevre]

On 2020-03-29 19:10:30 +0200, Ivo De Decker wrote:
> On Fri, Jun 14, 2019 at 04:31:16PM +0200, Vincent Lefevre wrote:
> > When logging out, a part of the previous session is still visible.
> > This might be used to compromise the user's account or leak other
> > private information, depending on what was written on the screen.
> 
> What do you mean exactly? Is the screen only erased partially, or not at all?

It was partially erased.

> Is there something specific about your setup that you think might be relevant
> here?

I don't think so, except the use of the nouveau driver, of course.
But there were no issues for years. I think that problems started
to occur after some kernel upgrade. Now, I haven't had any problem
since December, I think.

> Also, I don't think this bug is really 'grave'. Even if private information
> remains on the screen, the user can see that, and take action to avoid it.

Not if one logs out remotely.

Regards,

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#946437: systemd-udevd: event4: Failed to call EVIOCSKEYCODE with scan code 0x70068, and key code 110: Invalid argument

[Vincent Lefevre]

On 2019-12-09 00:31:29 +0100, Vincent Lefevre wrote:
> I've noticed the following error (in red) in the journalctl output:
> 
> Dec 09 00:10:18 zira systemd-udevd[506]: event4: Failed to call EVIOCSKEYCODE 
> with scan code 0x70068, and key code 110: Invalid argument
> 
> This is not new.
> 
> I have a file /etc/udev/hwdb.d/98-apple-keyboard.hwdb with:
> 
> evdev:input:b0003v05ACp0221*
>  KEYBOARD_KEY_70068=insert  # F13: Insert
> 
> and this corresponds to
> 
> Bus 002 Device 005: ID 05ac:0221 Apple, Inc. Aluminum Keyboard (ISO)
> 
> I use the F13 key for Insert, as there is no Insert key on this
> keyboard (this is a Fn key at the usual place of the Insert key
> and the driver honors this specificity).
> 
> I have not seen any side effect of this error, though.

According to the Xorg log[*], the keyboard uses 2 event devices
(in particular, due to that, I get many duplicate lines in this
log file: one for each event device). But the error I get in the
journalctl output is only for the second event device.

[*] The lines from /var/log/Xorg.0.log corresponding to these two
event devices:

[18.667] (II) config/udev: Adding input device Apple, Inc Apple Keyboard 
(/dev/input/event3)
[18.667] (**) Option "Device" "/dev/input/event3"
[18.669] (II) event3  - Apple, Inc Apple Keyboard: is tagged by udev as: 
Keyboard
[18.669] (II) event3  - Apple, Inc Apple Keyboard: device is a keyboard
[18.669] (II) event3  - Apple, Inc Apple Keyboard: device removed
[18.698] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb2/2-6/2-6.2/2-6.2:1.0/0003:05AC:0221.0001/input/input9/event3"
[18.700] (II) event3  - Apple, Inc Apple Keyboard: is tagged by udev as: 
Keyboard
[18.700] (II) event3  - Apple, Inc Apple Keyboard: device is a keyboard
[18.701] (II) config/udev: Adding input device Apple, Inc Apple Keyboard 
(/dev/input/event4)
[18.701] (**) Option "Device" "/dev/input/event4"
[18.704] (II) event4  - Apple, Inc Apple Keyboard: is tagged by udev as: 
Keyboard
[18.704] (II) event4  - Apple, Inc Apple Keyboard: device is a keyboard
[18.704] (II) event4  - Apple, Inc Apple Keyboard: device removed
[18.734] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb2/2-6/2-6.2/2-6.2:1.1/0003:05AC:0221.0002/input/input10/event4"
[18.736] (II) event4  - Apple, Inc Apple Keyboard: is tagged by udev as: 
Keyboard
[18.736] (II) event4  - Apple, Inc Apple Keyboard: device is a keyboard
[ 16244.494] (II) event3  - Apple, Inc Apple Keyboard: device removed
[ 16244.510] (II) event4  - Apple, Inc Apple Keyboard: device removed
[ 25897.048] (II) event3  - Apple, Inc Apple Keyboard: is tagged by udev as: 
Keyboard
[ 25897.048] (II) event3  - Apple, Inc Apple Keyboard: device is a keyboard
[ 25897.049] (II) event4  - Apple, Inc Apple Keyboard: is tagged by udev as: 
Keyboard
[ 25897.049] (II) event4  - Apple, Inc Apple Keyboard: device is a keyboard
[ 26635.074] (II) event3  - Apple, Inc Apple Keyboard: device removed
[ 26635.094] (II) event4  - Apple, Inc Apple Keyboard: device removed
[ 28690.158] (II) event3  - Apple, Inc Apple Keyboard: is tagged by udev as: 
Keyboard
[ 28690.158] (II) event3  - Apple, Inc Apple Keyboard: device is a keyboard
[ 28690.159] (II) event4  - Apple, Inc Apple Keyboard: is tagged by udev as: 
Keyboard
[ 28690.159] (II) event4  - Apple, Inc Apple Keyboard: device is a keyboard

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#949727: firmware-misc-nonfree: Missing dependency initramfs-tools-core

[Vincent Lefevre]

On 2020-01-26 04:42:13 +, Ben Hutchings wrote:
> On Fri, 2020-01-24 at 08:53 +0100, mando wrote:
> > I tried to install firmware-misc-nonfree and I got this error:
> > 
> > modprobe: ERROR: ../libkmod/libkmod.c:508 
> > kmod_lookup_alias_from_builtin_file() 
> > could not open builtin file '/lib/modules/xxx/modules.builtin.bin'
> >
> > ... where xxx is the result of $(uname -r)
> 
> Looks like bug #948257.

No, it isn't. The user's logs show that he installed

2020-01-24 08:43:15 status installed initramfs-tools-core:all 0.136

but version 0.136 is claimed as fixed.

The path in the error message starts with "/lib/modules" rather than
"/var/tmp/mkinitramfs_". So I would say that it's rather bug 949444.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#948257: "depmod: ERROR: ..." still occurs

[Vincent Lefevre]

Control: notfound -1 0.136
Control: fixed -1 0.136

On 2020-01-20 18:36:24 +, Ben Hutchings wrote:
> On Mon, 2020-01-20 at 10:30 +0100, Vincent Lefevre wrote:
> > Control: reopen -1
> > Control: found -1 0.136
> > 
> > After the Linux kernel upgrade (initramfs-tools was upgrade to 0.136
> > earlier), I still get many errors
> > 
> > depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not 
> > open builtin file '/lib/modules/5.4.0-3-amd64/modules.builtin.bin'
> 
> But that has nothing to do with initramfs-tools.  You should reopen
> #948350.

Indeed, this does not occur during update-initramfs. I've opened
a new bug (this is different from #948350):

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949444

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#948257: "depmod: ERROR: ..." still occurs

[Vincent Lefevre]

Control: reopen -1
Control: found -1 0.136

After the Linux kernel upgrade (initramfs-tools was upgrade to 0.136
earlier), I still get many errors

depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-3-amd64/modules.builtin.bin'

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#946524: linux-image-5.3.0-3-amd64: black screen: trapped write in the nouveau driver

[Vincent Lefevre]

On 2019-12-10 15:56:58 +0100, Vincent Lefevre wrote:
> After the upgrade to 5.3.0-3-amd64, I get a black screen, with random
> flickering pixels. The dmesg output below shows errors from the
> nouveau driver (trapped write...).

But after a reboot, the problem disappeared.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#946524: linux-image-5.3.0-3-amd64: black screen: trapped write in the nouveau driver

[Vincent Lefevre]

Package: src:linux
Version: 5.3.15-1
Severity: important

After the upgrade to 5.3.0-3-amd64, I get a black screen, with random
flickering pixels. The dmesg output below shows errors from the
nouveau driver (trapped write...).

[0.00] microcode: microcode updated early to revision 0x1d, date = 
2018-05-11
[0.00] Linux version 5.3.0-3-amd64 (debian-kernel@lists.debian.org) 
(gcc version 9.2.1 20191130 (Debian 9.2.1-21)) #1 SMP Debian 5.3.15-1 
(2019-12-07)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0-3-amd64 
root=UUID=e3631277-c4d0-460e-a2a3-6de16013e050 ro quiet
[0.00] x86/fpu: x87 FPU will use FXSAVE
[0.00] BIOS-provided physical RAM map:
[0.00] BIOS-e820: [mem 0x-0x000957ff] usable
[0.00] BIOS-e820: [mem 0x00095800-0x0009] reserved
[0.00] BIOS-e820: [mem 0x000e8000-0x000f] reserved
[0.00] BIOS-e820: [mem 0x0010-0xcefa57ff] usable
[0.00] BIOS-e820: [mem 0xcefa5800-0xcfff] reserved
[0.00] BIOS-e820: [mem 0xf000-0xf7ff] reserved
[0.00] BIOS-e820: [mem 0xfec0-0xfed3] reserved
[0.00] BIOS-e820: [mem 0xfed45000-0x] reserved
[0.00] BIOS-e820: [mem 0x0001-0x00062fff] usable
[0.00] NX (Execute Disable) protection: active
[0.00] SMBIOS 2.6 present.
[0.00] DMI: Hewlett-Packard HP Z800 Workstation/0AECh, BIOS 786G5 
v01.17 08/19/2009
[0.00] tsc: Fast TSC calibration using PIT
[0.00] tsc: Detected 2266.778 MHz processor
[0.003203] e820: update [mem 0x-0x0fff] usable ==> reserved
[0.003205] e820: remove [mem 0x000a-0x000f] usable
[0.003210] last_pfn = 0x63 max_arch_pfn = 0x4
[0.003214] MTRR default type: write-back
[0.003215] MTRR fixed ranges enabled:
[0.003216]   0-9 write-back
[0.003217]   A-B uncachable
[0.003218]   C-E7FFF write-protect
[0.003218]   E8000-E write-back
[0.003219]   F-F write-protect
[0.003220] MTRR variable ranges enabled:
[0.003221]   0 base 00D000 mask FFF000 uncachable
[0.003222]   1 base 00E000 mask FFE000 uncachable
[0.003223]   2 base 063000 mask FFF000 uncachable
[0.003224]   3 disabled
[0.003225]   4 disabled
[0.003225]   5 disabled
[0.003226]   6 disabled
[0.003226]   7 disabled
[0.003993] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
[0.004104] last_pfn = 0xcefa5 max_arch_pfn = 0x4
[0.013311] found SMP MP-table at [mem 0x000f9bf0-0x000f9bff]
[0.013389] BRK [0x25ce01000, 0x25ce01fff] PGTABLE
[0.013392] BRK [0x25ce02000, 0x25ce02fff] PGTABLE
[0.013393] BRK [0x25ce03000, 0x25ce03fff] PGTABLE
[0.013418] BRK [0x25ce04000, 0x25ce04fff] PGTABLE
[0.013420] BRK [0x25ce05000, 0x25ce05fff] PGTABLE
[0.013496] BRK [0x25ce06000, 0x25ce06fff] PGTABLE
[0.013513] BRK [0x25ce07000, 0x25ce07fff] PGTABLE
[0.013530] BRK [0x25ce08000, 0x25ce08fff] PGTABLE
[0.013559] BRK [0x25ce09000, 0x25ce09fff] PGTABLE
[0.013942] RAMDISK: [mem 0x33f5d000-0x35fa5fff]
[0.013949] ACPI: Early table checksum verification disabled
[0.013953] ACPI: RSDP 0x000E9010 24 (v02 HPQOEM)
[0.013956] ACPI: XSDT 0xCEFB88E8 6C (v01 HPQOEM SLIC-WKS 
20090819  )
[0.013962] ACPI: FACP 0xCEFB8A88 F4 (v03 HPQOEM TYLSBURG 
0001  )
[0.013966] ACPI BIOS Warning (bug): 32/64X length mismatch in 
FADT/Pm1aEventBlock: 32/16 (20190703/tbfadt-564)
[0.013969] ACPI BIOS Warning (bug): 32/64X length mismatch in 
FADT/Gpe0Block: 128/32 (20190703/tbfadt-564)
[0.013971] ACPI BIOS Warning (bug): Invalid length for FADT/Pm1aEventBlock: 
16, using default 32 (20190703/tbfadt-669)
[0.013974] ACPI: DSDT 0xCEFB92D7 00A73D (v01 COMPAQ DSDT_PRJ 
0001 MSFT 010E)
[0.013977] ACPI: FACS 0xCEFB8800 40
[0.013980] ACPI: FACS 0xCEFB8800 40
[0.013982] ACPI: APIC 0xCEFB8B7C 000114 (v01 HPQOEM TYLSBURG 
0001  )
[0.013986] ACPI: ASF! 0xCEFB8C90 63 (v32 HPQOEM TYLSBURG 
0001  )
[0.013989] ACPI: MCFG 0xCEFB8CF3 3C (v01 HPQOEM TYLSBURG 
0001  )
[0.013992] ACPI: TCPA 0xCEFB8D2F 32 (v01 HPQOEM TYLSBURG 
0001  )
[0.013996] ACPI: HPET 0xCEFB8ED7 38 (v01 HPQOEM TYLSBURG 
0001  )
[0.013999] ACPI: DMAR 0xCEFB8F0F 0001B8 (v01 HPQOEM TYLSBURG 
0001  )
[0.014002] ACPI: SRAT 0xCEFB90DF 0001F8 (v02 HPQOEM TYLSBURG 
0001  )
[0.014005] ACPI: SSDT 0xCEFC4EE6 0023D4 (v01 INTEL  PPM RCM  
8001 INTL 20061109)
[0.014015] ACPI: Local APIC address 

Bug#945140: linux-image-5.3.0-2-amd64: system occasionally hangs for several minutes

[Vincent Lefevre]

On 2019-11-20 12:52:09 +0100, Vincent Lefevre wrote:
> Package: src:linux
> Version: 5.3.9-2
> Severity: important
> 
> Since yesterday, the system occasionally hangs for several minutes.
> When this happens, I can observe in the journalctl output:
> 
> Nov 19 02:28:43 zira rtkit-daemon[752]: The canary thread is apparently 
> starving. Taking action.
[...]

Note sure whether this is a bug related to rtkit-daemon. I've found
the possible culprit (which also explains that I had no problems
before): xpdf takes several GB, even though the PDF file is rather
simple (26 slides, no images...). The consequence is that the machine
is swapping. I suspect a memory leak, possibly when the PDF file is
reloaded (I've been writing slides, thus with many reloads...).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#945140: linux-image-5.3.0-2-amd64: system occasionally hangs for several minutes

[Vincent Lefevre]

Package: src:linux
Version: 5.3.9-2
Severity: important

Since yesterday, the system occasionally hangs for several minutes.
When this happens, I can observe in the journalctl output:

Nov 19 02:28:43 zira rtkit-daemon[752]: The canary thread is apparently 
starving. Taking action.
Nov 19 02:28:43 zira rtkit-daemon[752]: Demoting known real-time threads.
Nov 19 02:28:43 zira rtkit-daemon[752]: Successfully demoted thread 20029 of 
process 19666.
Nov 19 02:28:43 zira rtkit-daemon[752]: Successfully demoted thread 20028 of 
process 19666.
Nov 19 02:28:43 zira rtkit-daemon[752]: Successfully demoted thread 19666 of 
process 19666.
Nov 19 02:28:43 zira rtkit-daemon[752]: Demoted 3 threads.

Nov 20 04:13:07 zira rtkit-daemon[747]: The canary thread is apparently 
starving. Taking action.
Nov 20 04:13:07 zira rtkit-daemon[747]: Demoting known real-time threads.
Nov 20 04:13:07 zira rtkit-daemon[747]: Successfully demoted thread 2057 of 
process 1567.
Nov 20 04:13:07 zira rtkit-daemon[747]: Successfully demoted thread 2056 of 
process 1567.
Nov 20 04:13:07 zira rtkit-daemon[747]: Successfully demoted thread 1567 of 
process 1567.
Nov 20 04:13:07 zira rtkit-daemon[747]: Demoted 3 threads.

Nov 20 12:33:37 zira rtkit-daemon[747]: The canary thread is apparently 
starving. Taking action.
Nov 20 12:33:37 zira rtkit-daemon[747]: Demoting known real-time threads.
Nov 20 12:33:38 zira rtkit-daemon[747]: Demoted 0 threads.

Possibly related, with also the messages about rtkit-daemon:

  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1712858

"Occasionally, the system freezes: display does not show mouse move,
clock display does not update itself, ssh impossible."

Ditto here. It is also said "But the machine remains pingable"
but I have not tried ping.

-- Package-specific info:
** Version:
Linux version 5.3.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 9.2.1 
20191109 (Debian 9.2.1-19)) #1 SMP Debian 5.3.9-2 (2019-11-12)

** Command line:
BOOT_IMAGE=/vmlinuz-5.3.0-2-amd64 root=/dev/mapper/zira--vg-root ro quiet

** Not tainted

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

** Model information
sys_vendor: Hewlett-Packard
product_name: HP ZBook 15 G2
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version: 
bios_vendor: Hewlett-Packard
bios_version: M70 Ver. 01.08
board_vendor: Hewlett-Packard
board_name: 2253
board_version: KBC Version 03.10

** Loaded modules:
ipt_REJECT
nf_reject_ipv4
xt_multiport
nft_compat
nft_counter
nf_tables
nfnetlink
psnap
llc
cpufreq_conservative
cpufreq_userspace
intel_rapl_msr
intel_rapl_common
cpufreq_powersave
cmac
bnep
x86_pkg_temp_thermal
intel_powerclamp
coretemp
iwlmvm
snd_hda_codec_hdmi
btusb
btrtl
mei_wdt
mac80211
btbcm
btintel
bluetooth
kvm
binfmt_misc
irqbypass
libarc4
nouveau
snd_hda_codec_realtek
snd_hda_codec_generic
ledtrig_audio
intel_cstate
iwlwifi
uvcvideo
videobuf2_vmalloc
videobuf2_memops
intel_uncore
snd_hda_intel
videobuf2_v4l2
snd_hda_codec
intel_rapl_perf
ttm
drbg
videobuf2_common
cfg80211
joydev
snd_hda_core
hp_wmi
videodev
drm_kms_helper
snd_hwdep
serio_raw
pcspkr
snd_pcm
ansi_cprng
iTCO_wdt
mei_me
sparse_keymap
mc
snd_timer
ecdh_generic
snd
ecc
rtsx_pci_ms
tpm_infineon
iTCO_vendor_support
drm
wmi_bmof
sg
memstick
watchdog
soundcore
mxm_wmi
rfkill
mei
i2c_algo_bit
ie31200_edac
battery
evdev
tpm_tis
tpm_tis_core
tpm
hp_accel
lis3lv02d
rng_core
button
input_polldev
ac
hp_wireless
parport_pc
ppdev
lp
parport
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
sr_mod
cdrom
sd_mod
hid_apple
hid_generic
usbhid
hid
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
rtsx_pci_sdmmc
mmc_core
ahci
libahci
aesni_intel
xhci_pci
libata
xhci_hcd
aes_x86_64
crypto_simd
cryptd
ehci_pci
glue_helper
ehci_hcd
scsi_mod
e1000e
psmouse
rtsx_pci
usbcore
i2c_i801
lpc_ich
mfd_core
ptp
pps_core
usb_common
video
wmi

** Network interface configuration:
*** /etc/network/interfaces:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

iface eth0 inet dhcp

allow-hotplug enx02060b0e
iface enx02060b0e inet dhcp
allow-hotplug enp0s20u2
iface enp0s20u2 inet dhcp
allow-hotplug enp0s20u9
iface enp0s20u9 inet dhcp
allow-hotplug enp0s20u10
iface enp0s20u10 inet dhcp


** 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 pfifo_fast state UP 
group default qlen 1000
link/ether 30:8d:99:25:ad:3f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic eth0
   valid_lft 71454sec preferred_lft 71454sec
inet6 fe80::328d:99ff:fe25:ad3f/64 scope link 
   valid_lft forever preferred_lft forever
3: wlp61s0:  mtu 1500 

Bug#914967: linux-image-4.18.0-3-amd64: errors "Failed to get unique processor _UID"

[Vincent Lefevre]

Control: found -1 4.19.67-2+deb10u2

On 2018-11-29 09:21:31 +0100, Vincent Lefevre wrote:
> I get the following errors at boot time:
> 
> Nov 29 09:04:20 cventin kernel: acpi LNXCPU:06: Failed to get unique 
> processor _UID (0xff)
> Nov 29 09:04:20 cventin kernel: acpi LNXCPU:07: Failed to get unique 
> processor _UID (0xff)
> Nov 29 09:04:20 cventin kernel: acpi LNXCPU:08: Failed to get unique 
> processor _UID (0xff)
> Nov 29 09:04:20 cventin kernel: acpi LNXCPU:09: Failed to get unique 
> processor _UID (0xff)
> Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0a: Failed to get unique 
> processor _UID (0xff)
> Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0b: Failed to get unique 
> processor _UID (0xff)
> Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0c: Failed to get unique 
> processor _UID (0xff)
> [...]
> Nov 29 09:04:21 cventin kernel: acpi LNXCPU:8f: Failed to get unique 
> processor _UID (0xff)
> 
> There were no such errors before linux-image-4.18.0-3-amd64.

Still occurs in the Debian/stable kernel.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#792778: nouveau: screen sometimes remains blank after "xset dpms force off"

[Vincent Lefevre]

Control: reopen -1
Control: found -1 5.2.9-2

On 2019-09-01 10:41:15 +0200, Vincent Lefevre wrote:
> On 2015-07-18 14:52:03 +0200, Vincent Lefevre wrote:
> > After I blank the screen of my laptop with "xset dpms force off", it
> > is usually unblanked as expected when I type a key or move the mouse,
> > but not always. When this occurs, the screen is no longer off, in the
> > sense I can see some light on it, but nothing is displayed.
> 
> This is old, and with a few tests on the same machine after using
> again nouveau since last night, I could not reproduce the problem
> with a 5.2.0-2-amd64 kernel. Closing.

I could reproduce it again. Exactly the same issue.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#939079: nouveau: screen dimensions and resolution are wrong

[Vincent Lefevre]

Package: src:linux
Version: 5.2.9-2
Severity: normal

With the nouveau driver, I get:

$ xdpyinfo
[...]
screen #0:
  dimensions:3200x1800 pixels (846x476 millimeters)
  resolution:96x96 dots per inch
[...]

which is wrong!

As a comparison, with the nvidia driver:

[...]
screen #0:
  dimensions:3200x1800 pixels (350x191 millimeters)
  resolution:232x239 dots per inch
[...]

which is correct.

This prevents HiDPI detection.

-- Package-specific info:
** Version:
Linux version 5.2.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 
(Debian 8.3.0-21)) #1 SMP Debian 5.2.9-2 (2019-08-21)

** Command line:
BOOT_IMAGE=/vmlinuz-5.2.0-2-amd64 root=/dev/mapper/zira--vg-root ro quiet

** Not tainted

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

** Model information
sys_vendor: Hewlett-Packard
product_name: HP ZBook 15 G2
product_version: A3008CD10003
chassis_vendor: Hewlett-Packard
chassis_version: 
bios_vendor: Hewlett-Packard
bios_version: M70 Ver. 01.08
board_vendor: Hewlett-Packard
board_name: 2253
board_version: KBC Version 03.10

** Loaded modules:
ipt_REJECT
nf_reject_ipv4
xt_multiport
nft_compat
nft_counter
nf_tables
nfnetlink
psnap
llc
cpufreq_conservative
cpufreq_userspace
cpufreq_powersave
cmac
bnep
snd_hda_codec_hdmi
intel_rapl
arc4
x86_pkg_temp_thermal
intel_powerclamp
mei_wdt
btusb
btrtl
btbcm
binfmt_misc
btintel
coretemp
snd_hda_codec_realtek
nouveau
bluetooth
iwlmvm
snd_hda_codec_generic
ledtrig_audio
mac80211
kvm
uvcvideo
irqbypass
ttm
videobuf2_vmalloc
videobuf2_memops
intel_cstate
videobuf2_v4l2
snd_hda_intel
intel_uncore
videobuf2_common
drm_kms_helper
snd_hda_codec
iwlwifi
videodev
snd_hda_core
drbg
iTCO_wdt
tpm_infineon
hp_wmi
snd_hwdep
joydev
intel_rapl_perf
pcspkr
serio_raw
iTCO_vendor_support
rtsx_pci_ms
sparse_keymap
mxm_wmi
wmi_bmof
media
pcc_cpufreq
cfg80211
memstick
sg
drm
ansi_cprng
watchdog
snd_pcm
ecdh_generic
snd_timer
mei_me
ecc
snd
mei
rfkill
soundcore
i2c_algo_bit
ie31200_edac
tpm_tis
battery
tpm_tis_core
hp_accel
lis3lv02d
tpm
evdev
input_polldev
hp_wireless
rng_core
button
ac
parport_pc
ppdev
lp
parport
sunrpc
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
dm_crypt
dm_mod
sr_mod
cdrom
sd_mod
hid_apple
hid_generic
usbhid
hid
crct10dif_pclmul
crc32_pclmul
crc32c_intel
ghash_clmulni_intel
rtsx_pci_sdmmc
mmc_core
ahci
libahci
aesni_intel
libata
aes_x86_64
crypto_simd
cryptd
glue_helper
xhci_pci
xhci_hcd
scsi_mod
psmouse
rtsx_pci
ehci_pci
ehci_hcd
i2c_i801
lpc_ich
mfd_core
e1000e
usbcore
ptp
pps_core
usb_common
video
wmi

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor DRAM Controller [8086:0c04] (rev 06)
Subsystem: Hewlett-Packard Company Xeon E3-1200 v3/4th Gen Core 
Processor DRAM Controller [103c:2253]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel modules: ie31200_edac

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal 
decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset 
Family USB xHCI [8086:8c31] (rev 04) (prog-if 30 [XHCI])
Subsystem: Hewlett-Packard Company 8 Series/C220 Series Chipset Family 
USB xHCI [103c:2253]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
SERR- 
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci

00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series 
Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
Subsystem: Hewlett-Packard Company 8 Series/C220 Series Chipset Family 
MEI Controller [103c:2253]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: mei_me
Kernel modules: mei_me

00:16.3 Serial controller [0700]: Intel Corporation 8 Series/C220 Series 
Chipset Family KT Controller [8086:8c3d] (rev 04) (prog-if 02 [16550])
Subsystem: Hewlett-Packard Company 8 Series/C220 Series Chipset Family 
KT Controller [103c:2253]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
 

Bug#930527: linux-image-4.19.0-5-amd64: when logging out, not the whole screen is erased, leaving private information

[Vincent Lefevre]

Package: src:linux
Version: 4.19.37-3
Severity: grave
Tags: security
Justification: user security hole

When logging out, a part of the previous session is still visible.
This might be used to compromise the user's account or leak other
private information, depending on what was written on the screen.

-- Package-specific info:
** Version:
Linux version 4.19.0-5-amd64 (debian-kernel@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-7)) #1 SMP Debian 4.19.37-3 (2019-05-15)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 
root=UUID=e3631277-c4d0-460e-a2a3-6de16013e050 ro quiet

** Tainted: I (2048)
 * Working around severe firmware bug.

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

** Model information
sys_vendor: Hewlett-Packard
product_name: HP Z800 Workstation
product_version: 
chassis_vendor: Hewlett-Packard
chassis_version: 
bios_vendor: Hewlett-Packard
bios_version: 786G5 v01.17
board_vendor: Hewlett-Packard
board_name: 0AECh
board_version: 

** Loaded modules:
devlink
cpufreq_powersave
cpufreq_conservative
cpufreq_userspace
bnep
bluetooth
drbg
ansi_cprng
ecdh_generic
binfmt_misc
nfsd
auth_rpcgss
nfs_acl
nfs
lockd
grace
fscache
sunrpc
smsc47b397
loop
firewire_sbp2
parport_pc
ppdev
lp
parport
nft_counter
ip6_tables
nft_compat
nf_tables
x_tables
nfnetlink
nouveau
mxm_wmi
video
intel_powerclamp
coretemp
kvm_intel
ttm
snd_hda_codec_realtek
drm_kms_helper
snd_hda_codec_generic
kvm
snd_hda_intel
drm
snd_hda_codec
hp_wmi
i2c_algo_bit
sparse_keymap
snd_hda_core
rfkill
irqbypass
snd_hwdep
evdev
snd_pcm
wmi_bmof
wmi
snd_timer
sg
intel_cstate
intel_uncore
serio_raw
snd
iTCO_wdt
iTCO_vendor_support
i7core_edac
soundcore
pcc_cpufreq
button
acpi_cpufreq
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
crypto_simd
cryptd
glue_helper
aes_x86_64
hid_generic
usbhid
hid
sr_mod
cdrom
sd_mod
ahci
mptsas
libahci
firewire_ohci
mptscsih
mptbase
psmouse
libata
crc32c_intel
scsi_transport_sas
ehci_pci
uhci_hcd
firewire_core
ehci_hcd
crc_itu_t
tg3
lpc_ich
scsi_mod
usbcore
libphy
floppy
usb_common

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 5520 I/O Hub to ESI Port 
[8086:3406] (rev 13)
Subsystem: Hewlett-Packard Company 5520 I/O Hub to ESI Port [103c:130b]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:01.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express 
Root Port 1 [8086:3408] (rev 13) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:03.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express 
Root Port 3 [8086:340a] (rev 13) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:07.0 PCI bridge [0604]: Intel Corporation 5520/5500/X58 I/O Hub PCI Express 
Root Port 7 [8086:340e] (rev 13) (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B-
PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
Capabilities: 
Kernel driver in use: pcieport

00:10.0 PIC [0800]: Intel Corporation 7500/5520/5500/X58 Physical and Link 
Layer Registers Port 0 [8086:3425] (rev 13) (prog-if 00 [8259])
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 

00:10.1 PIC [0800]: Intel Corporation 7500/5520/5500/X58 Routing and Protocol 
Layer Registers Port 0 [8086:3426] (rev 13) (prog-if 00 [8259])
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 

00:11.1 PIC [0800]: Intel Corporation 7500/5520/5500 Routing & Protocol Layer 
Register Port 1 [8086:3428] (rev 13) (prog-if 00 [8259])
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: i7core_edac
Kernel modules: i7core_edac

Bug#924545: linux-image-4.19.0-4-amd64: many errors "PKCS#7 signature not signed with a trusted key"

[Vincent Lefevre]

Package: src:linux
Version: 4.19.28-1
Severity: important

With this new kernel, I get the following error 487 times!

  PKCS#7 signature not signed with a trusted key

cventin:~> journalctl -b | grep -c 'PKCS#7 signature not signed with a trusted 
key'
487

There were no such errors with previous kernels.

-- Package-specific info:
** Version:
Linux version 4.19.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 
8.3.0 (Debian 8.3.0-2)) #1 SMP Debian 4.19.28-1 (2019-03-12)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.0-4-amd64 
root=UUID=4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0 ro quiet

** Tainted: POE (12289)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded.

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

** Model information
sys_vendor: Dell Inc.
product_name: Precision Tower 7810
product_version: 01
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: A07
board_vendor: Dell Inc.
board_name: 0GWHMW
board_version: A00

** Loaded modules:
fuse(E)
intel_rapl(E)
sb_edac(E)
cpufreq_conservative(E)
cpufreq_userspace(E)
cpufreq_powersave(E)
x86_pkg_temp_thermal(E)
intel_powerclamp(E)
coretemp(E)
kvm_intel(E)
kvm(E)
irqbypass(E)
crct10dif_pclmul(E)
crc32_pclmul(E)
ghash_clmulni_intel(E)
snd_hda_codec_hdmi(E)
snd_hda_codec_realtek(E)
mei_wdt(E)
dcdbas(E)
snd_hda_codec_generic(E)
intel_cstate(E)
snd_hda_intel(E)
snd_hda_codec(E)
snd_hda_core(E)
snd_hwdep(E)
snd_pcm(E)
snd_timer(E)
mei_me(E)
snd(E)
intel_uncore(E)
iTCO_wdt(E)
dell_smm_hwmon(E)
nvidia_drm(POE)
pcspkr(E)
evdev(E)
sg(E)
mei(E)
iTCO_vendor_support(E)
soundcore(E)
intel_rapl_perf(E)
wmi(E)
button(E)
pcc_cpufreq(E)
drm_kms_helper(E)
drm(E)
nvidia_modeset(POE)
binfmt_misc(E)
nvidia(POE)
ipmi_devintf(E)
ipmi_msghandler(E)
ip_tables(E)
x_tables(E)
autofs4(E)
ext4(E)
crc16(E)
mbcache(E)
jbd2(E)
crc32c_generic(E)
fscrypto(E)
ecb(E)
hid_generic(E)
usbhid(E)
hid(E)
sd_mod(E)
sr_mod(E)
cdrom(E)
crc32c_intel(E)
xhci_pci(E)
ehci_pci(E)
ahci(E)
ata_generic(E)
aesni_intel(E)
xhci_hcd(E)
libahci(E)
aes_x86_64(E)
ehci_hcd(E)
crypto_simd(E)
libata(E)
cryptd(E)
usbcore(E)
glue_helper(E)
e1000e(E)
scsi_mod(E)
lpc_ich(E)
i2c_i801(E)
usb_common(E)

** Network interface configuration:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** 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: enp0s25:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
link/ether 98:90:96:bd:7f:f7 brd ff:ff:ff:ff:ff:ff
inet 140.77.13.17/23 brd 140.77.13.255 scope global dynamic noprefixroute 
enp0s25
   valid_lft 86094sec preferred_lft 86094sec
inet6 fe80::9a90:96ff:febd:7ff7/64 scope link noprefixroute 
   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:1926  18000 0  0 0 1926  
18000 0   0  0
enp0s25: 64500057347000 0  0   968   338037
3255000 0   0  0

*** Protocol statistics:
Ip:
Forwarding: 2
4674 total packets received
2 with invalid addresses
0 forwarded
0 incoming packets discarded
4665 incoming packets delivered
3252 requests sent out
80 dropped because of missing route
Icmp:
0 ICMP messages received
0 input ICMP message failed
ICMP input histogram:
0 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
Tcp:
82 active connection openings
1 passive connection openings
2 failed connection attempts
0 connection resets received
16 connections established
3073 segments received
2651 segments sent out
0 segments retransmitted
0 bad segments received
36 resets sent
Udp:
1116 packets received
0 packets to unknown port received
0 packet receive errors
601 packets sent
0 receive buffer errors
0 send buffer errors
IgnoredMulti: 476
UdpLite:
TcpExt:
25 TCP sockets finished time wait in fast timer
41 delayed acks sent
Quick ack mode was activated 13 times
1985 packet headers predicted
404 acknowledgments not containing data payload received
136 predicted acknowledgments
TCPDSACKOldSent: 13
15 connections reset due to unexpected data
TCPDeferAcceptDrop: 1
TCPRcvCoalesce: 614
TCPAutoCorking: 15
TCPOrigDataSent: 514
TCPKeepAlive: 231
TCPDelivered: 580
IpExt:
InMcastPkts: 521

Bug#922873: linux-image-4.19.0-3-amd64: nouveau "PGRAPH TLB flush idle timeout fail" errors, machine unresponsive via ssh

[Vincent Lefevre]

Package: src:linux
Version: 4.19.20-1
Severity: important
Tags: upstream
Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=93828

I get lots of errors with nouveau, and I assume that this is what
makes the machine unresponsive (via ssh):

Feb 21 15:01:30 ypig kernel: [  266.270272] nouveau :0f:00.0: gr: TRAP_M2MF 
0002 [IN]
Feb 21 15:01:30 ypig kernel: [  266.270329] nouveau :0f:00.0: gr: TRAP_M2MF 
00320251 007aaf80  04000430
Feb 21 15:01:30 ypig kernel: [  266.270336] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[2893]] subc 5 class 5039 mthd 0328 data 
Feb 21 15:01:30 ypig kernel: [  266.270355] nouveau :0f:00.0: fb: trapped 
read at 7aa000 on channel 2 [0fa41000 Xorg[2893]] engine 00 [PGRAPH] client 
03 [DISPATCH] subclient 04 [M2M_IN] reason 0002 [PAGE_NOT_PRESENT]
Feb 21 15:01:30 ypig kernel: [  266.271323] nouveau :0f:00.0: gr: TRAP_M2MF 
0002 [IN]
Feb 21 15:01:30 ypig kernel: [  266.271332] nouveau :0f:00.0: gr: TRAP_M2MF 
00320851 00a0f017  04000430
Feb 21 15:01:30 ypig kernel: [  266.271337] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[2893]] subc 5 class 5039 mthd 0328 data 
Feb 21 15:01:30 ypig kernel: [  266.271352] nouveau :0f:00.0: fb: trapped 
read at a12000 on channel 2 [0fa41000 Xorg[2893]] engine 00 [PGRAPH] client 
03 [DISPATCH] subclient 04 [M2M_IN] reason 0002 [PAGE_NOT_PRESENT]
Feb 21 15:01:30 ypig kernel: [  266.271678] nouveau :0f:00.0: gr: magic set 
0:
Feb 21 15:01:30 ypig kernel: [  266.271684] nouveau :0f:00.0: gr:   
00408904: 20084e0a
Feb 21 15:01:30 ypig kernel: [  266.271688] nouveau :0f:00.0: gr:   
00408908: 00217d7f
Feb 21 15:01:30 ypig kernel: [  266.271691] nouveau :0f:00.0: gr:   
0040890c: 4430
Feb 21 15:01:30 ypig kernel: [  266.271695] nouveau :0f:00.0: gr:   
00408910: 4100
Feb 21 15:01:30 ypig kernel: [  266.271699] nouveau :0f:00.0: gr: 
TRAP_TEXTURE - TP0: 0003 [ FAULT]
Feb 21 15:01:30 ypig kernel: [  266.271704] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[2893]] subc 3 class 8297 mthd 15e0 data 
Feb 21 15:01:30 ypig kernel: [  266.271716] nouveau :0f:00.0: fb: trapped 
read at 00217d7f00 on channel 2 [0fa41000 Xorg[2893]] engine 00 [PGRAPH] client 
0a [TEXTURE] subclient 00 [] reason 0002 [PAGE_NOT_PRESENT]
Feb 21 15:01:30 ypig kernel: [  266.276860] nouveau :0f:00.0: gr: TRAP_M2MF 
0004 [OUT]
Feb 21 15:01:30 ypig kernel: [  266.276872] nouveau :0f:00.0: gr: TRAP_M2MF 
00340041 00a44400  05000430
Feb 21 15:01:30 ypig kernel: [  266.276877] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[2893]] subc 5 class 5039 mthd 0328 data 
Feb 21 15:01:30 ypig kernel: [  266.276890] nouveau :0f:00.0: fb: trapped 
write at 63ffdaa863 on channel 2 [0fa41000 Xorg[2893]] engine 00 [PGRAPH] 
client 03 [DISPATCH] subclient 05 [M2M_OUT] reason  [PT_NOT_PRESENT]
Feb 21 15:01:30 ypig kernel: [  266.277131] nouveau :0f:00.0: gr: TRAP_M2MF 
0002 [IN]
Feb 21 15:01:30 ypig kernel: [  266.277140] nouveau :0f:00.0: gr: TRAP_M2MF 
00320851 00a5e042  04000430
Feb 21 15:01:30 ypig kernel: [  266.277146] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[2893]] subc 5 class 5039 mthd 0328 data 
Feb 21 15:01:30 ypig kernel: [  266.277159] nouveau :0f:00.0: fb: trapped 
read at a6 on channel 2 [0fa41000 Xorg[2893]] engine 00 [PGRAPH] client 
03 [DISPATCH] subclient 04 [M2M_IN] reason 0002 [PAGE_NOT_PRESENT]
Feb 21 15:01:31 ypig kernel: [  267.271267] nouveau :0f:00.0: gr: TRAP_M2MF 
0002 [IN]
Feb 21 15:01:31 ypig kernel: [  267.271279] nouveau :0f:00.0: gr: TRAP_M2MF 
00320251 00718f80  04000430
Feb 21 15:01:31 ypig kernel: [  267.271287] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[2893]] subc 5 class 5039 mthd 0328 data 
Feb 21 15:01:31 ypig kernel: [  267.271305] nouveau :0f:00.0: fb: trapped 
read at 718000 on channel 2 [0fa41000 Xorg[2893]] engine 00 [PGRAPH] client 
03 [DISPATCH] subclient 04 [M2M_IN] reason 0002 [PAGE_NOT_PRESENT]
Feb 21 15:01:32 ypig kernel: [  268.272058] nouveau :0f:00.0: gr: TRAP_M2MF 
0002 [IN]
Feb 21 15:01:32 ypig kernel: [  268.272103] nouveau :0f:00.0: gr: TRAP_M2MF 
00320251 00672f80  04000430
Feb 21 15:01:32 ypig kernel: [  268.272109] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[2893]] subc 5 class 5039 mthd 0328 data 
Feb 21 15:01:32 ypig kernel: [  268.272126] nouveau :0f:00.0: fb: trapped 
read at 672000 on channel 2 [0fa41000 Xorg[2893]] engine 00 [PGRAPH] client 
03 [DISPATCH] subclient 04 [M2M_IN] reason 0002 [PAGE_NOT_PRESENT]
Feb 21 15:01:32 ypig kernel: [  268.273313] nouveau :0f:00.0: gr: TRAP_M2MF 
0002 [IN]
Feb 21 15:01:32 ypig kernel: [  268.273323] nouveau :0f:00.0: gr: TRAP_M2MF 
003209d1 00a29fa0  04000430
Feb 21 15:01:32 

Bug#914967: linux-image-4.18.0-3-amd64: errors "Failed to get unique processor _UID"

[Vincent Lefevre]

On 2019-01-11 11:17:03 -0500, Benjamin Redelings wrote:
> Package: src:linux
> Version: 4.18.20-2
> Followup-For: Bug #914967
> 
> Dear Maintainer,
> 
> Starting with package 4.18.0-3, my computer fails to finish booting.  I see 
> the message
> 
> acpi LNXCPU:bf: Failed to get unique processor _UID (0xff)
> 
> repeated many times (the bf seems to be a hexadecimal counter).

This is unrelated to the boot failure.

[...]
> board_name: X99 Extreme4/3.1
[...]

You're affected by the udev bug for the X99 chipset. See

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918322

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#918096: linux-image-4.19.0-1-amd64: disk and keyboard do not work - unusable even in recovery mode

[Vincent Lefevre]

Note: I have the same issue with the 4.9 kernel from stable, which
I have just installed, so that initrd.img-4.9.0-8-amd64 is recent
(this might matter).

See also bug 917607 (I get the same error), reported against udev.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#898814: When I log in, it hangs until crng init done

[Vincent Lefevre]

On 2018-12-14 11:23:39 +0100, Vincent Lefevre wrote:
> Interesting. On a machine where I have no such issues, I can see
> in journalctl info at shutdown:
> 
> Dec 13 15:44:14 zira systemd[1]: Stopping Load/Save Random Seed...
> [...]
> Dec 13 15:44:14 zira systemd[1]: Stopped Load/Save Random Seed.
> 
> but no such lines on a machine where the issue is present.

Sorry, I have these lines on both machines (I forgot the -1
after "journalctl -b" on one of the machines).

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#898814: When I log in, it hangs until crng init done

[Vincent Lefevre]

On 2018-12-14 10:24:51 +0100, Yves-Alexis Perez wrote:
> Something puzzles me with all those issues: as far as I can tell, on most
> install, systemd-random-seed.service should save a seed at shutdown and
> restore it at startup, and this (I think) should be enough to properly init
> the RNG.
> 
> Can you check if the service has been run in your case?

Interesting. On a machine where I have no such issues, I can see
in journalctl info at shutdown:

Dec 13 15:44:14 zira systemd[1]: Stopping Load/Save Random Seed...
[...]
Dec 13 15:44:14 zira systemd[1]: Stopped Load/Save Random Seed.

but no such lines on a machine where the issue is present.

Any idea of the cause of the difference?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#914967: linux-image-4.18.0-3-amd64: errors "Failed to get unique processor _UID"

[Vincent Lefevre]

Package: src:linux
Version: 4.18.20-2
Severity: normal

I get the following errors at boot time:

Nov 29 09:04:20 cventin kernel: acpi LNXCPU:06: Failed to get unique processor 
_UID (0xff)
Nov 29 09:04:20 cventin kernel: acpi LNXCPU:07: Failed to get unique processor 
_UID (0xff)
Nov 29 09:04:20 cventin kernel: acpi LNXCPU:08: Failed to get unique processor 
_UID (0xff)
Nov 29 09:04:20 cventin kernel: acpi LNXCPU:09: Failed to get unique processor 
_UID (0xff)
Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0a: Failed to get unique processor 
_UID (0xff)
Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0b: Failed to get unique processor 
_UID (0xff)
Nov 29 09:04:20 cventin kernel: acpi LNXCPU:0c: Failed to get unique processor 
_UID (0xff)
[...]
Nov 29 09:04:21 cventin kernel: acpi LNXCPU:8f: Failed to get unique processor 
_UID (0xff)

There were no such errors before linux-image-4.18.0-3-amd64.

-- Package-specific info:
** Version:
Linux version 4.18.0-3-amd64 (debian-kernel@lists.debian.org) (gcc version 
7.3.0 (Debian 7.3.0-30)) #1 SMP Debian 4.18.20-2 (2018-11-23)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.18.0-3-amd64 
root=UUID=4bcb3bbd-f516-4ddf-be96-6fa3a8cdc8a0 ro quiet

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

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

** Model information
sys_vendor: Dell Inc.
product_name: Precision Tower 7810
product_version: 01
chassis_vendor: Dell Inc.
chassis_version: 
bios_vendor: Dell Inc.
bios_version: A07
board_vendor: Dell Inc.
board_name: 0GWHMW
board_version: A00

** Loaded modules:
btrfs
zstd_compress
zstd_decompress
xxhash
xor
raid6_pq
ufs
qnx4
hfsplus
hfs
minix
ntfs
vfat
msdos
fat
jfs
xfs
libcrc32c
dm_mod
fuse
cpufreq_conservative
cpufreq_userspace
cpufreq_powersave
snd_hda_codec_hdmi
intel_rapl
sb_edac
x86_pkg_temp_thermal
intel_powerclamp
coretemp
kvm_intel
dcdbas
kvm
dell_smm_hwmon
irqbypass
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
intel_cstate
intel_uncore
intel_rapl_perf
snd_hda_codec_realtek
pcspkr
snd_hda_codec_generic
evdev
snd_hda_intel
snd_hda_codec
snd_hda_core
snd_hwdep
snd_pcm
snd_timer
sg
iTCO_wdt
snd
iTCO_vendor_support
soundcore
mei_me
mei
wmi
pcc_cpufreq
button
nvidia_drm(PO)
drm_kms_helper
drm
binfmt_misc
nvidia_modeset(PO)
nvidia(PO)
ipmi_devintf
ipmi_msghandler
ip_tables
x_tables
autofs4
ext4
crc16
mbcache
jbd2
crc32c_generic
fscrypto
ecb
hid_generic
usbhid
hid
sd_mod
sr_mod
cdrom
crc32c_intel
xhci_pci
ahci
aesni_intel
libahci
ata_generic
ehci_pci
aes_x86_64
xhci_hcd
ehci_hcd
crypto_simd
libata
cryptd
glue_helper
usbcore
i2c_i801
lpc_ich
e1000e
scsi_mod
usb_common

** Network interface configuration:

source /etc/network/interfaces.d/*

auto lo
iface lo inet loopback

** 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: enp0s25:  mtu 1500 qdisc pfifo_fast state 
UP group default qlen 1000
link/ether 98:90:96:bd:7f:f7 brd ff:ff:ff:ff:ff:ff
inet 140.77.13.17/23 brd 140.77.13.255 scope global dynamic noprefixroute 
enp0s25
   valid_lft 85572sec preferred_lft 85572sec
inet6 fe80::9a90:96ff:febd:7ff7/64 scope link noprefixroute 
   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:1792  16000 0  0 0 1792  
16000 0   0  0
enp0s25: 45156846758000 0  0  1813   461103
2924000 0   0  0

*** Protocol statistics:
Ip:
Forwarding: 2
4530 total packets received
2 with invalid addresses
0 forwarded
0 incoming packets discarded
4527 incoming packets delivered
2886 requests sent out
104 dropped because of missing route
Icmp:
0 ICMP messages received
0 input ICMP message failed
ICMP input histogram:
0 ICMP messages sent
0 ICMP messages failed
ICMP output histogram:
Tcp:
107 active connection openings
1 passive connection openings
1 failed connection attempts
1 connection resets received
10 connections established
2074 segments received
2242 segments sent out
22 segments retransmitted
1 bad segments received
57 resets sent
Udp:
1498 packets received
0 packets to unknown port received
0 packet receive errors
654 packets sent
0 receive buffer errors
0 send buffer errors
IgnoredMulti: 955
UdpLite:
TcpExt:
52 TCP sockets finished time wait in fast timer
60 delayed acks sent
 

Bug#904770: linux-image-4.17.0-1-amd64: sudden machine reboot - bug in nouveau?

[Vincent Lefevre]

Package: src:linux
Version: 4.17.8-1
Severity: grave
Justification: causes non-serious data loss

The machine suddenly rebooted. In the syslog file, I could see:

[...]
Jul 27 18:28:59 ypig kernel: [  158.220214] nouveau :0f:00.0: gr: TRAP_M2MF 
0004 [OUT]
Jul 27 18:28:59 ypig kernel: [  158.220224] nouveau :0f:00.0: gr: TRAP_M2MF 
00340241 011e8f80  05000430
Jul 27 18:28:59 ypig kernel: [  158.220229] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[3169]] subc 0 class 5039 mthd 0328 data 
Jul 27 18:28:59 ypig kernel: [  158.220247] nouveau :0f:00.0: fb: trapped 
write at 00011e8000 on channel 2 [0fa41000 Xorg[3169]] engine 00 [PGRAPH] 
client 03 [DISPATCH] subclient 05 [M2M_OUT] reason 0002 [PAGE_NOT_PRESENT]
Jul 27 18:29:00 ypig kernel: [  159.223768] nouveau :0f:00.0: gr: TRAP_M2MF 
0004 [OUT]
Jul 27 18:29:00 ypig kernel: [  159.223781] nouveau :0f:00.0: gr: TRAP_M2MF 
00340241 00ddef80  05000430
Jul 27 18:29:00 ypig kernel: [  159.223788] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[3169]] subc 0 class 5039 mthd 0328 data 
Jul 27 18:29:00 ypig kernel: [  159.223809] nouveau :0f:00.0: fb: trapped 
write at dde000 on channel 2 [0fa41000 Xorg[3169]] engine 00 [PGRAPH] 
client 03 [DISPATCH] subclient 05 [M2M_OUT] reason 0002 [PAGE_NOT_PRESENT]
Jul 27 18:29:00 ypig kernel: [  159.231778] nouveau :0f:00.0: gr: TRAP_M2MF 
0002 [IN]
Jul 27 18:29:00 ypig kernel: [  159.231790] nouveau :0f:00.0: gr: TRAP_M2MF 
00320251 00434f80  04000430
Jul 27 18:29:00 ypig kernel: [  159.231797] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[3169]] subc 0 class 5039 mthd 023c data 
Jul 27 18:29:00 ypig kernel: [  159.231815] nouveau :0f:00.0: fb: trapped 
read at 434000 on channel 2 [0fa41000 Xorg[3169]] engine 00 [PGRAPH] client 
03 [DISPATCH] subclient 04 [M2M_IN] reason 0002 [PAGE_NOT_PRESENT]
Jul 27 18:29:00 ypig kernel: [  159.231832] nouveau :0f:00.0: gr: TRAP_M2MF 
0002 [IN]
Jul 27 18:29:00 ypig kernel: [  159.231840] nouveau :0f:00.0: gr: TRAP_M2MF 
00320151 0900  0400
Jul 27 18:29:00 ypig kernel: [  159.231846] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[3169]] subc 0 class 5039 mthd 0328 data 
Jul 27 18:29:01 ypig kernel: [  160.223514] nouveau :0f:00.0: gr: TRAP_M2MF 
0002 [IN]
Jul 27 18:29:01 ypig kernel: [  160.223527] nouveau :0f:00.0: gr: TRAP_M2MF 
00320251 00862f80  04000430
Jul 27 18:29:01 ypig kernel: [  160.223534] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[3169]] subc 0 class 5039 mthd 0328 data 
Jul 27 18:29:01 ypig kernel: [  160.223552] nouveau :0f:00.0: fb: trapped 
read at 862000 on channel 2 [0fa41000 Xorg[3169]] engine 00 [PGRAPH] client 
03 [DISPATCH] subclient 04 [M2M_IN] reason 0002 [PAGE_NOT_PRESENT]
Jul 27 18:29:02 ypig kernel: [  161.226353] nouveau :0f:00.0: gr: TRAP_M2MF 
0002 [IN]
Jul 27 18:29:02 ypig kernel: [  161.226365] nouveau :0f:00.0: gr: TRAP_M2MF 
00320251 004d4f80  04000430
Jul 27 18:29:02 ypig kernel: [  161.226372] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[3169]] subc 0 class 5039 mthd 0328 data 
Jul 27 18:29:02 ypig kernel: [  161.226390] nouveau :0f:00.0: fb: trapped 
read at 4d4000 on channel 2 [0fa41000 Xorg[3169]] engine 00 [PGRAPH] client 
03 [DISPATCH] subclient 04 [M2M_IN] reason 0002 [PAGE_NOT_PRESENT]
Jul 27 18:29:02 ypig kernel: [  161.228866] nouveau :0f:00.0: gr: TRAP_M2MF 
0004 [OUT]
Jul 27 18:29:02 ypig kernel: [  161.228878] nouveau :0f:00.0: gr: TRAP_M2MF 
00340241 008e8f80  05000430
Jul 27 18:29:02 ypig kernel: [  161.228885] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[3169]] subc 0 class 5039 mthd 0328 data 
Jul 27 18:29:02 ypig kernel: [  161.228906] nouveau :0f:00.0: fb: trapped 
write at 8e8000 on channel 2 [0fa41000 Xorg[3169]] engine 00 [PGRAPH] 
client 03 [DISPATCH] subclient 05 [M2M_OUT] reason 0002 [PAGE_NOT_PRESENT]
Jul 27 18:29:03 ypig kernel: [  162.227756] nouveau :0f:00.0: gr: TRAP_M2MF 
0002 [IN]
Jul 27 18:29:03 ypig kernel: [  162.227769] nouveau :0f:00.0: gr: TRAP_M2MF 
00320251 00510f80  04000430
Jul 27 18:29:03 ypig kernel: [  162.227776] nouveau :0f:00.0: gr: 0020 
[] ch 2 [000fa41000 Xorg[3169]] subc 0 class 5039 mthd 0328 data 
Jul 27 18:29:03 ypig kernel: [  162.227794] nouveau :0f:00.0: fb: trapped 
read at 51 on channel 2 [0fa41000 Xorg[3169]] engine 00 [PGRAPH] client 
03 [DISPATCH] subclient 04 [M2M_IN] reason 0002 [PAGE_NOT_PRESENT]
Jul 27 18:29:03 ypig kernel: [  162.230832] nouveau :0f:00.0: gr: TRAP_M2MF 
0004 [OUT]
Jul 27 18:29:03 ypig kernel: [  162.230844] nouveau :0f:00.0: gr: TRAP_M2MF 
00340241 011b0f80  05000430
Jul 27 18:29:03 ypig kernel: [  162.230851] nouveau 

Bug#898814: When I log in, it hangs until crng init done

[Vincent Lefevre]

On 2018-05-16 14:55:07 +0800, 積丹尼 Dan Jacobson wrote:
> I am also experiencing:
> https://unix.stackexchange.com/questions/442698/when-i-log-in-it-hangs-until-crng-init-done

I have the same problem (when logging via lightdm).

One of the answers says "Apparently updating util-linux 2.32 should
fix the issue" but this is not true since I have util-linux 2.32-0.1.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Vincent Lefevre]

On 2018-07-15 04:27:39 +0100, Ben Hutchings wrote:
> On Sun, 2018-07-15 at 02:27 +0200, Vincent Lefevre wrote:
> > Package: src:linux
> > Version: 4.9.110-1
> > Severity: critical
> > Justification: breaks the whole system
> > 
> > After upgrade to Debian 9.5, I get a kernel panic with 4.9.0-7-amd64:
> [...]
> 
> Are you running it on Xen?

Yes.

-- 
Vincent Lefèvre  - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#903800: linux-image-4.9.0-7-amd64: general protection fault / kernel panic at boot

[Vincent Lefevre]

Package: src:linux
Version: 4.9.110-1
Severity: critical
Justification: breaks the whole system

After upgrade to Debian 9.5, I get a kernel panic with 4.9.0-7-amd64:

Loading Linux 4.9.0-7-amd64 ...
Loading initial ramdisk ...
[0.00] tsc: Unable to calibrate against PIT 17.14MiB  100%  7.83MiB/s ]
[0.108076] cpu 0 spinlock event irq 1
[0.109159] NMI watchdog: disabled (cpu0): hardware events not enabled
[0.183214] cpu 1 spinlock event irq 13
[0.184264] cpu 2 spinlock event irq 20
[0.184635] cpu 3 spinlock event irq 27
[0.184635] cpu 4 spinlock event irq 34
[0.184635] cpu 5 spinlock event irq 41
[0.188556] cpu 6 spinlock event irq 48
[0.188556] cpu 7 spinlock event irq 55
[0.188575] cpu 8 spinlock event irq 62
[0.188575] cpu 9 spinlock event irq 69
[0.192561] cpu 10 spinlock event irq 76
[0.192561] cpu 11 spinlock event irq 83
[0.192562] cpu 12 spinlock event irq 90
[0.196098] cpu 13 spinlock event irq 97
[0.196564] cpu 14 spinlock event irq 104
[0.196564] cpu 15 spinlock event irq 111
[0.201020] Grant table initialized
[0.708216] dmi: Firmware registration failed.
[0.708728] PCI: System does not support PCI
[0.709146] PCI: System does not support PCI
[2.161040] dmi-sysfs: dmi entry is absent.
[2.161725] mce: Unable to init device /dev/mcelog (rc: -5)
[2.183556] general protection fault:  [#1] SMP
[2.183799] Modules linked in:
[2.183955] CPU: 0 PID: 1 Comm: init Not tainted 4.9.0-7-amd64 #1 Debian 
4.9.110-1
[2.184010] task: 88001e6a3040 task.stack: c900400cc000
[2.184010] RIP: e030:[]  [] 
ret_from_fork+0x2d/0x70
[2.184010] RSP: e02b:c900400cff50  EFLAGS: 00010006
[2.184010] RAX: 000c5cc9b000 RBX: 816076d0 RCX: ea794b1f
[2.184010] RDX: 0002 RSI: 0002 RDI: c900400cff58
[2.184010] RBP:  R08:  R09: 880003073000
[2.184010] R10: 8080808080808080 R11: fefefefefefefeff R12: 
[2.184010] R13:  R14:  R15: 
[2.184010] FS:  () GS:88001ea0() 
knlGS:
[2.184010] CS:  e033 DS:  ES:  CR0: 80050033
[2.184010] CR2: 7ffd02276609 CR3: 0309a000 CR4: 00042660
[2.184010] Stack:
[2.184010]     

[2.184010]     

[2.184010]     

[2.184010] Call Trace:
[2.184010] Code: c7 e8 b8 fe a8 ff 48 85 db 75 2f 48 89 e7 e8 5b ed 9e ff 
50 90 0f 20 d8 65 48 0b 04 25 e0 02 01 00 78 08 65 88 04 25 e7 02 01 00 <0f> 22 
d8 58 66 0f 1f 44 00 00 e9 c1 07 00 00 4c 89 e7 eb 11 e8 
[2.184010] RIP  [] ret_from_fork+0x2d/0x70
[2.184010]  RSP 
[2.184010] ---[ end trace 4b76af717f0b50cf ]---
[2.190717] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x000b
[2.190717] 
[2.191083] Kernel Offset: disabled

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

** Model information

** Network interface configuration:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 155.133.131.76
netmask 255.255.255.0
gateway 155.133.131.254

** PCI devices:
not available

** USB devices:
not available


-- System Information:
Debian Release: 9.5
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages linux-image-4.9.0-7-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod23-2
ii  linux-base  4.5

Versions of packages linux-image-4.9.0-7-amd64 recommends:
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2.3

Versions of packages linux-image-4.9.0-7-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.02~beta3-5
pn  linux-doc-4.9   

Versions of packages linux-image-4.9.0-7-amd64 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  

Bug#887061: linux-image-4.9.0-5-amd64: KPTI (kaiser.c): please, no silent disable for Xen guests

[Vincent Lefevre]

Package: src:linux
Version: 4.9.65-3+deb9u2
Severity: wishlist

Hi,

My VM is a Xen guest, and I was confused not to find any information
about KPTI in the kernel logs. This is due to the silent_disable
case here:

In arch/x86/mm/kaiser.c:

void __init kaiser_check_boottime_disable(void)
{
[...]
if (boot_cpu_has(X86_FEATURE_XENPV))
goto silent_disable;
[...]
disable:
pr_info("disabled\n");

silent_disable:
kaiser_enabled = 0;
setup_clear_cpu_cap(X86_FEATURE_KAISER);
}

It would be better to have some logs, saying that it is disabled and
why (Xen PV).

-- Package-specific info:
** Version:
Linux version 4.9.0-5-amd64 (debian-kernel@lists.debian.org) (gcc version 6.3.0 
20170516 (Debian 6.3.0-18) ) #1 SMP Debian 4.9.65-3+deb9u2 (2018-01-04)

** Command line:
root=UUID=2ae1ff60-aeb0-4d39-8a98-ff98d5f63f7e ro console=ttyS0 console=hvc0 
nomce loglevel=5 net.ifnames=0

** Not tainted

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

** Model information

** Loaded modules:
ipt_REJECT
nf_reject_ipv4
xt_multiport
iptable_filter
evdev
pcspkr
intel_rapl
sb_edac
edac_core
x86_pkg_temp_thermal
coretemp
crct10dif_pclmul
crc32_pclmul
ghash_clmulni_intel
intel_rapl_perf
ip_tables
x_tables
autofs4
ext4
crc16
jbd2
crc32c_generic
fscrypto
ecb
mbcache
crc32c_intel
aesni_intel
xen_netfront
xen_blkfront
aes_x86_64
glue_helper
lrw
gf128mul
ablk_helper
cryptd

** PCI devices:
not available

** USB devices:
not available


-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages linux-image-4.9.0-5-amd64 depends on:
ii  initramfs-tools [linux-initramfs-tool]  0.130
ii  kmod23-2
ii  linux-base  4.5

Versions of packages linux-image-4.9.0-5-amd64 recommends:
ii  firmware-linux-free  3.4
ii  irqbalance   1.1.0-2.3

Versions of packages linux-image-4.9.0-5-amd64 suggests:
pn  debian-kernel-handbook  
ii  grub-efi-amd64  2.02~beta3-5
pn  linux-doc-4.9   

Versions of packages linux-image-4.9.0-5-amd64 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

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#869511: dependency on linux-headers-*-common

[Vincent Lefevre]

On 2017-08-13 23:36:53 +0200, Vincent Lefevre wrote:
> On 2017-08-13 14:40:12 -0600, Gustavo Castro wrote:
> > The "linux-headers-4.11.0-2-common" fault is uncorrected?
> 
> Not on my machine. It is still not possible to upgrade.

I assume that since this bug has been closed and marked as fixed
in linux/4.12.6-1, I assume that the linux-*-4.11.0-2-* packages
will never be fixed. So, I've reported a bug against
linux-image-amd64, so that it depends on linux-image-4.12.0-1-amd64
ASAP.

-- 
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#872055: linux-image-amd64: depends on a package that is no longer installable

[Vincent Lefevre]

On 2017-08-13 23:49:21 +0200, Vincent Lefevre wrote:
> linux-image-amd64 depends on linux-image-4.11.0-2-amd64, which is
> no longer installable (bug 869511). But since this bug 869511 has
> been fixed in linux/4.12.6-1 only and has been closed, it seems
> that linux-image-4.11.0-2-amd64 will never be fixed, and that
> linux-image-amd64 should depend on linux-image-4.12.0-1-amd64
> (already available) ASAP.

Actually that the corresponding headers file that it no longer
installable. But this file is needed by many users to be able
to build some drivers...

-- 
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#872055: linux-image-amd64: depends on a package that is no longer installable

[Vincent Lefevre]

Package: linux-image-amd64
Version: 4.11+83
Severity: grave
Justification: renders package unusable

linux-image-amd64 depends on linux-image-4.11.0-2-amd64, which is
no longer installable (bug 869511). But since this bug 869511 has
been fixed in linux/4.12.6-1 only and has been closed, it seems
that linux-image-4.11.0-2-amd64 will never be fixed, and that
linux-image-amd64 should depend on linux-image-4.12.0-1-amd64
(already available) ASAP.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing'), 
(500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.11.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=POSIX 
(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.11.0-2-amd64  4.11.11-1

linux-image-amd64 recommends no packages.

linux-image-amd64 suggests no packages.

-- no debconf information

Bug#869511: dependency on linux-headers-*-common

[Vincent Lefevre]

On 2017-08-13 14:40:12 -0600, Gustavo Castro wrote:
> The "linux-headers-4.11.0-2-common" fault is uncorrected?

Not on my machine. It is still not possible to upgrade.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

On 2017-01-11 17:40:09 +, Ben Hutchings wrote:
> On Wed, 2017-01-11 at 16:20 +0100, Vincent Lefevre wrote:
> > On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
> > > Unless you can show that some data had been written *and flushed* to
> > > disk by the application, but was not readable afterward - this does not
> > > count.  Writes are buffered, and user space has to deal with that.
> > 
> > If I understand the journalctl log correctly, the system does
> > a power off without a clean shutdown:
> 
> Sorry, I didn't understand what you were trying to point out in the
> system log.  I had thought that pressing the power button was causing
> an immediate power-off, but you're showing me that it results in a
> resume immediately followed by a software-controlled shutdown.  Right?

Yes, this is what seems to appear from the logs.

> It seems like there are two separate bugs:
> 
> 1. Power button resumes and also generates a power-off input event
> (kernel bug)
> 2. Some writes not flushed to disk during shutdown (probably a kernel
> bug, but systemd could potentially break this)

Bug 850959. Hmm... no shutdown or the journald log is truncated
for the same reason.

-- 
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

On 2017-01-11 18:36:30 +0100, Michael Biebl wrote:
> Am 11.01.2017 um 18:28 schrieb Michael Biebl:
> > Am 11.01.2017 um 18:25 schrieb Vincent Lefevre:
> >> On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
> >>> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
> >>>> Why is this no normal shutdown?
> >>
> >> Services are not stopped as usual.
> > 
> > How do you conclude that?

There is no log for stopped services in the journald logs.

> And if something is killing the power midway through the shutdown
> process, it's hardly something systemd can do about.

What would kill the power?

> That said, so far this bug report is lacking crucial information why
> this is supposed to be a systemd bug,

What info do you need?

> even more a grave one.

There is file corruption (not just theoretical, it really happened
in practice).

-- 
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

On 2017-01-11 18:09:51 +0100, Michael Biebl wrote:
> Am 11.01.2017 um 18:05 schrieb Michael Biebl:
> > Why is this no normal shutdown?

Services are not stopped as usual.

> > Did you actually have a file corruption?

Yes, /var/log/monit.log, which got null bytes in it, and some
other file created my monit, which was empty (thus invalid).

> And why is this a systemd bug?

I assumed that this was systemd as it decided to power off the
machine: "systemd-logind[803]: Powering Off...". Otherwise, which
part is responsible for the shutdown?

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

Control: clone -1 -2
Control: reassign -2 systemd 232-8
Control: retitle -2 systemd: power off without always a normal shutdown when 
resuming after suspend with the power button
Control: severity -2 grave

as the lack of shutdown yields visible file corruption and potentially
data loss.

On 2017-01-11 16:20:35 +0100, Vincent Lefevre wrote:
> On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
> > Unless you can show that some data had been written *and flushed* to
> > disk by the application, but was not readable afterward - this does not
> > count.  Writes are buffered, and user space has to deal with that.
> 
> If I understand the journalctl log correctly, the system does
> a power off without a clean shutdown:
> 
> [...]
> Dec 23 10:51:01 zira systemd-logind[803]: Powering Off...
> Dec 23 10:51:01 zira systemd-logind[803]: System is powering down.
> Dec 23 10:51:01 zira systemd[1]: Stopping Manage, Install and Generate Color 
> Pro
> 
> then nothing after that!!! This is where the problem is, not in the
> application, which cannot know when the machine will power off.

Well, there are two problems:

1. The fact that the system powers down instead of just resuming.
   systemd-logind reports "Power key pressed." but the power key
   was used to resume, so that I suppose that systemd-logind
   should have never seen this.

2. The fact that the system is powered off immediately without a
   clean shutdown. When I use the power button to power off the
   laptop, I get:

Sep 17 19:36:13 zira systemd-logind[17281]: Power key pressed.
Sep 17 19:36:13 zira systemd-logind[17281]: Powering Off...
Sep 17 19:36:13 zira systemd-logind[17281]: System is powering down.
Sep 17 19:36:13 zira systemd[1]: Stopped target Bluetooth.
Sep 17 19:36:13 zira systemd[1]: Stopping Session 2041 of user vinc17.
Sep 17 19:36:13 zira systemd[1]: Deactivating swap /dev/disk/by-id/dm-uuid-LVM-K
Sep 17 19:36:13 zira systemd[1]: Stopping Disk Manager...
[...]

i.e. a normal shutdown, but when this is used just after a suspend
in order to resume, I *occasionally* get (well, this occurred only
twice):

Jul 25 17:15:17 zira systemd-logind[769]: Power key pressed.
Jul 25 17:15:17 zira systemd-logind[769]: Powering Off...
Jul 25 17:15:17 zira systemd-logind[769]: System is powering down.
-- Reboot --

Dec 23 10:51:01 zira systemd-logind[803]: Power key pressed.
Dec 23 10:51:01 zira systemd-logind[803]: Powering Off...
Dec 23 10:51:01 zira systemd-logind[803]: System is powering down.
Dec 23 10:51:01 zira systemd[1]: Stopping Manage, Install and Generate Color Pro
-- Reboot --

No normal shutdown!

-- 
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

On 2017-01-11 15:09:49 +, Ben Hutchings wrote:
> Unless you can show that some data had been written *and flushed* to
> disk by the application, but was not readable afterward - this does not
> count.  Writes are buffered, and user space has to deal with that.

If I understand the journalctl log correctly, the system does
a power off without a clean shutdown:

[...]
Dec 23 10:51:01 zira systemd-logind[803]: Powering Off...
Dec 23 10:51:01 zira systemd-logind[803]: System is powering down.
Dec 23 10:51:01 zira systemd[1]: Stopping Manage, Install and Generate Color Pro

then nothing after that!!! This is were the problem is, not in the
application, which cannot know when the machine will power off.

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

Control: severity -1 grave

because it can corrupt files.

When this occurred on December 23, the log file of monit got
corrupted:

[CET Dec 22 07:35:07] info : 'zira' Monit reloaded
[CET Dec 22 07:35:07] error: Queued event file: unable to read event size 
-- end of file
[CET Dec 23 10:51:01] error: 'eth0' link down
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@[CET
 Dec 23 10:52:10] info : Starting Monit 5.20.0 daemon
[CET Dec 23 10:52:10] info : 'zira' Monit 5.20.0 started
[...]

And from journalctl:

[...]
Dec 23 10:51:01 zira kernel: PM: Finishing wakeup.
Dec 23 10:51:01 zira kernel: Restarting tasks ... 
Dec 23 10:51:01 zira kernel: acpi PNP0501:00: Still not present
Dec 23 10:51:01 zira kernel: done.
Dec 23 10:51:01 zira kernel: pci_bus :02: Allocating resources
Dec 23 10:51:01 zira kernel: pci_bus :3b: Allocating resources
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: bridge window [io  
0x1000-0x0fff] to [bus 5f] add_size 1000
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: res[13]=[io  0x1000-0x0fff] 
res_to_dev_res add_size 1000 min_align 1000
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: res[13]=[io  0x1000-0x1fff] 
res_to_dev_res add_size 1000 min_align 1000
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: BAR 13: no space for [io  
size 0x1000]
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: BAR 13: failed to assign 
[io  size 0x1000]
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: BAR 13: no space for [io  
size 0x1000]
Dec 23 10:51:01 zira kernel: pcieport :3c:03.0: BAR 13: failed to assign 
[io  size 0x1000]
Dec 23 10:51:01 zira kernel: Bluetooth: hci0: read Intel version: 
370710018002030d00
Dec 23 10:51:01 zira kernel: Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Dec 23 10:51:01 zira systemd[1]: Time has been changed
Dec 23 10:51:01 zira rtkit-daemon[2080]: The canary thread is apparently 
starving. Taking action.
Dec 23 10:51:01 zira systemd[1394]: Time has been changed
Dec 23 10:51:01 zira rtkit-daemon[2080]: Demoting known real-time threads.
Dec 23 10:51:01 zira systemd-logind[803]: Lid opened.
Dec 23 10:51:01 zira rtkit-daemon[2080]: Successfully demoted thread 2097 of 
process 2079 (n/a).
Dec 23 10:51:01 zira systemd[1]: apt-daily.timer: Adding 4h 42min 58.832894s 
random time.
Dec 23 10:51:01 zira rtkit-daemon[2080]: Successfully demoted thread 2096 of 
process 2079 (n/a).
Dec 23 10:51:01 zira systemd[1606]: Time has been changed
Dec 23 10:51:01 zira kernel: video LNXVIDEO:00: Restoring backlight state
Dec 23 10:51:01 zira kernel: ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument 
#4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20160422/nsarguments-95)
Dec 23 10:51:01 zira kernel: ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument 
#4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20160422/nsarguments-95)
Dec 23 10:51:01 zira kernel: ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument 
#4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20160422/nsarguments-95)
Dec 23 10:51:01 zira kernel: ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument 
#4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20160422/nsarguments-95)
Dec 23 10:51:01 zira rtkit-daemon[2080]: Successfully demoted thread 2095 of 
process 2079 (n/a).
Dec 23 10:51:01 zira systemd[1]: apt-daily.timer: Adding 1h 5min 28.127060s 
random time.
Dec 23 10:51:01 zira rtkit-daemon[2080]: Successfully demoted thread 2079 of 
process 2079 (n/a).
Dec 23 10:51:01 zira systemd[1]: Starting Load/Save RF Kill Switch Status...
Dec 23 10:51:01 zira rtkit-daemon[2080]: Demoted 4 threads.
Dec 23 10:51:01 zira systemd[1]: bluetooth.target: Unit not needed anymore. 
Stopping.
Dec 23 10:51:01 zira acpid[751]: client 984[0:0] has disconnected
Dec 23 10:51:01 zira systemd[1]: Stopped target Bluetooth.
Dec 23 10:51:01 zira postfix/smtpd[11811]: connect from 

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

[Vincent Lefevre]

Package: src:linux
Version: 4.8.11-1
Severity: important

After suspending my laptop (13:54:33 below), when I pressed the power
button to resume (19:35:53 below), the laptop was automatically
powered off. This is a regression (tried twice, occurred twice,
but there was no such problem in the past, AFAIK).

Excerpt from journalctl output:

[...]
Jan 02 13:54:33 zira systemd-logind[725]: Lid closed.
Jan 02 13:54:33 zira systemd-logind[725]: Suspending...
Jan 02 13:54:33 zira systemd[1]: Reached target Sleep.
Jan 02 13:54:33 zira systemd[1]: Starting Suspend...
Jan 02 13:54:33 zira systemd[1]: Stopping Atop advanced performance monitor...
Jan 02 13:54:34 zira systemd[1]: Stopped Atop advanced performance monitor.
Jan 02 13:54:34 zira systemd-sleep[13376]: Suspending system...
Jan 02 13:54:34 zira kernel: PM: Syncing filesystems ... done.
Jan 02 13:54:34 zira kernel: PM: Preparing system for sleep (mem)
Jan 02 13:54:35 zira kernel: ACPI Warning: \_SB.PCI0.PEGP.DGFX._DSM: Argument 
#4 type mismatch - Found [Buffer], ACPI requires [Package] 
(20160422/nsarguments-95)
Jan 02 19:35:53 zira kernel: (NULL device *): firmware: direct-loading firmware 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
Jan 02 19:35:53 zira kernel: (NULL device *): firmware: direct-loading firmware 
iwlwifi-7260-17.ucode
Jan 02 19:35:53 zira kernel: Freezing user space processes ... (elapsed 0.001 
seconds) done.
Jan 02 19:35:53 zira kernel: Double checking all user space processes after OOM 
killer disable... (elapsed 0.000 seconds) 
Jan 02 19:35:53 zira kernel: Freezing remaining freezable tasks ... (elapsed 
0.001 seconds) done.
Jan 02 19:35:53 zira kernel: PM: Suspending system (mem)
Jan 02 19:35:53 zira kernel: Suspending console(s) (use no_console_suspend to 
debug)
Jan 02 19:35:53 zira kernel: wlp61s0: deauthenticating from 00:1f:33:89:73:4e 
by local choice (Reason: 3=DEAUTH_LEAVING)
Jan 02 19:35:53 zira kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jan 02 19:35:53 zira kernel: sd 0:0:0:0: [sda] Stopping disk
Jan 02 19:35:53 zira kernel: parport_pc 00:04: disabled
Jan 02 19:35:53 zira kernel: e1000e: EEE TX LPI TIMER: 0011
Jan 02 19:35:53 zira kernel: PM: suspend of devices complete after 1306.520 
msecs
Jan 02 19:35:53 zira kernel: PM: late suspend of devices complete after 0.440 
msecs
Jan 02 19:35:53 zira kernel: ehci-pci :00:1d.0: System wakeup enabled by 
ACPI
Jan 02 19:35:53 zira kernel: ehci-pci :00:1a.0: System wakeup enabled by 
ACPI
Jan 02 19:35:53 zira kernel: e1000e :00:19.0: System wakeup enabled by ACPI
Jan 02 19:35:53 zira kernel: xhci_hcd :00:14.0: System wakeup enabled by 
ACPI
Jan 02 19:35:53 zira kernel: PM: noirq suspend of devices complete after 70.928 
msecs
Jan 02 19:35:53 zira kernel: ACPI: Preparing to enter system sleep state S3
Jan 02 19:35:53 zira kernel: ACPI : EC: EC stopped
Jan 02 19:35:53 zira kernel: PM: Saving platform NVS memory
Jan 02 19:35:53 zira kernel: Disabling non-boot CPUs ...
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 1 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 2 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 3 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 4 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 17
Jan 02 19:35:53 zira kernel: Broke affinity for irq 32
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 5 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 17
Jan 02 19:35:53 zira kernel: Broke affinity for irq 32
Jan 02 19:35:53 zira kernel: Broke affinity for irq 33
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 6 is now offline
Jan 02 19:35:53 zira kernel: Broke affinity for irq 1
Jan 02 19:35:53 zira kernel: Broke affinity for irq 8
Jan 02 19:35:53 zira kernel: Broke affinity for irq 9
Jan 02 19:35:53 zira kernel: Broke affinity for irq 12
Jan 02 19:35:53 zira kernel: Broke affinity for irq 16
Jan 02 19:35:53 zira kernel: Broke affinity for irq 17
Jan 02 19:35:53 zira kernel: Broke affinity for irq 32
Jan 02 19:35:53 zira kernel: Broke affinity for irq 33
Jan 02 19:35:53 zira kernel: Broke affinity for irq 36
Jan 02 19:35:53 zira kernel: Broke affinity for irq 37
Jan 02 19:35:53 zira kernel: smpboot: CPU 7 is now offline
Jan 02 19:35:53 zira kernel: ACPI: Low-level resume complete
Jan 02 19:35:53 zira kernel: ACPI : EC: EC started
Jan 02 19:35:53 zira kernel: PM: Restoring platform NVS memory
Jan 02 19:35:53 zira kernel: Enabling non-boot CPUs ...
Jan 02 19:35:53 zira kernel: x86: Booting SMP configuration:
Jan 02 19:35:53 zira kernel: smpboot: Booting Node 0 Processor 1 APIC 0x1
Jan 02 19:35:53 zira kernel:  cache: parent cpu1 should not be sleeping
Jan 02 19:35:53 zira kernel: 

Bug#847198: src:linux: dmesg should be allowed to print the kernel ring buffer for admins

[Vincent Lefevre]

Package: src:linux
Severity: wishlist

In the past, admins could get dmesg output without running it as root,
but this is no longer possible:

  * security,printk: Enable SECURITY_DMESG_RESTRICT, preventing non-root users
reading the kernel log by default (sysctl: kernel.dmesg_restrict)

(in changelog.linux.gz). It is good that normal users cannot read
the kernel log, but for admins (typically users in the adm group,
who can already read /var/log/kern.log, thus have access to the same
information), this is a regression.

Note: "journalctl -b" also gives kernel logs (among other logs).

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'stable-updates'), (500, 
'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.8.0-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Bug#823017: linux-image-4.5.0-1-amd64: can't read some files of a DVD+R: udf_read_inode: ... failed !bh

[Vincent Lefevre]

Control: found -1 4.6.4-1
Control: retitle -1 can't read some files of a DVD+R: udf_read_inode: ... 
failed !bh (regression)

Sorry for the late reply.

On 2016-04-30 12:53:23 +0200, Ben Hutchings wrote:
> On Sat, 2016-04-30 at 02:34 +0200, Vincent Lefevre wrote:
> > Reading most of the DVD+R is OK, though. And I don't get any error
> > on two other Debian/unstable machines (I can copy the whole DVD+R).
> [...]
> 
> Then I don't understand what makes you think this is a fault in the
> kernel, rather than that machine (specifically, that DVD drive).

Well, this is related to a specific drive (no problems on some
other machines), but it's a regression: I have no such problems
with linux-image-3.16.0-4-amd64 3.16.7-ckt25-2+deb8u3 (which is
still installed on this machine).

-- 
Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Bug#823017: linux-image-4.5.0-1-amd64: can't read some files of a DVD+R: udf_read_inode: ... failed !bh

[Vincent Lefevre]

Package: src:linux
Version: 4.5.1-1
Severity: important

Trying to copy some files of a DVD+R yields errors:

cp: cannot stat '...': Input/output error

In the logs:

Apr 30 01:52:28 zira kernel: UDF-fs: error (device sr0): udf_read_inode: (ino 
453) failed !bh
Apr 30 01:52:28 zira kernel: UDF-fs: error (device sr0): udf_read_inode: (ino 
454) failed !bh
Apr 30 01:52:28 zira kernel: UDF-fs: error (device sr0): udf_read_inode: (ino 
455) failed !bh
Apr 30 01:52:28 zira kernel: UDF-fs: error (device sr0): udf_read_inode: (ino 
456) failed !bh
Apr 30 01:52:28 zira kernel: UDF-fs: error (device sr0): udf_read_inode: (ino 
457) failed !bh
Apr 30 01:52:28 zira kernel: UDF-fs: error (device sr0): udf_read_inode: (ino 
458) failed !bh

Reading most of the DVD+R is OK, though. And I don't get any error
on two other Debian/unstable machines (I can copy the whole DVD+R).

The DVD+R was burnt with growisofs.

Note: I had exactly the same problem on this machine in December with
another DVD. At that time, I thought that the DVD was faulty.

-- Package-specific info:
** Version:
Linux version 4.5.0-1-amd64 (debian-kernel@lists.debian.org) (gcc version 5.3.1 
20160409 (Debian 5.3.1-14) ) #1 SMP Debian 4.5.1-1 (2016-04-14)

** Command line:
BOOT_IMAGE=/vmlinuz-4.5.0-1-amd64 root=/dev/mapper/zira--vg-root ro quiet

** Tainted: POE (12289)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.
 * Unsigned module has been loaded (currently expected).

** Kernel log:
[692811.106153] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 3583)
[692811.106154] mce: [Hardware Error]: Machine check events logged
[692811.107149] CPU2: Core temperature/speed normal
[692811.107150] CPU3: Core temperature/speed normal
[692811.107150] CPU4: Package temperature/speed normal
[692811.107151] CPU7: Package temperature/speed normal
[692811.107152] CPU5: Package temperature/speed normal
[692811.107153] CPU1: Package temperature/speed normal
[692811.107153] CPU0: Package temperature/speed normal
[692811.107154] CPU6: Package temperature/speed normal
[692811.107154] CPU3: Package temperature/speed normal
[692811.107160] CPU2: Package temperature/speed normal
[767674.823244] Process accounting resumed
[776697.327002] CPU3: Core temperature above threshold, cpu clock throttled 
(total events = 17)
[776697.327003] CPU2: Core temperature above threshold, cpu clock throttled 
(total events = 17)
[776697.327004] CPU5: Package temperature above threshold, cpu clock throttled 
(total events = 3584)
[776697.327005] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 3584)
[776697.327006] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 3584)
[776697.327007] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 3584)
[776697.327008] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 3584)
[776697.327010] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 3584)
[776697.327011] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 3584)
[776697.327013] mce_notify_irq: 2 callbacks suppressed
[776697.327013] mce: [Hardware Error]: Machine check events logged
[776697.327019] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 3584)
[776697.327020] mce: [Hardware Error]: Machine check events logged
[776697.327989] CPU2: Core temperature/speed normal
[776697.327990] CPU3: Core temperature/speed normal
[776697.327991] CPU1: Package temperature/speed normal
[776697.327991] CPU4: Package temperature/speed normal
[776697.327992] CPU5: Package temperature/speed normal
[776697.327993] CPU7: Package temperature/speed normal
[776697.327993] CPU0: Package temperature/speed normal
[776697.327994] CPU6: Package temperature/speed normal
[776697.327994] CPU3: Package temperature/speed normal
[776697.328000] CPU2: Package temperature/speed normal
[854071.639604] Process accounting resumed
[940468.459799] Process accounting resumed
[943903.535040] CPU5: Core temperature above threshold, cpu clock throttled 
(total events = 3573)
[943903.535042] CPU7: Package temperature above threshold, cpu clock throttled 
(total events = 3602)
[943903.535053] CPU4: Core temperature above threshold, cpu clock throttled 
(total events = 3573)
[943903.535054] CPU6: Package temperature above threshold, cpu clock throttled 
(total events = 3602)
[943903.535056] CPU4: Package temperature above threshold, cpu clock throttled 
(total events = 3602)
[943903.535057] CPU2: Package temperature above threshold, cpu clock throttled 
(total events = 3602)
[943903.535058] CPU3: Package temperature above threshold, cpu clock throttled 
(total events = 3602)
[943903.535059] CPU1: Package temperature above threshold, cpu clock throttled 
(total events = 3602)
[943903.535060] CPU0: Package temperature above threshold, cpu clock throttled 
(total events = 3602)

Bug#817049: linux-image-3.16.0-4-amd64: execve() gives EEXIST error under NFS if the file has been regenerated on a different machine

[Vincent Lefevre]

Package: src:linux
Version: 3.16.7-ckt20-1+deb8u3
Severity: normal

Under NFS, when an executable has been regenerated on a different machine,
execve() gives me an EEXIST error. To reproduce the bug:

francine:~> touch bin/tst
francine:~> cat bin/tst

cassis:~> cat tst.c
int main (void)
{ return 0; }
cassis:~> gcc -O3 tst.c -o tst
cassis:~> mv tst bin/
mv: overwrite ‘bin/tst’? y

At this point, I have to wait for 15 seconds for the "mv" to be
done: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799838

After that:

francine:~> strace -f -o tst.out sh -c "exec $HOME/bin/tst"
sh: 1: exec: /home/vlefevre/bin/tst: File exists
zsh: exit 2 strace -f -o tst.out sh -c "exec $HOME/bin/tst"
francine:~[2]> cat tst.out
21573 execve("/bin/sh", ["sh", "-c", "exec /home/vlefevre/bin/tst"], [/* 120 
vars */]) = 0
21573 brk(0)= 0x7f4aded7d000
21573 access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
21573 mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f4aded46000
21573 access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/tls/x86_64/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/tls/x86_64", 
0x7ffec78d5b00) = -1 ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/tls/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/tls", 0x7ffec78d5b00) = -1 
ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/x86_64/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib/x86_64", 0x7ffec78d5b00) = 
-1 ENOENT (No such file or directory)
21573 open("/home/vlefevre/debian8/gmp/westmere/lib/libc.so.6", 
O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
21573 stat("/home/vlefevre/debian8/gmp/westmere/lib", {st_mode=S_IFDIR|0755, 
st_size=13, ...}) = 0
21573 open("/usr/local/lib/tls/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 
ENOENT (No such file or directory)
21573 stat("/usr/local/lib/tls/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such 
file or directory)
21573 open("/usr/local/lib/tls/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No 
such file or directory)
21573 stat("/usr/local/lib/tls", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
directory)
21573 open("/usr/local/lib/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT 
(No such file or directory)
21573 stat("/usr/local/lib/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file 
or directory)
21573 open("/usr/local/lib/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
21573 stat("/usr/local/lib", {st_mode=S_IFDIR|S_ISGID|0775, st_size=4096, ...}) 
= 0
21573 open("/lib64/tls/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No 
such file or directory)
21573 stat("/lib64/tls/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
directory)
21573 open("/lib64/tls/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
21573 stat("/lib64/tls", 0x7ffec78d5b00) = -1 ENOENT (No such file or directory)
21573 open("/lib64/x86_64/libc.so.6", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
21573 stat("/lib64/x86_64", 0x7ffec78d5b00) = -1 ENOENT (No such file or 
directory)
21573 open("/lib64/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
21573 read(3, 
"\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0P\34\2\0\0\0\0\0"..., 832) = 832
21573 fstat(3, {st_mode=S_IFREG|0755, st_size=1738176, ...}) = 0
21573 mmap(NULL, 3844640, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) 
= 0x7f4ade55f000
21573 mprotect(0x7f4ade701000, 2093056, PROT_NONE) = 0
21573 mmap(0x7f4ade90, 24576, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1a1000) = 0x7f4ade90
21573 mmap(0x7f4ade906000, 14880, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f4ade906000
21573 close(3)  = 0
21573 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f4aded45000
21573 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f4aded44000
21573 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) 
= 0x7f4aded43000
21573 arch_prctl(ARCH_SET_FS, 0x7f4aded44700) = 0
21573 mprotect(0x7f4ade90, 16384, PROT_READ) = 0
21573 mprotect(0x7f4aded48000, 12288, PROT_READ) = 0
21573 mprotect(0x7f4adeb2a000, 4096, PROT_READ) = 0
21573 getpid()  = 21573
21573 rt_sigaction(SIGCHLD, {0x7f4adeb3efd0, ~[RTMIN RT_1], SA_RESTORER, 
0x7f4ade5940e0}, NULL, 8) = 0
21573 geteuid() = 1114
21573 brk(0)= 0x7f4aded7d000
21573 brk(0x7f4aded9e000)   = 0x7f4aded9e000
21573 getppid() = 21568
21573 stat("/home/vlefevre", 

Bug#757356: evtest: doesn't output scan codes for some keys

[Vincent Lefevre]

Control: retitle -1 Scan code event not generated for some keys of the Appple 
keyboard
Control: found -1 4.3.3-7

Things have improved since now the normal keys have their scan code.
This is not the case of the Fn key, but this may be normal since this
is a special key that modifies other keys. But this is not the case
either for Fn+F1, etc.

$ head /sys/module/hid_apple/parameters/*
==> /sys/module/hid_apple/parameters/fnmode <==
2

==> /sys/module/hid_apple/parameters/iso_layout <==
0

==> /sys/module/hid_apple/parameters/swap_opt_cmd <==
0

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)