Re: libata fails to recover from HSM violation involving DRQ status

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Mark Lord wrote:
> Tejun Heo wrote:
>>
>> Hmmm... that's very weird.  I've never seen such problems.  The report
>> messages are printed in ata_eh_report() and both the cmd and res lines
>> are printed by single invocation to printk().  Is the log captured using
>> serial console?  I think it could be transmission error or buffer
>> overflow on serial link.
> 
> Naw, just "dmesg > file", so it should be a pretty reliable capture.
> Just odd.  Something weird.

The format string is pretty long with a lot of parameters.  Maybe we're
hitting some obscure bug in printk and friends?

-- 
tejun

-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux