Mailinglist Archive: opensuse-bugs (5372 mails)
| < Previous | Next > |
[Bug 259992] kernel acpi read wrong temperature - critical shutdown
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Tue, 5 Jun 2007 08:49:56 -0600 (MDT)
- Message-id: <20070605144956.B9344110F@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=259992
trenn@xxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |astarikovskiy@xxxxxxxxxx
------- Comment #36 from trenn@xxxxxxxxxx 2007-06-05 08:49 MST -------
No next patch, it's just the same but does not do the _soft and further drivers
trying to request such a resource will fail.
Here some dmesg output of patch from comment #35, the conflicts show specific
IO regions that get used for sure, parsed from fadt and also declared as
SYSTEM_IO operating region:
IO resource region conflicts with IO ACPI PM1a_EVT_BLK regions, conflict is
ignored, system might run unstable.
IO resource region conflicts with IO ACPI PM1a_CNT_BLK regions, conflict is
ignored, system might run unstable.
IO resource region conflicts with IO ACPI PM_TMR regions, conflict is ignored,
system might run unstable.
IO resource region conflicts with IO ACPI GPE0_BLK regions, conflict is
ignored, system might run unstable.
IO resource region conflicts with IO ACPI GPE1_BLK regions, conflict is
ignored, system might run unstable.
This needs some more fiddling (should just be an example patch I like to send
to ACPI/hwmon list if you think it's worth it), but could be a beginning to get
a picture which drivers might conflict with ACPI?
When cleaned up there should a message be print when it87 is trying to be
loaded:
IO resource region conflicts with acpi IO region [0x295-0x296], conflict is
ignored, system might run unstable.
If it comes out that no important drivers are affected, we could let the
drivers fail to load.
Jean, I grepped over my DSDTs, here is a list of common SystemIO addresses
used/claimed by DSDTs: /suse/trenn/Export/SystemIO.txt
Any comments welcome...
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
trenn@xxxxxxxxxx changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |astarikovskiy@xxxxxxxxxx
------- Comment #36 from trenn@xxxxxxxxxx 2007-06-05 08:49 MST -------
No next patch, it's just the same but does not do the _soft and further drivers
trying to request such a resource will fail.
Here some dmesg output of patch from comment #35, the conflicts show specific
IO regions that get used for sure, parsed from fadt and also declared as
SYSTEM_IO operating region:
IO resource region conflicts with IO ACPI PM1a_EVT_BLK regions, conflict is
ignored, system might run unstable.
IO resource region conflicts with IO ACPI PM1a_CNT_BLK regions, conflict is
ignored, system might run unstable.
IO resource region conflicts with IO ACPI PM_TMR regions, conflict is ignored,
system might run unstable.
IO resource region conflicts with IO ACPI GPE0_BLK regions, conflict is
ignored, system might run unstable.
IO resource region conflicts with IO ACPI GPE1_BLK regions, conflict is
ignored, system might run unstable.
This needs some more fiddling (should just be an example patch I like to send
to ACPI/hwmon list if you think it's worth it), but could be a beginning to get
a picture which drivers might conflict with ACPI?
When cleaned up there should a message be print when it87 is trying to be
loaded:
IO resource region conflicts with acpi IO region [0x295-0x296], conflict is
ignored, system might run unstable.
If it comes out that no important drivers are affected, we could let the
drivers fail to load.
Jean, I grepped over my DSDTs, here is a list of common SystemIO addresses
used/claimed by DSDTs: /suse/trenn/Export/SystemIO.txt
Any comments welcome...
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
| < Previous | Next > |