** No longer affects: linux (Ubuntu)
** Package changed: udev (Fedora) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Importance: Medium => Undecided
** Changed in: linux (Ubuntu)
Status: Won't Fix => New
** Changed in: linux (Ubuntu)
Remote watch: Red Hat Bugzilla #684599 => None
Launchpad has imported 23 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=684599.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Marcel, this bug report is being closed due to your last comment
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285892/comments/32
regarding this being fixed with a BIOS configuration change. For future
reference you can manage the status of your own bugs by clicking on the
current status in
*** This bug is a duplicate of bug 965213 ***
https://bugs.launchpad.net/bugs/965213
** This bug has been marked a duplicate of bug 965213
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,
Same error here:
Linux Bellerophon-117 3.0.0-15-generic #24-Ubuntu SMP Mon Dec 12
15:23:55 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Model Family: Seagate Barracuda 7200.11
Device Model: ST31500341AS
Serial Number:9VS0931W
LU WWN Device Id: 5 000c50 01051e2ab
Firmware Version: SD17
This bug might be the same as bug #640525 that I encounter on a Dell
Inspiron 9300 with a Samsung HM160HC HD.
It's still present in Oneiric with all kernels up to and including
3.0.0-14-generic.
Symptom : System very often boots either while starting a KDE or Gnome
session (right after bootup),
Sorry, I wrote System very often boots when I meant System very often
HANGS, this correction may make my comment above more understandable
;-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/285892
I have the same problem on a Asus E35M1-I DELUXE with two samsung
spinpoints F1's and one F4 ecogreen, running Ubuntu 11.04 Linux
2.6.38-8-server:
[68623.060362] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[68623.060521] ata2.00: failed command: WRITE DMA EXT
[68623.060626]
** Changed in: udev (Debian)
Status: Unknown = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/285892
Title:
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
To
have the same problem recently.
ubuntu11.04 natty
Linux enet 2.6.38-8-server #42-Ubuntu SMP Mon Apr 11 03:49:04 UTC 2011 x86_64
x86_64 x86_64 GNU/Linux
nameWDC WD3200AAJS-00L7A0
size320 GB
speed 7200 r/m
cache 8 MB
interface SATA Rev 2.5
transrate 300 MB/s
feature
** Bug watch added: Debian Bug tracker #622340
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622340
** Also affects: udev (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622340
Importance: Unknown
Status: Unknown
** Bug watch added: Red Hat Bugzilla #684599
Same issue here.
OS: Ubuntu Server lucid
Kernel: 2.6.38-7-generic (kernel-ppa)
HD: WDC WD10EARS-00Y
Error:
[ 222.848056] ata2: lost interrupt (Status 0x50)
[ 222.848094] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 222.848166] ata2.00: failed command: READ DMA EXT
[
I'm still seeing the problem in the most recent build of Natty as well:
2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64
x86_64 GNU/Linux
ext4 / partition for the whole drive (minus a bit of swap)
This is on a new (to me) box that was happily running Windows 7 prior to
Hi, I also can confirm the problem, because I am experiencing it with
Ubuntu 10.10 2.6.35-28-generic on Dell Latitude E6500. Dell's
Diagnostic Tool reports no errors (I have checked it several times).
** Attachment added: dmesg output
Hi, it looks that this problem still exist in 2.6.38 kernel.
Is someone work on this maybe?
Regards
Jarek
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/285892
Title:
ata1.00: exception Emask 0x0
** Attachment added: dmesg
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285892/+attachment/1947694/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/285892
Title:
ata1.00:
Since upgrading to natty alpha about month ago the issue has more or
less disappeared for me (see my comment earlier re problem in lucid and
maverick) - previously used to get it every single boot (i.e. daily)
plus intermittently on top - since upgrading only had the issue once.
Note that
please read my comment here, maybe this is related?
https://bugs.launchpad.net/ubuntu/+bug/550559/comments/41
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/285892
Title:
ata1.00: exception Emask
I've solved temporaly adding this parameter on kernel:
libata.force=noncq
The fix when will released?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/285892
Title:
ata1.00: exception Emask 0x0 SAct
** Changed in: linux
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/285892
Title:
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
--
[Español, por favor traducir]
Yo tengo este error y después de eso parece como si me bloqueara el
disco (o me lo dañara) por q' ese error pasa a ser persistente en
windows hasta q' lanza el pantallazo azul:
Jan 18 14:08:03 familia-K7S41GX kernel: [14769.056043] ata2: lost interrupt
(Status
fwiw, I am having the same problems with the latest Natty packages.
The kernel is
Linux mythtv 2.6.37-11-generic #25-Ubuntu SMP Tue Dec 21 23:42:56 UTC 2010
x86_64 GNU/Linux
My setup is
Asus P7P55D-E LX Motherboard with the Marvell 88SE9125 SATA 3 controller
Intel i5 760 CPU
PC1333 8G RAM (4GB
** Description changed:
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/285892
Title:
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
--
ubuntu-bugs mailing list
Wow, guys, I have the fullest respect for your patience and insisting
behavior after the long time this bug has been around.
Well, what can I say? Two months ago, I built myself a brand new machine
with the following components:
Asus P7H57D-V Evo
Intel Core i7 875K
4 x 4 GB Corsair PC3-16000
I have switched the HD, I am sure the cables are properly plugged now.
Also I don't experience this issue with a different OS, so it's very
unlikely to be a cabling issue.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received
I am also experiencing this problem with Maverick.
The disk is:
Western Digital Caviar Black: WD1002FAEX-00Z3A0, 1 TB
The error:
[ 1870.860322] ata1: lost interrupt (Status 0x50)
[ 1870.860343] ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x5850002 action 0xe
frozen
[ 1870.860348] ata1.00:
My hard drive's SMART check shows that there are about 2 million Command
Timeout's and high Seek Error rate. There are two wires connected to the
plate the hard drive is connected to that seem to be the power cables and
they are a bit loose. Check you power cables and SMART results.
2010/10/21
Confirming this is still an issue in Maverick beta - it's worse than
ever. In lucid I had this error occasionally - since moving to maverick
it takes two or three failed boots (dumping down to busybox as grub
couldn't find the disk) plus lots of keypresses during boot to get it
going - it's like
In the end, it seems that this bug is related to
- HDD problems like unreadable blocks / sectors
- possibly changes in how HDDs act in such situations
- some controllers like the one in AMD SB700
- kernel / libata changes after 2.6.24 (?)
I worry that maybe
- HDD manufacturers are changing the
I think I have this bad block for a year now... the thing is that I
would never write much data on this disk. The problem started when the
headers actually started to cross over this spot, since I almost filled
the disk a couple of times.
I never cared to make a full surface scan using the
Do you still think it may be a hardware issue? I have an ASUS X83Vm notebok
with Seagate hard drive. Have no idea how to get more details about my
motherboard.
I don't get that many hang-ups after reinstall so I can't tell yet
if libata.noacpi=1 is working. BTW, what side effects does
Hi there, libata.noacpi=1 seems to have no side-effects... the only
kernel switch that had a side effect was libata.force=norst which
prevents soft and hard link resettings. If you have that switch on, when
this bug comes up, there is a system lock down (because obviously the
kernel prevented the
I just performed a full test in this hard drive and ESTOOL returned a
LBA 287034602 Bad Sector. Now I wonder if this is because the hardware
had influence on the test itself, or if it is a real bad sector. Guess I
will have to do one more test.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr
Concluded the second test, BAD BLOCK confirmed, at the same spot.
Looks to me this is the trouble maker, and this made me look ridiculous...
I was believing that fsck would grasp any inconsistencies or bad blocks upon
boot up, silly me, it just does partial check-ups.
The Samsung's ESTOOL
@DjznBR My cable swap was equally ineffective. I'm assuming that I
have the same bad block problems.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which
Ok, tried different and combined things, like libata.noacpi=1,
libata.force=noncq,norst being that this last one was to block the
soft and hard resetting, which eventually cause the whole system to
crash and kernel panic for the first opportunity this bug came up.
Now I am hopeless... I can
I may try to go back to kernel 2.6.24.7, by the time Hardy Heron was
released. This bug got introduced right after Intrepid Ibex, so I am
gonna try Hardy Heron-time kernel. Stock 2.6.24.7 in ArchLinux.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
Added option in kernel,
In my current GRUB (Arch):
kernel /boot/vmlinuz26 root=/dev/sda1 ro nomodeset libata.noacpi=1
The option you might want to test:
libata.noacpi=1
So far no hang ups.
I still get these messages in dmesg (without any symptom):
ata3: softreset failed (device not ready)
Back. Changing the cables did not work. I may consider some few options
to the kernel such as turning off some ACPI options.
Here is a list of what I did WITHOUT SUCCESS:
[X] TURNED HDPARM OFF
[X] CHANGED CABLE
[X] EXPERIMENTED AHCI RAID MODES
[X] DISABLED NCQ
[X] COMPILED KERNEL WITH
@Grigory Rechistov: I should've read your message first... At least I
have a 32-bit system now and java doesn't eat twice as much memory. If
only I knew about pae-enabled kernels before...
Anyways, I've had only one hang up in these two days, as oppose to one
every 5 minutes. On the other hand,
I have changed cables, but I was stubborn and stuck it in the same SATA
port. I am going to change this. I don't think it's going to work, but I
will try, after I test kernel parameter libata.force=1.5Gbps -
UNFORTUNATELY, CONFIG_SATA_PMP=n *DOES NOT WORK* to fix this issue...
it is only a rumour
libata.force=1.5Gbps DIDN'T WORK as well...
Changed the cables to different routes... SATA1 - SATA2 SATA2 - SATA3
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
libata.force=noncq --- no go. Problem persists even with ncq being
turned off.
Next step now is to configure a new kernel through the ABS method, and without
PMP option enabled.
I'll let you guys know.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
Hey I wanted to mention that I just got this on a Fedora box
(2.6.30.10-105.2.23.fc11.i586) today. Yesterday I had to swap out the
motherboard, AND I HAD TO CHANGE AN IDE CABLE. This never happened with
the old motherboard and cable.
I will try to put in a new cable next week an will report
Is it 64-bit related? Will it stop if I install 32-bit system?
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Ok, after biting the bullet, I called it a day again... everything I
wrote before about fglrx, google-chrome, flash player is crap... meaning
that it was a huge coincidence... Forget also BIOS settings, RAID, AHCI,
and stuff like that, coz this is only in the kernel...
I have dumped Ubuntu 10.04
Hi there.
Trying to reassemble failed raid1 array, I encountered the problem.
If this is not a real hardware crash, the problem looks similar as this bug.
I hope to recover my raid1 and return to peaceful operation of ubuntu server,
but have no idea what to do.
Please give me a suggestion if
Ok, now I have reached the point where nothing really works for this
matter, except the kernel compiling step which I didn't try.
In some forum I found this:
all you need to is that, re-compile your kernel with CONFIG_SATA_PMP=n
(default is CONFIG_SATA_PMP=y)
Can anyone confirm if this could be
I have an ASUS motherboard and there is the SATA configuration in the
BIOS. I have changed the SATA controller mode to RAID mode (there is IDE
and SATA mode). I have done this, and it worked, even with one drive.
The BIOS does not give many details about this...
[ 0.942521] ahci :00:11.0:
What a killer bug... drives me crazy... I will wait till 10.04.1 is out,
and then make a clean install on new ext4 partitions... But I hope it's
fixed by that time.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug
Just updated kernel to Linux tulskiy-laptop 2.6.32-24-generic #38-Ubuntu
SMP Mon Jul 5 09:20:59 UTC 2010 x86_64 GNU/Linux
Still getting this issue:
Jul 9 17:11:20 tulskiy-laptop kernel: [ 2082.010069] ata1.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jul 9 17:11:20
I've the same problem with last lucid kernel. No problem with karmic.
2.6.35 too.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Did a update today, 04/07 and this bug is back. I wonder which package
triggered it again... gnome vfs?
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which
I confirm that I have had no ATA errors since the removal of fglrx
driver.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Removed fglrx yesterday and so far no errors... I will be back in a
week.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Hi, back. I am using kernel - Linux orion 2.6.32-23-generic #37-Ubuntu
SMP Fri Jun 11 07:54:58 UTC 2010 i686 GNU/Linux.
I formatted my disk and did a fresh ubuntu install, applied all updates,
etc. I had been using Lucid and it seemed that this issue disappeared.
Today I went and installed the
I've been testing the system for eight hours without Chrome or Flash
plugin. As I told, I had done a Catalyst 10.6 installation prior to the
previous mentioned software here. I suspect that fglrx is causing all
this trouble. I realized an hour ago that my dmesg log was full of SATA
errors while
** Tags removed: kernel-candidate
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Tags added: kernel-candidate kernel-reviewed
** Tags removed: kernel-needs-review
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Installed the last kernel via update, and problem seems to be gone... didn't
show up for 4 days now...
Used to show up at least once every 2 days.
Linux my-desktop 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC
2010 i686 GNU/Linux
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0
Please, can backport this to lucid, the kernel mainline
v2.6.35-rc1-lucid work OK
https://bugzilla.kernel.org/show_bug.cgi?id=14314
Comment #35 From Tejun Heo 2010-01-14 07:49:17
Patches posted upstream.
http://article.gmane.org/gmane.linux.ide/44381
** Tags added: kernel-core kernel-needs-review
** Tags removed: needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: New = Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
repro on my samsung n130 on ubuntu lucid
the patch libata-ata_piix-clear-spurious-IRQ.patch fix the problem.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs,
I got this error with a ubuntu installation running as guest os in Parallels.
I was using kernel:
2.6.32-22-generic-pae #33-Ubuntu SMP
and / became read-only and the last line in syslog was:
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
--
ata1.00: exception Emask 0x0 SAct
Definitely this is a bug... i'm getting reports at university... it
would be such a coincidence hard drives failing at worldwide scale. I
think this is definitely the linux kernel. Please also refer to this
bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/397096
--
ata1.00: exception
BTW, there is a Launchpad repository for Samsung netbooks with this
problem fixed: https://launchpad.net/~voria/+archive/ppa/
I tried it yesterday and now my Samsung N130 works without disk freezes.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
Grigory - for netbook owners it's a great news. Hovewer if someone is
struggling with this bug on desktop machine... well, seems like it's still some
work to be done.
I've tried to boot 2.6.32-22 kernel with both libata.noacpi and
libata.force=noncq - without big success... HDD worked for 10
...some additional info: lspci...
** Attachment added: lspci.txt
http://launchpadlibrarian.net/47463250/lspci.txt
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of
...kern.log... (on 02.05.2010 around 13:20 this message came few times
in a row - every 55 seconds...)
** Attachment added: kern.log
http://launchpadlibrarian.net/47463459/kern.log
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
...lsmod...
** Attachment added: lsmod.txt
http://launchpadlibrarian.net/47463565/lsmod.txt
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is
...and /var/log/messages...
** Attachment added: messages
http://launchpadlibrarian.net/47463685/messages
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs,
Same bug here - I encountered it both on lucid kernel (2.6.32-22) and 2.6.34rc6
from http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.34-rc6-lucid/
I'm struggling with that problem on desktop computer with Samsung HDD
[ 52.804559] ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
upgraded to Linux version 2.6.31-20-generic.
Freezes ATA continues.
Workaround with inserted CD continues.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs,
I managed to compile and install a kernel taken from git with the
aforementioned patch. Now it works all right no hang ups are experienced
anymore.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification
I experience the same problem on my Samsung N130. I use it with custom
installed Kingston SSD Now 64GB hard drive. The problem has risen during
installation attempt. So I had to perform the installation of 9.10 with
options acpi=off noapic. Everything went fine, but the freshly
installed system
thank's for the workaround, works fine.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I've had a little chat with Greg, who has very good contacts to samsungs
support.
They say we can use this new firmware/bios file:
@ Sandeep Wadhwa: So, if Ray-Ven is right, what BIOS-Version do you have
installed on your N128?. If it is version 05IG, do you have any freezes
left?
Andy
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug
this bios can be installed on n130 too.
BUT, Samsung now, as a consequence of my question, now upped a new bios in the
n130 section.
So please use the n130 bios
An arch-linux user (2.6.32) said 06cm still has freezes.
Are there different experiences?
If so, can someone test n182 BIOS please?
And, use a 2.6.33 Kernel for working samsung-laptop modules.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
A8J freezes continues
a very stupid possible solution is to leave a CD in the CD reader: seems to
works, no freezes occurs after.
I saw this idea on another post on the same issue.
but why? does this information doesn't give any clues to developers?
--
ata1.00: exception Emask 0x0 SAct
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen.
I am facing the same problem on the N-128 Samsung Netbook with Ubuntu
9.10 UNR. The freeze happens for about 20 seconds after about 5 minutes
of switching on. After that it dosen't repeat itself as long as the
Netbook is ON. Next
with today's last update the laptop is not more experiencing HD freezes,
maybe a temporary good combination between kernel and other modules.
Anyway NO kernel update as occoured since last bugs, only other modules updates.
hope still stable...
linux 2.6.31-9-rt
using ext3 filesystem
--
ata1.00:
the HD for A8J is an ST9100824A Ultra ATA/100 100GB (seagate)
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Attention: a not simple workaround has been found for some of us
(specially Samsung hard disk/bios users), look at this link:
http://wiki.archlinux.org/index.php/Samsung_N140
Please, kernel developers of Ubuntu, insert these workarounds in the
next kernel version:
Here I copy the relevant
Same problem on a Samsung N140.
Windows and other Linux do not suffer this issue.
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
# tail /var/log/kern.log
Dec 25 16:55:18 baddha-laptop kernel: [ 250.816351] ata1.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Dec 25 16:55:18 baddha-laptop kernel: [ 250.816395] ata1.00: cmd
ca/00:08:da:4c:e6/00:00:00:00:00/ea tag 0 dma 4096 out
Dec 25 16:55:18 baddha-laptop
please have a look to bugs: # 297058, # 397096, # 279693
linking together different hypothesis on hdparm, linut-rt, AHCI, HW
failures,and so on... without a real way out of the bug.
Actually running karmic -rt on ausu A8J and the same issue still remains.
seriously after 2 years of ubuntu and
As a supplementary infoo the asus A8J bios don't have AHCI option.
This could be a solution for someone... not yet a solution of the bug.
Any one found different solutions?
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received
I don't have this option
...
Removing or commenting out the option 'resume=/dev/swap' from the grub
installation file in /boot/grub/menu.lst should solve this.
...
in my GRUB, anyway the bug still there, see reports abowe.
and below syslog
Dec 21 19:48:57 my2912071352 kernel: [ 3102.000243]
In reply to kernel-janitor on 2009-08-25
I did not notice your request before, but this bug is not an issue for me
anymore.
On 2008-11-03, I reinstalled 8.10 without AHCI enabled in the bios and I did
not encounter any freezes.
At this moment I'm running Karmic with 2.6.31-16-generic, still
I have had the same problem on Ubuntu karmic and Suse 11.1. Both
installations went well (apart for the fact the GRUB overwrites the disk
area used by the RAID on my system in both cases - this is solved by
removing stage1_5 from the GRUB installation directory - rename/move or
delete the file).
Thanks gab0r,
I didn' notice the issue happens after standby, I use it very often and didn't
relate the issue to the standby.
Now I always shutdown and the freeze don't happen any more. System is now
usable, but without standby :(
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action
Same here on a Samsung N140, running latest Karmic kernel
2.6.31-14-generic
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Same in a Macbook2,1 using a recently installed karmic x86_64 on ext4.
Kernel 2.6.31-15-generic
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have the same problem. I've just upgraded to Karmic (Linux asus-lapi
2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009 i686 GNU/Linux)
on my Asus M6VA laptop, also with a 160GB Samsung HDD. I have this problem only
when I put the laptop in standby, or resume from it, but not all
I also have this issue with Jaunty (2.6.28-15-generic #52-Ubuntu SMP Wed
Sep 9 10:49:34 UTC 2009 i686 GNU/Linux) on an IBM Thinkpad X31 with an
160GB Samsung disk:
from dmesg startup:
[4.087964] ata_piix :00:1f.1: PCI INT A - Link[LNKC] - GSI 11 (level,
low) - IRQ 11
[4.088073]
I just experienced this after an upgrade from Jaunty to Karmic Beta with
kernel: 2.6.31-11-generic #38-Ubuntu SMP Fri Oct 2 11:55:55 UTC 2009
i686 GNU/Linux
[ 221.816249] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 221.816279] ata1.00: cmd
Hi Marcel,
This bug was reported a while ago and there hasn't been any activity in
it recently. We were wondering if this is still an issue? Can you try
with the latest development release of Ubuntu? ISO CD images are
available from http://cdimage.ubuntu.com/releases/karmic .
If it remains an
This seems to be similar to my problem.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/279693
--
ata1.00: exception Emask 0x0 SAct 0x807f SErr 0x0 action 0x6 frozen
https://bugs.launchpad.net/bugs/285892
You received this bug notification because you are a member of Ubuntu
Bugs, which is
1 - 100 of 102 matches
Mail list logo
