http://bugzilla.kernel.org/show_bug.cgi?id=8842





------- Comment #9 from [EMAIL PROTECTED]  2007-08-07 00:15 -------
    >Are you running with (latest) BIOS SETUP options all in default settings?
    >Are there any fan-related options such as quiet vs performance settings?

    In the BIOS setup not everything is default. It is possible to select
between
    three modes:
    - all fans at a configurable speed
    - all fans at full speed
    - smart mode (fans are switched on and off dependent on temperature.

    In all three modes the trip points reported to linux are as described
earlier.

    >Please attach the complete output from dmesg -s64000
    >including the cooling device message above.
    >(the bus_set_power message is unrelated)

    Well, it is not unrelated. thermal.c is trying to activate the fan, that
    fails and triggers the message:

    Jul 31 10:29:40 linux kernel: [  857.048000]  thermal-0738 [-410]
thermal_check
            : THRM: temperature[3222] sleep[2000]
    [  859.048000] Execute Method: [\_TZ_.THRM._TMP] (Node c18dc8ec)
    [  859.048000] exregion-0185 [-396] ex_system_memory_space: System-Memory
    (width 16) R/W 0 Address=C025D8350$
    [  859.048000] exregion-0287 [-395] ex_system_io_space_han: System-IO
(width 8)
    R/W 1 Address=C026644B000002$
    [  859.048000] exregion-0287 [-395] ex_system_io_space_han: System-IO
(width 8)
    R/W 1 Address=C026644B000002$
    [  859.048000] exregion-0287 [-395] ex_system_io_space_han: System-IO
(width 8)
    R/W 1 Address=C026644B000002$
    [  859.048000] exregion-0287 [-396] ex_system_io_space_han: System-IO
(width 8)
    R/W 0 Address=C026644B000002$
    [  859.048000] exregion-0185 [-396] ex_system_memory_space: System-Memory
    (width 8) R/W 0 Address=C025D83500$
    [  859.048000]    utils-0287 [-411] evaluate_integer      : Return value
[3242]
    [  859.048000]  thermal-0230 [-411] thermal_get_temperatur: Temperature is
3242
    dK
    [  859.048000]  thermal-0511 [-411] thermal_passive       :
    trend[110]=(tc1[4]*(tmp[3242]-last[3222]))+(tc2[$
    [  859.048000]      bus-0201 [-411] bus_set_power         : Device
    `[PNP0C0B:00]' is not power manageable
    [  859.048000] ACPI: Unable to turn cooling device [c18dc9dc] 'on'
    [  859.048000]  thermal-0738 [-411] thermal_check         : THRM:
    temperature[3242] sleep[6000]
    [  865.048000] Execute Method: [\_TZ_.THRM._TMP] (Node c18dc8ec)

    >What do you see in /proc/acpi/fan/*/state before and after the
    >temperature crosses the 50C threshold -- is that when
    > the message above comes out, or does that occur upon boot?

    Fan state is always on, no matter if the fan is running or not. Writing to
    /proc/acpi/fan/FAN/state fails. As you can see from the system log snippet
    above, the message is only triggered if a more verbose acpi debug mode is
    selected and thermal.c tries to activate the fan.


    >Does the fan actually come on automatically when you reach 50,
    >or at another temperature?

    In "smart" mode, the fan comes on at about the selected temperature. But
it´s
    not a fast response. Otherwise the cpu fan runs always at full speed or at
the
    BIOS selected speed.

    >If you echo 0 and 3 into the the fan state files(s) are you able
    >to have any effect on the fan state?

    linux:/var/log # echo 3 > /proc/acpi/fan/FAN/state
    -bash: echo: write error: No such device

    No effect.

    >Curiously, the DSDT has an SFAN method with FON/FOFF
    >which are likely for controlling the fan, but these
    >methods are not referenced.

    Yes, isn´t that nice? ;-))

    >Looking over the DSDT, it does appear that this system intends
    >to support passive and active cooling modes.   However, both
    >the trip_points file and the dd above agree that the BIOS
    >is for some reason initializing both the active and passive
    >high-trip points to 50C.  Curiously, the DSDT records low
    >trip points that dd shows are 46C, but it doesn't seem to
    >implement hysteresis -- at least not in AML.
    >It would be interesting to observe at what temperature the
    >fan turns off at when the system cools.

    Fan on: For some seconds a bit above 50 deg. Celsius
    Fan off: Fore some secondes a bit below that temperature
    Switch off temp somewhere in the range 45 ... 47.

    >It would be interesting if any system events at all had
    >any effect on the output of the dd above.

    >Please echo 1 and 0 into /proc/acpi/thermal_zone/*/cooling_mode
    >While the AML will not change the trip-points, it is possible
    >that something needs to trigger an SMI that would change
    >them and then updated trip-points would be picked up by AML
    >from the region you describe above. (and thus they'd be
    >visible in the trip_points file)

    Echoing 0 and 1 to cooling_mode does reset the trip points to those
    stored in the BIOS data (50/50 deg. Celsius). That´s the behaviour
    programmed in the DSDT, isn´t it?

    >BTW. there is no danger of harming the flash soldered onto the board
    >by using dd to over-write the underlying trip-points above.
    >If that region is mapped to FLASH, then dd would simply fail.
    >If it works, then you'd be updating writable memory
    >(and the effect would go away after reboot/reset)
    >However, you'd have to notify AML of the update, such
    >as by executing an _SCP by writing to the cooling_mode file
    >as above.  Further, it is possible that SMM may overwrite
    >the value that you write...

    Well, the memory at 0x000FF810 is read only. As I was talking
    about patching the BIOS I meant to unpack an AOpen bios file,
    to patch the main BIOS image, to recalculate the check sums, to
    store the patched main BIOS to the compressed BIOS image and to
    flash that product to the chip. I had to do that for several
    computers years ago to overcome hard disk size limits, but I
    always had a spare programmed flash with an original BIOS.

    >The other question is where and what thermal events this
    >machine actually produces and what controls them.
    >Please kill acpid and cat /proc/acpi/event and see
    >what thermal events you get as the temperature changes.
    >(you can press the power button to make sure this scheme
    > is working -- /proc/interrupts should show the acpi line
    > increment for each press, and you should get a text line
    > out of /proc/acpi/event)

    There are no thermal events as the trip points are crossed,
    but as thermal.c polls every two seconds it detects the 
    temperature changes. Writing to cooling_mode produces an event,
    but not an increment in the irq 9 (acpi) count.

    >When you boot with "acpi=off", does the system boot properly,
    >run full load at full speed, and enable the fan as needed?

    It does boot and work at full speed, but some devices do not work.
    That includes but is not limited to all the USB stuff.

    >Can you detect from the sound if the fan speed in this mode
    >is the about same as the fan speed in ACPI mode, or can
    >you perceive a speed difference?

    The fan is controlled by the BIOS, and the machine is running
    at full speed. 

    >Finally, please confirm that your kernel has CONFIG_HWMON=n

    I tried that, but there is no difference to CONFIG_HWMON=y.


-- 
Configure bugmail: http://bugzilla.kernel.org/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.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
acpi-bugzilla mailing list
acpi-bugzilla@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla

Reply via email to