Bug #1423
ata_id_common: BUSY status 0xfe error 0x0
Start date:
2011-08-28
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
ata_id_common
Description
frequently upon reboot I noticed this error since installing oi_151, although I noticed it on nexenta 3.1 as well:
Aug 28 17:30:56 amilo genunix: [ID 386595 kern.notice] ata_id_common: BUSY status 0xfe error 0x0
mostly twice.
I found the following g$$gle https://defect.opensolaris.org/bz/show_bug.cgi?format=multiple;id=2368
I tried changing ata.conf to the following:
# # don't change these # device_type="ide"; flow_control="dmult"; queue="qfifo"; max_transfer=0x100; # Enable dma ata-options=0x1; # # for PIO performance upgrade - set block factor to 0x10 # #drive0_block_factor=0x1; #drive1_block_factor=0x1; drive0_block_factor=0x10; drive1_block_factor=0x10; # # some laptop systems require setting this flag # #timing_flags=0x0; timing_flags=0x1;
so far seems ok, perhaps the defaults (like in many other areas) are not very good.
Updated by Richard PALO over 9 years ago
Well it appears "seems" was short lived, as this morning I get the message.. only once this time.
Apparently the timing_flags "workaround" is rather a misnomer.
Updated by Chris Jordan over 9 years ago
- Category set to OS/Net (Kernel and Userland)
- Assignee set to OI illumos
- Priority changed from Normal to Low
- Tags changed from needs-triage to ata_id_common
Updated by Ken Mays over 6 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
This was reviewed and fixed in one of the Illumos commits awhile ago.
Use: http://dlc.openindiana.org/isos/hipster/OI-hipster-text-20140701.iso for any reverification testing.