Since some days, I noticed that "resync" of md device triggers at boot time.
Sometimes, it triggers at every boot.
It slows down the computer and the disks access for 90minutes.
I didn't notice this kind of behavior at the beginning.
Lately I didn't change anything except changing a component (PCI
Processing control commands:
> tag -1 moreinfo
Bug #963017 [src:linux] linux-image-5.6.0-2-amd64: System freezes shortly after
boot
Added tag(s) moreinfo.
--
963017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963017
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 moreinfo
Bug #963239 [src:linux] linux-image-4.19.0-9-amd64: software raid array resync
at boot (raid5)
Added tag(s) moreinfo.
--
963239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 moreinfo
Is this reproducible when not using the Nvidia proprietary driver?
Ben.
--
Ben Hutchings
It is impossible to make anything foolproof
because fools are so ingenious.
signature.asc
Description: This is a digitally signed message part
Processing commands for cont...@bugs.debian.org:
> tags 963033 - d-i
Bug #963033 [linux-image-arm64] linux-image-arm64: kexec loses EFI system
tables with Debian kernels
Removed tag(s) d-i.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
963033: https://bugs.debi
Control: tag -1 moreinfo
You need to explain what the bug is. The subject says that a RAID
array was resynced at boot, but that's supposed to happen in some
circumstances.
* Why did you not expect it?
* Did you notice anything happen before, or did you make any change,
that might have triggere
Processing commands for cont...@bugs.debian.org:
> found 942861 linux-signed-amd64/5.6.14+1
Bug #942861 [linux-image-amd64] linux-image-amd64: missing-copyright-file
/usr/share/doc/linux-image-amd64/copyright
Bug #962588 [linux-image-amd64] linux-image-amd64:amd64: missing-copyright-file
/usr/sh
Package: src:linux
Version: 5.6.14-1
Severity: normal
Dear Maintainer,
I found this kernel call trace in dmesg after an upgrade. I believe it might
be important to someone because it happened during a interruption handling
or something. Feel free to close otherwise.
The computer seems to work j
Package: src:linux
Version: 4.19.118-2+deb10u1
Severity: normal
-- Package-specific info:
** Version:
Linux version 4.19.0-9-amd64 (debian-kernel@lists.debian.org) (gcc version
8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.118-2+deb10u1 (2020-06-07)
** Command line:
BOOT_IMAGE=/boot/vmlinuz-4.19.
9 matches
Mail list logo