Skip to contentSkip to conversation

4.2-rc4 kernel warnings on HSW laptop

DISCUSSION Takashi Iwai 5 participants 8 messages Oct 10, 2015 – Oct 14, 2015

lore
Share & tools
lore
#0 lore raw

Hi,

I noticed that a HSW laptop gets a few new warnings since 4.2-rc kernels. One error messages pops at each boot time:

Console: switching to colour dummy device 80x25
[drm] Replacing VGA console driver
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0!

Then a warning when I start powertop:

 WARNING: CPU: 1 PID: 1674 at drivers/gpu/drm/drm_atomic.c:889 drm_atomic_get_property+0x232/0x2b0 [drm]()
 CPU: 1 PID: 1674 Comm: powertop Tainted: G        W       4.3.0-rc4-test+ #93
 Hardware name: Hewlett-Packard HP ProBook 430 G1/1946, BIOS L73 Ver. 08.05 2013/03/15
  ffffffffa005b289 ffff880059173ca8 ffffffff81346fa9 0000000000000000
  ffff880059173ce0 ffffffff81063232 ffff8800372bc028 ffff8800373f3740
  ffff8800372bc000 ffff880062ad37c0 0000000000000001 ffff880059173cf0
 Call Trace:
  [<ffffffff81346fa9>] dump_stack+0x4b/0x72
  [<ffffffff81063232>] warn_slowpath_common+0x82/0xc0
  [<ffffffff8106332a>] warn_slowpath_null+0x1a/0x20
  [<ffffffffa0047a12>] drm_atomic_get_property+0x232/0x2b0 [drm]
  [<ffffffffa00356dc>] drm_object_property_get_value+0x6c/0x70 [drm]
  [<ffffffffa003330f>] dpms_show+0x2f/0x70 [drm]
  [<ffffffff8145f090>] dev_attr_show+0x20/0x50
  [<ffffffff8124b48c>] sysfs_kf_seq_show+0xbc/0x130
  [<ffffffff81249d73>] kernfs_seq_show+0x23/0x30
  [<ffffffff811f3d8a>] seq_read+0xca/0x360
  [<ffffffff8124a7da>] kernfs_fop_read+0x10a/0x160
  [<ffffffff811d0888>] __vfs_read+0x28/0xd0
  [<ffffffff812cbe80>] ? security_file_permission+0xa0/0xc0
  [<ffffffff811d102f>] ? rw_verify_area+0x4f/0xe0
  [<ffffffff811d1143>] vfs_read+0x83/0x130
  [<ffffffff811d1df6>] SyS_read+0x46/0xa0
  [<ffffffff81001b40>] ? syscall_return_slowpath+0x50/0x130
  [<ffffffff81659636>] entry_SYSCALL_64_fastpath+0x16/0x75

Both don't look like serious issues, but not sexy to see at each time.

thanks,

Takashi
_______________________________________________
dri-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/dri-devel

#1 lore raw

Re: 4.2-rc4 kernel warnings on HSW laptop [regression]

Another pile of regressions for Jairo to track ...

Quoted 11 lines · Takashi Iwai

Hi,

I noticed that a HSW laptop gets a few new warnings since 4.2-rc kernels. One error messages pops at each boot time:

Console: switching to colour dummy device 80x25
[drm] Replacing VGA console driver
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0!

There's patches for this one already, but I accidentally applied them for -next, not -fixes. They should land for -rc6.

Quoted 29 lines

