Re: [Intel-gfx] kernel 5.5.4: BUG: kernel NULL pointer dereference, address: 000000000000000

2020-02-16 Thread Toralf Förster
On 2/16/20 3:55 PM, Hillf Danton wrote: > > On Sun, 16 Feb 2020 11:33:02 +0100 Toralf Foerster wrote: >> On 2/16/20 4:26 AM, Hillf Danton wrote: >>> Looks like a stray lock counts for the above NULL dereference. >>> >> Hi, the patch applied on top of 5.5.4 breaks the internal display now even >>

Re: [Intel-gfx] kernel 5.5.4: BUG: kernel NULL pointer dereference, address: 000000000000000

2020-02-16 Thread Toralf Förster
On 2/16/20 4:26 AM, Hillf Danton wrote: > Looks like a stray lock counts for the above NULL dereference. Hi, the patch applied on top of 5.5.4 breaks the internal display now even in the boot phase. Gert just a black screen after few seconds, nothing in the logs except: Feb 16 11:21:57 t44 kernel

[Intel-gfx] kernel 5.5.4: BUG: kernel NULL pointer dereference, address: 000000000000000

2020-02-15 Thread Toralf Förster
Since 5.5.1 I do experience hangs under a hardend Gerntoo Linux + KDE, neither mouse nor keyboard are then working anymore, power off is the only one. The syslog tells: Feb 15 12:56:31 t44 kernel: BUG: kernel NULL pointer dereference, address: Feb 15 12:56:31 t44 kernel: #PF: s

[Intel-gfx] Fwd: 4.8.x : [drm:ffffffffa0454792] *ERROR* failed to update link training

2016-11-26 Thread Toralf Förster
Whilst 4.7.10 is fine, the current 4.8.10 kernel spews that message in dmesg during boot and later can't be undocked any longer - the vt7 display then will stay black forever. Switching to another vt works fine FWIW. Update: attached dmesg -- Toralf PGP: C4EACDDE 0076E94E Linux version 4.8.10-h

[Intel-gfx] 4.8.x : [drm:ffffffffa0454792] *ERROR* failed to update link training

2016-11-26 Thread Toralf Förster
Whilst 4.7.10 is fine, the current 4.8.10 kernel spews that message in dmesg during boot and later can't be undocked any longer - the vt7 display then will stay black forever. Switching to another vt works fine FWIW. -- Toralf PGP: C4EACDDE 0076E94E _

Re: [Intel-gfx] 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-10-30 Thread Toralf Förster
On 10/29/2015 10:49 PM, Pavel Machek wrote: > On Sun 2015-10-04 18:30:14, Toralf Förster wrote: >> On 08/04/2015 02:29 PM, Toralf Förster wrote: >>> On 08/02/2015 09:43 AM, Pavel Machek wrote: >>>> Any chance to bisect it? >>> Did it. >>> >>&g

Re: [Intel-gfx] 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-10-04 Thread Toralf Förster
On 08/04/2015 02:29 PM, Toralf Förster wrote: > On 08/02/2015 09:43 AM, Pavel Machek wrote: >> Any chance to bisect it? > Did it. > > FWIW: the mentioned commit was introduced between 3.18 and 3.19. > But my system (hardened 64 bit Gentoo) did not suffer from it till ve

Re: [Intel-gfx] 4.1->4.2 regression : intel_display.c:12324 check_crtc_state warning

2015-09-06 Thread Toralf Förster
On 09/02/2015 10:31 PM, Konduru, Chandra wrote: > It is due to ips_enabled mismatch in crtc_state. > I can't think how below patch is triggering mismatch in ips_enabled. tested it 2 times in a row, the bad commits fails, the commit before works fine. Unfortunately that commit id cannot be reverte

[Intel-gfx] 4.1->4.2 regression : intel_display.c:12324 check_crtc_state warning

2015-09-02 Thread Toralf Förster
The following commit was bisected and tested to be the first bad commit which causes the warning as seen below at a ThinkPad T40s: commit a1b2278e4dfcd2dbea85e319ebf73a6b7b2f180b Author: Chandra Konduru Date: Tue Apr 7 15:28:45 2015 -0700 drm/i915: skylake panel fitting using shared sca

Re: [Intel-gfx] 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-08-15 Thread Toralf Förster
On 08/04/2015 02:29 PM, Toralf Förster wrote: > On 08/02/2015 09:43 AM, Pavel Machek wrote: >> Any chance to bisect it? > Did it. > > FWIW: the mentioned commit was introduced between 3.18 and 3.19. > But my system (hardened 64 bit Gentoo) did not suffer from it till ve

Re: [Intel-gfx] 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-08-04 Thread Toralf Förster
On 08/02/2015 09:43 AM, Pavel Machek wrote: > Any chance to bisect it? Did it. FWIW: the mentioned commit was introduced between 3.18 and 3.19. But my system (hardened 64 bit Gentoo) did not suffer from it till version 4.0.8. The hardened kernel 4.1.x was the first where the bug was visible at my

Re: [Intel-gfx] 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-08-03 Thread Toralf Förster
On 08/03/2015 11:53 AM, Toralf Förster wrote: > A quick look at the latest 4.1.3+hardened just shows that the power button at > the docking station does not produce an ACPI event. This is fixed between 4.1.3 and 4.1.4 - would be helpful to know the commit id for the following bisecting

