http://bugzilla.kernel.org/show_bug.cgi?id=7648
------- Additional Comments From [EMAIL PROTECTED] 2007-02-21 04:08 ------- More messages, this time at 1.6 GHz and 82 C temp. ACPI: EC: acpi_ec_wait timeout, status = 32, expect_event = 1 ACPI: EC: read timeout, command = 128 ACPI Exception (evregion-0424): AE_TIME, Returned by Handler for [EmbeddedControl] [20060707] ACPI Exception (dswexec-0458): AE_TIME, While resolving operands for [OpcodeName unavailable] [20060707] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.RWRD] (Node dfecdc84), AE_TIME ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.BAT0.BIF1] (Node dfeca324), AE_TIME ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.BAT0._BIF] (Node dfeca400), AE_TIME ACPI Exception (acpi_battery-0148): AE_TIME, Evaluating _BIF [20060707] ACPI: EC: acpi_ec_wait timeout, status = 0, expect_event = 1 ACPI: EC: read timeout, command = 128 ACPI Exception (evregion-0424): AE_TIME, Returned by Handler for [EmbeddedControl] [20060707] ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.PCI0.SBRG.EC0_.BATS] (Node dfecdf18), AE_TIME ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.BAT0._BST] (Node dfeca3d8), AE_TIME ACPI Exception (acpi_battery-0207): AE_TIME, Evaluating _BST [20060707] By now, despite these errors the system keeps up on running... but maybe it's just luck :) I've seen new messages I'm not sure if they're related to the ACPI: PM: Writing back config space on device 0000:02:00.0 at offset b (was 3ed173b, writing 17351043) PM: Writing back config space on device 0000:02:00.0 at offset 3 (was 0, writing 4010) PM: Writing back config space on device 0000:02:00.0 at offset 2 (was 2000000, writing 2000003) PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 2b00000, writing 2b00106) PM: Writing back config space on device 0000:02:00.0 at offset 0 (was 3ed173b, writing 169c14e4) bridge-eth1: disabling the bridge bridge-eth1: down PM: Writing back config space on device 0000:02:00.0 at offset b (was 3ed173b, writing 17351043) PM: Writing back config space on device 0000:02:00.0 at offset 3 (was 0, writing 4010) PM: Writing back config space on device 0000:02:00.0 at offset 2 (was 2000000, writing 2000003) PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 2b00000, writing 2b00106) PM: Writing back config space on device 0000:02:00.0 at offset 0 (was 3ed173b, writing 169c14e4) Thanks again!! :) I hope this to be useful to solve the problem with ACPI. Is it worth to try with 2.6.21-rc1? I mean, are there worthy changes on ACPI in that version? New observation: each time this error occurs I loose my network config, exactly resolv.conf config (which is alocated under /dev/shm/resolvconf. Could these errors be doing something with /dev/shm or is it just casualness? ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