Then a warning when I start powertop:

 WARNING: CPU: 1 PID: 1674 at drivers/gpu/drm/drm_atomic.c:889 drm_atomic_get_property+0x232/0x2b0 [drm]()
 CPU: 1 PID: 1674 Comm: powertop Tainted: G        W       4.3.0-rc4-test+ #93
 Hardware name: Hewlett-Packard HP ProBook 430 G1/1946, BIOS L73 Ver. 08.05 2013/03/15
  ffffffffa005b289 ffff880059173ca8 ffffffff81346fa9 0000000000000000
  ffff880059173ce0 ffffffff81063232 ffff8800372bc028 ffff8800373f3740
  ffff8800372bc000 ffff880062ad37c0 0000000000000001 ffff880059173cf0
 Call Trace:
  [<ffffffff81346fa9>] dump_stack+0x4b/0x72
  [<ffffffff81063232>] warn_slowpath_common+0x82/0xc0
  [<ffffffff8106332a>] warn_slowpath_null+0x1a/0x20
  [<ffffffffa0047a12>] drm_atomic_get_property+0x232/0x2b0 [drm]
  [<ffffffffa00356dc>] drm_object_property_get_value+0x6c/0x70 [drm]
  [<ffffffffa003330f>] dpms_show+0x2f/0x70 [drm]
  [<ffffffff8145f090>] dev_attr_show+0x20/0x50
  [<ffffffff8124b48c>] sysfs_kf_seq_show+0xbc/0x130
  [<ffffffff81249d73>] kernfs_seq_show+0x23/0x30
  [<ffffffff811f3d8a>] seq_read+0xca/0x360
  [<ffffffff8124a7da>] kernfs_fop_read+0x10a/0x160
  [<ffffffff811d0888>] __vfs_read+0x28/0xd0
  [<ffffffff812cbe80>] ? security_file_permission+0xa0/0xc0
  [<ffffffff811d102f>] ? rw_verify_area+0x4f/0xe0
  [<ffffffff811d1143>] vfs_read+0x83/0x130
  [<ffffffff811d1df6>] SyS_read+0x46/0xa0
  [<ffffffff81001b40>] ? syscall_return_slowpath+0x50/0x130
  [<ffffffff81659636>] entry_SYSCALL_64_fastpath+0x16/0x75
Quoted 1 line

Both don't look like serious issues, but not sexy to see at each time.

This should be fixed with

commit 621bd0f6982badd6483acb191eb7b6226a578328

Author: Daniel Vetter <[email protected]>
Date:   Tue Sep 29 09:56:53 2015 +0200

drm: Fix locking for sysfs dpms file

If not please scream.

Thanks, Daniel

Signature · 7 lines
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
#2 lore raw

Re: 4.2-rc4 kernel warnings on HSW laptop [regression]

Quoted 16 lines · Daniel Vetter

Another pile of regressions for Jairo to track ...

Quoted 11 lines · Takashi Iwai

Hi,

I noticed that a HSW laptop gets a few new warnings since 4.2-rc kernels. One error messages pops at each boot time:

Console: switching to colour dummy device 80x25
[drm] Replacing VGA console driver
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0!

Quoted 2 lines

There's patches for this one already, but I accidentally applied them for -next, not -fixes. They should land for -rc6.

Could you point commit ids?

Quoted 33 lines
Quoted 29 lines

Then a warning when I start powertop:

 WARNING: CPU: 1 PID: 1674 at drivers/gpu/drm/drm_atomic.c:889 drm_atomic_get_property+0x232/0x2b0 [drm]()
 CPU: 1 PID: 1674 Comm: powertop Tainted: G        W       4.3.0-rc4-test+ #93
 Hardware name: Hewlett-Packard HP ProBook 430 G1/1946, BIOS L73 Ver. 08.05 2013/03/15
  ffffffffa005b289 ffff880059173ca8 ffffffff81346fa9 0000000000000000
  ffff880059173ce0 ffffffff81063232 ffff8800372bc028 ffff8800373f3740
  ffff8800372bc000 ffff880062ad37c0 0000000000000001 ffff880059173cf0
 Call Trace:
  [<ffffffff81346fa9>] dump_stack+0x4b/0x72
  [<ffffffff81063232>] warn_slowpath_common+0x82/0xc0
  [<ffffffff8106332a>] warn_slowpath_null+0x1a/0x20
  [<ffffffffa0047a12>] drm_atomic_get_property+0x232/0x2b0 [drm]
  [<ffffffffa00356dc>] drm_object_property_get_value+0x6c/0x70 [drm]
  [<ffffffffa003330f>] dpms_show+0x2f/0x70 [drm]
  [<ffffffff8145f090>] dev_attr_show+0x20/0x50
  [<ffffffff8124b48c>] sysfs_kf_seq_show+0xbc/0x130
  [<ffffffff81249d73>] kernfs_seq_show+0x23/0x30
  [<ffffffff811f3d8a>] seq_read+0xca/0x360
  [<ffffffff8124a7da>] kernfs_fop_read+0x10a/0x160
  [<ffffffff811d0888>] __vfs_read+0x28/0xd0
  [<ffffffff812cbe80>] ? security_file_permission+0xa0/0xc0
  [<ffffffff811d102f>] ? rw_verify_area+0x4f/0xe0
  [<ffffffff811d1143>] vfs_read+0x83/0x130
  [<ffffffff811d1df6>] SyS_read+0x46/0xa0
  [<ffffffff81001b40>] ? syscall_return_slowpath+0x50/0x130
  [<ffffffff81659636>] entry_SYSCALL_64_fastpath+0x16/0x75