Re: [Intel-gfx] 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-08-03 Thread Toralf Förster
On 08/02/2015 09:43 AM, Pavel Machek wrote: > On Wed 2015-07-29 15:54:00, Toralf Förster wrote: >> Undocking helps, and then I can dock again. >> >> This happens at a hardened 64 bit Gentoo with i915, but I think, it is >> not hardened related, or ? > > Any chan

[Intel-gfx] 4.0.8->4.1.3 : after resume from s2ram both internal and external display of a docked ThinkPad ate black

2015-07-29 Thread Toralf Förster
Undocking helps, and then I can dock again. This happens at a hardened 64 bit Gentoo with i915, but I think, it is not hardened related, or ? -- Toralf, pgp key: 872AE508 0076E94E ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists

Re: [Intel-gfx] [drm:hsw_unclaimed_reg_detect] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.

2014-12-15 Thread Toralf Förster
On 12/15/2014 11:16 AM, Daniel Vetter wrote: > On Mon, Dec 15, 2014 at 10:24:53AM +0100, Toralf Förster wrote: >> On 12/15/2014 08:45 AM, Daniel Vetter wrote: >>> Nah, this is just a kernel cmdlineoption. So please boot with >>> i915.mmio_debug=1 added to the kernel

Re: [Intel-gfx] [drm:hsw_unclaimed_reg_detect] *ERROR* Unclaimed register detected. Please use the i915.mmio_debug=1 to debug this problem.

2014-12-15 Thread Toralf Förster
On 12/15/2014 08:45 AM, Daniel Vetter wrote: > Nah, this is just a kernel cmdlineoption. So please boot with > i915.mmio_debug=1 added to the kernel cmdline, reproduce and then grab the > entire dmesg. > > Thanks, Daniel errm, I did it, rebooted, suspended and then the WARNING appeared: >Dec 12

Re: [Intel-gfx] 3.10.2 : new warning WARNING: at drivers/gpu/drm/i915/intel_display.c:1656 ironlake_crtc_disable+0x7ce/0x800 [i915]()

2013-08-08 Thread Toralf Förster
On 08/06/2013 08:03 PM, Daniel Vetter wrote: > On Tue, Aug 6, 2013 at 7:42 PM, Toralf Förster wrote: >> On 07/26/2013 07:58 PM, Daniel Vetter wrote: >>> On Wed, Jul 24, 2013 at 05:51:41PM +0200, Toralf Förster wrote: >>>> Realized this today while booting a Think

Re: [Intel-gfx] i915/intel_display.c:1656 ironlake_crtc_disable+0x7ce/0x800 [i915]()

2013-08-06 Thread Toralf Förster
On 08/06/2013 07:38 PM, Toralf Förster wrote: > with kernel 3.10.5 at a ThinkPad T420 at a 32bit stable Gentoo Linux I > got the attached trace today. > > I'm not sure if it is a regression of 3.10.4 or if it is new. > > > ick - overlooked an existing thread t

Re: [Intel-gfx] 3.10.2 : new warning WARNING: at drivers/gpu/drm/i915/intel_display.c:1656 ironlake_crtc_disable+0x7ce/0x800 [i915]()

2013-08-06 Thread Toralf Förster
On 07/26/2013 07:58 PM, Daniel Vetter wrote: > On Wed, Jul 24, 2013 at 05:51:41PM +0200, Toralf Förster wrote: >> Realized this today while booting a ThinkPad T420 with integrated intel >> graphic : > > Can you please retest with latest upstream git from Linus' tree? e

[Intel-gfx] i915/intel_display.c:1656 ironlake_crtc_disable+0x7ce/0x800 [i915]()

2013-08-06 Thread Toralf Förster
with kernel 3.10.5 at a ThinkPad T420 at a 32bit stable Gentoo Linux I got the attached trace today. I'm not sure if it is a regression of 3.10.4 or if it is new. -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 Aug 6 17:37:52 n22 kerne

[Intel-gfx] 3.10.2 : new warning WARNING: at drivers/gpu/drm/i915/intel_display.c:1656 ironlake_crtc_disable+0x7ce/0x800 [i915]()

2013-07-24 Thread Toralf Förster
: [] ? flush_kthread_worker+0x90/0x90 Jul 24 17:36:10 n22 kernel: ---[ end trace 7f63a6cbe7b8fcf4 ]--- Jul 24 17:36:10 n22 kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Jul 24 17:36:10 n22 kernel: ata5: SATA link down (SStatus 0 SControl 300) -- MfG/Sincerely Toralf Förster pgp

Re: [Intel-gfx] ThinkPad T420 + kernel 3.8.x + external VGA display == wrong resolution

2013-03-05 Thread Toralf Förster
On 03/05/2013 11:41 AM, Daniel Vetter wrote: > against DRI -> DRM(Intel) and attach the files there together with > your quick description of the regression above. > > Thanks, Daniel np : https://bugs.freedesktop.org/show_bug.cgi?id=61861 -- MfG/Sincerely Toralf Förster pgp fin

[Intel-gfx] RC6 for an Intel GU doesn't always work

2012-10-11 Thread Toralf Förster
. -- MfG/Sincerely Toralf Förster pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3 ___ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/intel-gfx