Host Bus Error
Contents |
Technology - unRAID Server Community » Legacy Support (unRAID 5 and Older) » General Support (V5 and Older) » [SOLVED] Errors in syslog - host bus errors with Gigabyte GA-X58A-UD3R_rev2 « previous next » Send this topic Print options libata noacpi=1 Pages: [1] 2 Go Down Author Topic: [SOLVED] Errors in syslog - host bus errors status: { drdy err } with Gigabyte GA-X58A-UD3R_rev2 (Read 2988 times) Switchblade Hero Member Posts: 747 [SOLVED] Errors in syslog - host bus errors with Gigabyte GA-X58A-UD3R_rev2 « ata bus error on: June 27, 2014, 05:55:23 PM » My rig was running great with no errors for months. A couple of weeks ago I started seeing errors on my console, cache drive errors. you can read all about that exception emask 0x0 sact 0x0 serr 0x0 action 0x6 frozen thread here,http://lime-technology.com/forum/index.php?topic=33856.new;topicseen#new I never did get anyone to confirm if the cache drive was the issue, but no more CRC errors and the system seems very happy - well except... So I replaced my cache drive, ran preclear, and now have a working cache drive again. I have confirmed I have no SMART errors on any of my drives and unraid shows no errors on the webgui. No errors on the console either. Ran a parity
Ata1.00 Status Drdy Err
check, zero errors. However, there are some errors in the syslog that concern me.I built this new server several months ago and have had no issues (other than the cache drive mentioned above) and I have not changed the BIOS settings, drives or anything else. I went back and confirmed that the errors did not exist with my old mb setup, good to have backups of my flash drive with syslogs. . This makes me think if I perhaps have a BIOS settings incorrect re the hard drive controllers. This mb has 3 of them. If it is a cable, it would be good to know which drive/cable is having the issue. In the syslog, it refers to ata15 and ata16. I need drive number or drive ID. Perhaps there is a simple way to convert / tell.Before I go changing anything in the BIOS, I'd appreciate some advice on what these errors mean and if they warrant immediate action. I kindly request a review of my syslog.syslog errors that I found:host bus errorioapic: probe of 0000:00:13.0 failed with error -22Jun 27 02:42:40 Tower kernel: ata16: illegal qc_active transition (00000001->ffffffff)Jun 27 02:42:40 Tower kernel: ata16.00: exception Emask 0x2 SAct 0x0 SErr 0x0 action 0x6 frozenJun 27 02:42:40 Tower kernel: ata16.00: failed command: READ DMA EXTJun 27 02:42:40 Tower kernel: ata16.00: cmd 25/00:48:b0:3f:62/00:01:60:00:00/e0 tag 0 dma 167936 inJun 27 02:4
Overview All libata error messages produced by the kernel use a standard format: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen ata3.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 res 40/00:00:01:4f:c2/00:00:00:00:00/00
Ata1.00: Failed Command: Read Fpdma Queued
Emask 0x4 (timeout) ata3.00: status: { DRDY } Prefix The prefix ata3.00: decodes as ata1.00 device reported invalid chs sector 0 ata prefix, indicating this is a libata port or device message 3 port number, counting from one (1) 00 device number, usually ata1: eh complete zero unless Port Multiplier or PATA master/slave is involved Exception line The exception line gives an overview of the EH (Error Handler) state. exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen Emask Error http://lime-technology.com/forum/index.php?topic=33937.0 classification bitmask (AC_ERR_xxx in source code) SAct SATA SActive register SErr SATA SError register action ATA_EH_xxx actions, like revalidate, softreset, hardreset (see include/linux/libata.h) frozen if present, indicates the port was frozen for EH t
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company http://stackoverflow.com/questions/212466/what-is-a-bus-error Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up What is a bus error? up vote 156 down vote favorite 49 What does the "bus error" message mean, and how does it bus error differ from a segfault? c unix segmentation-fault bus-error share|improve this question edited Oct 18 '15 at 10:44 Cool Guy 15.7k51952 asked Oct 17 '08 at 14:48 raldi 7,257216178 add a comment| 15 Answers 15 active oldest votes up vote 151 down vote accepted Bus errors are rare nowadays on x86 and occur when your processor cannot even attempt the memory access requested, typically: using a processor instruction with an address that does not satisfy host bus error its alignment requirements. Segmentation faults occur when accessing memory which does not belong to your process, they are very common and are typically the result of: using a pointer to something that was deallocated. using an uninitialized hence bogus pointer. using a null pointer. overflowing a buffer. PS: To be more precise this is not manipulating the pointer itself that will cause issues, it's accessing the memory it points to (dereferencing). share|improve this answer edited Oct 17 '08 at 15:18 answered Oct 17 '08 at 15:12 bltxd 5,72322336 52 They aren't rare; I'm just at Exercise 9 from How to Learn C the Hard Way and already encountered one... –11684 Mar 26 '13 at 20:12 5 Another cause of bus errors (on Linux anyway) is when the operating system can't back a virtual page with physical memory (e.g. low-memory conditions or out of huge pages when using huge page memory.) Typically mmap (and malloc) just reserve the virtual address space, and the kernel assigns the physical memory on demand (so called soft page faults.) Make a large enough malloc, and then write to enough of it and you'll get a bus error. –Eloff Jul 14 '15 at 0:09 add a comment| up vote 58 down vote A segfault is accessing memory that you're not allowed to access. It's read-only,