Quoted 1 line

Both don't look like serious issues, but not sexy to see at each time.

This should be fixed with

Quoted 7 lines

commit 621bd0f6982badd6483acb191eb7b6226a578328

Author: Daniel Vetter <[email protected]>
Date:   Tue Sep 29 09:56:53 2015 +0200

drm: Fix locking for sysfs dpms file

If not please scream.

OK, I'll give a shot.

thanks,

Takashi
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

author Tested-by
#3 lore raw

Re: 4.2-rc4 kernel warnings on HSW laptop [regression]

Quoted 38 lines · Takashi Iwai
Quoted 38 lines
Quoted 30 lines

Then a warning when I start powertop:

 WARNING: CPU: 1 PID: 1674 at drivers/gpu/drm/drm_atomic.c:889 drm_atomic_get_property+0x232/0x2b0 [drm]()
 CPU: 1 PID: 1674 Comm: powertop Tainted: G        W       4.3.0-rc4-test+ #93
 Hardware name: Hewlett-Packard HP ProBook 430 G1/1946, BIOS L73 Ver. 08.05 2013/03/15
  ffffffffa005b289 ffff880059173ca8 ffffffff81346fa9 0000000000000000
  ffff880059173ce0 ffffffff81063232 ffff8800372bc028 ffff8800373f3740
  ffff8800372bc000 ffff880062ad37c0 0000000000000001 ffff880059173cf0
 Call Trace:
  [<ffffffff81346fa9>] dump_stack+0x4b/0x72
  [<ffffffff81063232>] warn_slowpath_common+0x82/0xc0
  [<ffffffff8106332a>] warn_slowpath_null+0x1a/0x20
  [<ffffffffa0047a12>] drm_atomic_get_property+0x232/0x2b0 [drm]
  [<ffffffffa00356dc>] drm_object_property_get_value+0x6c/0x70 [drm]
  [<ffffffffa003330f>] dpms_show+0x2f/0x70 [drm]
  [<ffffffff8145f090>] dev_attr_show+0x20/0x50
  [<ffffffff8124b48c>] sysfs_kf_seq_show+0xbc/0x130
  [<ffffffff81249d73>] kernfs_seq_show+0x23/0x30
  [<ffffffff811f3d8a>] seq_read+0xca/0x360
  [<ffffffff8124a7da>] kernfs_fop_read+0x10a/0x160
  [<ffffffff811d0888>] __vfs_read+0x28/0xd0
  [<ffffffff812cbe80>] ? security_file_permission+0xa0/0xc0
  [<ffffffff811d102f>] ? rw_verify_area+0x4f/0xe0
  [<ffffffff811d1143>] vfs_read+0x83/0x130
  [<ffffffff811d1df6>] SyS_read+0x46/0xa0
  [<ffffffff81001b40>] ? syscall_return_slowpath+0x50/0x130
  [<ffffffff81659636>] entry_SYSCALL_64_fastpath+0x16/0x75
