https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #1 from shanti@mojo.cc 2007-04-03 05:50 MST ------- Created an attachment (id=128495) --> (https://bugzilla.novell.com/attachment.cgi?id=128495&action=view) detailed systeminfo some more sysinfo -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 shanti@mojo.cc changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |shanti@mojo.cc ------- Comment #2 from shanti@mojo.cc 2007-04-07 12:09 MST ------- interesting maybe: my Bios show an additional fan sensor for the cpu-cooling device , but the linux-module (rs480-mainboard) doesnt show this "fan3" value , with is the integrated smartfan of the CPU ( normally about 800-900 rpms as shown in BIOS ) .. this could be the missing "cooling device" that is not reachable .. must be a missing feature of the RS480-mainboard driver just FYI best regards -c- -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cadaha@novell.com, pavel@novell.com Status|NEW |ASSIGNED ------- Comment #5 from trenn@novell.com 2007-05-03 02:42 MST ------- Yep, the temp looks bogus. It may be that something interferes with ACPI causing this.

i think that the i2c_ali15x3,i2c_ali1535-modules are buggy .. they at least miss on active fan. At least this shows that the driver is incomplete .. Those could likely interfere with ACPI, better don't use them. There were some patches to unhide smbus to use it with such legacy modules, which might conflict with ACPI.

but the linux-module (rs480-mainboard) What's that? I can't find this module?

I'd like to close this one invalid if without above modules this does not happen any more. Some more questions: How often does/did it happen? frequently? These modules do not load automatically? What is the machine's vendor/model name? Adding Pavel and Daniel, they might be interested in this. Daniel already had a fix with this smbus (un)hiding, any ideas/comments? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #7 from shanti@mojo.cc 2007-05-03 06:56 MST ------- i blacklisted the modules for now (i2c_ali15x3,i2c_ali1535) , hope it will bring some improvement .. yet

...

but the linux-module (rs480-mainboard) What's that? I can't find this module?

i meant the regarding ali*-modules, since they fir for this mainboard .. my hardware is a shuttle st20g5 (IPX-Board) http://global.shuttle.com/Product/Barebone/ST20G5.asp the specs tell its a ULi 1573 mainboard and yes indeed it happens frequently ( once a week ) .. after rebooting and going straight for the PC-HEalth in the bios , the temperatures are quite ok ( under 50°C ) .. i got the latest available bios-version for this board please gimme 2 weeks testing period before closing this ticket :-/ tnx -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #9 from shanti@mojo.cc 2007-05-09 05:22 MST -------

I'd like to close this one invalid if without above modules this does not happen any more.

