[Bug 89362] Re: system locking up (forcing a hard reboot)
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Summary changed: - system locking up (forcing a hard reboot) + Asus F3JC system locking up (forcing a hard reboot) -- Asus F3JC system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
Unfortunately, indeed. This is still an issue with 9.04; it already happened few times since my upgrade. -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
Unfortunately it seems this bug is still an issue. Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks. -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
Update to my previous comment : I am starting to think that this is a hardware issue ; my hard disk seems to be dying. Badblocks gave me 33 bad blocks on the home partition, plus the drive is emitting a horrible scratching noise. (hitachi drive on asus laptop) -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
Re: [Bug 89362] Re: system locking up (forcing a hard reboot)
If you are considering an update, know that 2.6.24-21-generic does *not* solve the problem for me. On Sat, 2008-11-08 at 19:29 +, michael mestre wrote: > Hi guys, I have the same problem since yesterday. > I am not sure if this is due to a hard drive failure or a kernel upgrade (I > am using > 2.6.24-19-generic on a Ubuntu 8.04). > > The messages I get in /var/log/messages are : > > Nov 8 19:17:50 odeon kernel: [ 5895.216562] res > 40/00:00:00:4f:c2/00:01:00:00:00/00 Emask 0x4 (timeout) > Nov 8 19:17:50 odeon kernel: [ 5895.216580] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Nov 8 19:17:50 odeon kernel: [ 5895.216599] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Nov 8 19:17:50 odeon kernel: [ 5895.216617] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Nov 8 19:17:50 odeon kernel: [ 5895.216635] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Nov 8 19:17:50 odeon kernel: [ 5895.216653] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Nov 8 19:17:50 odeon kernel: [ 5895.216670] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Nov 8 19:17:50 odeon kernel: [ 5895.216688] res > 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > Nov 8 19:17:50 odeon kernel: [ 5895.528718] ata1: soft resetting link > Nov 8 19:17:55 odeon kernel: [ 5900.728870] ata1: port is slow to respond, > please be patient (Status 0xd0) > Nov 8 19:18:00 odeon kernel: [ 5905.538192] ata1: hard resetting link > Nov 8 19:18:06 odeon kernel: [ 5911.046524] ata1: port is slow to respond, > please be patient (Status 0x80) > Nov 8 19:18:10 odeon kernel: [ 5915.577217] ata1: hard resetting link > Nov 8 19:18:16 odeon kernel: [ 5921.088562] ata1: port is slow to respond, > please be patient (Status 0x80) > Nov 8 19:18:45 odeon kernel: [ 5950.568605] ata1: limiting SATA link speed > to 1.5 Gbps > Nov 8 19:18:45 odeon kernel: [ 5950.568610] ata1: hard resetting link > Nov 8 19:18:47 odeon kernel: [ 5952.329175] ata1: SATA link up 1.5 Gbps > (SStatus 113 SControl 310) > Nov 8 19:18:47 odeon kernel: [ 5952.331304] ata1.00: ACPI cmd > f5/00:00:00:00:00:a0 filtered out > Nov 8 19:18:47 odeon kernel: [ 5952.335164] ata1.00: ACPI cmd > f5/00:00:00:00:00:a0 filtered out > Nov 8 19:18:47 odeon kernel: [ 5952.336615] ata1.00: configured for UDMA/100 > Nov 8 19:18:47 odeon kernel: [ 5952.336656] ata1: EH complete > Nov 8 19:18:47 odeon kernel: [ 5952.336788] sd 0:0:0:0: [sda] 234441648 > 512-byte hardware sectors (120034 MB) > Nov 8 19:18:47 odeon kernel: [ 5952.336813] sd 0:0:0:0: [sda] Write Protect > is off > Nov 8 19:18:47 odeon kernel: [ 5952.336856] sd 0:0:0:0: [sda] Write cache: > enabled, read cache: enabled, doesn't support DPO or FUA > > > The computer crashes sometimes, but not always. Plus the hard disk makes a > louder and higher-pitched scratching noise than usual. > lspci gives this output for the SATA controler : > SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI > Controller (rev 03) > > If you have any updates, i'm all ears. > Michael > -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
Hi guys, I have the same problem since yesterday. I am not sure if this is due to a hard drive failure or a kernel upgrade (I am using 2.6.24-19-generic on a Ubuntu 8.04). The messages I get in /var/log/messages are : Nov 8 19:17:50 odeon kernel: [ 5895.216562] res 40/00:00:00:4f:c2/00:01:00:00:00/00 Emask 0x4 (timeout) Nov 8 19:17:50 odeon kernel: [ 5895.216580] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 8 19:17:50 odeon kernel: [ 5895.216599] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 8 19:17:50 odeon kernel: [ 5895.216617] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 8 19:17:50 odeon kernel: [ 5895.216635] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 8 19:17:50 odeon kernel: [ 5895.216653] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 8 19:17:50 odeon kernel: [ 5895.216670] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 8 19:17:50 odeon kernel: [ 5895.216688] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Nov 8 19:17:50 odeon kernel: [ 5895.528718] ata1: soft resetting link Nov 8 19:17:55 odeon kernel: [ 5900.728870] ata1: port is slow to respond, please be patient (Status 0xd0) Nov 8 19:18:00 odeon kernel: [ 5905.538192] ata1: hard resetting link Nov 8 19:18:06 odeon kernel: [ 5911.046524] ata1: port is slow to respond, please be patient (Status 0x80) Nov 8 19:18:10 odeon kernel: [ 5915.577217] ata1: hard resetting link Nov 8 19:18:16 odeon kernel: [ 5921.088562] ata1: port is slow to respond, please be patient (Status 0x80) Nov 8 19:18:45 odeon kernel: [ 5950.568605] ata1: limiting SATA link speed to 1.5 Gbps Nov 8 19:18:45 odeon kernel: [ 5950.568610] ata1: hard resetting link Nov 8 19:18:47 odeon kernel: [ 5952.329175] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Nov 8 19:18:47 odeon kernel: [ 5952.331304] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out Nov 8 19:18:47 odeon kernel: [ 5952.335164] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 filtered out Nov 8 19:18:47 odeon kernel: [ 5952.336615] ata1.00: configured for UDMA/100 Nov 8 19:18:47 odeon kernel: [ 5952.336656] ata1: EH complete Nov 8 19:18:47 odeon kernel: [ 5952.336788] sd 0:0:0:0: [sda] 234441648 512-byte hardware sectors (120034 MB) Nov 8 19:18:47 odeon kernel: [ 5952.336813] sd 0:0:0:0: [sda] Write Protect is off Nov 8 19:18:47 odeon kernel: [ 5952.336856] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA The computer crashes sometimes, but not always. Plus the hard disk makes a louder and higher-pitched scratching noise than usual. lspci gives this output for the SATA controler : SATA controller: Intel Corporation 82801HBM/HEM (ICH8M/ICH8M-E) SATA AHCI Controller (rev 03) If you have any updates, i'm all ears. Michael -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
The problem is still around with 8.04. I have not tried 8.10, since this is my main machine at the moment, and the reported network card surprises some had put me off. -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
The 18 month support period for Feisty Fawn 7.04 has reached it's end of life - http://www.ubuntu.com/news/ubuntu-7.04-end-of-life . As a result, we are closing the linux-source-2.6.20 kernel task. Additionally, there has been no feedback with this bug for over 3 months so I'm going to close the 2.6.22 task as well and mark the current linux task to Incomplete. If we can get confirmation this is still an issue with Intrepid that would be great. Thanks. ** Changed in: linux-source-2.6.20 (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux-source-2.6.22 (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test: 1) If you are comfortable installing packages on your own, the linux- image-2.6.27-* package is currently available for you to install and test. --or-- 2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD. Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback. ** Tags added: cft-2.6.27 -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
Beginning with the Hardy Heron 8.04 development cycle the kernel source package naming convention changed from "linux-source-2.6.xx" to just "linux". Going forward, kernel bugs should now be reported against the "linux" package. I'm removing the linux-source-2.6.24 task as this is already correctly reported against the "linux" package. ** Changed in: ubuntu Sourcepackagename: linux-source-2.6.24 => None Status: New => Invalid -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task. However, please note that this report will remain open against the actively developed kernel. Thank you for your continued support and help as we debug this issue. ** Changed in: linux-source-2.6.17 (Ubuntu) Status: Incomplete => Invalid ** Description changed: Binary package hint: linux-image-generic [still happening with 2.6.20-14 although less often than it used to] [up-to-date feisty... the problem was present with edgy as well, which prompted me to upgrade] [hardy heron... all hell broke loose since 2.6.24. Freezes are more frequent than ever.] [hardware: Asus F3JC (notebook)] Problems with ata2 seem strongly correlated with system freeze (hard to trace because of the complete freeze). The symptoms are generally: 1- freeze on X 2- if quick enough, I can switch to a console (Ctrl + F*) 3- trying to log on the console prompts error messages like "ata2: speed down requests" "Error sending Cmd #07" "Write error on swap device", etc... The systems never get to log me in 4- trying to access the computer remotely is unsuccessful (the machine does not answer anymore) 5- only a hard reboot is possible /var/log/messages contains the following during normal operations Mar 3 10:30:23 hot-spring kernel: [ 1810.944000] ata2.00: limiting speed to PIO2 Mar 3 10:30:23 hot-spring kernel: [ 1810.944000] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) Mar 3 10:30:30 hot-spring kernel: [ 1817.948000] ata2: port is slow to respond, please be patient (Status 0xd0) Mar 3 10:30:53 hot-spring kernel: [ 1840.964000] ata2: soft resetting port Mar 3 10:30:54 hot-spring kernel: [ 1841.30] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:30:54 hot-spring kernel: [ 1841.30] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.30] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ata2.00: configured for PIO2 Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ata2: EH complete Mar 3 10:32:20 hot-spring kernel: [ 1927.576000] ata2.00: limiting speed to PIO1 Mar 3 10:32:20 hot-spring kernel: [ 1927.576000] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) Mar 3 10:32:27 hot-spring kernel: [ 1934.584000] ata2: port is slow to respond, please be patient (Status 0xd0) Mar 3 10:32:50 hot-spring kernel: [ 1957.60] ata2: soft resetting port Mar 3 10:32:50 hot-spring kernel: [ 1957.944000] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:32:50 hot-spring kernel: [ 1957.944000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:32:50 hot-spring kernel: [ 1957.944000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:32:50 hot-spring kernel: [ 1958.136000] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:32:50 hot-spring kernel: [ 1958.136000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:32:50 hot-spring kernel: [ 1958.136000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:32:50 hot-spring kernel: [ 1958.136000] ata2.00: configured for PIO1 Mar 3 10:32:50 hot-spring kernel: [ 1958.136000] ata2: EH complete Mar 3 10:34:52 hot-spring kernel: [ 2079.484000] ata2.00: limiting speed to PIO0 Mar 3 10:34:52 hot-spring kernel: [ 2079.484000] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) + Mar 3 10:34:59 hot-spring kernel: [ 2086.488000] ata2: port is slow to respond, please be patient (Status 0xd0) Mar 3 10:35:22 hot-spring kernel: [ 2109.504000] ata2: soft resetting port Mar 3 10:35:22 hot-spring kernel: [ 2109.848000] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3
[Bug 89362] Re: system locking up (forcing a hard reboot)
I was having these regular freezes, sometimes 3 or 4 time in a row and had to force reboot every time. Later on i noticed another freeze (this one reproducible) while connecting my WM6 PPC to DUN --activesync... that was already reported. The following thought came to mind: "What if they are somehow related?" After disconnecting my bluetooth adapter the random freezes completely disappeared, one week without any freezes... -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
Using 2.6.24-18...
Freeze again, but this time I managed to copy/paste what should go into
/var/log/syslog into a webmail
before the complete freeze.
Jun 6 12:58:24 my kernel: [15886.070164] ata1.00: exception Emask 0x0 SAct 0x0
SErr 0x0 action 0x2 frozen
Jun 6 12:58:24 my kernel: [15886.070181] ata1.00: cmd
ca/00:08:80:d4:03/00:00:00:00:00/e7 tag 0 dma 4096 out
Jun 6 12:58:24 my kernel: [15886.070183] res
40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jun 6 12:58:24 my kernel: [15886.070188] ata1.00: status: { DRDY }
Jun 6 12:58:29 my kernel: [15891.103152] ata1: port is slow to respond, please
be patient (Status 0xd0)
Jun 6 12:58:34 my kernel: [15896.079265] ata1: device not ready (errno=-16),
forcing hardreset
Jun 6 12:58:34 my kernel: [15896.079275] ata1: soft resetting link
Jun 6 12:59:04 my kernel: [15926.243460] ata1.00: qc timeout (cmd 0xec)
Jun 6 12:59:04 my kernel: [15926.243476] ata1.00: failed to IDENTIFY (I/O
error, err_mask=0x4)
Jun 6 12:59:04 my kernel: [15926.243481] ata1.00: revalidation failed
(errno=-5)
Jun 6 12:59:04 my kernel: [15926.243488] ata1: failed to recover some devices,
retrying in 5 secs
Jun 6 12:59:14 my kernel: [15936.270551] ata1: port is slow to respond, please
be patient (Status 0xd0)
Jun 6 12:59:19 my kernel: [15941.250652] ata1: device not ready (errno=-16),
forcing hardreset
Jun 6 12:59:19 my kernel: [15941.250662] ata1: soft resetting link
Jun 6 12:59:49 my kernel: [15971.514689] ata1.00: qc timeout (cmd 0xec)
Jun 6 12:59:49 my kernel: [15971.514702] ata1.00: failed to IDENTIFY (I/O
error, err_mask=0x4)
Jun 6 12:59:49 my kernel: [15971.514706] ata1.00: revalidation failed
(errno=-5)
Jun 6 12:59:49 my kernel: [15971.514712] ata1: failed to recover some devices,
retrying in 5 secs
Jun 6 12:59:59 my kernel: [15981.542773] ata1: port is slow to respond, please
be patient (Status 0xd0)
Jun 6 13:00:04 my kernel: [15986.518887] ata1: device not ready (errno=-16),
forcing hardreset
Jun 6 13:00:04 my kernel: [15986.518896] ata1: soft resetting link
Jun 6 13:00:35 my kernel: [16016.782922] ata1.00: qc timeout (cmd 0xec)
Jun 6 13:00:35 my kernel: [16016.782937] ata1.00: failed to IDENTIFY (I/O
error, err_mask=0x4)
Jun 6 13:00:35 my kernel: [16016.782942] ata1.00: revalidation failed
(errno=-5)
Jun 6 13:00:35 my kernel: [16016.782948] ata1.00: disabled
Jun 6 13:00:40 my kernel: [16022.319122] ata1: port is slow to respond, please
be patient (Status 0xd0)
Jun 6 13:00:45 my kernel: [16027.294883] ata1: device not ready (errno=-16),
forcing hardreset
Jun 6 13:00:45 my kernel: [16027.294894] ata1: soft resetting link
Jun 6 13:00:45 my kernel: [16027.550889] ata1: EH complete
Jun 6 13:00:45 my kernel: [16027.550919] sd 0:0:0:0: [sda] Result:
hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Jun 6 13:00:45 my kernel: [16027.550926] end_request: I/O error, dev sda,
sector 117691520
Jun 6 13:00:45 my kernel: [16027.550933] Buffer I/O error on device sda11,
logical block 379444
Jun 6 13:00:45 my kernel: [16027.550938] lost page write due to I/O error on
sda11
--
system locking up (forcing a hard reboot)
https://bugs.launchpad.net/bugs/89362
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
[Bug 89362] Re: system locking up (forcing a hard reboot)
I have had no time to play with the "acpi=off" option and enjoyed two weeks of freeze-free bliss... until today. I am a little worried playing with that one option on a notebook (doesn't no acpi mean no fan ?). When seeing the early signs of a freeze (that is the light for the hard disk continuously on for few seconds, without blinking), dashing "tail /var/log/messages" gave a last line like: kernel: [4249.908524] res 40/00:00:00 [... many 00 ...] Emask 0x4 (timeout) After reboot that last line does not appear in log/messages anymore (makes sense, no I/O when the problem occurs... but might appear on the spot because of some sort of buffering happening). Since ACPI's involment in the case is suspected, here is what I have in logs with ACPI (no idea whether this is relevant or not) [ 32.899330] ACPI: Looking for DSDT in initramfs... error, file /DSDT.aml not found. Thanks, L. -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
** Also affects: linux-source-2.6.24 (Ubuntu) Importance: Undecided Status: New -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
Lau, Thanks for the information. The SC04 firmware in your TSSTcorpCD/DVDW TS-L632D confirms that this is NOT Bug #75295 (as you correctly pointed out earlier). Thanks for confirming this. Also, I must apologise. I led you astray in suggesting the dmesg may include the freeze point. It won't unless the freeze occurs during boot- up (dmesg is required by the Kernel Team anyway - so not wasted). syslog and/or messages logs is what we're after. syslog should show then then then . The freeze point may not show an error message but may show what was happening at the time of the freeze. Anything that can narrow this down will be useful. The detail you gave in your initial bug report indicates an issue with ACPI [during normal operation & not during boot]. I would have thought that any issues with ACPI should show up during boot (in dmesg) - but boot looks Ok and PC seems well supported to me. Can you boot with the additional kernel boot option "acpi=off" and test machine for freeze again? Thanks. Confirming & passing to Kernel Team. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ubuntu Kernel Team (ubuntu-kernel-team) Status: Incomplete => Confirmed -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
Re: [Bug 89362] Re: system locking up (forcing a hard reboot)
Gareth, Thanks for the quick following up. I have to moderate my earlier complain about kernel 2.6. Doing further tests, I noticed that firefox was able to cause trouble (wild CPU and disk usage and I am becoming a little quick to force a computer shutdown because of the freezes). Nevertheless, I still experience freezes. Here are the data: 1- "uname" Linux localhost 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux 2- dmesg (see file attached - done right after a freeze-forced reboot; doing dmesg during a freeze does not let me save the output anywhere on the disk, neither on a thumbdrive, and email software is frozen - all IO on storage seem unavailable) 3- lspci (see file attached) 4- dmidecode (see file attached) Notes: I have found nothing that seemed relevant in either syslog, kern.log, or messages. log/messages says ata2.00: ATAPI: TSSTcorpCD/DVDW TS-L632D, SC04, max UDMA/33 about the optical drive. All the above was done while booting with the kernel parameter combined_mode=libata 2008/4/23 Gareth Fitzworthington <[EMAIL PROTECTED]>: > Lau, > OK we've checked some likely causes with no success. I think we need to move > this issue along to the Kernel Team. > > However, we need to re-establish the baseline data for this bug report since > the problem was originally reported under Feisty and you now appear to be > using Hardy. The Kernel Team will need this. > Can you supply the following information for your present system [Hardy]: > 1. Please include the output of the command "uname -a" in your next response. > 2. Please run the command "dmesg > dmesg.log" which includes the freeze > point and attach the resulting file "dmesg.log" to this bug report. > 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the > resulting file "lspci-vvnn.log" to this bug report. > 4. Please run the command "sudo dmidecode > dmidecode.txt" and attach the > resulting file "dmidecode.txt" to this bug report. > Thanks. > > Note1: Point (2) above should include the freeze point. If you can get it to > freeze again and then reboot the dmesg should contain the freeze point. > Note2: Also, after a freeze & reboot can you check syslog and kernel.log to > see if anything useful is recorded such as a kernel oops. > Note3: Your TSSTcorpCD/DVDW TS-L632D optical drive still concerns me. Can > you check & report the present firmware version [AS05, SC03, SC04, something > else?] just to put our minds at ease. > > Thanks again. > > ** Also affects: linux-source-2.6.22 (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: linux-source-2.6.22 (Ubuntu) >Status: New => Incomplete > > ** Also affects: linux-source-2.6.24 (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: linux (Ubuntu) > Sourcepackagename: linux-source-2.6.24 => linux >Status: New => Incomplete > > ** Also affects: linux-source-2.6.17 (Ubuntu) >Importance: Undecided >Status: New > > ** Changed in: linux-source-2.6.17 (Ubuntu) >Status: New => Incomplete > > -- > > > system locking up (forcing a hard reboot) > https://bugs.launchpad.net/bugs/89362 > You received this bug notification because you are a direct subscriber > of the bug. > ** Attachment added: "dmesg_postfreeze.txt" http://launchpadlibrarian.net/14189341/dmesg_postfreeze.txt ** Attachment added: "lspci-vvnn.log" http://launchpadlibrarian.net/14189342/lspci-vvnn.log ** Attachment added: "dmidecode.txt" http://launchpadlibrarian.net/14189343/dmidecode.txt -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
Lau, OK we've checked some likely causes with no success. I think we need to move this issue along to the Kernel Team. However, we need to re-establish the baseline data for this bug report since the problem was originally reported under Feisty and you now appear to be using Hardy. The Kernel Team will need this. Can you supply the following information for your present system [Hardy]: 1. Please include the output of the command "uname -a" in your next response. 2. Please run the command "dmesg > dmesg.log" which includes the freeze point and attach the resulting file "dmesg.log" to this bug report. 3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report. 4. Please run the command "sudo dmidecode > dmidecode.txt" and attach the resulting file "dmidecode.txt" to this bug report. Thanks. Note1: Point (2) above should include the freeze point. If you can get it to freeze again and then reboot the dmesg should contain the freeze point. Note2: Also, after a freeze & reboot can you check syslog and kernel.log to see if anything useful is recorded such as a kernel oops. Note3: Your TSSTcorpCD/DVDW TS-L632D optical drive still concerns me. Can you check & report the present firmware version [AS05, SC03, SC04, something else?] just to put our minds at ease. Thanks again. ** Also affects: linux-source-2.6.22 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-source-2.6.22 (Ubuntu) Status: New => Incomplete ** Also affects: linux-source-2.6.24 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Sourcepackagename: linux-source-2.6.24 => linux Status: New => Incomplete ** Also affects: linux-source-2.6.17 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-source-2.6.17 (Ubuntu) Status: New => Incomplete -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
Re: [Bug 89362] Re: system locking up (forcing a hard reboot)
Gareth, I have finally tried some of the options proposed at http://linux-ata.org/faq.html#combined At the time you sent the email I was not experiencing lockups, but since kernel 2.6.24 in Hardy I have problems every few hours (I suspect 2.6.24 being particularly problematic, as it causes a "kernel NULL reference" Oops on my other machine, but that's the object of a separate bug report). So far I looked at: - BIOS settings: Recommended (where BIOS permits): Change BIOS IDE mode from "legacy" or "combined" mode to "AHCI" (recommended), "RAID" or "native". Nothing indicated on the page is possible with my BIOS - kernel parameters: Boot with the kernel commandline parameter "combined_mode=libata" or "combined_mode=ide" to allow the specified driver to claim all IDE ports. No real effect when applying either of libata or ide. Still locks up :/ Thanks, L. 2008/3/13, Gareth Fitzworthington <[EMAIL PROTECTED]>: > OK. > Yes, if you are able, try the SATA/PATA combination test. Looking through > your dmesg above it appears that you are an ideal candidate as you appear to > have both SATA & PATA and an Intel ICH6 chipset. > > I have suspected for some time that several reporters of this bug type with > the TS-L632D optical drive have been experiencing more than one bug. > Thanks. > > > -- > > system locking up (forcing a hard reboot) > https://bugs.launchpad.net/bugs/89362 > You received this bug notification because you are a direct subscriber > of the bug. > ** Description changed: Binary package hint: linux-image-generic [still happening with 2.6.20-14 although less often than it used to] [up-to-date feisty... the problem was present with edgy as well, which prompted me to upgrade] + + [hardy heron... all hell broke loose since 2.6.24. Freezes are more + frequent than ever.] + + [hardware: Asus F3JC (notebook)] Problems with ata2 seem strongly correlated with system freeze (hard to trace because of the complete freeze). The symptoms are generally: 1- freeze on X 2- if quick enough, I can switch to a console (Ctrl + F*) 3- trying to log on the console prompts error messages like "ata2: speed down requests" "Error sending Cmd #07" "Write error on swap device", etc... The systems never get to log me in 4- trying to access the computer remotely is unsuccessful (the machine does not answer anymore) 5- only a hard reboot is possible /var/log/messages contains the following during normal operations Mar 3 10:30:23 hot-spring kernel: [ 1810.944000] ata2.00: limiting speed to PIO2 Mar 3 10:30:23 hot-spring kernel: [ 1810.944000] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) Mar 3 10:30:30 hot-spring kernel: [ 1817.948000] ata2: port is slow to respond, please be patient (Status 0xd0) Mar 3 10:30:53 hot-spring kernel: [ 1840.964000] ata2: soft resetting port Mar 3 10:30:54 hot-spring kernel: [ 1841.30] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:30:54 hot-spring kernel: [ 1841.30] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.30] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ata2.00: configured for PIO2 Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ata2: EH complete Mar 3 10:32:20 hot-spring kernel: [ 1927.576000] ata2.00: limiting speed to PIO1 Mar 3 10:32:20 hot-spring kernel: [ 1927.576000] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) Mar 3 10:32:27 hot-spring kernel: [ 1934.584000] ata2: port is slow to respond, please be patient (Status 0xd0) Mar 3 10:32:50 hot-spring kernel: [ 1957.60] ata2: soft resetting port Mar 3 10:32:50 hot-spring kernel: [ 1957.944000] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:32:50 hot-spring kernel: [ 1957.944000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:32:50 hot-spring kernel: [ 1957.944000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:32:50 hot-spring kernel: [ 1958.136000] ACPI Error (dsopcode-0481): A
[Bug 89362] Re: system locking up (forcing a hard reboot)
OK. Yes, if you are able, try the SATA/PATA combination test. Looking through your dmesg above it appears that you are an ideal candidate as you appear to have both SATA & PATA and an Intel ICH6 chipset. I have suspected for some time that several reporters of this bug type with the TS-L632D optical drive have been experiencing more than one bug. Thanks. -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
Re: [Bug 89362] Re: system locking up (forcing a hard reboot)
I do have that, and I did cross-flash it some time ago (I have an ASUS notebook, but I took the chance since other did). However, the problem is not completely gone. The frequence of the freezes seems lower to me, but they do happen. (A recent example was during my upgrade from Gutsy to Hardy-alpha6: I had 2 freezes during the process, forcing me to rescue thing manually). Thanks for the hint still, I have not explored the PATA/SATA lead yet. L. 2008/3/13, Gareth Fitzworthington <[EMAIL PROTECTED]>: > Lau above has a TSSTcorpCD/DVDW TS-L632D optical drive. This drive causes > system freezes with some firmware versions. See here for details: > > https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/75295/comments/97 > > Also, another possible cause is the PATA/SATA combination in Intel chipsets > and the way this works with libata. Examine the following link it may provide > your solution. > http://linux-ata.org/faq.html#combined > The slow down as a result of the PATA/SATA combination may be causing at > least some of the above mentioned problems. > This will only affect those with Intel chipsets. > > > -- > system locking up (forcing a hard reboot) > https://bugs.launchpad.net/bugs/89362 > You received this bug notification because you are a direct subscriber > of the bug. > -- -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iEYEARECAAYFAkYgwJ4ACgkQB/w/MLoyRDeQlgCeMp8v69/Wy24Q4IaBVhoG1M5R 2h4AoIOTvKbrFpTklRDjV7u8tEOeSQqt =JPph -END PGP SIGNATURE- -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
Lau above has a TSSTcorpCD/DVDW TS-L632D optical drive. This drive causes system freezes with some firmware versions. See here for details: https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/75295/comments/97 Also, another possible cause is the PATA/SATA combination in Intel chipsets and the way this works with libata. Examine the following link it may provide your solution. http://linux-ata.org/faq.html#combined The slow down as a result of the PATA/SATA combination may be causing at least some of the above mentioned problems. This will only affect those with Intel chipsets. -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 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
[Bug 89362] Re: system locking up (forcing a hard reboot)
Hi all, I'm on a Asus A6km, running Ubuntu 7.04 (installed from scratch) and I think i'm running through the same problem reported above. This is the part of dmesg containing the error: [ 36.257798] snd-usb-audio 3-4:1.2: PM: resume from 1, parent 3-4 still 1 [ 36.257800] snd-usb-audio 3-4:1.2: resuming [ 36.257802] ide-disk 0.0: resuming [ 36.258574] ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index (0) is beyond end of object [20060707] [ 36.258585] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDEC.IDE0._STM] (Node 81001e72d590), AE_AML_PACKAGE_LIMIT [ 36.260548] ide-cdrom 1.0: resuming [ 36.261312] ACPI Exception (exoparg2-0442): AE_AML_PACKAGE_LIMIT, Index (0) is beyond end of object [20060707] [ 36.261322] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDEC.IDE1._STM] (Node 81001e72d450), AE_AML_PACKAGE_LIMIT [ 36.263002] usbdev4.1_ep00: PM: resume from 0, parent usb4 still 2 [ 36.263005] usbdev4.1_ep81: PM: resume from 0, parent 4-0:1.0 still 2 [ 36.263010] usbdev3.2_ep84: PM: resume from 0, parent 3-4:1.2 still 1 [ 36.263013] pcmC1D0c: PM: resume from 0, parent 3-4:1.1 still 1 Uname -a: Linux vger 2.6.20-15-lowlatency #2 SMP PREEMPT Sun Apr 15 06:20:10 UTC 2007 x86_64 GNU/Linux (freeze happens with -generic kernel as well) The problem happens only when resuming from suspend (but it might have happened a couple of times also when resuming from hibernate, i'll pay more attention about it now, and eventually report it) Differently from the others i usually can restart session (CTRL+ALT+BCKSPACE) and enter again without forcing reboot, anyway sometimes forced reboot is needed (couldn't recognize differences in these situations). SIDE NOTES I don't know if this could be related, but i'll put it in. - After resuming from suspend (and sometimes even from hibernate) cpu scaling is not working anymore. CPU Freq is stuck at maximum (1,6 Mhz on my turion 64bit), even with no other tasks going on. - In the situation described above, it happened few times that my system rebooted automatically with no signal and no advice. Something similar to loss of electricity power or overheating of the CPU. If i do not suspend nor hibernate the system seems to work perfectly and run smoothly. -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89362] Re: system locking up (forcing a hard reboot)
** Description changed: Binary package hint: linux-image-generic + + [still happening with 2.6.20-14 although less often than it used to] [up-to-date feisty... the problem was present with edgy as well, which prompted me to upgrade] [hardware: Asus F3JC (notebook)] Problems with ata2 seem strongly correlated with system freeze (hard to trace because of the complete freeze). The symptoms are generally: 1- freeze on X 2- if quick enough, I can switch to a console (Ctrl + F*) 3- trying to log on the console prompts error messages like "ata2: speed down requests" "Error sending Cmd #07" "Write error on swap device", etc... The systems never get to log me in 4- trying to access the computer remotely is unsuccessful (the machine does not answer anymore) 5- only a hard reboot is possible /var/log/messages contains the following during normal operations Mar 3 10:30:23 hot-spring kernel: [ 1810.944000] ata2.00: limiting speed to PIO2 Mar 3 10:30:23 hot-spring kernel: [ 1810.944000] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) Mar 3 10:30:30 hot-spring kernel: [ 1817.948000] ata2: port is slow to respond, please be patient (Status 0xd0) Mar 3 10:30:53 hot-spring kernel: [ 1840.964000] ata2: soft resetting port Mar 3 10:30:54 hot-spring kernel: [ 1841.30] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:30:54 hot-spring kernel: [ 1841.30] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.30] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ata2.00: configured for PIO2 Mar 3 10:30:54 hot-spring kernel: [ 1841.492000] ata2: EH complete Mar 3 10:32:20 hot-spring kernel: [ 1927.576000] ata2.00: limiting speed to PIO1 Mar 3 10:32:20 hot-spring kernel: [ 1927.576000] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) Mar 3 10:32:27 hot-spring kernel: [ 1934.584000] ata2: port is slow to respond, please be patient (Status 0xd0) Mar 3 10:32:50 hot-spring kernel: [ 1957.60] ata2: soft resetting port Mar 3 10:32:50 hot-spring kernel: [ 1957.944000] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:32:50 hot-spring kernel: [ 1957.944000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:32:50 hot-spring kernel: [ 1957.944000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:32:50 hot-spring kernel: [ 1958.136000] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:32:50 hot-spring kernel: [ 1958.136000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:32:50 hot-spring kernel: [ 1958.136000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:32:50 hot-spring kernel: [ 1958.136000] ata2.00: configured for PIO1 Mar 3 10:32:50 hot-spring kernel: [ 1958.136000] ata2: EH complete Mar 3 10:34:52 hot-spring kernel: [ 2079.484000] ata2.00: limiting speed to PIO0 Mar 3 10:34:52 hot-spring kernel: [ 2079.484000] res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) Mar 3 10:34:59 hot-spring kernel: [ 2086.488000] ata2: port is slow to respond, please be patient (Status 0xd0) Mar 3 10:35:22 hot-spring kernel: [ 2109.504000] ata2: soft resetting port Mar 3 10:35:22 hot-spring kernel: [ 2109.848000] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:35:22 hot-spring kernel: [ 2109.848000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.RATA] (Node df994770), AE_AML_OPERAND_VALUE Mar 3 10:35:22 hot-spring kernel: [ 2109.848000] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.IDE0.CHN1.DRV0._GTF] (Node df9948c4), AE_AML_OPERAND_VALUE Mar 3 10:35:22 hot-spring kernel: [ 2110.04] ACPI Error (dsopcode-0481): Attempt to CreateField of length zero [20060707] Mar 3 10:35:22 hot-spring k
Re: [Bug 89362] Re: system locking up (forcing a hard reboot)
Hi Lau, you should definitely mention that in the official bug log! It'll help it to be resolved quicker. Best, Ori On 4/8/07, Lau <[EMAIL PROTECTED]> wrote: > > Well, I did not have any freeze for a week... and I just had one right > after entering my previous post :-/ > (and that was not during a wake-up... it just happened suddenly while > using the machine). > > -- > system locking up (forcing a hard reboot) > https://bugs.launchpad.net/bugs/89362 > You received this bug notification because you are a direct subscriber > of the bug. > -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89362] Re: system locking up (forcing a hard reboot)
Well, I did not have any freeze for a week... and I just had one right after entering my previous post :-/ (and that was not during a wake-up... it just happened suddenly while using the machine). -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89362] Re: system locking up (forcing a hard reboot)
Not for me. I've upgraded to 2.6.20-14-generic SMP and my laptop just had three successive hang-ups, each for thirty seconds as it waits for some ATA function to time out. This is on a clean boot (i.e., not resuming from suspend or hibernation.) I should also note that this is sporadic: I can work a whole day and not have it happen once, or it'll happen every other minute and I'll have to restart. I'm attaching the last 150 lines from my dmesg. ** Attachment added: "dmesg | tail -150 > dmesg2.txt" http://librarian.launchpad.net/7220196/dmesg2.txt -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89362] Re: system locking up (forcing a hard reboot)
The situation has improved much. I had still had sporadic freezes when waking from suspend with 2.6.20-13, but for the moment these appear to have disappeared with 2.6.20-14 (2.6.20-14-generic). -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89362] Re: system locking up (forcing a hard reboot)
Frequent freezes also occur with 2.6.20-13 kernel. I too have had this problem since Edgy (before that I didn't have this computer.) It is incredibly disruptive and frustrating. I don't suspect a hardware problem, since I ran Windows Vista on this machine for a short while and did not have this problem, or any other problem with the drive controllers. ** Attachment added: "dmesg | tail -100" http://librarian.launchpad.net/7134707/dmesg.txt -- system locking up (forcing a hard reboot) https://bugs.launchpad.net/bugs/89362 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89362] Re: system locking up (forcing a hard reboot)
Please try latest 2.6.20-12 kernel. We've had lots of updates to the libata subsystem. ** Changed in: linux-source-2.6.20 (Ubuntu) Assignee: (unassigned) => Ben Collins Status: Unconfirmed => Needs Info -- system locking up (forcing a hard reboot) https://launchpad.net/bugs/89362 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89362] Re: system locking up (forcing a hard reboot)
I think I've got the same problem here, with ata2 as well... What command output must I attach to make an efficient bug repport ? Thanks :) -- system locking up (forcing a hard reboot) https://launchpad.net/bugs/89362 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89362] Re: system locking up (forcing a hard reboot)
Here, it does not appear to recover (at least not after several minutes). I attacht the output of dmesg. ** Attachment added: "output from dmesg" http://librarian.launchpad.net/6608935/dmesg -- system locking up (forcing a hard reboot) https://launchpad.net/bugs/89362 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89362] Re: system locking up (forcing a hard reboot)
I have a similar problem. The system gets slow, then freezes, then recovers. Dmesg can be accessed after the system recovers. Particularly pertinent portions are here: [27865.468000] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen [27865.468000] ata1.00: cmd 35/00:00:a5:f6:2f/00:04:03:00:00/e0 tag 0 cdb 0x0 data 524288 out [27865.468000] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) [27872.468000] ata1: port is slow to respond, please be patient (Status 0xd0) [27895.484000] ata1: port failed to respond (30 secs, Status 0xd0) [27895.484000] ata1: soft resetting port [27895.656000] ata1.00: configured for UDMA/100 [27895.656000] ata1: EH complete [27895.668000] SCSI device sda: 58605120 512-byte hdwr sectors (30006 MB) [27895.672000] sda: Write Protect is off [27895.672000] sda: Mode Sense: 00 3a 00 00 [27895.824000] SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA The full dmesg is attached ** Attachment added: "Dmesg" http://librarian.launchpad.net/6606138/dmesglog -- system locking up (forcing a hard reboot) https://launchpad.net/bugs/89362 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89362] Re: system locking up (forcing a hard reboot)
The trouble seems to be with libata. http://bugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=402751 The absence of logs for the complete freeze points in direction of trouble with the harddisk (and the system unable to cough up what is happening to a log file). -- system locking up (forcing a hard reboot) https://launchpad.net/bugs/89362 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 89362] Re: system locking up (forcing a hard reboot)
** Changed in: linux-meta (Ubuntu) Sourcepackagename: linux-meta => linux-source-2.6.20 -- system locking up (forcing a hard reboot) https://launchpad.net/bugs/89362 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
