Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[Luca Tettamanti]

(your mailer didn't insert the From: header... weird)

On Fri, Dec 11, 2009 at 12:51 AM,  <> wrote:
> i wanted to report the above mentioned.
> The sensors display with atk0110 itself is ok.
> But after a while, like one or two minutes after reboot, my keyboard and my
> mouse stops responding.

It's very strange since I had a tester that helped my with the very same board.
What kind of keyboard/mouse are you using? PS2 or USB?
Can you access the machine remotely (ssh)? If so, please send me a
dump of /proc/interrupts _after_ the keyboard becomes unresponsive.

> The system is still running, i can see "things happen" ;) like
> the seconds of my statusbar clock.
> Its just the mouse and the keyboard, anyway i had to cold reboot.
> After removing the driver again, everything works fine (except
> speedstepping/turboboost, which completely freezes my box, but thats
> another thing ;)

Ok, the only difference between working and non-working is the atk0110 driver?

Locate atk_ec_present function in asus_atk0110.c; put a

return 0;

as first instruction; recompile and see if it still locks up the keyboard.
Also enable HWMON_DEBUG_CHIP.

thanks,
Luca

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[Luca Tettamanti]

On Fri, Dec 11, 2009 at 7:03 PM,  <comsublant@gmx.net> wrote:
> On Fri, Dec 11, 2009 at 02:04:52PM +0100, Luca Tettamanti wrote:
>> It's very strange since I had a tester that helped my with the very same board.
>
> This might be mistakable: this is a pure p7p55d, not -premium or
> something.

I have a report of a working "pro" board, shouldn't change much, at
least as far as the ACPI interface is concerned.

