Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #75040 > unrolled thread

Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update

Started byVincas Dargis <vindrg@gmail.com>
First post2022-04-12 20:00 +0200
Last post2022-08-22 18:50 +0200
Articles 5 — 3 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.


Contents

  Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update Vincas Dargis <vindrg@gmail.com> - 2022-04-12 20:00 +0200
    Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update Salvatore Bonaccorso <carnil@debian.org> - 2022-04-24 11:30 +0200
      Processed: Re: Bug#1008585: linux-image-5.10.0-13-amd64:  "clocksource:" log spam after 5.10.103-1 update "Debian Bug Tracking System" <owner@bugs.debian.org> - 2022-04-24 11:30 +0200
      Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update Vincas Dargis <vindrg@gmail.com> - 2022-05-09 20:20 +0200
      Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update Vincas Dargis <vindrg@gmail.com> - 2022-08-22 18:50 +0200

#75040 — Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update

FromVincas Dargis <vindrg@gmail.com>
Date2022-04-12 20:00 +0200
SubjectBug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update
Message-ID<EbsY1-8i3u-3@gated-at.bofh.it>
It seems that this might be fixed in ~5.17, based on this [0] message in thread that speaks about problem seemingly 
similar to mine:

> Yes, I expect to submit it into the next merge window (not the current
> v5.16 merge window, but v5.17).  However, if your situation is urgent, and
> if it works for you, I could submit it as a fix for an earlier regression.

Although all that thread is beyond me to understand...

[0] https://lore.kernel.org/all/20211111000414.GH641268@paulmck-ThinkPad-P17-Gen-1/

[toc] | [next] | [standalone]


#75129

FromSalvatore Bonaccorso <carnil@debian.org>
Date2022-04-24 11:30 +0200
Message-ID<EfGJ4-aQa7-5@gated-at.bofh.it>
In reply to#75040
Control: tags -1 + moreinfo

On Tue, Apr 12, 2022 at 08:49:38PM +0300, Vincas Dargis wrote:
> It seems that this might be fixed in ~5.17, based on this [0] message in
> thread that speaks about problem seemingly similar to mine:
> 
> > Yes, I expect to submit it into the next merge window (not the current
> > v5.16 merge window, but v5.17).  However, if your situation is urgent, and
> > if it works for you, I could submit it as a fix for an earlier regression.
> 
> Although all that thread is beyond me to understand...
> 
> [0] https://lore.kernel.org/all/20211111000414.GH641268@paulmck-ThinkPad-P17-Gen-1/

Would you be able to test the current kernel from unstable so we can
confirm it's fixed in 5.17.3-1?

Regards,
Salvatore

[toc] | [prev] | [next] | [standalone]


#75130 — Processed: Re: Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2022-04-24 11:30 +0200
SubjectProcessed: Re: Bug#1008585: linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update
Message-ID<EfGJ4-aQa7-9@gated-at.bofh.it>
In reply to#75129
Processing control commands:

> tags -1 + moreinfo
Bug #1008585 [src:linux] linux-image-5.10.0-13-amd64: "clocksource:" log spam after 5.10.103-1 update
Added tag(s) moreinfo.

-- 
1008585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008585
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]


#75205

FromVincas Dargis <vindrg@gmail.com>
Date2022-05-09 20:20 +0200
Message-ID<Elg9b-enmr-5@gated-at.bofh.it>
In reply to#75129
2022-04-24 12:20, Salvatore Bonaccorso rašė:
> Would you be able to test the current kernel from unstable so we can
> confirm it's fixed in 5.17.3-1?

I am not sure if I want to install kernel from unstable into production machine.. :) . I believe I'll wait for Bullseye 
backport to see if it helps.

[toc] | [prev] | [next] | [standalone]


#76174

FromVincas Dargis <vindrg@gmail.com>
Date2022-08-22 18:50 +0200
Message-ID<EXiMF-2ku7-5@gated-at.bofh.it>
In reply to#75129
On Sun, 24 Apr 2022 11:20:30 +0200 Salvatore Bonaccorso <carnil@debian.org> wrote:
> Would you be able to test the current kernel from unstable so we can
> confirm it's fixed in 5.17.3-1?

I've installed 5.18 from bullseye-backports:

Aug 19 23:45:36 dl380 kernel: [    0.000000] Linux version 5.18.0-0.bpo.1-amd64 (debian-kernel@lists.debian.org) (gcc-10 
(Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PREEMPT_DYNAMIC Debian 
5.18.2-1~bpo11+1 (2022-06-14

And still got these messages:

Aug 20 09:05:46 dl380 kernel: [33623.544669] clocksource: timekeeping watchdog on CPU14: hpet wd-wd read-back delay of 
84787ns
Aug 20 09:05:46 dl380 kernel: [33623.544685] clocksource: wd-tsc-wd read-back delay of 105669ns, clock-skew test skipped!

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web