Hello,
(cc'ing Dan, hi!)
On Thu, Sep 29, 2016 at 08:25:58AM -0300, Henrique de Moraes Holschuh wrote:
> Actually, according to Shah's post from the 26th to this thread,
> everything works just fine even with the IOMMU enabled, as long as the
> system is configured to NOT auto-shutdown unused
Hello,
(cc'ing Dan, hi!)
On Thu, Sep 29, 2016 at 08:25:58AM -0300, Henrique de Moraes Holschuh wrote:
> Actually, according to Shah's post from the 26th to this thread,
> everything works just fine even with the IOMMU enabled, as long as the
> system is configured to NOT auto-shutdown unused
On Thu, 29 Sep 2016, t...@kernel.org wrote:
> On Wed, Sep 28, 2016 at 05:45:08AM +, Shah, Nehal-bakulchandra wrote:
> > Can someone please help me to debug this issue?
>
> The only thing I can do from libata side is disbling msi on the
> affected platform, but the problem doesn't seem
On Thu, 29 Sep 2016, t...@kernel.org wrote:
> On Wed, Sep 28, 2016 at 05:45:08AM +, Shah, Nehal-bakulchandra wrote:
> > Can someone please help me to debug this issue?
>
> The only thing I can do from libata side is disbling msi on the
> affected platform, but the problem doesn't seem
Hello,
On Wed, Sep 28, 2016 at 05:45:08AM +, Shah, Nehal-bakulchandra wrote:
> Can someone please help me to debug this issue?
The only thing I can do from libata side is disbling msi on the
affected platform, but the problem doesn't seem confined to ahci, so
probably the right thing to do
Hello,
On Wed, Sep 28, 2016 at 05:45:08AM +, Shah, Nehal-bakulchandra wrote:
> Can someone please help me to debug this issue?
The only thing I can do from libata side is disbling msi on the
affected platform, but the problem doesn't seem confined to ahci, so
probably the right thing to do
m>; linux-...@vger.kernel.org;
hol...@ahsoftware.de; t...@kernel.org; linux-...@vger.kernel.org;
linux-kernel@vger.kernel.org
Subject: RE: ATA failure regression
Hi Bharat
Thanks for the reply. I have observed following thing
If IOMMU is enabled in BIOS and I use following option FCH SATA Debug Options
-...@vger.kernel.org;
linux-kernel@vger.kernel.org
Subject: RE: ATA failure regression
Hi Bharat
Thanks for the reply. I have observed following thing
If IOMMU is enabled in BIOS and I use following option FCH SATA Debug Options
--> Unused SATA Port Auto Shut Down Disabled. Issue is not happening
> Hi All,
>
> Resending this wider audience
>
> Currently I am working on AMD future platform. I am hitting the same bug of
> ATA Failure Regression reported in past.
> (https://patchwork.kernel.org/patch/6875661/) or
> http://lkml.iu.edu/hypermail/linux/kernel/150
> Hi All,
>
> Resending this wider audience
>
> Currently I am working on AMD future platform. I am hitting the same bug of
> ATA Failure Regression reported in past.
> (https://patchwork.kernel.org/patch/6875661/) or
> http://lkml.iu.edu/hypermail/linux/kernel/150
Hi All,
Resending this wider audience
Currently I am working on AMD future platform. I am hitting the same bug of
ATA Failure Regression reported in past.
(https://patchwork.kernel.org/patch/6875661/) or
http://lkml.iu.edu/hypermail/linux/kernel/1507.3/01961.html
I am newbie
Hi All,
Resending this wider audience
Currently I am working on AMD future platform. I am hitting the same bug of
ATA Failure Regression reported in past.
(https://patchwork.kernel.org/patch/6875661/) or
http://lkml.iu.edu/hypermail/linux/kernel/1507.3/01961.html
I am newbie
Hi Jiang,
Currently I am working on AMD future platform. I am hitting the same bug of
ATA Failure Regression reported in past.
(https://patchwork.kernel.org/patch/6875661/) or
http://lkml.iu.edu/hypermail/linux/kernel/1507.3/01961.html
I am newbie to this and because of this Ubuntu 16.04
Hi Jiang,
Currently I am working on AMD future platform. I am hitting the same bug of
ATA Failure Regression reported in past.
(https://patchwork.kernel.org/patch/6875661/) or
http://lkml.iu.edu/hypermail/linux/kernel/1507.3/01961.html
I am newbie to this and because of this Ubuntu 16.04
Am 31.07.2015 um 12:42 schrieb Jiang Liu:
On 2015/7/31 18:38, Alexander Holler wrote:
Am 28.07.2015 um 20:37 schrieb Alexander Holler:
Same problem here with the AMD SATA controller (1022:7801). It failed to
identify the second disk when using 4.2-rc4.
nointremap helped, nothing else
On 2015/7/31 18:38, Alexander Holler wrote:
> Am 28.07.2015 um 20:37 schrieb Alexander Holler:
>
>> Same problem here with the AMD SATA controller (1022:7801). It failed to
>> identify the second disk when using 4.2-rc4.
>>
>> nointremap helped, nothing else tested
>
> A quick look at the
Am 28.07.2015 um 20:37 schrieb Alexander Holler:
Same problem here with the AMD SATA controller (1022:7801). It failed to
identify the second disk when using 4.2-rc4.
nointremap helped, nothing else tested
A quick look at the change history and two tests are suggesting that the
right one
Am 31.07.2015 um 12:42 schrieb Jiang Liu:
On 2015/7/31 18:38, Alexander Holler wrote:
Am 28.07.2015 um 20:37 schrieb Alexander Holler:
Same problem here with the AMD SATA controller (1022:7801). It failed to
identify the second disk when using 4.2-rc4.
nointremap helped, nothing else
Am 28.07.2015 um 20:37 schrieb Alexander Holler:
Same problem here with the AMD SATA controller (1022:7801). It failed to
identify the second disk when using 4.2-rc4.
nointremap helped, nothing else tested
A quick look at the change history and two tests are suggesting that the
right one
On 2015/7/31 18:38, Alexander Holler wrote:
Am 28.07.2015 um 20:37 schrieb Alexander Holler:
Same problem here with the AMD SATA controller (1022:7801). It failed to
identify the second disk when using 4.2-rc4.
nointremap helped, nothing else tested
A quick look at the change history
Am 28.07.2015 um 20:19 schrieb Alex Deucher:
On Mon, Jul 27, 2015 at 12:30 PM, Jiang Liu wrote:
On 2015/7/27 23:21, Alex Deucher wrote:
On Sun, Jul 26, 2015 at 11:01 PM, Jiang Liu wrote:
On 2015/7/25 1:38, Alex Deucher wrote:
On Thu, Jul 23, 2015 at 2:44 PM, Alex Deucher wrote:
On Thu,
On Mon, Jul 27, 2015 at 12:30 PM, Jiang Liu wrote:
> On 2015/7/27 23:21, Alex Deucher wrote:
>> On Sun, Jul 26, 2015 at 11:01 PM, Jiang Liu
>> wrote:
>>> On 2015/7/25 1:38, Alex Deucher wrote:
On Thu, Jul 23, 2015 at 2:44 PM, Alex Deucher
wrote:
> On Thu, Jul 23, 2015 at 2:35
On Mon, Jul 27, 2015 at 12:30 PM, Jiang Liu jiang@linux.intel.com wrote:
On 2015/7/27 23:21, Alex Deucher wrote:
On Sun, Jul 26, 2015 at 11:01 PM, Jiang Liu jiang@linux.intel.com
wrote:
On 2015/7/25 1:38, Alex Deucher wrote:
On Thu, Jul 23, 2015 at 2:44 PM, Alex Deucher
Am 28.07.2015 um 20:19 schrieb Alex Deucher:
On Mon, Jul 27, 2015 at 12:30 PM, Jiang Liu jiang@linux.intel.com wrote:
On 2015/7/27 23:21, Alex Deucher wrote:
On Sun, Jul 26, 2015 at 11:01 PM, Jiang Liu jiang@linux.intel.com wrote:
On 2015/7/25 1:38, Alex Deucher wrote:
On Thu, Jul
On 2015/7/27 23:21, Alex Deucher wrote:
> On Sun, Jul 26, 2015 at 11:01 PM, Jiang Liu wrote:
>> On 2015/7/25 1:38, Alex Deucher wrote:
>>> On Thu, Jul 23, 2015 at 2:44 PM, Alex Deucher wrote:
On Thu, Jul 23, 2015 at 2:35 PM, Tejun Heo wrote:
> Hello,
>
> On Thu, Jul 23, 2015 at
On 2015/7/27 23:21, Alex Deucher wrote:
On Sun, Jul 26, 2015 at 11:01 PM, Jiang Liu jiang@linux.intel.com wrote:
On 2015/7/25 1:38, Alex Deucher wrote:
On Thu, Jul 23, 2015 at 2:44 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Thu, Jul 23, 2015 at 2:35 PM, Tejun Heo t...@kernel.org
On 2015/7/25 1:38, Alex Deucher wrote:
> On Thu, Jul 23, 2015 at 2:44 PM, Alex Deucher wrote:
>> On Thu, Jul 23, 2015 at 2:35 PM, Tejun Heo wrote:
>>> Hello,
>>>
>>> On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote:
Something new in kernel 4.2 seems to have broken one of my hard
On 2015/7/25 1:38, Alex Deucher wrote:
On Thu, Jul 23, 2015 at 2:44 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Thu, Jul 23, 2015 at 2:35 PM, Tejun Heo t...@kernel.org wrote:
Hello,
On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote:
Something new in kernel 4.2 seems to have
On Thu, Jul 23, 2015 at 2:44 PM, Alex Deucher wrote:
> On Thu, Jul 23, 2015 at 2:35 PM, Tejun Heo wrote:
>> Hello,
>>
>> On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote:
>>> Something new in kernel 4.2 seems to have broken one of my hard drives
>>> (ssd) in kernel 4.2. 4.1 and
On Thu, Jul 23, 2015 at 2:44 PM, Alex Deucher alexdeuc...@gmail.com wrote:
On Thu, Jul 23, 2015 at 2:35 PM, Tejun Heo t...@kernel.org wrote:
Hello,
On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote:
Something new in kernel 4.2 seems to have broken one of my hard drives
(ssd) in
On Thu, Jul 23, 2015 at 2:35 PM, Tejun Heo wrote:
> Hello,
>
> On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote:
>> Something new in kernel 4.2 seems to have broken one of my hard drives
>> (ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the
>> relevant logs.
>>
> ...
Hello,
On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote:
> Something new in kernel 4.2 seems to have broken one of my hard drives
> (ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the
> relevant logs.
>
...
> [6.547628] ata2.00: qc timeout (cmd 0xec)
> [
Something new in kernel 4.2 seems to have broken one of my hard drives
(ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the
relevant logs.
Kernel 4.1:
[1.435809] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[1.435837] ata1: SATA link up 3.0 Gbps (SStatus 123
Hello,
On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote:
Something new in kernel 4.2 seems to have broken one of my hard drives
(ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the
relevant logs.
...
[6.547628] ata2.00: qc timeout (cmd 0xec)
[6.547721]
On Thu, Jul 23, 2015 at 2:35 PM, Tejun Heo t...@kernel.org wrote:
Hello,
On Thu, Jul 23, 2015 at 01:48:24PM -0400, Alex Deucher wrote:
Something new in kernel 4.2 seems to have broken one of my hard drives
(ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the
relevant logs.
Something new in kernel 4.2 seems to have broken one of my hard drives
(ssd) in kernel 4.2. 4.1 and older kernels work fine. Here are the
relevant logs.
Kernel 4.1:
[1.435809] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[1.435837] ata1: SATA link up 3.0 Gbps (SStatus 123
36 matches
Mail list logo
