Harald Schmalzbauer wrote:
> Alexander Motin schrieb am 29.03.2010 21:25 (localtime):
>> If you wish to send drive - my address is:
>
> Can you use such a drive? I mean for yourself. If yes, then I'll ship
> it, but if you say "na, thanks, no such crap" then I don't want to waste
> your time and h
Alexander Motin schrieb am 29.03.2010 21:25 (localtime):
Harald Schmalzbauer wrote:
I have the drives now running in another server, ich7 chipset.
Using UFS, the complete machine locks up for ~30 secs with disk load of
3.5MB/s. But I don't get any timeout messages and the machine always
recovere
Harald Schmalzbauer wrote:
> I have the drives now running in another server, ich7 chipset.
> Using UFS, the complete machine locks up for ~30 secs with disk load of
> 3.5MB/s. But I don't get any timeout messages and the machine always
> recovered.
Most of ICH7's do not support AHCI. What's about
Alexander Motin schrieb am 03.03.2010 09:18 (localtime):
Harald Schmalzbauer wrote:
Alexander Motin schrieb am 23.02.2010 16:10 (localtime):
Harald Schmalzbauer wrote:
I'm frequently getting my machine locked with ahcichX timeouts:
ahcich2: Timeout on slot 0
ahcich2: is cs 0001 ss
Harald Schmalzbauer schrieb am 14.03.2010 12:12 (localtime):
Harald Schmalzbauer schrieb am 13.03.2010 22:27 (localtime):
Am 03.03.2010 12:06, schrieb Jeremy Chadwick:
On Wed, Mar 03, 2010 at 09:28:25AM +0100, Harald Schmalzbauer wrote:
Alexander Motin schrieb am 03.03.2010 09:18 (localtime):
Harald Schmalzbauer schrieb am 13.03.2010 22:27 (localtime):
Am 03.03.2010 12:06, schrieb Jeremy Chadwick:
On Wed, Mar 03, 2010 at 09:28:25AM +0100, Harald Schmalzbauer wrote:
Alexander Motin schrieb am 03.03.2010 09:18 (localtime):
Harald Schmalzbauer wrote:
Alexander Motin schrieb am 23.02.
Am 03.03.2010 12:06, schrieb Jeremy Chadwick:
> On Wed, Mar 03, 2010 at 09:28:25AM +0100, Harald Schmalzbauer wrote:
>> Alexander Motin schrieb am 03.03.2010 09:18 (localtime):
>>> Harald Schmalzbauer wrote:
Alexander Motin schrieb am 23.02.2010 16:10 (localtime):
> Harald Schmalzbauer wro
On Wed, Mar 03, 2010 at 09:28:25AM +0100, Harald Schmalzbauer wrote:
> Alexander Motin schrieb am 03.03.2010 09:18 (localtime):
> >Harald Schmalzbauer wrote:
> >>Alexander Motin schrieb am 23.02.2010 16:10 (localtime):
> >>>Harald Schmalzbauer wrote:
> I'm frequently getting my machine locked w
Alexander Motin schrieb am 03.03.2010 09:18 (localtime):
Harald Schmalzbauer wrote:
Alexander Motin schrieb am 23.02.2010 16:10 (localtime):
Harald Schmalzbauer wrote:
I'm frequently getting my machine locked with ahcichX timeouts:
ahcich2: Timeout on slot 0
ahcich2: is cs 0001 ss
Harald Schmalzbauer wrote:
> Alexander Motin schrieb am 23.02.2010 16:10 (localtime):
>> Harald Schmalzbauer wrote:
>>> I'm frequently getting my machine locked with ahcichX timeouts:
>>> ahcich2: Timeout on slot 0
>>> ahcich2: is cs 0001 ss rs 0001 tfd c0 serr
>>> 000
On Wed, Mar 03, 2010 at 08:49:29AM +0100, Harald Schmalzbauer wrote:
> Alexander Motin schrieb am 23.02.2010 16:10 (localtime):
> >Harald Schmalzbauer wrote:
> >>I'm frequently getting my machine locked with ahcichX timeouts:
> >>ahcich2: Timeout on slot 0
> >>ahcich2: is cs 0001 ss 00
Alexander Motin schrieb am 23.02.2010 16:10 (localtime):
Harald Schmalzbauer wrote:
I'm frequently getting my machine locked with ahcichX timeouts:
ahcich2: Timeout on slot 0
ahcich2: is cs 0001 ss rs 0001 tfd c0 serr
ahcich2: Timeout on slot 8
ahcich2: is
on 23/02/2010 21:13 George Liaskos said the following:
> I booted my old kernel (was from Feb 13) and i had the same issue.
>
> The timeout occurs when i try to burn CDs with the k3b application,
> after some queries i found this thread:
> http://www.pubbs.net/kde/200910/40852/
>
> I have no prob
C. P. Ghost wrote:
> On Tue, Feb 23, 2010 at 12:15 PM, George Liaskos
> wrote:
>> I am having the same issue since Feb 20 which was my last update.
>>
>> ahcich1: Timeout on slot 3
>> ahcich1: is cs 0018 ss rs 0018 tfd d0 serr
>> ahcich1: Timeout on slot 5
>> ah
On Tue, Feb 23, 2010 at 12:15 PM, George Liaskos wrote:
> I am having the same issue since Feb 20 which was my last update.
>
> ahcich1: Timeout on slot 3
> ahcich1: is cs 0018 ss rs 0018 tfd d0 serr
> ahcich1: Timeout on slot 5
> ahcich1: is cs 0060
Harald Schmalzbauer wrote:
> Am 23.02.2010 19:14, schrieb Alexander Motin:
>>> I'll restore the default vfs.zfs.txg.timeout=30, so the hang can be
>>> easily reproduced and see if I can 'camcontrol stop' the drive. Do you
>>> think I can get usefull information with that test?
>> Stop won't work fo
I booted my old kernel (was from Feb 13) and i had the same issue.
The timeout occurs when i try to burn CDs with the k3b application,
after some queries i found this thread:
http://www.pubbs.net/kde/200910/40852/
I have no problem burning CDs with cdrecord so i guess this must be an
error at the
Am 23.02.2010 19:14, schrieb Alexander Motin:
...
>> I can remember that ZFS hadn't showed the removed drive as offline, but
>> there was no hang. The pool was degraded and after reinserting and
>> rebooting I could resilver the pool. I couldn't manage to get it
>> consistent without rebooting, but
Harald Schmalzbauer wrote:
> Alexander Motin schrieb am 23.02.2010 18:35 (localtime):
> ...
>>> One understanding question: If the drive doesn't complete a command,
>>> regardless if it's due to a firmware bug, a disk surface error or
>>> whatever, is there no way for the driver to terminate the re
Alexander Motin schrieb am 23.02.2010 18:35 (localtime):
...
One understanding question: If the drive doesn't complete a command,
regardless if it's due to a firmware bug, a disk surface error or
whatever, is there no way for the driver to terminate the request and
take the drive offline after so
Harald Schmalzbauer wrote:
> Alexander Motin schrieb am 23.02.2010 17:18 (localtime):
> ...
>>> I guess if it's a HDD firmware issue with NCQ the hang shouldn't happen
>>> when NCQ is disabled.
>>
>> Just for case of real I/O timeout, run full surface test with SMART.
>
> Unfortunately I couldn't
Alexander Motin schrieb am 23.02.2010 17:18 (localtime):
...
I guess if it's a HDD firmware issue with NCQ the hang shouldn't happen
when NCQ is disabled.
Just for case of real I/O timeout, run full surface test with SMART.
Unfortunately I couldn't find new firmware from Samsung, although one
Harald Schmalzbauer wrote:
> Maybe it's helpful to you. Since I haven't seen the hang after
> upgrading, although doing extensive network transfer tests, I thought it
> vanished and haven't kept logs safe...
Enabling verbose kernel messages may give a bit more info.
>>> Kernel is from Feb. 19, so
Alexander Motin schrieb am 23.02.2010 16:10 (localtime):
Harald Schmalzbauer wrote:
I'm frequently getting my machine locked with ahcichX timeouts:
ahcich2: Timeout on slot 0
ahcich2: is cs 0001 ss rs 0001 tfd c0 serr
ahcich2: Timeout on slot 8
ahcich2: is
George Liaskos wrote:
> I am having the same issue since Feb 20 which was my last update.
Which version was before?
> ahcich1: Timeout on slot 3
> ahcich1: is cs 0018 ss rs 0018 tfd d0 serr
> ahcich1: Timeout on slot 5
> ahcich1: is cs 0060 ss 0
Harald Schmalzbauer wrote:
> I'm frequently getting my machine locked with ahcichX timeouts:
> ahcich2: Timeout on slot 0
> ahcich2: is cs 0001 ss rs 0001 tfd c0 serr
>
> ahcich2: Timeout on slot 8
> ahcich2: is cs 0100 ss rs 0100 tfd c0
I am having the same issue since Feb 20 which was my last update.
ahcich1: Timeout on slot 3
ahcich1: is cs 0018 ss rs 0018 tfd d0 serr
ahcich1: Timeout on slot 5
ahcich1: is cs 0060 ss rs 0060 tfd d0 serr
ahcich1: Timeout on sl
Hello,
I'm frequently getting my machine locked with ahcichX timeouts:
ahcich2: Timeout on slot 0
ahcich2: is cs 0001 ss rs 0001 tfd c0 serr
ahcich2: Timeout on slot 8
ahcich2: is cs 0100 ss rs 0100 tfd c0 serr
ahcich2: Tim
28 matches
Mail list logo