hmmm .. i would not, because after latest Kernel-update-RPM from Suse , these modules are back in play .. and no more blacklisted .. so i suggest that Modules that are so unclearly incomplete shouldnt find their way into standard configuration after beeing blacklisted before .. i will open a new bug for this , because its a little offtopic anyway since latest kernel-patch i was happily found running my computer for 24hours (!!!!) without crashing or shoutting down .. but gimme one more week for testing :-) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #11 from shanti@mojo.cc 2007-05-09 05:58 MST ------- i now blacklist : blacklist it87 blacklist i2c_ali15x3 blacklist i2c_ali1535 should i blacklist i2c_isa and i2c_core as well ? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #13 from shanti@mojo.cc 2007-05-09 09:53 MST ------- well i think that this message points out a blind spot in the driver . i may be wrong: <4>ali1535_smbus 0000:00:1e.1: ALI1535_smb region uninitialized - upgrade BIOS? <4>ali1535_smbus 0000:00:1e.1: ALI1535 not detected, module not inserted. <3>ali15x3_smbus 0000:00:1e.1: ALI15X3_smb region uninitialized - upgrade BIOS or use force_addr=0xaddr <3>ali15x3_smbus 0000:00:1e.1: ALI15X3 not detected, module not inserted. maybe on top of this missing part in the driver its not working as it should regards -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jdelvare@novell.com Status|ASSIGNED |NEEDINFO Info Provider| |shanti@mojo.cc ------- Comment #15 from trenn@novell.com 2007-05-29 06:23 MST ------- Yes, looks scary, but could be harmless, if e.g. BIOS exports trip point table(s), but the fans are still handled by BIOS. I more expect wrong/weird EC values (110 C and 80 C values should be simply wrongly reported), than real fan failure. You may want to monitor this a bit: watch -n1 cat /proc/acpi/fan/*/* /proc/acpi/thermal_zone/*/{temperature,trip_points} (Also use your ears for monitoring :), if fan control is done by BIOS, you can at least guess from temperature and fan activity if things seem to work normal). To increase temp, you can e.g. do: "cat /dev/zero >/dev/null &" (this should keep one core busy and let increase temperature or fan activity fast. Do you still get the critical shutdowns with the smbus accessing module disabled? You should also be able to trigger this bug more often if you set THERMAL_POLLING_FREQUENCY="1" in /etc/powersave/thermal and /etc/sysconfig/powersave/thermal and restart powersaved (rcpowersaved restart). You should then be able to verify the critical shutdown more easily (only if the smbus module is loaded?). Jean Delvare has some ideas about getting legacy sensor modules and ACPI working together -> adding to CC. Christoph: If you don't see critical shutdowns anymore without legacy smbus modules, I'd like to close this one (hmm, it's worth to still make sure not loading them per default for 10.2, maybe Daniel or Jean could give me a hint how to do that, the modules should also taint the kernel IMO). Christoph: It would also be very interesting to see how this machine behaves with latest 10.3 Alpha (it's the 4th AFAIK). If you still have a free partition on your machine, it would be great to give it a test. Now we still can fix things, as soon as 10.3 is released it's getting difficult. Christoph: Could you also attach acpidump output please. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #17 from shanti@mojo.cc 2007-05-29 07:24 MST ------- cat /proc/acpi/fan/FAN/state status: on cat /proc/acpi/thermal_zone/THRM/temperature temperature: 46 C cat /proc/acpi/thermal_zone/THRM/trip_points critical (S5): 60 C passive: 50 C: tc1=4 tc2=3 tsp=60 devices=0xffff810037fe72b0 active[0]: 50 C: devices=0xffff810037fde290 this fan is the CPU which is set to "SmartFan" in BIOS .. i also have ksensors running. Since i cannot monitore northbridge/Systemfan anymore (nomore it87 and related) this is not optimal i know when this shutdown occured there was definitly NO problem with temperature at all , silent smooth and cool my system is. ATM i am running `cat /dev/zero >/dev/null` on both core (AMDx2) generating full utilaziation on the CPUs for 15 minutes and my /proc/acpi/thermal_zone/THRM/temperature doesnt even raise more than 2° , even fan is still working rather silently. My point was only if there shouldnt be a workaround in the kernel or the module or the powerwatch to concern the mistaken panic and at least wait for next result ( like a UPS would care about powerfailure ) .. as you see , this result are meaningless after the next poll ( after a few seconds ) .. now i will change to modprobed it87 and lett you know again :-) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #19 from shanti@mojo.cc 2007-05-29 07:58 MST ------- /etc/sysconfig/lm_sensors suggest me also that it might not be an issue width the it87 alone or neither .. MODULE_0=k8temp #<- :-( ?? MODULE_1=it87 shanti@zion:~> lsmod |grep k8 powernow_k8 32416 1 freq_table 22912 1 powernow_k8 processor 53864 2 powernow_k8,thermal shanti@zion:~> lsmod |grep i2 i2c_ali15x3 25348 0 i2c_isa 23040 1 it87 i2c_core 41472 3 i2c_ali15x3,it87,i2c_isa i remember from some gentoo-forums in 2005 ( when i started with this PC ) that that time there hab been issues with powernow_k8 and AMD64/SMP CPUs, but after fixing this ( came in kernelupdates ) there was no more thought on this this shutdown issue also first touched me with OPENSUSE10.2 .. never had some of this in my life ( even in custom-kernels ) since RPM says "file /etc/sysconfig/lm_sensors is not owned by any package" i will comment those lines, bring back it87 and proceed :-) PS: kernel: ali15x3_smbus 0000:00:1e.1: ALI15X3 not detected, module not inserte d. so i guess i should use ali1563 instead , albeit my hardware is a 00:1e.1 Bridge: ALi Corporation M7101 Power Management Controller [PMU] ??? tnx4support -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #21 from jdelvare@novell.com 2007-05-29 09:41 MST ------- I disassembled the DSDT and took a look. I am no ACPI expert but it is clear that ACPI is accessing a device at 0x295-0x296, which is the default address of the IT87xxF hardware monitoring function. This confirms that you should be using either thermal+fan, or it87, but not both. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #23 from jdelvare@novell.com 2007-05-30 02:51 MST ------- (In reply to comment #22)

