Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #67214 > unrolled thread
| Started by | Stefan Pietsch <stefan+debian@shellforce.org> |
|---|---|
| First post | 2020-06-01 23:00 +0200 |
| Last post | 2020-09-07 11:50 +0200 |
| Articles | 5 — 3 participants |
Back to article view | Back to linux.debian.kernel
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> - 2020-06-01 23:00 +0200
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> - 2020-06-07 11:10 +0200
Bug#962003: Bug found still present In current debian Kernels "Simon Iremonger (debian)" <debian@iremonger.me.uk> - 2020-09-06 08:10 +0200
Bug#962003: Bug found still present In current debian Kernels Salvatore Bonaccorso <carnil@debian.org> - 2020-09-06 10:50 +0200
Bug#962003: Bug found still present In current debian Kernels "Simon Iremonger (debian)" <debian@iremonger.me.uk> - 2020-09-07 11:50 +0200
| From | Stefan Pietsch <stefan+debian@shellforce.org> |
|---|---|
| Date | 2020-06-01 23:00 +0200 |
| 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 | <AcZHj-3Qz-1@gated-at.bofh.it> |
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.
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).
The error message does not appear with linux-image-5.4.0-4-amd64
(5.4.19-1).
Hardware is a Lenovo T410 with integrated Intel graphics controller.
[toc] | [next] | [standalone]
| From | Stefan Pietsch <stefan+debian@shellforce.org> |
|---|---|
| Date | 2020-06-07 11:10 +0200 |
| Message-ID | <AeZtv-691-5@gated-at.bofh.it> |
| In reply to | #67214 |
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.
[toc] | [prev] | [next] | [standalone]
| From | "Simon Iremonger (debian)" <debian@iremonger.me.uk> |
|---|---|
| Date | 2020-09-06 08:10 +0200 |
| Subject | Bug#962003: Bug found still present In current debian Kernels |
| Message-ID | <ALW2d-5wW-9@gated-at.bofh.it> |
| In reply to | #67214 |
Bug still present, affects for-example X201-Tablet, similar hardware to T410 with Intel Graphics variant. Affects at least debian kernels:- 5.6.0-2-amd64 5.6.14-2 5.7.0-2-amd64 5.7.10-1 5.7.0-3-amd64 5.7.17-1 --Simon
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2020-09-06 10:50 +0200 |
| Subject | Bug#962003: Bug found still present In current debian Kernels |
| Message-ID | <ALYx3-6RF-1@gated-at.bofh.it> |
| In reply to | #67998 |
Hi, On Sun, Sep 06, 2020 at 06:53:56AM +0100, Simon Iremonger (debian) wrote: > Bug still present, affects for-example X201-Tablet, similar > hardware to T410 with Intel Graphics variant. > > > Affects at least debian kernels:- > > 5.6.0-2-amd64 5.6.14-2 > 5.7.0-2-amd64 5.7.10-1 > 5.7.0-3-amd64 5.7.17-1 Please do test as well the yesterday uploaded 5.8.7-1 but I suspect the bug is still present there. To isolate the issue it might be worth trying to bisect were the issue is introduced and ideally then reported upstream. Some hints are in https://wiki.debian.org/DebianKernelReportingBugs#Identifying_when_the_bug_was_introduced In particular if you found the introducing Debian revision, then do check the respective upstream stable versions, and then try to bisect to find the introducing commit. See https://wiki.debian.org/DebianKernel/GitBisect Hope this helps, Regards, Salvatore
[toc] | [prev] | [next] | [standalone]
| From | "Simon Iremonger (debian)" <debian@iremonger.me.uk> |
|---|---|
| Date | 2020-09-07 11:50 +0200 |
| Subject | Bug#962003: Bug found still present In current debian Kernels |
| Message-ID | <AMlWF-4tN-3@gated-at.bofh.it> |
| In reply to | #68003 |
> Please do test as well the yesterday uploaded 5.8.7-1 but I suspect > the bug is still present there. Yes, indeed. > To isolate the issue it might be worth trying to bisect were the issue > is introduced and ideally then reported upstream. Confirmed between 5.4.19-1 and 5.5.13-1. > Some hints are in > https://wiki.debian.org/DebianKernelReportingBugs#Identifying_when_the_bug_was_introduced "You can find older versions of the kernel in various locations, including http://snapshot.debian.org." Where else are these "various locations" !?!? Can they be linked onto above wiki page? In this case some earlier 5.5's would be clearly useful test-cases. Another point that I'd like to see on above page, is -- clear information on where kernel bugs *should* be filed or *are* filed with explanation. I.e. src:linux linux-image-amd64 linux-image-VERSION-amd64 and so-on and so-forth!. Another point that I'd like to see on above page, is clear information what to do to search for existing kernel bugs, as "reportbug kernel" would NOT find 962003 for me, this is related to the above confusion really. --Simon
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web