git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: 2.6.21-rc1: known regressions (part 2)

From
IMIngo Molnar <mingo@elte.hu>
Date
Mar 5, 2007, 16:41 UTC
Message-ID
<20070305164133.GA2441@elte.hu>
In-Reply-To
<20070305161450.GA4972@mellanox.co.il>
* Michael S. Tsirkin <mst@mellanox.co.il> wrote:
Show 6 quoted lines
> > Quoting Ingo Molnar <mingo@elte.hu>:
> >  git-bisect good      0539771d7236b425f285652f6f297cc7939c8f9a
> > 
> >  81450b73dde07f473a4a7208b209b4c8b7251d90 is first bad commit
> 
> I have confirmed these two on my system.

you could probably get quite a bit further in bisecting the other breakage, by using the following method:

manully apply the patch below to 81450b73dde and retest. It will most likely work. Then FIRST unapply the patch and mark the tree via 'git-bisect good' and continue the bisection. Then try to apply the patch again. If it's already included - ignore the rejected patch. Whenever git-bisect offers you a new commit, just try to apply the patch. Ok? This way you'll be able to avoid the known ACPI breakage, and zoom in on the unknown breakage.

	Ingo
---------------->
commit f3ccb06f3b8e0cf42b579db21f3ca7f17fcc3f38
Author: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
Date:   Tue Feb 13 02:35:50 2007 -0500
    ACPI: Disable wake GPEs only once.
    
    fixes Suspend/Resume regressions due to recent ACPICA update.
    
    Signed-off-by: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
    Signed-off-by: Len Brown <len.brown@intel.com>
diff --git a/drivers/acpi/events/evgpe.c b/drivers/acpi/events/evgpe.c
index dfac3ec..635ba44 100644
--- a/drivers/acpi/events/evgpe.c
+++ b/drivers/acpi/events/evgpe.c
@@ -636,17 +636,6 @@ acpi_ev_gpe_dispatch(struct acpi_gpe_event_info *gpe_event_info, u32 gpe_number)
 		}
 	}
 
-	if (!acpi_gbl_system_awake_and_running) {
-		/*
-		 * We just woke up because of a wake GPE. Disable any further GPEs
-		 * until we are fully up and running (Only wake GPEs should be enabled
-		 * at this time, but we just brute-force disable them all.)
-		 * 1) We must disable this particular wake GPE so it won't fire again
-		 * 2) We want to disable all wake GPEs, since we are now awake
-		 */
-		(void)acpi_hw_disable_all_gpes();
-	}
-
 	/*
 	 * Dispatch the GPE to either an installed handler, or the control method
 	 * associated with this GPE (_Lxx or _Exx). If a handler exists, we invoke
Previous: Michael S. TsirkinNext: Jens Axboe
Message 15 of 16 in “Re: 2.6.21-rc1: known regressions (part 2)”
  1. Ingo MolnarMar 2, 2007
  2. Ingo MolnarMar 2, 2007
  3. KVM: T60 resume fixIngo Molnar, Mar 2, 2007
  4. Michael S. TsirkinMar 2, 2007
  5. Avi KivityMar 3, 2007
  6. Avi KivityMar 3, 2007
  7. Andrew MortonMar 3, 2007
  8. Ingo MolnarMar 5, 2007
  9. Michael S. TsirkinMar 5, 2007
  10. Ingo MolnarMar 5, 2007
  11. Linus TorvaldsMar 2, 2007
  12. Ingo MolnarMar 5, 2007
  13. Michael S. TsirkinMar 5, 2007
  14. Michael S. TsirkinMar 5, 2007
  15. Ingo MolnarMar 5, 2007
  16. Jens AxboeMar 5, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.