Jean, IMO we have to set sensor modules to unsupported and must somehow make sure they get not loaded (for ACPI archs), but still let people a chance to load them manually. How are those modules loaded?

The hardware monitoring drivers are already all unsupported.

Can you come up with a list of modules that access smbus/i2c bus and could interfere with ACPI, pls.

Virtually all of them can. Note that the it87 driver doesn't even touch smbus/i2c in this case. So the list you want is all smbus/i2c master drivers _and_ all non-i2c-based hardware monitoring drivers, limited to devices which can be found on ACPI-enabled systems: i2c-ali1535 i2c-ali1563 i2c-ali15x3 i2c-amd756 i2c-amd756-s4882 i2c-amd8111 i2c-i801 i2c-nforce2 i2c-piix4 i2c-sis5595 i2c-sis630 i2c-sis96x i2c-viapro abituguru f71805f hdaps it87 k8temp pc87360 pc87427 sis5595 smsc47b397 smsc47m1 via686a vt1211 vt8231 w83627ehf w83627hf That's a pretty long list, isn't it? Note: of these, the smsc47m1, vt8231 and via686a are probably less risky than the others because their access is stateless. So even if ACPI is accessing these devices, the drivers shouldn't get in the way. Shouldn't...

How does the modules get loaded? I can't find any autoloading in kernel (quick look, I might have overseen something), does this work that you run some userspace hwmon-test app, that one writes /etc/sysconfig/lm_sensors with suggestions which modules to load via /etc/init.d/hwmon (re-)start?

The only hardware monitoring modules which autload are k8temp, sis5595, via686a and vt8231, because they are PCI devices. All SMBus master drivers listed above autoload too, again because they are PCI devices. For the other hardware monitoring drivers, they are loaded by /etc/rc.d/lm_sensors based on the list found in /etc/sysconfig/lm_sensors. This configuration file is generated by /usr/sbin/sensors-detect. One thing that could be done would be to add an ACPI check in sensors-detect, so that we can warn the user that a conflict could happen. However, only checking for the presence of ACPI would result in many false positives. So ideally we would need a way to determine if a given DSDT contains functions which access the I/O ports of the devices detected by sensors-detect. But I guess this would be pretty hard to automatize. Another (hopefully temporary) approach is to add DMI-based blacklists to individual SMBus and hardware monitoring drivers. If the list of motherboards with a conflict is small enough, it might work. If not, it might become quickly unmaintainable :(

Jean, I did a quick check of the DSDT, this machine is hopeless to run ACPI and it87 module.

I agree.

This functions all access the device: - SFAN, FON, FOFF, RTMP, STHY, STOS, SCFG

Are these functions called if neither the "fan" nor "thermal" drivers are loaded? My guess is that Christoph would rather use the it87 driver than the less featured ACPI drivers.

It also looks like the it87 addresses seem not to be used by default, but I would not trust this assumption.

I don't understand what you mean here. Can you please explain?

Next thing is, that the above functions are all in _SI scope, but are not assigned to a specific ACPI device. That means writting an ACPI driver for it87 could get difficult and all this looks very machine/BIOS/vendor specific... (on the other hands side I am sure I already have seen the SFAN method, looks like one need a acer-acpi module including this or it could be added to asus-acpi or whatever machine this is, what kind of machine/model is this?)

Please remember I am no ACPI expert. What is the "_SI scope"?

IMO it87 module must vanish anyway (or must not get loaded for ACPI machines) and we need something ACPI (probably also BIOS/vendor/model) specific.

ACPI was supposed to be a standard, and now I seem to understand that we would need to write a dedicated driver for every motherboard vendor, or maybe even every motherboard model out there? *sigh* The it87 driver is supporting the ITE IT87xxF/FG chips on _all_ motherboard models. But sure, just do it. The problem right now is that the ACPI people keep complaining that non-ACPI hardware monitoring drivers are causing trouble, but users keep using them because ACPI doesn't offer anything next to what lm-sensors has been providing for years. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #25 from jdelvare@novell.com 2007-05-30 04:13 MST ------- Stefan, please attach your acpidump. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 jsj@jsj.dyndns.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jsj@jsj.dyndns.org | ------- Comment #26 from jsj@jsj.dyndns.org 2007-05-30 11:31 MST ------- Created an attachment (id=142976) --> (https://bugzilla.novell.com/attachment.cgi?id=142976&action=view) acpidump of MSI MegaPC 865 barebone Here you are... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #27 from jdelvare@novell.com 2007-05-31 04:05 MST ------- Stefan, I checked your DSDT table and it seems that your ACPI implementation includes a fairly complete fan speed control mechanism. It is setting the fan speed using the SMSC LPC47M1xx PWM outputs based on the temperatures readings from a chip on the SMBus at address 0x2d. This can't possibly be an LM90-compatible chip, as these live at 0x4c or 0x4d. You must have a 3rd hardware monitoring driver which you didn't list. Could be smsc47m192 (which is NOT the same as smsc47m1)? Or some LM85-compatible device. Anyway, I double-checked the smsc47m1 driver, the device has a flat I/O space and the driver doesn't even write to it by default so I just can't see how it would interact with ACPI, especially not with temperatures as the smsc47m1 driver only deals with fans. There could be some unexpected interaction if you tried to control the fan by yourself (using fancontrol), but no invalid temperature reads as you have been seeing. Given the ACPI implementation your system has, I recommend that you do not load non-ACPI hardware monitoring drivers nor SMBus master drivers. The ACPI stuff should work just fine for you. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 trenn@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |jdelvare@novell.com ------- Comment #29 from trenn@novell.com 2007-05-31 04:29 MST ------- Back to the bug, are there any offending modules loaded automatically now? Do we need to do something? I'd like to close or rename this one (enhancement -> implement hwmon acpi drivers :) ). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 jdelvare@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|jdelvare@novell.com | ------- Comment #31 from jdelvare@novell.com 2007-05-31 06:25 MST ------- (In reply to comment #29)

