linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Niccolò Belli" <niccolo.belli@linuxsystems.it>
To: Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-acpi@vger.kernel.org>
Subject: Re: [Dell XPS 13 9343] Random kernel Oops at boot with "acpi=ht", disappearing with "acpi=off"
Date: Thu, 08 Oct 2015 12:17:39 +0200	[thread overview]
Message-ID: <9517e70c-d3ec-4dd0-8064-a06546812d16@linuxsystems.it> (raw)
In-Reply-To: <20151008100615.GO1506@lahna.fi.intel.com>

Il giovedì 8 ottobre 2015 12:06:15 CEST, Mika Westerberg ha scritto:
> On Mon, Oct 05, 2015 at 05:59:38PM +0200, Niccolò Belli wrote:
>> Il lunedì 5 ottobre 2015 15:54:49 CEST, Mika Westerberg ha scritto: ...
>
> It looks like a memory corruption somewhere. Unfortunately it is not
> obvious from the log where :-(

It seems I'm the only one with this issue, both Dell and an Aaron Lu (an 
Intel employee which uses Fedora) told me they don't experience it: 
https://bugzilla.kernel.org/show_bug.cgi?id=105251
So maybe it has something to do with my configuration, maybe the combo 
dm-crypt + btrfs which is pretty unusual, but I really don't know.

If you can tell me how to obtain a more useful log I can provide it.

Thanks,
Niccolò Belli

  reply	other threads:[~2015-10-08 10:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-02  9:59 [Dell XPS 13 9343] Random kernel Oops at boot with "acpi=ht", disappearing with "acpi=off" Niccolò Belli
2015-10-02 10:19 ` Mika Westerberg
2015-10-03 10:11   ` Niccolò Belli
2015-10-05 10:46     ` Mika Westerberg
2015-10-05 13:41       ` Niccolò Belli
2015-10-05 13:54         ` Mika Westerberg
2015-10-05 15:59           ` Niccolò Belli
2015-10-08 10:06             ` Mika Westerberg
2015-10-08 10:17               ` Niccolò Belli [this message]
2015-10-08 10:28                 ` Mika Westerberg
2015-10-12 14:36                   ` Niccolò Belli
2015-10-18 22:18                   ` Niccolò Belli

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=9517e70c-d3ec-4dd0-8064-a06546812d16@linuxsystems.it \
    --to=niccolo.belli@linuxsystems.it \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    /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).