Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang

On 30.12.22 11:42, Diederik de Haas wrote: On Friday, 30 December 2022 01:48:53 CET Stefan Pietsch wrote: Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and linux-image-5.6.0-2-amd64 (5.6.14-1).> This also affects 5.5.0-rc5-amd64. (https://snapshot.debian.org/archive/deb

Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang

On 07.06.20 08:48, Stefan Pietsch wrote: On 2020-06-01 20:44, Stefan Pietsch wrote: Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and linux-image-5.6.0-2-amd64 (5.6.14-1). This also affects 5.5.0-rc5-amd64. (https://snapshot.debian.org/archive/debian/20200106T211159Z/pool/main/l

Bug#963025: fixed in firmware-nonfree 20210315-1~exp1

On 08.04.21 11:50, Stefan Pietsch wrote: On 30.03.21 13:35, maximilian attems wrote: reopen 963025 found -1 20210315-2 tags -1 moreinfo stop [18661.586025] CPU: 0 PID: 8408 Comm: hostapd Tainted: G    W 5.10.0-5-amd64 #1 Debian 5.10.24-1 [18661.586029] Hardware name: LENOVO

Bug#963025: fixed in firmware-nonfree 20210315-1~exp1

On 30.03.21 13:35, maximilian attems wrote: reopen 963025 found -1 20210315-2 tags -1 moreinfo stop [18661.586025] CPU: 0 PID: 8408 Comm: hostapd Tainted: GW 5.10.0-5-amd64 #1 Debian 5.10.24-1 [18661.586029] Hardware name: LENOVO 20N2007GGE/20N2007GGE, BIOS N2IET81W (1.59 ) 11

Bug#963025: fixed in firmware-nonfree 20210315-1~exp1

On 16.03.21 17:34, Debian FTP Masters wrote: > Source: firmware-nonfree > Source-Version: 20210315-1~exp1 > Done: maximilian attems > > We believe that the bug you reported is fixed in the latest version of > firmware-nonfree, which is due to be installed in the Debian FTP archive. > > A summary

Bug#963025: firmware-iwlwifi: Microcode SW error detected / 9000-pu-b0-jf-b0-46.ucode

On 22.01.21 20:48, maximilian attems wrote: Firmware 9000-pu-b0-jf-b0-46.ucode stops working when used with hostapd as soon as a wireless client connects. Is that still happening with latest 5.10 linux and newer firmware-iwlwifi version >= 202011? The problem still exists with firmware-iwlwi

Bug#963025: firmware-iwlwifi: Microcode SW error detected / 9000-pu-b0-jf-b0-46.ucode

Package: firmware-iwlwifi Version: 20190717-2 Severity: important Firmware 9000-pu-b0-jf-b0-46.ucode stops working when used with hostapd as soon as a wireless client connects. This also affects firmware 9000-pu-b0-jf-b0-41.ucode. I was not able to reproduce this with firmware 9000-pu-b0-jf-b0-

Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang

On 2020-06-01 20:44, Stefan Pietsch wrote: Affected is at least linux-image-5.6.0-1-amd64 (5.6.7-1) and linux-image-5.6.0-2-amd64 (5.6.14-1). This also affects 5.5.0-rc5-amd64. (https://snapshot.debian.org/archive/debian/20200106T211159Z/pool/main/l/linux/) The kernel boot option

Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang

Package: linux-image-amd64 Version: 5.6.14-1 Starting with Linux kernel package linux-image-5.6.0-1-amd64 (5.6.7-1) I get the following error message that is repeating every few seconds: kernel: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang. Affecte

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 26.06.2013 12:47, Gleb Natapov wrote: > On Mon, Jun 24, 2013 at 10:42:57PM +0200, Stefan Pietsch wrote: >> On 24.06.2013 14:30, Gleb Natapov wrote: >>> On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote: >>>> As soon as I remove "kvmvapic.

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 24.06.2013 14:30, Gleb Natapov wrote: > On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote: >> As soon as I remove "kvmvapic.bin" the virtual machine boots with >> qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5. >> &qu

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 24.06.2013 13:47, Gleb Natapov wrote: > On Mon, Jun 24, 2013 at 01:43:26PM +0200, Stefan Pietsch wrote: >> On 23.06.2013 19:36, Gleb Natapov wrote: >>> On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote: >>>> On 23.06.2013 09:51, Gleb Natapov wrote: &g

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 23.06.2013 19:36, Gleb Natapov wrote: > On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote: >> On 23.06.2013 09:51, Gleb Natapov wrote: >>> On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote: >>>>> Can you provide the output of 2539145

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 23.06.2013 09:51, Gleb Natapov wrote: > On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote: >>> Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94 >>> and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 19.06.2013 16:38, Gleb Natapov wrote: > On Wed, Jun 19, 2013 at 04:12:04PM +0200, Stefan Pietsch wrote: >> On 19.06.2013 15:41, Gleb Natapov wrote: >>> On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote: >>>> >>>> first bad commit: [25391454

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 19.06.2013 15:41, Gleb Natapov wrote: > On Sun, Jun 16, 2013 at 02:25:04AM +0200, Stefan Pietsch wrote: >> >> first bad commit: [25391454e73e3156202264eb3c473825afe4bc94] >> KVM: VMX: don't clobber segment AR of unusable segments. >> >> >&

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 17.06.2013 18:07, Paolo Bonzini wrote: > Il 16/06/2013 02:25, Stefan Pietsch ha scritto: >> Bisecting leads to >> >> git bisect bad 378a8b099fc207ddcb91b19a8c1457667e0af398 >> git bisect good 007a3b547512d69f67ceb9641796d64552bd337e >> git bisect good 1f3141e

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 13.06.2013 16:59, Stefan Pietsch wrote: > On 13.06.2013 15:42, Paolo Bonzini wrote: >> Il 13/06/2013 07:57, Stefan Pietsch ha scritto: >>> git bisect tells me: >>> 79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit >> >> This is an s390 c

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 13.06.2013 15:42, Paolo Bonzini wrote: > Il 13/06/2013 07:57, Stefan Pietsch ha scritto: >> git bisect tells me: >> 79fd50c67f91136add9726fb7719b57a66c6f763 is the first bad commit > > This is an s390 commit, so the bisect somehow went wrong. Can you > confirm that 3

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 09.06.2013 11:43, Gleb Natapov wrote: > On Thu, Jun 06, 2013 at 02:10:39PM +0200, Stefan Pietsch wrote: >> On 06.06.2013 13:40, Gleb Natapov wrote: >>> On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote: >> >>>> I had no success with the Debian

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 06.06.2013 13:40, Gleb Natapov wrote: > On Thu, Jun 06, 2013 at 01:35:13PM +0200, Stefan Pietsch wrote: >> I had no success with the Debian kernel 3.10~rc4-1~exp1 (3.10-rc4-686-pae). >> >> The machine hangs after "Enabling APIC mode: Flat. Using 1 I/O APICs"

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 06.06.2013 08:42, Gleb Natapov wrote: > On Wed, Jun 05, 2013 at 02:51:19PM +0200, Stefan Pietsch wrote: >> On 05.06.2013 14:10, Gleb Natapov wrote: >>> On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote: >>>> On 19.05.2013 14:32, Gleb Natapov wrote: &g

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 05.06.2013 14:10, Gleb Natapov wrote: > On Wed, Jun 05, 2013 at 01:57:25PM +0200, Stefan Pietsch wrote: >> On 19.05.2013 14:32, Gleb Natapov wrote: >>> On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote: >>>> Dear KVM maintainers, it appears that t

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 19.05.2013 14:32, Gleb Natapov wrote: > On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote: >> Dear KVM maintainers, it appears that there is a gap in x86 emulation, >> at least on a 32-bit host. Stefan found this when running GRML, a live >> distribution which can be downloaded from

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 19.05.2013 14:32, Gleb Natapov wrote: > On Sun, May 19, 2013 at 02:00:31AM +0100, Ben Hutchings wrote: >> Dear KVM maintainers, it appears that there is a gap in x86 emulation, >> at least on a 32-bit host. Stefan found this when running GRML, a live >> distribution which can be downloaded from

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 09.05.2013 20:56, Stefan Pietsch wrote: > On 09.05.2013 03:08, Ben Hutchings wrote: > >> Please could you test some of the intermediate versions at >> <http://snapshot.debian.org/package/linux/> to find the first upstream >> version where this was broken. > &

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

On 09.05.2013 03:08, Ben Hutchings wrote: > Please could you test some of the intermediate versions at > to find the first upstream > version where this was broken. The first version which does not work is 3.6.4-1~experimental.1. 3.5.5-1~experimental.1

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"

Package: linux-image-3.8-1-686-pae Version: 3.8.11-1 KVM fails with the unstable kernel 3.8.11-1. # kvm -m 512 -cdrom grml32-full_2013.02.iso KVM: entry failed, hardware error 0x8021 If you're running a guest on an Intel machine without unrestricted mode support, the failure can be m