>> What kind of keyboard/mouse are you using? PS2 or USB?
>
> PS2
>
>> Can you access the machine remotely (ssh)? If so, please send me a
>> dump of /proc/interrupts _after_ the keyboard becomes unresponsive.
>
> no remote access at the moment :(

Ok, does it respond to the power button? A clean shutdown may help to
preserve something interesting in the logs.

>> Ok, the only difference between working and non-working is the atk0110 driver?
>
> yes
>
>> Locate atk_ec_present function in asus_atk0110.c; put a
>>
>> return 0;
>> as first instruction; recompile and see if it still locks up the keyboard.
>> Also enable HWMON_DEBUG_CHIP.
>
> done.
> its not locking up anymore,
[...]
> its not changing though.

This is expected, since the EC is responsible of updating the values.
The behaviour that you describe seems to indicate a runaway interrupt
(possibly from the EC).
Please send me a copy of the DSDT (/sys/firmware/acpi/tables/DSDT) and
the output of lspci -vn

thanks,
Luca
PS: don't strip the CC

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[comsublant]

[-- Attachment #1: Type: text/plain, Size: 405 bytes --]

On Fri, Dec 11, 2009 at 09:44:38PM +0100, Luca Tettamanti wrote:
[snip] 
> This is expected, since the EC is responsible of updating the values.
> The behaviour that you describe seems to indicate a runaway interrupt
> (possibly from the EC).
> Please send me a copy of the DSDT (/sys/firmware/acpi/tables/DSDT) and
> the output of lspci -vn

still stable.
DSDT and lscpi output attached.
Thank you.
cteg

[-- Attachment #2: dsdt --]
[-- Type: application/octet-stream, Size: 59632 bytes --]

[-- Attachment #3: lspci.txt --]
[-- Type: text/plain, Size: 8794 bytes --]

00:00.0 0600: 8086:d131 (rev 11)
	Subsystem: 1043:8383
	Flags: fast devsel
	Capabilities: [40] #00 [0000]

00:03.0 0604: 8086:d138 (rev 11) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000c000-0000cfff
	Memory behind bridge: f8000000-fbcfffff
	Prefetchable memory behind bridge: 00000000c0000000-00000000dfffffff
	Capabilities: [40] Subsystem: 1043:8383
	Capabilities: [60] MSI: Enable+ Count=1/2 Maskable+ 64bit-
	Capabilities: [90] Express Root Port (Slot+), MSI 00
	Capabilities: [e0] Power Management version 3
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [150] Access Control Services
	Capabilities: [160] Vendor Specific Information <?>
	Kernel driver in use: pcieport

00:08.0 0880: 8086:d155 (rev 11)
	Subsystem: 0043:0083
	Flags: fast devsel
	Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Vendor Specific Information <?>

00:08.1 0880: 8086:d156 (rev 11)
	Subsystem: 0043:0083
	Flags: fast devsel
	Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Vendor Specific Information <?>

00:08.2 0880: 8086:d157 (rev 11)
	Subsystem: 0043:0083
	Flags: fast devsel
	Capabilities: [40] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Vendor Specific Information <?>

00:08.3 0880: 8086:d158 (rev 11)
	Flags: fast devsel

00:10.0 0880: 8086:d150 (rev 11)
	Flags: fast devsel

00:10.1 0880: 8086:d151 (rev 11)
	Flags: fast devsel

00:1a.0 0c03: 8086:3b3c (rev 05) (prog-if 20 [EHCI])
	Subsystem: 1043:8383
	Flags: bus master, medium devsel, latency 0, IRQ 16
	Memory at f7ffe000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
	Kernel driver in use: ehci_hcd

00:1b.0 0403: 8086:3b56 (rev 05)
	Subsystem: 1043:8375
	Flags: bus master, fast devsel, latency 0, IRQ 22
	Memory at f7ff8000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Virtual Channel <?>
	Capabilities: [130] Root Complex Link <?>
	Kernel driver in use: HDA Intel

00:1c.0 0604: 8086:3b42 (rev 05) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=06, subordinate=06, sec-latency=0
	I/O behind bridge: 00001000-00001fff
	Memory behind bridge: f0000000-f01fffff
	Prefetchable memory behind bridge: 00000000f0200000-00000000f03fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 1043:8383
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport

00:1c.4 0604: 8086:3b4a (rev 05) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=05, subordinate=05, sec-latency=0
	I/O behind bridge: 00002000-00002fff
	Memory behind bridge: f0400000-f05fffff
	Prefetchable memory behind bridge: 00000000f0600000-00000000f07fffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 1043:8383
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport

00:1c.5 0604: 8086:3b4c (rev 05) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: 00003000-00003fff
	Memory behind bridge: f0800000-f09fffff
	Prefetchable memory behind bridge: 00000000f0a00000-00000000f0bfffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 1043:8383
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport

00:1c.6 0604: 8086:3b4e (rev 05) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: fbe00000-fbefffff
	Prefetchable memory behind bridge: 00000000f0c00000-00000000f0dfffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 1043:8383
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport

00:1c.7 0604: 8086:3b50 (rev 05) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Memory behind bridge: fbd00000-fbdfffff
	Prefetchable memory behind bridge: 00000000f6f00000-00000000f6ffffff
	Capabilities: [40] Express Root Port (Slot+), MSI 00
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [90] Subsystem: 1043:8383
	Capabilities: [a0] Power Management version 2
	Kernel driver in use: pcieport

00:1d.0 0c03: 8086:3b34 (rev 05) (prog-if 20 [EHCI])
	Subsystem: 1043:8383
	Flags: bus master, medium devsel, latency 0, IRQ 23
	Memory at f7ffd000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: [50] Power Management version 2
	Capabilities: [58] Debug port: BAR=1 offset=00a0
	Capabilities: [98] PCI Advanced Features
	Kernel driver in use: ehci_hcd

00:1e.0 0604: 8086:244e (rev a5) (prog-if 01 [Subtractive decode])
	Flags: bus master, fast devsel, latency 0
	Bus: primary=00, secondary=07, subordinate=07, sec-latency=32
	Capabilities: [50] Subsystem: 1043:8383

00:1f.0 0601: 8086:3b02 (rev 05)
	Subsystem: 1043:8383
	Flags: bus master, medium devsel, latency 0
	Capabilities: [e0] Vendor Specific Information <?>

00:1f.2 0106: 8086:3b22 (rev 05) (prog-if 01 [AHCI 1.0])
	Subsystem: 1043:8383
	Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 34
	I/O ports at b880 [size=8]
	I/O ports at b800 [size=4]
	I/O ports at b480 [size=8]
	I/O ports at b400 [size=4]
	I/O ports at b080 [size=32]
	Memory at f7ff7000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
	Capabilities: [70] Power Management version 3
	Capabilities: [a8] SATA HBA <?>
	Capabilities: [b0] PCI Advanced Features
	Kernel driver in use: ahci

00:1f.3 0c05: 8086:3b30 (rev 05)
	Subsystem: 1043:8383
	Flags: medium devsel, IRQ 18
	Memory at f7ffc000 (64-bit, non-prefetchable) [size=256]
	I/O ports at ffe0 [size=32]
	Kernel driver in use: i801_smbus

01:00.0 0300: 10de:0641 (rev a1) (prog-if 00 [VGA controller])
	Subsystem: 1462:1571
	Flags: bus master, fast devsel, latency 0, IRQ 16
	Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
	Memory at c0000000 (64-bit, prefetchable) [size=512M]
	Memory at f8000000 (64-bit, non-prefetchable) [size=32M]
	I/O ports at cc00 [size=128]
	[virtual] Expansion ROM at fbc80000 [disabled] [size=512K]
	Capabilities: [60] Power Management version 3
	Capabilities: [68] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [78] Express Endpoint, MSI 00
	Capabilities: [b4] Vendor Specific Information <?>
	Capabilities: [100] Virtual Channel <?>
	Capabilities: [128] Power Budgeting <?>
	Capabilities: [600] Vendor Specific Information <?>
	Kernel driver in use: nvidia
	Kernel modules: nvidia

02:00.0 0200: 10ec:8168 (rev 03)
	Subsystem: 1043:83a3
	Flags: bus master, fast devsel, latency 0, IRQ 35
	I/O ports at d800 [size=256]
	Memory at f6fff000 (64-bit, prefetchable) [size=4K]
	Memory at f6ff8000 (64-bit, prefetchable) [size=16K]
	Expansion ROM at fbdf0000 [disabled] [size=64K]
	Capabilities: [40] Power Management version 3
	Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Endpoint, MSI 01
	Capabilities: [ac] MSI-X: Enable- Count=4 Masked-
	Capabilities: [cc] Vital Product Data
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Virtual Channel <?>
	Capabilities: [160] Device Serial Number 00-00-00-00-00-00-00-00
	Kernel driver in use: r8169

03:00.0 0106: 197b:2363 (rev 03) (prog-if 01 [AHCI 1.0])
	Subsystem: 1043:824f
	Flags: bus master, fast devsel, latency 0, IRQ 18
	Memory at fbefa000 (32-bit, non-prefetchable) [size=8K]
	Capabilities: [68] Power Management version 2
	Capabilities: [50] Express Legacy Endpoint, MSI 01
	Kernel driver in use: ahci

03:00.1 0101: 197b:2363 (rev 03) (prog-if 85 [Master SecO PriO])
	Subsystem: 1043:824f
	Flags: bus master, fast devsel, latency 0, IRQ 19
	I/O ports at ec00 [size=8]
	I/O ports at e880 [size=4]
	I/O ports at e800 [size=8]
	I/O ports at e480 [size=4]
	I/O ports at e400 [size=16]
	Capabilities: [68] Power Management version 2
	Kernel driver in use: pata_jmicron


[-- Attachment #4: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[Luca Tettamanti]

On Fri, Dec 11, 2009 at 10:33 PM,  <comsublant@gmx.net> wrote:
> On Fri, Dec 11, 2009 at 09:44:38PM +0100, Luca Tettamanti wrote:
> [snip]
>> This is expected, since the EC is responsible of updating the values.
>> The behaviour that you describe seems to indicate a runaway interrupt
>> (possibly from the EC).
>> Please send me a copy of the DSDT (/sys/firmware/acpi/tables/DSDT) and
>> the output of lspci -vn
>
> still stable.
> DSDT and lscpi output attached.

I have a report of a working P7P55D (plain) with BIOS 0711; the DSDT
of the working board is very different from yours. Can you try and
upgrade the BIOS?

Luca

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[comsublant]

On Wed, Dec 16, 2009 at 03:05:16PM +0100, Luca Tettamanti wrote:
> 
> I have a report of a working P7P55D (plain) with BIOS 0711; the DSDT
> of the working board is very different from yours. Can you try and
> upgrade the BIOS?
> 
> Luca

My board was already shipped with 1102, and really don't want to
downgrade.

-r--r--r-- 1 ftp ftp         994530 Aug 27  2009 P7P55D-ASUS-0501.zip
-r--r--r-- 1 ftp ftp        1001476 Sep 08  2009 P7P55D-ASUS-0606.zip
-r--r--r-- 1 ftp ftp        1014992 Sep 30  2009 P7P55D-ASUS-0711.zip
-r--r--r-- 1 ftp ftp        1021356 Nov 05  2009 P7P55D-ASUS-0911.zip
-r--r--r-- 1 ftp ftp        1021410 Nov 12 17:01 P7P55D-ASUS-0915.zip
-r--r--r-- 1 ftp ftp        1022785 Nov 20 17:05 P7P55D-ASUS-1002.zip
-r--r--r-- 1 ftp ftp        1023694 Nov 28 01:00 P7P55D-ASUS-1102.zip
-r--r--r-- 1 ftp ftp        1025919 Dec 14 17:01 P7P55D-ASUS-1207.zip

i'll might give 1207 a try, which is just 2 days old, can't tell if
this is fixing anything, from what they say.
Although it might help with my speedstepping/turboboost problem, which
i have deactivated atm.

[ 1207 ]
----------------------
1.Update JMicron 361 Option ROM
2.Update EZ-flash 2 function
3.Fix some PCIEx1 LAN card can't be detected at PCH PCIEx1 slot.
4.Update CPU Level Up function.
5.Fix CPU power always show 2.5W in EPU software.

-cteg

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[comsublant]

On Wed, Dec 16, 2009 at 03:05:16PM +0100, Luca Tettamanti wrote:
> I have a report of a working P7P55D (plain) with BIOS 0711; the DSDT
> of the working board is very different from yours. Can you try and
> upgrade the BIOS?

I upgraded the bios to 1207.
First i was like "yay", but then again, this time after appr. 30
minutes, same error again. Machine still runs, keyboard and mouse
locked up.
Made intense memory checks, checked my bios settings over and over.
Disabling the atk0110 driver, it's stable.
Other thing. The 30 minutes with enabled sensors, i noticed the cpu
temp was way too low, like 20 degrees C. In the bios hw monitor this
is usually around 45 degrees Celsius.
Is that something i have to set like for those old lm78/wd* chips?

cteg

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[Luca Tettamanti]

On Thu, Dec 17, 2009 at 12:43 AM,  <comsublant@gmx.net> wrote:
> On Wed, Dec 16, 2009 at 03:05:16PM +0100, Luca Tettamanti wrote:
>> I have a report of a working P7P55D (plain) with BIOS 0711; the DSDT
>> of the working board is very different from yours. Can you try and
>> upgrade the BIOS?
>
> I upgraded the bios to 1207.
> First i was like "yay", but then again, this time after appr. 30
> minutes, same error again. Machine still runs, keyboard and mouse
> locked up.
> Made intense memory checks, checked my bios settings over and over.
> Disabling the atk0110 driver, it's stable.
> Other thing. The 30 minutes with enabled sensors, i noticed the cpu
> temp was way too low, like 20 degrees C. In the bios hw monitor this
> is usually around 45 degrees Celsius.
> Is that something i have to set like for those old lm78/wd* chips?

No, the conversion/scaling is done by the ACPI interface.
I really don't know what's going on here... do you have Windows
installed? If so, does Asus monitoring app work?
At this point the only advice I can give you is to avoid asus_atk0110
driver and use the native one.

Luca

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[Michael Dreher]

Hello Luca,

by googling I found this discussion on the sensors-mailinglist 
(so maybe some CC: are lost), and I observe the same problem (comments below)


>On Fri, Dec 11, 2009 at 7:03 PM,  <comsublant <at> gmx.net> wrote:
>> On Fri, Dec 11, 2009 at 02:04:52PM +0100, Luca Tettamanti wrote:
>>> It's very strange since I had a tester that helped my with the very same 
>>> board.
>>
>> This might be mistakable: this is a pure p7p55d, not -premium or
>> something.
>
> I have a report of a working "pro" board, shouldn't change much, at
> least as far as the ACPI interface is concerned.
>
>>> What kind of keyboard/mouse are you using? PS2 or USB?
>>
>> PS2
>>
>>> Can you access the machine remotely (ssh)? If so, please send me a
>>> dump of /proc/interrupts _after_ the keyboard becomes unresponsive.
>>
>> no remote access at the moment :(
>
> Ok, does it respond to the power button? A clean shutdown may help to
> preserve something interesting in the logs.
> 
>>> Ok, the only difference between working and non-working is the 
>>> atk0110 driver? 
>>
>> yes
>>
>>> Locate atk_ec_present function in asus_atk0110.c; put a
>>>
>>> return 0;
>>> as first instruction; recompile and see if it still locks up the keyboard.
>>> Also enable HWMON_DEBUG_CHIP.
>>
>> done.
>> its not locking up anymore,
> [...]
>> its not changing though.
>
> This is expected, since the EC is responsible of updating the values.
> The behaviour that you describe seems to indicate a runaway interrupt
> (possibly from the EC).
> Please send me a copy of the DSDT (/sys/firmware/acpi/tables/DSDT) and
> the output of lspci -vn
>
> thanks,
> Luca



in my situation: just a few minutes into a KDE session (doing nothing
extraordinary) first the mouse becomes unresponsive, and about 15 seconds
later also the keyboard (toggling num-lock does nothing). Both are connected
via PS. This has happened with 2.6.33-rc5 and rc6 as taken from the opensuse
repository. I was thinking that maybe the X-server is doing something wrong, 
and for both kernels, I had renamed the module "nouveau.ko" to something else
(and also the libdrmnouveau files), and the error has not yet come back (but
I need more testing). 
I don't know how this is related to the atk0110, but at least sensors-detect
finds some i2-c devices on the nvidia card (and can not do much with them).

My board is a P7P55D, and I also obtain these deep temperatures:

[...]
CPU Temperature: +32.5°C (high = +45.0°C, crit = +45.5°C)
 MB Temperature: +31.0°C (high = +45.0°C, crit = +46.0°C)
[...]

Is there a chance to change the "high" and "crit" values to something higher ?
Because the chassis fan is extremely loud ...

best regards,
Michael





_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[Luca Tettamanti]

On Mon, Feb 8, 2010 at 11:31 AM, Michael Dreher
<michael.dreher@uni-konstanz.de> wrote:
> Hello Luca,
>
> by googling I found this discussion on the sensors-mailinglist
> (so maybe some CC: are lost), and I observe the same problem (comments below)
>
>
>>On Fri, Dec 11, 2009 at 7:03 PM,  <comsublant <at> gmx.net> wrote:
>>> On Fri, Dec 11, 2009 at 02:04:52PM +0100, Luca Tettamanti wrote:
>>>> It's very strange since I had a tester that helped my with the very same
>>>> board.
>>>
>>> This might be mistakable: this is a pure p7p55d, not -premium or
>>> something.
>>
>> I have a report of a working "pro" board, shouldn't change much, at
>> least as far as the ACPI interface is concerned.
>>
>>>> What kind of keyboard/mouse are you using? PS2 or USB?
>>>
>>> PS2
>>>
>>>> Can you access the machine remotely (ssh)? If so, please send me a
>>>> dump of /proc/interrupts _after_ the keyboard becomes unresponsive.
>>>
>>> no remote access at the moment :(
>>
>> Ok, does it respond to the power button? A clean shutdown may help to
>> preserve something interesting in the logs.
>>
>>>> Ok, the only difference between working and non-working is the
>>>> atk0110 driver?
>>>
>>> yes
[...]
> in my situation: just a few minutes into a KDE session (doing nothing
> extraordinary) first the mouse becomes unresponsive, and about 15 seconds
> later also the keyboard (toggling num-lock does nothing). Both are connected
> via PS. This has happened with 2.6.33-rc5 and rc6 as taken from the opensuse
> repository. I was thinking that maybe the X-server is doing something wrong,
> and for both kernels, I had renamed the module "nouveau.ko" to something else
> (and also the libdrmnouveau files), and the error has not yet come back (but
> I need more testing).
> I don't know how this is related to the atk0110, but at least sensors-detect
> finds some i2-c devices on the nvidia card (and can not do much with them).

atk0110 doesn't touch the bus directly, so there's no chance that it
could mess with the nVidia card.
Two things:
- are you positive that removing atk0110 fixes the problem?
- does it happen without X (i.e. from console)?

> My board is a P7P55D, and I also obtain these deep temperatures:
>
> [...]
> CPU Temperature: +32.5°C (high = +45.0°C, crit = +45.5°C)
>  MB Temperature: +31.0°C (high = +45.0°C, crit = +46.0°C)
> [...]
>
> Is there a chance to change the "high" and "crit" values to something higher ?
> Because the chassis fan is extremely loud ...

Nope; the values are set by the BIOS. Fan speed is also controlled by
the BIOS (Q-FAN), try setting a different profile (like "Silent").

Luca

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[Michael Dreher]

Am Dienstag, 9. Februar 2010 17:15 schrieb Luca Tettamanti:
>>>>> Ok, the only difference between working and non-working is the
>>>>> atk0110 driver?
>>>>
>>>> yes
>
> [...]
>
>> in my situation: just a few minutes into a KDE session (doing nothing
>> extraordinary) first the mouse becomes unresponsive, and about 15 seconds
>> later also the keyboard (toggling num-lock does nothing). Both are
>> connected via PS. This has happened with 2.6.33-rc5 and rc6 as taken from
>> the opensuse repository. I was thinking that maybe the X-server is doing
>> something wrong, and for both kernels, I had renamed the module
>> "nouveau.ko" to something else (and also the libdrmnouveau files), and
>> the error has not yet come back (but I need more testing).
>> I don't know how this is related to the atk0110, but at least
>> sensors-detect finds some i2-c devices on the nvidia card (and can not do
>> much with them).
>
> atk0110 doesn't touch the bus directly, so there's no chance that it
> could mess with the nVidia card.
> Two things:
> - are you positive that removing atk0110 fixes the problem?
> - does it happen without X (i.e. from console)?

testing still goes on, and the results up to now are:
* with nouveau loaded, but atk0110 removed: lockup of keyboard and mouse,
  easily reproducible
* without noveau, but atk0110 loaded: lockup with same symptoms, but 
  harder to reproduce

> > My board is a P7P55D, and I also obtain these deep temperatures:
> >
> > [...]
> > CPU Temperature: +32.5°C (high = +45.0°C, crit = +45.5°C)
> >  MB Temperature: +31.0°C (high = +45.0°C, crit = +46.0°C)
> > [...]
> >
> > Is there a chance to change the "high" and "crit" values to something
> > higher ? Because the chassis fan is extremely loud ...
>
> Nope; the values are set by the BIOS. Fan speed is also controlled by
> the BIOS (Q-FAN), try setting a different profile (like "Silent").

well, I have already chosen "Silent" (and I hear no difference). 
And Windows 7 somehow can control the fans/sensors directly, bringing
the noise down to a much lower level ...


thanks,
Michael


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[Jean Delvare]

On Wed, 10 Feb 2010 19:57:24 +0100, Michael Dreher wrote:
> Am Dienstag, 9. Februar 2010 17:15 schrieb Luca Tettamanti:
> > Nope; the values are set by the BIOS. Fan speed is also controlled by
> > the BIOS (Q-FAN), try setting a different profile (like "Silent").
> 
> well, I have already chosen "Silent" (and I hear no difference). 
> And Windows 7 somehow can control the fans/sensors directly, bringing
> the noise down to a much lower level ...

Windows 7, or some vendor-provided application?

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[Michael Dreher]

Am Mittwoch, 10. Februar 2010 20:43 schrieb Jean Delvare:
> On Wed, 10 Feb 2010 19:57:24 +0100, Michael Dreher wrote:
> > Am Dienstag, 9. Februar 2010 17:15 schrieb Luca Tettamanti:
> > > Nope; the values are set by the BIOS. Fan speed is also controlled by
> > > the BIOS (Q-FAN), try setting a different profile (like "Silent").
> >
> > well, I have already chosen "Silent" (and I hear no difference).
> > And Windows 7 somehow can control the fans/sensors directly, bringing
> > the noise down to a much lower level ...
>
> Windows 7, or some vendor-provided application?

this is windows 7 vanilla, direct from Microsoft. Shortly before the 
login prompt, you hear a dropping down of the noise level. 
Afterwards, I have installed the utilities from asus, and there you can
set the temperature for CPU and MB, the standard setting is 60 degrees
for both, and the lowest possible value (and standard setting from bios)
is 45 degrees. But I have no idea how risky it is to play with these
settings.

Michael


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] ATK0110 breaks keyboard and mouse on asus p7p55d -

[Jean Delvare]

On Fri, 12 Feb 2010 13:46:06 +0100, Michael Dreher wrote:
> Am Mittwoch, 10. Februar 2010 20:43 schrieb Jean Delvare:
> > On Wed, 10 Feb 2010 19:57:24 +0100, Michael Dreher wrote:
> > > well, I have already chosen "Silent" (and I hear no difference).
> > > And Windows 7 somehow can control the fans/sensors directly, bringing
> > > the noise down to a much lower level ...
> >
> > Windows 7, or some vendor-provided application?
> 
> this is windows 7 vanilla, direct from Microsoft. Shortly before the 
> login prompt, you hear a dropping down of the noise level. 

Could be the hardware (or ACPI) doing automatic temperature-based fan
speed regulation. The system is usually very busy during boot,
resulting in high CPU temperature. When you get to the login prompt,
the hard work is done and the CPU might get cooler, leading to slower
fans.

But of course if you don't notice the same on Linux, then that would
indeed be Windows doing something about it. This would be good news, so
far Microsoft had been entirely ignoring temperature management.

> Afterwards, I have installed the utilities from asus, and there you can
> set the temperature for CPU and MB, the standard setting is 60 degrees
> for both, and the lowest possible value (and standard setting from bios)
> is 45 degrees. But I have no idea how risky it is to play with these
> settings.

You can probably assume it is safe if the vendor itself lets you change
the values. It is usually a trade-off between noise and component
lifetime. With higher limits, the hardware will age faster. That being
said, it depends on what exactly these limits are changing... if they
are changing the trip points for fan speed control, or the CPU
throttling, or the emergency shutdown, the effects are quite different.

Anyway, 45째C seems like an unreasonably low limit these days for a CPU.
Some machines are running hotter than that even when idle. I can't
remember ever setting the high limit for my CPU temperature below 55째C.
45째C may be OK for the case temperature, but I wouldn't mind increasing
it to 50째C.

-- 
Jean Delvare
http://khali.linux-fr.org/wishlist.html

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors