Hello Guest, if you are reading this it means you have not registered yet. Please take a second, Click here to register, and in a few simple steps you will be able to enjoy our community and use our OpenViX support section.
Results 1 to 8 of 8

Thread: Kernel throwing some ata errors

  1. #1

    Title
    Member
    Join Date
    Jan 2015
    Posts
    72
    Thanks
    19
    Thanked 8 Times in 7 Posts

    Kernel throwing some ata errors

    Greetings,

    I have a Mut@nt 2400 and I am seeing some weird stuff on the kernel logs:

    <snip>

    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    ata1: irq_stat 0x00000040, connection status changed
    ata1: SError: { CommWake DevExch }
    ata1: limiting SATA link speed to 1.5 Gbps
    ata1: hard resetting link
    ata1: SATA link down (SStatus 0 SControl 310)
    ata1: EH complete
    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    ata1: irq_stat 0x00000040, connection status changed
    ata1: SError: { CommWake DevExch }
    ata1: limiting SATA link speed to 1.5 Gbps
    ata1: hard resetting link
    ata1: SATA link down (SStatus 0 SControl 310)
    ata1: EH complete
    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    ata1: irq_stat 0x00000040, connection status changed
    ata1: SError: { CommWake DevExch }
    ata1: limiting SATA link speed to 1.5 Gbps
    ata1: hard resetting link
    ata1: SATA link down (SStatus 0 SControl 310)
    ata1: EH complete
    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    ata1: irq_stat 0x00000040, connection status changed
    ata1: SError: { CommWake DevExch }
    ata1: limiting SATA link speed to 1.5 Gbps
    ata1: hard resetting link
    ata1: SATA link down (SStatus 0 SControl 310)
    ata1: EH complete
    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    ata1: irq_stat 0x00000040, connection status changed
    ata1: SError: { CommWake DevExch }
    ata1: limiting SATA link speed to 1.5 Gbps
    ata1: hard resetting link
    ata1: SATA link down (SStatus 0 SControl 310)
    ata1: EH complete
    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    ata1: irq_stat 0x00000040, connection status changed
    ata1: SError: { CommWake DevExch }
    ata1: limiting SATA link speed to 1.5 Gbps
    ata1: hard resetting link
    ata1: SATA link down (SStatus 0 SControl 310)
    ata1: EH complete
    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    ata1: irq_stat 0x00000040, connection status changed
    ata1: SError: { CommWake DevExch }
    ata1: limiting SATA link speed to 1.5 Gbps
    ata1: hard resetting link
    ata1: SATA link down (SStatus 0 SControl 310)
    ata1: EH complete
    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    ata1: irq_stat 0x00000040, connection status changed
    ata1: SError: { CommWake DevExch }
    ata1: limiting SATA link speed to 1.5 Gbps
    ata1: hard resetting link
    ata1: SATA link down (SStatus 0 SControl 310)
    ata1: EH complete
    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    ata1: irq_stat 0x00000040, connection status changed
    ata1: SError: { CommWake DevExch }
    ata1: limiting SATA link speed to 1.5 Gbps
    ata1: hard resetting link
    ata1: SATA link down (SStatus 0 SControl 310)
    ata1: EH complete
    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4040000 action 0xe frozen
    ata1: irq_stat 0x00000040, connection status changed
    ata1: SError: { CommWake DevExch }
    ata1: limiting SATA link speed to 1.5 Gbps
    ata1: hard resetting link
    ata1: SATA link down (SStatus 0 SControl 310)
    ata1: EH complete

    </snip>

    I have swapped the hard disk for a new one and it's still giving me the same errors.
    Is it a kernel bug OR the SATA controller having issues? This box is not even a week old.


    Thanks.
    Last edited by xhemp; 03-01-16 at 19:06.

  2. #2

    Title
    Member
    Join Date
    Jan 2015
    Posts
    72
    Thanks
    19
    Thanked 8 Times in 7 Posts
    Hmm, after emailing WOS, they asked me to try on OpenPli and there I didn't see anything like that on the kernel logs.
    A bit puzzled seeing the kernel is the same.
    Does anyone have any idea?

  3. The Following User Says Thank You to xhemp For This Useful Post:

    Flyingpig (06-01-16)

  4. #3
    twol's Avatar
    Title
    Moderator
    Join Date
    Apr 2012
    Posts
    8,427
    Thanks
    997
    Thanked 2,899 Times in 2,252 Posts
    Openpli is not part of the oe-a so in general is different.
    Gigablue Quad 4K & UE 4K
    .........FBC Tuners:
    ------------------> GT-Sat unicable LNB to 1.5M dish(28.2E)
    ------------------> Gigablue unicable LNB to 80 cm dish(19.2E)
    .......................> FBC & DVB-S2X into 90cm dish (27.5W) Opticum robust Unicable LNB
    AX HD61, Edision Osmio 4K+, Zgemma H9Combo, Octagon SF8008 , gbtrio4k, h9se using unicable ports
    Zgemma H9 C/S into Giga4K

  5. #4

    Title
    Member
    Join Date
    Jan 2015
    Posts
    72
    Thanks
    19
    Thanked 8 Times in 7 Posts
    Just tested with latest OpenATV, no errors there as well, looks to be something specific with Vix.

  6. #5
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,277 Times in 1,089 Posts
    I see something similar (ET10K), it looks like the drive connection speed is being established.

    Lots on google - eg try checking/resetting drive cable.

    Code:
    ata1: link is slow to respond, please be patient (ready=0)
    ata1: COMRESET failed (errno=-16)
    ata1: link is slow to respond, please be patient (ready=0)
    ata1: COMRESET failed (errno=-16)
    ata1: link is slow to respond, please be patient (ready=0)
    ata1: COMRESET failed (errno=-16)
    ata1: limiting SATA link speed to 3.0 Gbps
    ata1: SATA link down (SStatus 0 SControl 320)
    ata1.00: link online but device misclassified
    ata1: link online but 1 devices misclassified, device detection might fail
    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen t4
    ata1: irq_stat 0x00400040, connection status changed
    ata1: SError: { PHYRdyChg CommWake DevExch }
    ata1: hard resetting link
    ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    ata1.00: ATA-8: HGST HTS541010A9E680, JA0OA560, max UDMA/133
    ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata1.00: configured for UDMA/133
    ata1: EH complete

  7. #6

    Title
    Member
    Join Date
    Jan 2015
    Posts
    72
    Thanks
    19
    Thanked 8 Times in 7 Posts
    Quote Originally Posted by ccs View Post
    I see something similar (ET10K), it looks like the drive connection speed is being established.

    Lots on google - eg try checking/resetting drive cable.

    Code:
    ata1: link is slow to respond, please be patient (ready=0)
    ata1: COMRESET failed (errno=-16)
    ata1: link is slow to respond, please be patient (ready=0)
    ata1: COMRESET failed (errno=-16)
    ata1: link is slow to respond, please be patient (ready=0)
    ata1: COMRESET failed (errno=-16)
    ata1: limiting SATA link speed to 3.0 Gbps
    ata1: SATA link down (SStatus 0 SControl 320)
    ata1.00: link online but device misclassified
    ata1: link online but 1 devices misclassified, device detection might fail
    ata1: exception Emask 0x10 SAct 0x0 SErr 0x4050000 action 0xe frozen t4
    ata1: irq_stat 0x00400040, connection status changed
    ata1: SError: { PHYRdyChg CommWake DevExch }
    ata1: hard resetting link
    ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    ata1.00: ATA-8: HGST HTS541010A9E680, JA0OA560, max UDMA/133
    ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata1.00: configured for UDMA/133
    ata1: EH complete
    Hi ccs,

    Looks like you have an Hitachi hard drive, right? Same here.
    Have you tried OpenATV to check if you get the same messages?

  8. #7
    ccs's Avatar
    Title
    ViX Beta Tester
    Join Date
    Sep 2014
    Posts
    5,836
    Thanks
    554
    Thanked 1,277 Times in 1,089 Posts
    Quote Originally Posted by xhemp View Post
    Hi ccs,

    Looks like you have an Hitachi hard drive, right? Same here.
    Have you tried OpenATV to check if you get the same messages?
    I've just restarted the box (still on VIX) and now all I see is...

    Code:
    ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    ata1.00: ATA-8: HGST HTS541010A9E680, JA0OA560, max UDMA/133
    ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata1.00: configured for UDMA/133
    so maybe a cold start needs a few attempts, but when warmed up it gets there 1st time.

    Drive is an Hitachi.

  9. #8

    Title
    Member
    Join Date
    Jan 2015
    Posts
    72
    Thanks
    19
    Thanked 8 Times in 7 Posts
    Quote Originally Posted by ccs View Post
    I've just restarted the box (still on VIX) and now all I see is...

    Code:
    ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    ata1.00: ATA-8: HGST HTS541010A9E680, JA0OA560, max UDMA/133
    ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
    ata1.00: configured for UDMA/133
    so maybe a cold start needs a few attempts, but when warmed up it gets there 1st time.

    Drive is an Hitachi.
    Cool,thanks.
    Funny enough, I also have an Hitachi on another Mutant and I saw some of these errors but not as frequent as the one here at my brother's.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
This website uses cookies
We use cookies to store session information to facilitate remembering your login information, to allow you to save website preferences, to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners.