From: Carolin Latze <carolin.latze@gmail.com>
To: Tejun Heo <tj@kernel.org>
Cc: hdegoede@redhat.com, linux-ide@vger.kernel.org
Subject: Re: kernel crash with lite-on sata controller Dell XPS 13 9343
Date: Thu, 25 Feb 2016 22:53:18 +0100 [thread overview]
Message-ID: <56CF77CE.2040204@gmail.com> (raw)
In-Reply-To: <20160225215130.GK6092@mtj.duckdns.org>
Hi Tejun
I actually boot with "libata.force=noncq,1.5G". Sorry, forgot to mention
that. Same behavior.
best regards
Carolin
On 25.02.2016 22:51, Tejun Heo wrote:
> Hello, Carolin.
>
> On Thu, Feb 25, 2016 at 10:45:10PM +0100, Carolin Latze wrote:
> ...
>> Since the beginning (started with 3.19.x kernels on this notebook) I had
>> problems with this sata controller:
>>
>> 03:00.0 SATA controller: Lite-On Technology Corporation Device 0224 (rev 10)
>>
>> Very often during boot, the boot just failed with error messages like
>>
>> ata1.00: exception... (I was only able to capture them by taking a picture:
>> https://launchpadlibrarian.net/227876135/IMG_20151128_230313.jpg)
>>
>> Then I keep trying, sometimes I boot into Windows inbetween, and eventually,
>> the kernel comes up.
>>
>> Then, when running and putting a lot of load on the disk (e.g. running dump
>> or a simple update via apt-get upgrade), the system looses its disk and I
>> have to hard reset.
>>
>> The machine runs perfectly fine under Windows, so I don't believe it is a
>> hardware issue.
>>
>> I hope there is a solution to this issue.
> Can you please boot with libata.force=noncq and if that fails post the
> kernel messages of the failure?
>
> Thanks.
>
next prev parent reply other threads:[~2016-02-25 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-25 21:45 kernel crash with lite-on sata controller Dell XPS 13 9343 Carolin Latze
2016-02-25 21:51 ` Tejun Heo
2016-02-25 21:53 ` Carolin Latze [this message]
2016-02-25 22:01 ` Tejun Heo
[not found] ` <56D6A86C.9070007@gmail.com>
2016-03-02 15:25 ` Tejun Heo
2016-03-14 16:02 ` Carolin Latze
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=56CF77CE.2040204@gmail.com \
--to=carolin.latze@gmail.com \
--cc=hdegoede@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=tj@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.