Comment 51 for bug 217920

Hi!

I am experiencing the same ATA errors (Emask..), and have tried numerous things without finding a solution yet.
The following is the case:

- the fact that Emask errors are occurring is not obvious, initially the problem just shows as HALD hanging when starting. But when disabling that process it just 'hangs' somewhere else. Only when going to single user mode and changing HALD to start without detaching and full logging to the console, it shows the errors (I cannot log in to the system when HALD 'hangs')
- the problem manifests itself both on SATA harddisks as well as PATA harddisks (tried a SATA 500g, SATA 160g, PATA 80g), so I'm doubting my harddisks or harddisk cables are failing.
- the problem manifests itself only on Ubuntu Hardy, Ubuntu Intrepid and Debian Lenny. Debian Etch and Ubuntu Gutsy work just fine. The weird thing is that Ubuntu Hardy did work before (as I've used it for mythtv for over a year)... When I'm now installing it it doesn't work anymore.. To me it seems that a new kernel feature is the culprit or triggers some very common hardware problem that occurs for many people.
- I've tried disabling several devices and busses in the BIOS, but no luck (USB, Serial, Parallel, Audio, PATA, SATA, FDC, HPET; of course not all together, else I couldn't boot ubuntu)
- I've tried the recommendation above with all_generic_ide and hpet=disable on the kernel line, with and without HPET disabled in the BIOS. No luck.
- I've tried ripping all unnecessary hardware (USB cardreader, PCI wificard, USB DVD-ROM), no luck
- tried other RAM, no luck

My hardware configuration:
- Shuttle SD32G2 Barebone (http://www.shuttle.eu/en/desktopdefault.aspx/tabid-72/170_read-13568/)
 * Shuttle FD32 Motherboard
 * Intel 945G (Lakeport-G) + ICH7 Chipset
 * Award V6.0PG BIOS, 4MBit flash memory BIOS
 * Bios Version SD32S30E
- Intel Core 2 Duo E6420 CPU

since changing RAM and HDDs didn't solve anything I'm guessing they are not important to specify here..

Just now I upgraded my BIOS to version SD32S30G, and was able to boot my system without problems for 10+ times, so it seems it is solved anyway. (I have been debugging this problem about two months back also, but back then there wasn't a new BIOS version yet; so if you're using a shuttle also and running into the same problems, check whether there's a new BIOS version available)

Bye!