Hi!
Just wanted to say - in my case the AHCI timeouts (and therefor the
panics afterwards) were solved by updating the firmware of my SSDs.
[Corsair Force 3, 120GB, old firmware: 1.3, new firmware: 1.3.3]
Armin
On 10/28/11 01:19, Pegasus Mc Cleaft wrote:
If it's only one process, the machine
>> If it's only one process, the machine (usually) doesn't hang, even
>> when that process is copying big files back and forth for a long
>> period of time (it's a backup process). But interleave that process
>> with another one accessing the same disk, and poof!, almost
>> immediately ahci tim
On Wed, 26 Oct 2011 16:00:55 +0200
"C. P. Ghost" wrote:
> On Wed, Oct 26, 2011 at 2:27 AM, Alexander Kabaev
> wrote:
> > I do see timeouts on one of my Samsung ST3750330A disks and they
> > definitely do not cause any panics. The weird part in my case is
> > that disk then immediately reappears
In article <111926.10138.25387@localhost> you wrote:
> On Wed, Oct 26, 2011 at 2:27 AM, Alexander Kabaev wrote:
> > I do see timeouts on one of my Samsung ST3750330A disks and they
> > definitely do not cause any panics. The weird part in my case is that
> > disk then immediately reappears as onli
On Wed, Oct 26, 2011 at 2:27 AM, Alexander Kabaev wrote:
> I do see timeouts on one of my Samsung ST3750330A disks and they
> definitely do not cause any panics. The weird part in my case is that
> disk then immediately reappears as online and mirror zpool can be
> rebuilt by just onlining the dis
On Tue, 18 Oct 2011 14:28:07 +0100
"Steven Hartland" wrote:
>
> - Original Message -
> From: "Alexey Shuvaev"
> To:
> Sent: Tuesday, October 18, 2011 2:13 PM
> Subject: Re: Panics after AHCI timeouts
>
>
> > On Tue, Oct 18, 2011
On Mon, Oct 24, 2011 at 08:27:49PM +0200, C. P. Ghost wrote:
> On Tue, Oct 18, 2011 at 3:13 PM, Alexey Shuvaev
> wrote:
> > On Tue, Oct 18, 2011 at 06:19:19AM +0800, Adrian Chadd wrote:
> >> On 18 October 2011 03:00, Alexey Shuvaev
> >> wrote:
> >> > On Sat, Oct 08, 2011 at 10:14:56PM +0200, Alex
On Tue, Oct 18, 2011 at 3:13 PM, Alexey Shuvaev
wrote:
> On Tue, Oct 18, 2011 at 06:19:19AM +0800, Adrian Chadd wrote:
>> On 18 October 2011 03:00, Alexey Shuvaev
>> wrote:
>> > On Sat, Oct 08, 2011 at 10:14:56PM +0200, Alexey Shuvaev wrote:
>> >> Hello list!
>> >>
>> > Errr... Replying to myself
Hi.
Alexey Shuvaev wrote:
> On Sat, Oct 08, 2011 at 10:14:56PM +0200, Alexey Shuvaev wrote:
> Errr... Replying to myself... Ping? Should I file a PR and put it
> in the back burner? :)
Sorry for not replying, I wasn't home to look on it closely.
>> In the view of upcoming RELEASE-9.0 I should ha
- Original Message -
From: "Alexey Shuvaev"
To:
Sent: Tuesday, October 18, 2011 2:13 PM
Subject: Re: Panics after AHCI timeouts
On Tue, Oct 18, 2011 at 06:19:19AM +0800, Adrian Chadd wrote:
On 18 October 2011 03:00, Alexey Shuvaev
wrote:
> On Sat, Oct 08, 2011
On Tue, Oct 18, 2011 at 06:19:19AM +0800, Adrian Chadd wrote:
> On 18 October 2011 03:00, Alexey Shuvaev
> wrote:
> > On Sat, Oct 08, 2011 at 10:14:56PM +0200, Alexey Shuvaev wrote:
> >> Hello list!
> >>
> > Errr... Replying to myself... Ping? Should I file a PR and put it
> > in the back burner?
On 18 October 2011 03:00, Alexey Shuvaev
wrote:
> On Sat, Oct 08, 2011 at 10:14:56PM +0200, Alexey Shuvaev wrote:
>> Hello list!
>>
> Errr... Replying to myself... Ping? Should I file a PR and put it
> in the back burner? :)
I think filing a PR is a good move. Then just be proactive and poke
peop
On Sat, Oct 08, 2011 at 10:14:56PM +0200, Alexey Shuvaev wrote:
> Hello list!
>
Errr... Replying to myself... Ping? Should I file a PR and put it
in the back burner? :)
> In the view of upcoming RELEASE-9.0 I should have reported it earlier,
> but it is better later than never... Every time I wan
Hello list!
In the view of upcoming RELEASE-9.0 I should have reported it earlier,
but it is better later than never... Every time I wanted to report
this, the system was ~one month old and I tried to upgrade it
to see, if the problem was still there, waiting for the next panic...
and when it fina
14 matches
Mail list logo