Quoted 1 line

Both don't look like serious issues, but not sexy to see at each time.

This should be fixed with

commit 621bd0f6982badd6483acb191eb7b6226a578328

Author: Daniel Vetter <[email protected]>
Date:   Tue Sep 29 09:56:53 2015 +0200
Quoted 5 lines
Quoted 3 lines

drm: Fix locking for sysfs dpms file

If not please scream.

OK, I'll give a shot.

This one was confirmed to work. Feel free to my tested-by tag if you can still add.

thanks,

Takashi
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

#4 lore raw

Re: [Intel-gfx] 4.2-rc4 kernel warnings on HSW laptop [regression]

In reply to Takashi Iwai
Quoted 18 lines · Takashi Iwai
Quoted 16 lines · Daniel Vetter

Another pile of regressions for Jairo to track ...

Quoted 11 lines · Takashi Iwai

Hi,

I noticed that a HSW laptop gets a few new warnings since 4.2-rc kernels. One error messages pops at each boot time:

Console: switching to colour dummy device 80x25
[drm] Replacing VGA console driver
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0!

Quoted 4 lines
Quoted 2 lines

There's patches for this one already, but I accidentally applied them for -next, not -fixes. They should land for -rc6.

Could you point commit ids?

It was wishful thinking on my side, mixed them up with other patches. I think this one's still open :(
-Daniel

Signature · 7 lines
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/dri-devel
#5 lore raw

Re: 4.2-rc4 kernel warnings on HSW laptop [regression]

Quoted 19 lines · Daniel Vetter
Quoted 18 lines · Takashi Iwai
Quoted 16 lines · Daniel Vetter

Another pile of regressions for Jairo to track ...

Quoted 11 lines · Takashi Iwai

Hi,

I noticed that a HSW laptop gets a few new warnings since 4.2-rc kernels. One error messages pops at each boot time:

Console: switching to colour dummy device 80x25
[drm] Replacing VGA console driver
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0!

Quoted 7 lines
Quoted 4 lines
Quoted 2 lines

There's patches for this one already, but I accidentally applied them for -next, not -fixes. They should land for -rc6.

Could you point commit ids?

It was wishful thinking on my side, mixed them up with other patches. I think this one's still open :(

7f4c628 drm/i915: Assign hwmode after encoder state readout 0f64614 drm/i915: Fix clock readout when pipes are enabled w/o ports

not enough?

Signature · 6 lines
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
#6 lore raw

Re: [Intel-gfx] 4.2-rc4 kernel warnings on HSW laptop [regression]

Quoted 25 lines · Ville Syrjälä
Quoted 24 lines · Daniel Vetter
Quoted 22 lines · Takashi Iwai
Quoted 16 lines · Daniel Vetter

Another pile of regressions for Jairo to track ...

Quoted 11 lines · Takashi Iwai

Hi,

I noticed that a HSW laptop gets a few new warnings since 4.2-rc kernels. One error messages pops at each boot time:

Console: switching to colour dummy device 80x25
[drm] Replacing VGA console driver
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes: PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0!

Quoted 2 lines

There's patches for this one already, but I accidentally applied them for -next, not -fixes. They should land for -rc6.

Could you point commit ids?

Quoted 7 lines
Quoted 2 lines

It was wishful thinking on my side, mixed them up with other patches. I think this one's still open :(

7f4c628 drm/i915: Assign hwmode after encoder state readout 0f64614 drm/i915: Fix clock readout when pipes are enabled w/o ports

not enough?

The relevant bug is [1], everyone please let's track this there.

BR,
Jani.

[1] https://bugs.freedesktop.org/show_bug.cgi?id=91428

Quoted 8 lines
Signature · 7 lines
-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
Signature · 5 lines
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/dri-devel
#7 lore raw

Re: 4.2-rc4 kernel warnings on HSW laptop [regression]

In reply to Daniel Vetter