Back to the bug, are there any offending modules loaded automatically now? Do we need to do something?

I already listed the potentially offending drivers which autoload, see comment #23. Basically these are all the pci drivers in the list. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #33 from jdelvare@novell.com 2007-05-31 08:08 MST ------- (In reply to comment #32)

With the update to 2.6.18.8-0.3 some modules have been loaded automatically. I did not load any monitoring modules before. With 0.1-kernel the diff of loaded modules was: i2c_isa lm90 hwmon smsc47m1

I am fairly certain this isn't true. There is no way these modules could be loaded automatically, because these hardware monitoring devices cannot be easily detected. Please check your /etc/sysconfig/lm_sensors file. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #35 from trenn@novell.com 2007-06-05 08:22 MST ------- Created an attachment (id=144232) --> (https://bugzilla.novell.com/attachment.cgi?id=144232&action=view) Request IO and mem resources for ACPI operation regions This patch requests IO and mem resources for ACPI operation regions. Unfortunately it still clashes with some of it's own resources (see line 5000). 002e-002f : acpi* 0072-0073 : acpi* 0090-0091 : acpi* 0295-0296 : acpi* 5000-50fe : acpi* 5000-5003 : ACPI PM1a_EVT_BLK 5004-5005 : ACPI PM1a_CNT_BLK 5008-500b : ACPI PM_TMR 5010-5015 : ACPI CPU throttle 5020-5023 : ACPI GPE0_BLK 50b0-50b7 : ACPI GPE1_BLK adalid:~ # cat /proc/iomem |grep -i acpi Purpose of this patch is to still allow other drivers to request the io/mem resources and only throw a kern_err if a driver's done so. Like that we could get a picture which Operation Regions DSDT are generally using and which machines possibly might have potential problems with it. At some later time the request_resource_soft might fall away again if possible (see next patch). Then the only way to access the regions is via ACPI. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 astarikovskiy@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #144232|0 |1 is obsolete| | ------- Comment #37 from astarikovskiy@novell.com 2007-06-06 14:31 MST ------- Created an attachment (id=144583) --> (https://bugzilla.novell.com/attachment.cgi?id=144583&action=view) Set correct name of the resource Thomas, I think it's convenient to know the name of the resource, not just acpi*. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 info@tristanhoffmann.de changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |info@tristanhoffmann.de ------- Comment #39 from info@tristanhoffmann.de 2007-06-07 13:38 MST ------- Hi, I just want to add that I also have this problem since OpenSUSE 10.2 on a HP nx6125 laptop. I now have openSUSE 10.3 Alpha 3 and it still occurs. but I've never loaded hardware monitoring modules manually. /var/log/messages: Jun 7 20:14:04 turion-laptop kernel: ACPI: Critical trip point Jun 7 20:14:04 turion-laptop kernel: Critical temperature reached (7168 C), shutting down. Jun 7 20:14:05 turion-laptop shutdown[5639]: shutting down for system halt Jun 7 20:14:05 turion-laptop init: Switching to runlevel: 0 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #41 from jdelvare@novell.com 2007-06-08 04:56 MST ------- (In reply to comment #40)

