Bug#969979: linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system

2020-09-10 Thread Seb
Hi, This version is 10 months old; please upgrade and try again as the bug may have been fixed already. This was spot-on, thank you. After a dist-upgrade, the machine stopped crashing while syncing the RAID arrays at boot and didn't crash while checking the array, which is now clean. I

Bug#969979: linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system

2020-09-09 Thread Seb
Hi, Package: src:linux Version: 4.19.67-2+deb10u2 [...] This version is 10 months old; please upgrade and try again as the bug may have been fixed already. OK, I will, but I do not know how to properly upgrade the kernel on a Debain-stable system (which is up-to-date with respect to "apt

Bug#969979: linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system

2020-09-09 Thread Seb
Package: src:linux Version: 4.19.67-2+deb10u2 Severity: critical Justification: breaks the whole system Dear Maintainer, This machine runs a six-disks RAID10 array with mdadm. This morning, cat /sys/block/md2/md/mismatch_cnt reported 128, indicating errors on the array. This may be

Bug#641906: firmware-brcm80211: freezing of system after loading

2011-09-17 Thread seb
Package: firmware-brcm80211 Severity: critical Justification: breaks the whole system After installing the firmware packet for BCM4313 (firmware-brcm80211) and reloading the brcm80211 module the system freezes and refuses to boot. On booting, the system freezes somewhere in the init prosess

Bug#495750: linux-image-2.6.26-1-686: iwl3945 doesn't run on Lenovo 3000N100

2008-08-20 Thread seb
Package: linux-image-2.6.26-1-686 Version: 2.6.26-1 Subject: iwl3945 doesn't run on Lenovo 3000N100 Kernel: Linux seb-laptop 2.6.26-1-686 #1 SMP Fri Aug 8 13:53:24 CEST 2008 i686 GNU/Linux System: Debian unstable, gcc 4:4.3.1-2, libc6 2.7-13 dmesg: [ 462.228273] firmware: requesting iwlwifi

Blade2K and qla2xxx

2007-06-18 Thread seb
--- After this, I got no access from the scsi target. What do you think the problem can be ? how to workaround ? Seb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]