Bug#762148: marked as done (Fix intel_pstate kernel panic in wheezy, already done upstream)

["Debian Bug Tracking System" <owner@bugs.debian.org>]

Your message dated Sun, 01 Jul 2018 02:08:59 +0100
with message-id <72304fa0a7a151e6f477a33bb6a5e172199bc8fa.camel@decadent.org.uk>
and subject line Re: Bug#762148: Fix intel_pstate kernel panic in wheezy, already done upstream
has caused the Debian Bug report #762148,
regarding Fix intel_pstate kernel panic in wheezy, already done upstream
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


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

--- Begin Message ---

• To: submit@bugs.debian.org
• Subject: Fix intel_pstate kernel panic in wheezy, already done upstream
• From: Jimmy Kaplowitz <jkaplowitz@google.com>
• Date: Thu, 18 Sep 2014 16:18:08 -0700
• Message-id: <CAJbdudXiGvHxiXM2TLXEkYfKDsTkoYqH62BPqeMekLx0fmTdEQ@mail.gmail.com>

Package: linux-image-3.2.0-4-amd64

Version: 3.2.60-1+deb7u3

Severity: normal

Tags: patch

Hi kernel folks,

The intel_pstate driver in wheezy fails to calculate its timer timeout correctly, which can cause the driver to race with itself. Google's kernel engineers identified this as the cause for an occasional kernel panic which our test infrastructure picked up. The fix is one-line and was accepted upstream in April of last year.

Could you please apply the one-line fix to the next wheezy stable update? While we've only encountered this infrequently, this is the kind of patch that can only help things.

kernel.org git commit ID: ec376a2ab97ec3be52ca282dc6ac102e805d1005

Link to the diff in kernel.org: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/cpufreq/intel_pstate.c?id=ec376a2ab97ec3be52ca282dc6ac102e805d1005

Thanks!

- Jimmy

--- End Message ---

--- Begin Message ---

• To: 762148-done@bugs.debian.org
• Subject: Re: Bug#762148: Fix intel_pstate kernel panic in wheezy, already done upstream
• From: Ben Hutchings <ben@decadent.org.uk>
• Date: Sun, 01 Jul 2018 02:08:59 +0100
• Message-id: <72304fa0a7a151e6f477a33bb6a5e172199bc8fa.camel@decadent.org.uk>
• In-reply-to: <1411560916.3659.20.camel@decadent.org.uk>
• References: <CAJbdudXiGvHxiXM2TLXEkYfKDsTkoYqH62BPqeMekLx0fmTdEQ@mail.gmail.com> <1411560916.3659.20.camel@decadent.org.uk>

On Wed, 24 Sep 2014 13:15:16 +0100 Ben Hutchings <ben@decadent.org.uk> wrote:
> Control: tag -1 - patch
> Control: tag -1 moreinfo
> 
> On Thu, 2014-09-18 at 16:18 -0700, Jimmy Kaplowitz wrote:
> > Package: linux-image-3.2.0-4-amd64
> > Version: 3.2.60-1+deb7u3
> > Severity: normal
> > Tags: patch
> > 
> > 
> > Hi kernel folks,
> > 
> > 
> > The intel_pstate driver in wheezy
> [...]
> 
> No such thing in 3.2, and we didn't backport it either.  Is there a
> similar bug elsewhere?

Even if there was, Debian 7 "wheezy" support has ended, so closing this.

Ben.

-- 
Ben Hutchings
Q.  Which is the greater problem in the world today,
    ignorance or apathy?
A.  I don't know and I couldn't care less.

Attachment: signature.asc
Description: This is a digitally signed message part

--- End Message ---