Do you have anything in /etc/sysconfig/lm_sensors? Do you see problems if you remove all sensors out of this file and re-start hwmon?

That's not the right order. You must first stop hwmon ("/etc/rc.d/lm_sensors stop"), and then delete /etc/sysconfig/lm_sensors, otherwise the hwmon drivers will not be removed. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 info@tristanhoffmann.de changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|info@tristanhoffmann.de | ------- Comment #43 from info@tristanhoffmann.de 2007-06-08 05:51 MST ------- sorry, I wanted to write "lm_sensors" -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #45 from info@tristanhoffmann.de 2007-06-08 08:06 MST ------- Do you really think this is a different bug? Maybe it's just not lm_sensors causing this? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #47 from shanti@mojo.cc 2007-06-10 11:19 MST ------- here again: #dmesg |grep ACPI there are some quirks and an invalid value for PBLK within: BIOS-e820: 0000000077ef0000 - 0000000077ef3000 (ACPI NVS) BIOS-e820: 0000000077ef3000 - 0000000077f00000 (ACPI data) ACPI: RSDP (v000 XPC ) @ 0x00000000000f7e50 ACPI: RSDT (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0000000077ef3040 ACPI: FADT (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0000000077ef30c0 ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @ 0x0000000077ef74c0 ACPI: HPET (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000098) @ 0x0000000077ef76c0 ACPI: MCFG (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0000000077ef7740 ACPI: MADT (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x0000000077ef7400 ACPI: DSDT (v001 XPC ST20V10 0x00001000 MSFT 0x0100000e) @ 0x0000000000000000 ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. ACPI: HPET id: 0x10b9a201 base: 0xfed00000 Using ACPI (MADT) for SMP configuration information ACPI: Core revision 20060707 ACPI: bus type pci registered ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 PCI quirk: region 4000-403f claimed by ali7101 ACPI ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2PB._PRT] ACPI: PCI Interrupt Link [LNK1] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK2] (IRQs 1 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNK3] (IRQs 1 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNK4] (IRQs 1 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNK5] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK6] (IRQs 1 3 4 5 6 *7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNK7] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK8] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *9 ACPI: PCI Interrupt Link [LNK9] (IRQs 1 *3 4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT] PCI: Using ACPI for IRQ routing ACPI: (supports S0 S1 S4 S5) ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 19 (level, low) -> IRQ 185 ACPI: Fan [FAN] (on) ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 23 (level, low) -> IRQ 193 ACPI: PCI Interrupt 0000:00:1f.0[A] -> GSI 19 (level, low) -> IRQ 185 ACPI: PCI Interrupt 0000:00:1d.0[C] -> GSI 21 (level, low) -> IRQ 201 ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 18 (level, low) -> IRQ 209 ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 18 (level, low) -> IRQ 209 ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 209 ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 209 ACPI: PCI Interrupt 0000:03:16.0[A] -> GSI 18 (level, low) -> IRQ 209 ACPI: PCI Interrupt 0000:03:15.0[A] -> GSI 17 (level, low) -> IRQ 217 ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] ACPI: Invalid PBLK length [7] ACPI: Unable to turn cooling device [ffff810037fde290] 'on' ACPI: Thermal Zone [THRM] (50 C) ACPI: Unable to turn cooling device [ffff810037fde290] 'on' ACPI: Unable to turn cooling device [ffff810037fde290] 'on' ACPI: Unable to turn cooling device [ffff810037fde290] 'on' ACPI: Unable to turn cooling device [ffff810037fde290] 'on' ACPI: Unable to turn cooling device [ffff810037fde290] 'on' ACPI: Unable to turn cooling device [ffff810037fde290] 'on' ACPI: Unable to turn cooling device [ffff810037fde290] 'on' ACPI: Unable to turn cooling device [ffff810037fde290] 'on' ACPI: Unable to turn cooling device [ffff810037fde290] 'on' ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 17 (level, low) -> IRQ 217 ACPI: Unable to turn cooling device [ffff810037fde290] 'on' -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992 ------- Comment #49 from info@tristanhoffmann.de 2007-06-11 06:07 MST ------- Thanks, I will try the new kernel with openSUSE Alpha 5 when it's released. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c51 --- Comment #51 from Christoph Resch 2007-08-17 15:25:56 MST --- i havent had those nasty shutdown for a month or more now ... i switch to x86-arch last week .. still i have those debug in messages: Aug 17 02:13:12 zion kernel: ACPI: Unable to turn cooling device [dffecd88] 'on' and lots of them , but not all the time :-o my actual acpiout: shanti@zion:~> dmesg |grep ACPI BIOS-e820: 0000000077ef0000 - 0000000077ef3000 (ACPI NVS) BIOS-e820: 0000000077ef3000 - 0000000077f00000 (ACPI data) ACPI: RSDP (v000 XPC ) @ 0x000f7e50 ACPI: RSDT (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x77ef3040 ACPI: FADT (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x77ef30c0 ACPI: SSDT (v001 PTLTD POWERNOW 0x00000001 LTP 0x00000001) @ 0x77ef74c0 ACPI: HPET (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000098) @ 0x77ef76c0 ACPI: MCFG (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x77ef7740 ACPI: MADT (v001 XPC AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x77ef7400 ACPI: DSDT (v001 XPC ST20V10 0x00001000 MSFT 0x0100000e) @ 0x00000000 ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee00000 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. ACPI: HPET id: 0x10b9a201 base: 0xfed00000 Using ACPI (MADT) for SMP configuration information ACPI: Core revision 20060707 ACPI: bus type pci registered ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (0000:00) ACPI: Assume root bridge [\_SB_.PCI0] bus is 0 PCI quirk: region 4000-403f claimed by ali7101 ACPI ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P2PB._PRT] ACPI: PCI Interrupt Link [LNK1] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK2] (IRQs 1 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNK3] (IRQs 1 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNK4] (IRQs 1 3 4 5 6 7 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNK5] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK6] (IRQs 1 3 4 5 6 *7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNK7] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNK8] (IRQs 1 3 4 5 6 7 10 11 12 14 15) *9 ACPI: PCI Interrupt Link [LNK9] (IRQs 1 *3 4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT] pnp: PnP ACPI init pnp: PnP ACPI: found 11 devices PnPBIOS: Disabled by ACPI PNP PCI: Using ACPI for IRQ routing ACPI: (supports S0 S1 S4 S5) ACPI: Invalid PBLK length [7] ACPI: Thermal Zone [THRM] (46 C) ACPI: PCI Interrupt 0000:00:1f.0[A] -> GSI 19 (level, low) -> IRQ 185 ACPI: PCI Interrupt 0000:00:1f.1[A] -> GSI 19 (level, low) -> IRQ 185 ACPI: PCI Interrupt 0000:03:16.0[A] -> GSI 18 (level, low) -> IRQ 193 ACPI: Fan [FAN] (on) ACPI: PCI Interrupt 0000:00:1d.0[C] -> GSI 21 (level, low) -> IRQ 201 ACPI: PCI Interrupt 0000:00:1c.0[A] -> GSI 18 (level, low) -> IRQ 193 ACPI: PCI Interrupt 0000:00:1c.1[B] -> GSI 18 (level, low) -> IRQ 193 ACPI: PCI Interrupt 0000:00:1c.2[C] -> GSI 18 (level, low) -> IRQ 193 ACPI: PCI Interrupt 0000:00:1c.3[D] -> GSI 23 (level, low) -> IRQ 209 ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 18 (level, low) -> IRQ 193 ACPI: PCI Interrupt 0000:03:15.0[A] -> GSI 17 (level, low) -> IRQ 217 ACPI: Power Button (FF) [PWRF] ACPI: Power Button (CM) [PWRB] ACPI: PCI Interrupt 0000:01:05.0[A] -> GSI 17 (level, low) -> IRQ 217 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c53 --- Comment #53 from Christoph Resch 2007-08-22 14:26:44 MST --- not at all ;-( happened again today meanwhile my hole architecture changed to x86 and since long time never had this before of course my opensuse is at latest patch Aug 22 21:48:47 zion kernel: ACPI: Critical trip point Aug 22 21:48:47 zion kernel: Critical temperature reached (65 C), shutting down. Aug 22 21:48:47 zion shutdown[7106]: shutting down for system halt Aug 22 21:48:47 zion powersaved[3587]: WARNING (checkTemperatureStateChanges:218) Temperature state changed to critical. Aug 22 21:48:47 zion init: Switching to runlevel: 0 Aug 22 21:48:49 zion kernel: Critical temperature reached (47 C), shutting down. again my point is to change code to give ACPI a second try after few seconds .. as you can see this is pure panic on a bogus x-o , but the system is responding unappropiate. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c55 --- Comment #55 from Christoph Resch 2007-08-22 15:19:10 MST --- Created an attachment (id=159317) --> (https://bugzilla.novell.com/attachment.cgi?id=159317) update: changed from x86_64 to pure x86 update: changed from x86_64 to pure x86 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c57 --- Comment #57 from Pavel Machek 2007-08-24 01:51:42 MST --- No, I do not think we want to break our thermal handling by adding "hmm lets try again" because single broken system. Can you confirm that you are not running lm_sensors any more? Len Brown has "lets make acpi thermal work as well as it does in window" goal, perhaps you should report it to bugzilla.kernel.org and see what happens? You may also be able to unload thermal module and/or tweak some bios settings. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c59 --- Comment #59 from Jean Delvare 2007-10-16 11:48:13 MST --- Christoph, see comment #21. Do not use the it87 driver on this machine, it interacts with ACPI in an unpredictable way. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c61 --- Comment #61 from Jean Delvare 2007-10-16 12:50:07 MST --- Please read comment #18 again. Using force_addr won't help you. Why can't you "rmmod thermal"? It works for me. I'm not saying that it's a great idea though, as this also means that you lose the automatic thermal regulation that might be implemented by your BIOS. Need less to say that this may have very bad consequences. Without the it87 driver you should still be able to get the system temperature with "acpi -t". I know that it's inferior to what the it87 driver offers, but for openSuse 10.2 there's no other way. We're working on a solution but it is a complex issue and it will take some more time before it's ready. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c63 --- Comment #63 from Christoph Resch 2007-10-16 13:46:34 MST --- i read about the troubles regarding ACPI .. seems the modern hardware wont have any access anymore to powertrotteling-functions :-( -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c65 Pavel Machek changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Normal Priority|P1 - Urgent |P5 - None --- Comment #65 from Pavel Machek 2007-10-17 02:35:01 MST --- Can we close this monsterbug? If you are running lm_sensors, your machine is unsupported... If you are NOT running lm_sensors, please open specific bug for your system. If you claim we need to detect false readings, take it to Len. We should make sure there are no false readings in the first place. I have done "lets read again" attempt to detecting false readings, and even that fails -- if you are unlucky, you'll get two bad readings in row. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c67 --- Comment #67 from Christoph Resch 2007-10-17 05:31:34 MST --- so how can i tell suse10.2 to disable "thermal" in favour to it87 ???? rmmod thermal tells me its in use .. i cannot remove it .. and IMHO the blacklistin of modules doesnt work out as expected please help ! best regards -c- -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c69 --- Comment #69 from Christoph Resch 2007-10-17 05:57:47 MST --- # fuser -m /proc/acpi/thermal tells me: Cannot stat /proc/acpi/thermal: No such file or directory Cannot stat /proc/acpi/thermal: No such file or directory Cannot stat /proc/acpi/thermal: No such file or directory i only have /proc/acpi/thermal_zone/THRM/ i albeitly removed "thermal" from INITRD_MODULES and ran mkinitrd .. on next reboot i will tell you .. thank you for support -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c71 --- Comment #71 from Thomas Renninger 2007-10-17 07:04:19 MST --- Sorry:

remove thermal from ACPI_MODULES (or similar) variable in /etc/sysconfig/kernel Shoud be: remove thermal from ACPI_MODULES (or similar) variable in /etc/sysconfig/powersave/common You have to enter explicitly the modules you like to have not remove thermal: "processor button" ,possibly battery ac or more if you have a laptop.

-- 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.

https://bugzilla.novell.com/show_bug.cgi?id=259992#c73 --- Comment #73 from Thomas Renninger 2007-10-22 01:39:02 MST --- If you read the comment above the variable: # If this variable is empty, the default is used. If you want to disable # module loading, enter "NONE". That means, if it's empty all default modules (stated some lines above) are tried to be loaded. Either add the drivers you like to have loaded or set it to NONE. -- 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.