Am 17.10.18 um 10:14 schrieb Christoph Hellwig:
> On Tue, Oct 16, 2018 at 07:33:53PM +0200, Stefan Priebe - Profihost AG wrote:
>> Hi David,
>>
>> can you give as any hint? We're running aroud 120 Adaptec Controllers
>> and i don't want to replace them
Hi David,
can you give as any hint? We're running aroud 120 Adaptec Controllers
and i don't want to replace them all...
Greets,
Stefan
Am 27.09.2018 um 14:23 schrieb Stefan Priebe - Profihost AG:
>
> Am 27.09.2018 um 12:59 schrieb Emmanuel Florac:
>> Le Wed, 19 S
Hi Dave,
Am 03.10.2018 um 19:32 schrieb dave.carr...@microchip.com:
>> Am 27.09.2018 um 12:59 schrieb Emmanuel Florac:
>>> Le Wed, 19 Sep 2018 08:10:41 +0200
>>> Stefan Priebe - Profihost AG écrivait:
>>>
>>>> Hello,
>>>>
>>>&
Am 27.09.2018 um 12:59 schrieb Emmanuel Florac:
> Le Wed, 19 Sep 2018 08:10:41 +0200
> Stefan Priebe - Profihost AG écrivait:
>
>> Hello,
>>
>> after upgrading the aacraid driver / kernel from aacraid 50792 to
>> aacraid 50877.
>>
>> I get aborte
Am 23.09.2018 um 20:22 schrieb Stefan Priebe - Profihost AG:
>
> Am 22.09.2018 um 23:40 schrieb Bart Van Assche:
>> On 9/18/18 11:10 PM, Stefan Priebe - Profihost AG wrote:
>>> after upgrading the aacraid driver / kernel from aacraid 50792 to
>>> aacraid 50877.
&g
Am 22.09.2018 um 23:40 schrieb Bart Van Assche:
> On 9/18/18 11:10 PM, Stefan Priebe - Profihost AG wrote:
>> after upgrading the aacraid driver / kernel from aacraid 50792 to
>> aacraid 50877.
>
> The aacraid driver version was updated to 50792 in commit 0662cc968ace
>
nobody?
Greets,
Stefan
Am 19.09.2018 um 08:10 schrieb Stefan Priebe - Profihost AG:
> Hello,
>
> after upgrading the aacraid driver / kernel from aacraid 50792 to
> aacraid 50877.
>
> I get aborted comands every night.
>
> kern-20180830.gz:Aug 30 01:55:26 server1044-h
Hello,
after upgrading the aacraid driver / kernel from aacraid 50792 to
aacraid 50877.
I get aborted comands every night.
kern-20180830.gz:Aug 30 01:55:26 server1044-han kernel: [63693.009056]
aacraid: Host adapter abort request.
kern-20180830.gz:Aug 30 01:55:26 server1044-han kernel: [63693.00
Am 06.01.2018 um 12:40 schrieb Simon Leinen:
> Yves-Alexis Perez wrote:
>> since kernel 4.11 (sorry it took so long to report) I have a box
>> failing to boot with a NULL pointer dereference (the box is stuck
>> there afterwards).
>
> I get the same result on a Quanta server with several 4.13 and
ping - anybody?
Greets,
Stefan
Am 08.11.2017 um 10:33 schrieb Stefan Priebe - Profihost AG:
> Hello,
>
> after upgrading some servers from 4.9 to a kernel > 4.11 i saw a
> regression where i cannot boot into the os.
>
> The kernel is crashing in the isci (NOT iscsi)
Hello,
after upgrading some servers from 4.9 to a kernel > 4.11 i saw a
regression where i cannot boot into the os.
The kernel is crashing in the isci (NOT iscsi) driver in task abort.
Message:
Unable to handle kernel NULL pointer dereference at isci_task_abort_task
git bisect detected the foll
Am 07.01.2015 um 15:31 schrieb Christoph Hellwig:
> On Tue, Jan 06, 2015 at 02:39:16PM -0800, Nicholas A. Bellinger wrote:
>> The fabric_max_sectors=8192 value is already being exposed by target in
>> block limits EVPD as MAXIMUM TRANSFER LENGTH.
>>
>> I'm guessing that since the host side support
Am 30.12.2014 um 12:32 schrieb Christoph Hellwig:
> On Sun, Dec 28, 2014 at 01:08:59PM +0100, Stefan Priebe wrote:
>>> Nic, can you fix LIO to expose the proper max xfer size?
>>
>> some more problems while running this patch.
>>
>> My crucial m500 and m550 ssds (i have around 60 in 30 different c
Hi,
while using vanilla 3.10.44 with drbd on top of a md raid1.
I'm pretty often hitting the followin kernel bug.
It reminds me of:
http://lists.openwall.net/linux-kernel/2014/02/19/428
But i don't use bcache.
[sched_delayed] sched: RT throttling activated
BUG: unable to handle kernel NULL poi
14 matches
Mail list logo
