Find the answer to your Linux question:
Results 1 to 1 of 1
Ok, I have a amd x2 with asus a8v motherboard. I recently installed a new Western Digital Caviar SE16 sata drive. ( http://www.newegg.com/Product/Produc...2E16822144701) . I then installed fedora 64 and ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Apr 2006
    Posts
    15

    ata2: command 0xca timeout


    Ok, I have a amd x2 with asus a8v motherboard. I recently installed a new Western Digital Caviar SE16 sata drive. (http://www.newegg.com/Product/Produc...2E16822144701).

    I then installed fedora 64 and fedora 32 with a shared home partition. However my system locks up completly unusable (Magic Sysrq wont even work). And will display these errors when. I ctrl alt F1 :
    ata2: command 0xca timeout, stat 0x50 host_stat 0x4
    ata2: status=0x50 { DriveReady SeekComplete }

    It happens at least so far after: I stopped working, and come back 30 min plus later.
    Then I try to do something,(click on menu)
    then it locks up and but the mouse still moves.
    (Sometimes I ctrl at F1 to get those error messages.)
    Then the mouse dies
    And forced to do a hard reboot

    Today I left the system on for about 7 hours, and came back and, the screensaver exits, click on the fedora menu. Then it locks up as usual.
    looking in the log ( the complete attached). I find this

    Sep 11 10:06:12 localhost dhclient: bound to 10.0.0.2 -- renewal in 509 seconds.
    Sep 11 10:11:43 localhost kernel: ata2: command 0xca timeout, stat 0x50 host_stat 0x4
    Sep 11 10:11:43 localhost kernel: ata2: status=0x50 { DriveReady SeekComplete }
    Sep 11 10:11:43 localhost kernel: sda: Current: sense key: No Sense
    Sep 11 10:11:43 localhost kernel: Additional sense: No additional sense information
    Sep 11 10:11:43 localhost kernel: Info fld=0x46212e8
    Sep 11 10:12:43 localhost kernel: ata2: command 0xca timeout, stat 0x50 host_stat 0x4
    Sep 11 10:12:43 localhost kernel: ata2: status=0x50 { DriveReady SeekComplete }
    Sep 11 10:12:43 localhost kernel: sda: Current: sense key: No Sense
    Sep 11 10:12:43 localhost kernel: Additional sense: No additional sense information
    Sep 11 10:12:43 localhost kernel: Info fld=0x46212f8
    Sep 11 10:13:43 localhost kernel: ata2: command 0xca timeout, stat 0x50 host_stat 0x4
    Sep 11 10:13:43 localhost kernel: ata2: status=0x50 { DriveReady SeekComplete }
    Sep 11 10:13:43 localhost kernel: sda: Current: sense key: No Sense
    Sep 11 10:14:41 localhost dhclient: DHCPREQUEST on eth0 to 10.0.0.1 port 67
    Sep 11 10:16:43 localhost kernel: Additional sense: No additional sense information
    Sep 11 16:22:39 localhost syslogd 1.4.1: restart.

    Viewing the log it appears that the ata2 ocurred (or were logged 4 hours before I came and restarted the computer. Nevertheless, the same lockup procedure happened.

    The log is attached. of the same log I took the above from including the complete bootup.
    Attached Files Attached Files

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •