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 libata.noacpi=1 have? On Thu, Jul 29, 2010 at 8:42 AM, DjznBR <285...@bugs.launchpad.net> wrote: > 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 tell that nothing in the realm of what a user > can do will solve this. At least I got to a conclusion. > > So what you guys advise... > > Do I trash my SAMSUNG drive, along with my trust in this company... > > or > > Do I trash my ASUS M3A78-EM equipped with SB700 chipset... > > -- > 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 direct subscriber > of the bug. > > Status in The Linux Kernel: Unknown > Status in “linux” package in Ubuntu: Triaged > > Bug description: > Binary package hint: linux-headers-2.6.27-7-generic > > Since I'm running 8.10 alpha6 64-bit, I'm having now and then a frozen > machine for 1 or more minutes. > Although I can not pinpoint the reason, it seems to happen soon after > booting and round the whole hour. > I guess there is some process in the background responsible. So I include > the entries of the system log from the freezes at 12:00 and 14:00. > > I'm not sure if I file this issue under the right package. Sorry for that. > > To unsubscribe from this bug, go to: > https://bugs.launchpad.net/linux/+bug/285892/+subscribe > -- -------------------------------- Best, Denis Tulskiy -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs