At 20:20 Uhr +0200 28.04.1998, Allen Briggs wrote:
>> I've had a different problem with one drive that started about the same
>> time that "(quick)" started showing up in dmesg. Any access to the drive
>> (dd, disklabel) drops into the debugger, lately only after printing all
>> the requested output to the console.
>
>Really?  This is the first I've heard about any such thing.

Hi Allen,

good you're back.  :)

Have you looked at PR#5174? I saw the same symptoms as listed above with an
IBM DCAS 4G drive. What "fixed" the problem for me was limiting the number
of partitions to 7 [abcdefg]. Adding an eighth partition no matter what
type would inevitably crash >=1.3 machines. Any idea?

PR#5214 lists my experience with

>dmaintr: discarded 32 b (last transfer was 2544 b).
>esp0: !TC [intr 10, stat 83, step 4] prevphase 0, resid 9f0
>sd0(esp0:0:0): esp0: timed out [ecb 0x6baa8d0 (flags 0x3, dleft 9f0, stat
>0)], <state 4, nexus 0x6baa8d0, phase(c 3, p 3), resid 0, msg(q 0,o 0) >
>sd0(esp0:0:0): esp0: timed out [ecb 0x6baa8d0 (flags 0x43, dleft 9f0, stat
>0)], <state 4, nexus 0x6baa8d0, phase(c 3, p 3), resid 0, msg(q 20,o 0) >
>AGAIN

like problems. Normal operation is fine, but large data transfers ( >50MB)
show similar messages.

	hauke




--
"It's never straight up and down"     (DEVO)