From: Oleksandr Natalenko <oleksandr@natalenko.name>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Re: [BUG] oops in cpufreq driver with AMD Kaveri CPU
Date: Tue, 14 Apr 2015 19:07:46 +0300 [thread overview]
Message-ID: <1465982.AWUTj1UaDo@spock> (raw)
In-Reply-To: <9508464.Rg48i9FdUc@spock>
Cross-posting from kernel bugzilla:
===
Definitely not a kernel bug.
I've replaced RAM module with another one and the issue went away.
No idea why oopses refered to ACPI, but they seem to be the result of simple
hardware incompatibility.
===
On Tuesday 18 November 2014 21:07:51 Oleksandr Natalenko wrote:
> Hmmm, weird, acpi=off as well as disabling ASPM and NMI watchdog didn't help
> : (.
>
> Now trying to update BIOS.
>
> P.S. Still affected while using 3.17.2 kernel.
>
> On Tuesday 11 November 2014 12:41:18 Oleksandr Natalenko wrote:
> > It seems that this bug has nothing to do with acpi-cpufreq code but with
> > another ACPI area.
> >
> > With ACPI enabled kernel may hang in a day or in a week (never survived
> > more than approx. 2 weeks). With acpi=off it seems to work OK. For
> > instance, I had to boot Ubuntu installer with acpi disabled to finish it
> > successfully.
> >
> > Usually, hanging is not accompanied by panic log. Only small vertical red
> > lines appear on the screen near letters (tried to use plaintext 80x25
> > console without radeon and got the same issue).
> >
> > Still observing this for 3.16 kernel.
> >
> > On Wednesday 13 August 2014 10:12:06 Viresh Kumar wrote:
> > > On 13 August 2014 00:24, Oleksandr Natalenko <oleksandr@natalenko.name>
> >
> > wrote:
> > > > Updated logs.
> > >
> > > Also will it be possible for you to find the last working kernel after
> > > which this
> > > happened?
--
Oleksandr post-factum Natalenko, MSc
pf-kernel community
https://natalenko.name/
next prev parent reply other threads:[~2015-04-14 16:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-04 21:39 [BUG] oops in cpufreq driver with AMD Kaveri CPU Oleksandr Natalenko
2014-08-07 20:53 ` Oleksandr Natalenko
2014-08-08 17:26 ` Oleksandr Natalenko
2014-08-12 5:52 ` Viresh Kumar
2014-08-12 5:55 ` Oleksandr Natalenko
2014-08-12 6:16 ` Viresh Kumar
2014-08-12 7:26 ` Oleksandr Natalenko
2014-08-12 7:46 ` Viresh Kumar
2014-08-12 18:04 ` Oleksandr Natalenko
2014-08-12 18:18 ` Oleksandr Natalenko
2014-08-12 18:54 ` Oleksandr Natalenko
[not found] ` <CAOjmkp_mrMYJJfEqqKtPVrbMuaoJ9W6212LKHETeUsOsJryh-Q@mail.gmail.com>
[not found] ` <CAOjmkp8h19de3bYaLpqmXxEynKi--gHBf6MxXuuNoDzZXw=O8Q@mail.gmail.com>
2014-08-12 23:39 ` Fwd: " Aravind Gopalakrishnan
2014-08-13 8:02 ` Oleksandr Natalenko
2014-08-13 4:36 ` Viresh Kumar
2014-08-13 4:42 ` Viresh Kumar
2014-08-13 5:43 ` Oleksandr Natalenko
2014-11-11 10:41 ` Oleksandr Natalenko
2014-11-18 19:07 ` Oleksandr Natalenko
2015-04-14 16:07 ` Oleksandr Natalenko [this message]
2014-08-13 4:32 ` Viresh Kumar
2014-08-13 5:56 ` Oleksandr Natalenko
2014-08-13 12:45 ` Oleksandr Natalenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1465982.AWUTj1UaDo@spock \
--to=oleksandr@natalenko.name \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=viresh.kumar@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).