Created the following bug --> https://bugs.freedesktop.org/show_bug.cgi?id=92451 to follow up this regression

Regards

-----Original Message-----
From: Daniel Vetter [mailto:[email protected]] On Behalf Of Daniel Vetter
Sent: Monday, October 12, 2015 2:04 AM
To: Takashi Iwai
Cc: [email protected]; [email protected]; Miramontes Caton, Jairo Daniel
Subject: Re: [Intel-gfx] 4.2-rc4 kernel warnings on HSW laptop [regression]

Another pile of regressions for Jairo to track ...

Quoted 5 lines · Takashi Iwai

Hi,

I noticed that a HSW laptop gets a few new warnings since 4.2-rc kernels. One error messages pops at each boot time:

Quoted 7 lines

Console: switching to colour dummy device 80x25 [drm] Replacing VGA
console driver [drm] Supports vblank timestamp caching Rev 2
(21.10.2013).
[drm] Driver supports precise vblank timestamp query.
vgaarb: device changed decodes:
PCI:0000:00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[drm:drm_calc_timestamping_constants [drm]] *ERROR* crtc 21: Can't calculate constants, dotclock = 0!

There's patches for this one already, but I accidentally applied them for -next, not -fixes. They should land for -rc6.

Quoted 29 lines

Then a warning when I start powertop:

 WARNING: CPU: 1 PID: 1674 at drivers/gpu/drm/drm_atomic.c:889 drm_atomic_get_property+0x232/0x2b0 [drm]()
 CPU: 1 PID: 1674 Comm: powertop Tainted: G        W       4.3.0-rc4-test+ #93
 Hardware name: Hewlett-Packard HP ProBook 430 G1/1946, BIOS L73 Ver. 08.05 2013/03/15
  ffffffffa005b289 ffff880059173ca8 ffffffff81346fa9 0000000000000000
  ffff880059173ce0 ffffffff81063232 ffff8800372bc028 ffff8800373f3740
  ffff8800372bc000 ffff880062ad37c0 0000000000000001 ffff880059173cf0  
Call Trace:
  [<ffffffff81346fa9>] dump_stack+0x4b/0x72
  [<ffffffff81063232>] warn_slowpath_common+0x82/0xc0
  [<ffffffff8106332a>] warn_slowpath_null+0x1a/0x20
  [<ffffffffa0047a12>] drm_atomic_get_property+0x232/0x2b0 [drm]
  [<ffffffffa00356dc>] drm_object_property_get_value+0x6c/0x70 [drm]
  [<ffffffffa003330f>] dpms_show+0x2f/0x70 [drm]
  [<ffffffff8145f090>] dev_attr_show+0x20/0x50
  [<ffffffff8124b48c>] sysfs_kf_seq_show+0xbc/0x130
  [<ffffffff81249d73>] kernfs_seq_show+0x23/0x30
  [<ffffffff811f3d8a>] seq_read+0xca/0x360
  [<ffffffff8124a7da>] kernfs_fop_read+0x10a/0x160
  [<ffffffff811d0888>] __vfs_read+0x28/0xd0
  [<ffffffff812cbe80>] ? security_file_permission+0xa0/0xc0
  [<ffffffff811d102f>] ? rw_verify_area+0x4f/0xe0
  [<ffffffff811d1143>] vfs_read+0x83/0x130
  [<ffffffff811d1df6>] SyS_read+0x46/0xa0
  [<ffffffff81001b40>] ? syscall_return_slowpath+0x50/0x130
  [<ffffffff81659636>] entry_SYSCALL_64_fastpath+0x16/0x75
Quoted 1 line

Both don't look like serious issues, but not sexy to see at each time.

This should be fixed with

commit 621bd0f6982badd6483acb191eb7b6226a578328

Author: Daniel Vetter <[email protected]>
Date:   Tue Sep 29 09:56:53 2015 +0200

drm: Fix locking for sysfs dpms file

If not please scream.

Thanks, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/intel-gfx