Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #77761 > unrolled thread
| Started by | Stefan Pietsch <stefan+debian@shellforce.org> |
|---|---|
| First post | 2022-12-30 02:00 +0100 |
| Last post | 2023-01-14 23:50 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang Stefan Pietsch <stefan+debian@shellforce.org> - 2022-12-30 02:00 +0100
Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang Diederik de Haas <didi.debian@cknow.org> - 2022-12-30 13:00 +0100
Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang Stefan Pietsch <stefan+debian@shellforce.org> - 2023-01-14 23:50 +0100
| From | Stefan Pietsch <stefan+debian@shellforce.org> |
|---|---|
| Date | 2022-12-30 02:00 +0100 |
| Subject | Bug#962003: Linux kernel 5.6: [drm:i915_gem_gtt_finish_pages [i915]] *ERROR* Failed to wait for idle; VT'd may hang |
| Message-ID | <FIbUB-edpS-3@gated-at.bofh.it> |
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/linux/) > > The kernel boot option "intel_iommu=igfx_off" prevents the error message. This seems to be resolved in newer kernel versions. I'm not able to reproduce this with kernel version 5.14.0-4-amd64 (5.14.16-1). Regards, Stefan
[toc] | [next] | [standalone]
| From | Diederik de Haas <didi.debian@cknow.org> |
|---|---|
| Date | 2022-12-30 13:00 +0100 |
| Message-ID | <FImdj-ejOp-1@gated-at.bofh.it> |
| In reply to | #77761 |
[Multipart message — attachments visible in raw view] — view raw
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/debian/20200106T211159Z/pool/main/l/l > > inux/) > > > > The kernel boot option "intel_iommu=igfx_off" prevents the error message. > > This seems to be resolved in newer kernel versions. > I'm not able to reproduce this with kernel version 5.14.0-4-amd64 > (5.14.16-1). Great that it is resolved :-) As many people are affected and the Stable kernel version still seems to exhibit the problem, I want to ask a question: Are you willing to help out to narrow down as much as possible which version introduced the error and in which is was fixed? Wrt the latter, does 5.14.12-1 still show the issue? Via https://snapshot.debian.org/binary/linux-image-amd64/ you get (easily) get all the kernel versions that were released. If we know a (reasonably) small range of kernel versions in which it surfaced and a small range in which it was fixed, then we could make some educated guesses as to which commit caused the issue in the first place. TIA, Diederik
[toc] | [prev] | [next] | [standalone]
| From | Stefan Pietsch <stefan+debian@shellforce.org> |
|---|---|
| Date | 2023-01-14 23:50 +0100 |
| Message-ID | <FNXvz-rG2-3@gated-at.bofh.it> |
| In reply to | #77767 |
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/debian/20200106T211159Z/pool/main/l/l >>> inux/) >>> >>> The kernel boot option "intel_iommu=igfx_off" prevents the error message. >> >> This seems to be resolved in newer kernel versions. >> I'm not able to reproduce this with kernel version 5.14.0-4-amd64 >> (5.14.16-1). > > Great that it is resolved :-) > > As many people are affected and the Stable kernel version still seems to > exhibit the problem, I want to ask a question: > Are you willing to help out to narrow down as much as possible which version > introduced the error and in which is was fixed? Wrt the latter, does 5.14.12-1 > still show the issue? [...] Just a small update: kernel version 5.13.9-1~exp2 is also not affected by the problem.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web