[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
** No longer affects: linux (Ubuntu) ** Package changed: linux (Fedora) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: High => Undecided ** Changed in: linux (Ubuntu) Status: Won't Fix => New ** Changed in: linux (Ubuntu) Remote watch: Red Hat Bugzilla #474552 => None ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
** Changed in: linux (Fedora) Status: Unknown => Won't Fix ** Changed in: linux (Fedora) Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
Sasa Paporovic, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/comments/11 regarding this being due to hardware failure. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find. ** Changed in: linux (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
Hi, I thought I contribute some additional info to this problem. We have about ~50 nearly identical all-in-one PCs out there that are experiencing relatively often the exact problem described here. The industrial-grade hardware is based on Intel Atom N270 (1.6 GHz) - see full specs here: http://www.cartft.com/catalog/il/1325 We use different kinds of non-mechanical hard disks: - either a Kingston 8GB SSD SATA drive (most are using these, then we tried using other drives to avoid the problem we're talking about here) - or a SATA-to-CompactFlash adapter with a 4GB SanDisk Extreme CompactFlash card (we use those cards - without adapter - in other configurations and never had any problems with them) - or a Transcend TS8GHSD310 8GB SSD SATA drive They are all running the same Linux image based on Debian 6, Kernel 2.6.38.6 and run 24/7. The system has been specifically modified to avoid any unnecessary Flash writes. All partitions are r/w and occasional writes are possible, but overall there are certainly far less than 1 MByte writes per day. Basically we're only using half of the 8 GB drive space so these drives have a lot of room for wear leveling. In the past months we had a number of failures that were mostly related to the frozen SATA link described in this bug. The drives would not even recover with a software reboot - the PCs need to be powered down and up again. We're using high quality cables and also tried to use different cables. Note that these machines are firmly mounted, have no moving parts whatsoever and are located in lonely places - i.e. there is no mechanical reason why the SATA cable should suddenly have problems. We only started recently to log in detail which hardware failed but I can defenitely say that it happens relatively often with the Kingston drives and it happened at least once with the CF adapter. I have no bad records for the Transcend drives so far but only five machines are using them so far. I wouldn't be surprised if even those fail. My personal opinion is that there is some sort of incompatibility between the Linux drivers and the SATA controller or SATA drives that reveals itself only in certain rare situations. But other that that I'm clueless. These machines most of the time do nothing but wait, so CPU time and disk accesses are very low. BTW, the same Linux image is used in a number of other machines without SATA drives (they have CF card slots) and never had any comparable problems. Also I was never able to reproduce the problem in our office, which makes testing very hard. I hope this helps to narrow down the problem. Let me know if I can be of any further help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
Sorry, For this line: This comment is directed at David Barker and post #13 I meant to write: This comment is directed at David Barker and post #12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
This comment is directed at David Barker and post #13. Why? Because the timing and versions that work / not work fit my issue. David: I wonder if you might post your logs. And does the issue still occur for you? In my case, I have isolated the issue to revision numbers 2760 and 2761 of udev (launchpad reference), which was late in the 12.04 pre-release cycle. I have been searching for someone else with the same issue. References: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/986654 http://www.smythies.com/~doug/network/hd_race/index.html http://ubuntuforums.org/showthread.php?t=1958838 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
I have had this same or very similar issue on my fresh new Kubuntu 12.04
install with Gigabyte ga-990fxa-ud3 v1.1 motherboard with the following
disks
[2.069621] ata4.00: ATA-8: ST31500341AS, SD1B, max UDMA/133
[2.078992] ata2.00: ATA-8: WDC WD5000AAKS-00YGA0, 12.01C02, max UDMA/133
[2.084532] ata5.00: ATA-9: SAMSUNG SSD 830 Series, CXM03B1Q, max UDMA/133
[2.128540] ata1.00: ATA-7: ST3500830AS, 3.AFE, max UDMA/133
[2.410522] ata3.00: ATA-8: WDC WD20EADS-00S2B0, 01.00A01, max UDMA/133
Here is example of errors I was receiving
Nov 17 21:17:03 desktop kernel: [287733.791309] ata3.00: exception Emask 0x0
SAct 0xff SErr 0x0 action 0x0
Nov 17 21:17:03 desktop kernel: [287733.791320] ata3.00: irq_stat 0x4008
Nov 17 21:17:03 desktop kernel: [287733.791329] ata3.00: failed command: READ
FPDMA QUEUED
Nov 17 21:17:03 desktop kernel: [287733.791345] ata3.00: cmd
60/08:38:3f:11:00/00:00:9f:00:00/40 tag 7 ncq 4096 in
Nov 17 21:17:03 desktop kernel: [287733.791349] res
41/40:00:3f:11:00/00:00:9f:00:00/40 Emask 0x409 (media error) F
Nov 17 21:17:03 desktop kernel: [287733.791357] ata3.00: status: { DRDY ERR }
Nov 17 21:17:03 desktop kernel: [287733.791362] ata3.00: error: { UNC }
Nov 17 21:17:03 desktop kernel: [287733.797639] ata3.00: configured for UDMA/133
Nov 17 21:17:03 desktop kernel: [287733.797670] ata3: EH complete
Nov 17 21:17:05 desktop kernel: [287736.447090] ata3.00: exception Emask 0x0
SAct 0xff SErr 0x0 action 0x0
Nov 17 21:17:05 desktop kernel: [287736.447100] ata3.00: irq_stat 0x4008
Nov 17 21:17:05 desktop kernel: [287736.447109] ata3.00: failed command: READ
FPDMA QUEUED
Nov 17 21:17:05 desktop kernel: [287736.447124] ata3.00: cmd
60/08:00:3f:11:00/00:00:9f:00:00/40 tag 0 ncq 4096 in
Nov 17 21:17:05 desktop kernel: [287736.447127] res
41/40:00:3f:11:00/00:00:9f:00:00/40 Emask 0x409 (media error) F
Nov 17 21:17:05 desktop kernel: [287736.447136] ata3.00: status: { DRDY ERR }
Nov 17 21:17:05 desktop kernel: [287736.447141] ata3.00: error: { UNC }
Nov 17 21:17:05 desktop kernel: [287736.453208] ata3.00: configured for UDMA/133
Nov 17 21:17:05 desktop kernel: [287736.453237] sd 2:0:0:0: [sdc] Unhandled
sense code
Nov 17 21:17:05 desktop kernel: [287736.453243] sd 2:0:0:0: [sdc] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Nov 17 21:17:05 desktop kernel: [287736.453251] sd 2:0:0:0: [sdc] Sense Key :
Medium Error [current] [descriptor]
Nov 17 21:17:05 desktop kernel: [287736.453261] Descriptor sense data with
sense descriptors (in hex):
Nov 17 21:17:05 desktop kernel: [287736.453266] 72 03 11 04 00 00 00 0c
00 0a 80 00 00 00 00 00
Nov 17 21:17:05 desktop kernel: [287736.453286] 9f 00 11 3f
Nov 17 21:17:05 desktop kernel: [287736.453295] sd 2:0:0:0: [sdc] Add. Sense:
Unrecovered read error - auto reallocate failed
Nov 17 21:17:05 desktop kernel: [287736.453306] sd 2:0:0:0: [sdc] CDB:
Read(10): 28 00 9f 00 11 3f 00 00 08 00
Nov 17 21:17:05 desktop kernel: [287736.453325] end_request: I/O error, dev
sdc, sector 2667581759
Nov 17 21:17:05 desktop kernel: [287736.453369] ata3: EH complete
Nov 17 21:17:05 desktop kernel: [287736.453946] EXT4-fs error (device dm-3):
__ext4_get_inode_loc:3676: inode #83361793: block 333447200: comm rsync: unable
to read itable block
Nov 17 21:17:05 desktop kernel: [287736.453959] Aborting journal on device
dm-3-8.
Nov 17 21:17:05 desktop kernel: [287736.454440] EXT4-fs (dm-3): Remounting
filesystem read-only
Nov 17 21:17:08 desktop kernel: [287739.035935] ata3.00: exception Emask 0x0
SAct 0xff SErr 0x0 action 0x0
Nov 17 21:17:08 desktop kernel: [287739.035945] ata3.00: irq_stat 0x4008
Nov 17 21:17:08 desktop kernel: [287739.035954] ata3.00: failed command: READ
FPDMA QUEUED
Nov 17 21:17:08 desktop kernel: [287739.035969] ata3.00: cmd
60/08:00:47:11:00/00:00:9f:00:00/40 tag 0 ncq 4096 in
Nov 17 21:17:08 desktop kernel: [287739.035973] res
41/40:00:47:11:00/00:00:9f:00:00/40 Emask 0x409 (media error) F
Nov 17 21:17:08 desktop kernel: [287739.035981] ata3.00: status: { DRDY ERR }
Nov 17 21:17:08 desktop kernel: [287739.035986] ata3.00: error: { UNC }
Nov 17 21:17:08 desktop kernel: [287739.042031] ata3.00: configured for UDMA/133
Nov 17 21:17:08 desktop kernel: [287739.042063] sd 2:0:0:0: [sdc] Unhandled
sense code
Nov 17 21:17:08 desktop kernel: [287739.042069] sd 2:0:0:0: [sdc] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Nov 17 21:17:08 desktop kernel: [287739.042078] sd 2:0:0:0: [sdc] Sense Key :
Medium Error [current] [descriptor]
Nov 17 21:17:08 desktop kernel: [287739.042088] Descriptor sense data with
sense descriptors (in hex):
Nov 17 21:17:08 desktop kernel: [287739.042093] 72 03 11 04 00 00 00 0c
00 0a 80 00 00 00 00 00
Nov 17 21:17:08 desktop kernel: [287739.042113] 9f 00 11 47
Nov 17 21:17:08 desktop kernel: [287739.042122] sd 2:0:0:0: [sdc] Add. Sense:
Unrecovered read error - auto reallocate failed
Nov 17 21:17:08 desktop kernel:
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
** Tags added: quantal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
Hi,
I came via
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285892?comments=all
which said, it would be a duplicate of this bug. I experience the bug
after having changed from a legacy hdd to a ssd (ocz agility 3), running
Ubuntu 11.10, all cables are fine, but everytime there are excessive
write or read actions on this drive I experience a system freeze with
the following appearing in the syslog. This is perfectly reproducable by
just copying a big file.
kernel: [ 1958.016076] ata3: lost interrupt (Status 0x50)
kernel: [ 1958.016102] ata3.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action
0x6 frozen
kernel: [ 1958.016111] ata3.01: failed command: READ DMA
kernel: [ 1958.016131] ata3.01: cmd c8/00:18:40:0b:50/00:00:00:00:00/fb tag 0
dma 12288 in
kernel: [ 1958.016144] res 40/00:00:00:4f:c2/00:00:00:00:00/10 Emask 0x4
(timeout)
kernel: [ 1958.016151] ata3.01: status: { DRDY }
kernel: [ 1958.016168] ata3: soft resetting link
kernel: [ 1958.220628] ata3.01: configured for UDMA/33
kernel: [ 1958.220636] ata3.01: device reported invalid CHS sector 0
kernel: [ 1958.220647] ata3: EH complete
kernel: [ 1989.088064] ata3: lost interrupt (Status 0x50)
kernel: [ 1989.088090] ata3.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action
0x6 frozen
kernel: [ 1989.088099] ata3.01: failed command: WRITE DMA EXT
kernel: [ 1989.088122] ata3.01: cmd 35/00:20:b0:b2:20/00:01:07:00:00/f0 tag 0
dma 147456 out
kernel: [ 1989.088124] res 40/00:00:00:4f:c2/00:00:00:00:00/10 Emask 0x4
(timeout)
kernel: [ 1989.088129] ata3.01: status: { DRDY }
kernel: [ 1989.088142] ata3: soft resetting link
kernel: [ 1989.292604] ata3.01: configured for UDMA/33
kernel: [ 1989.292609] ata3.01: device reported invalid CHS sector 0
kernel: [ 1989.292615] ata3: EH complete
The support from ocz told me, that I might have a chance resolving this by
either applying a firmware update or the SATA3 to SATA2 fix. The latter
seemed very interesting to me, could it be the main reason for the whole issue?
I haven't tried yet since the ssd sits in an all in one pc that can't boot from
usb, has a broken dvd drive, and is not really built for being repaired often,
so I'd like to make sure it really solves the issue. And since I'm reading a
lot about people having no problems with another OS I keep on waiting for a bit
more ;)
Anyone got a opinion about this sata3 to sata2 fix or whether it's OS or
hardware connected?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/965213
Title:
ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
I am seeing similar symptoms. With a Sony Y Series laptop (containing an AMD/ATI SBx00 SATA interface), whenever AC power is removed I see similar messages in dmesg. There are no issues at all under AC power, only when operating on battery. The issue is present whether booting under battery power or booting under AC and then switching to battery. I suspect it may be a pm-utils or kernel regression (based on similar bugs reported circa 2010). The issue was not present with Ubuntu or XUbuntu 11.10 however is present in both Ubuntu and XUbuntu 12.04. I have tried using 12.04 beta 2 and daily (as of 16/04/2012). I have also tried using the most recent mainline kernel and still experienced the issue. I will attach detailed logs once I have access to the machine again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
I have found what it is. In respect to: http://lime- technology.com/wiki/index.php?title=The_Analysis_of_Drive_Issues with the text passage(citing): Drive Interface Issues These are problems with the cables and connections to the drive, both power and data, or the quality of the power supplied. If your errors match one of these, then almost certainly, your drive is completely fine. There have been many drives returned or thrown out, after numerous errors similar to the following issues, that were entirely the fault of the cables or power or connectors used, NOT the drive itself. - You may read on on the linked website for which kernel entries are indicating this. I went in the next computer store and came back with a new SATA data and a new SATA energy cable(arround 20€ - propably cheaper when you have time to look for). I changed both against my old ones. I have had runned the system since many days to be sure under haesy hardrive load(virtulisation with qemu-kvm with many guests in parallel). - No ata1 errors anymore with the same harddrive! A deeper look at the cables shows me that the plastic connector of the SATA energy supply to the harddrive was deformed a bit. It was nearly invisible but seems to be enough to interrupt the harddrive and causes this errors. I would like to bring this issue up as a blueprint for Ubuntu/apport, because it was a time stealing one which is not easy to identify. The system should inform the user/superuser when there are entries of this type in the kernel log that this affected with the possibility of defect cable or cable connectors to the harddrive. I let this open for now, so that user affected by this can find it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
** Attachment added: hwinfo output https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+attachment/2975836/+files/hwinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
Additional: I have made several installations following each other on the same sytem with Ubuntu11.10. With linux-generic 3.0.0.16.x Ubuntu serie is this problem not observable to me. With linux-generic 3.0.0.17.x Ubuntu serie it occures regular! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
Regular short after appearing in the kern.log my system is crashing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
** Attachment added: host 11.10 syslog additional https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+attachment/2940351/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
** Changed in: linux (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
Can not gather the Ubuntu12.04 guest logs. The I/O errors have prevent the logging/writing to the virtual harddrive. ** Bug watch added: Red Hat Bugzilla #474552 https://bugzilla.redhat.com/show_bug.cgi?id=474552 ** Also affects: linux (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=474552 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Once testing of the upstream kernel is complete, please mark this bug as Confirmed. Thanks in advance. [1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/ ** Changed in: linux (Ubuntu) Importance: Undecided = Medium ** Tags added: needs-upstream-testing ** Changed in: linux (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
** Tags removed: needs-upstream-testing ** Tags added: kernel-unable-to-test-upstream ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
@melchiaros regarding bug #958188, I'm not sure if mine is a duplicate or not. Mine is specifically related to being an SSD, because I also have a HDD installed which doesn't fail. Let me know if there's anything I can do to help diagnose mine to see if it is at all related to this (#965213). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 965213] Re: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen
I have set this to kernel-unable-to test-upstream. If somene of the subscribers is able and willing to test, feel free. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/965213 Title: ata1.00: exception Emask 0x50 SAct 0x1 SErr 0x480800 action 0x6 frozen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/965213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
