Kernel hangs with i2c-i801 driver?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Rudolf, Jean,

Can you give some hints now?
Frankly I have no idea about this issue yet.
It seems the SMI caused system hang?


Hi Daniel,
Yesterday I send the new datasheet to you.
I received the reject mail from Jean just now, so let assume you have
received the datasheet now :)
In that mail I mentioned the SMI#/IRQ mask registers, how about set
these mask? I'm trying to disable SMI.
I'm hoping to get the read back value of these commands.

i2cset -y 0 0x2c 0x43 0xff
i2cset -y 0 0x2c 0x44 0x7f
i2cset -y 0 0x2c 0x9c 0xff

If it does not work, let use following command to try other SMI mode.
Now the mode of your board is two time interrupt mode.
i2cset -y 0 0x2c 0x4c 0x01 #comparator interrupt mode
or
i2cset -y 0 0x2c 0x4c 0x81 #One time interrupt mode

Or BIOS will not let us do this too.... I don't know.

Or the SMI is triggered by fan limit/ voltage limit... The fan 4/5/6 low
limit of your MB is not 0.
Try to set all your fan limit value to zero.
i2cset -y 0 0x2c 0x3b 0xff
i2cset -y 0 0x2c 0x3c 0xff
i2cset -y 0 0x2c 0x3d 0xff
i2cset -y 0 0x2c 0xbb 0xff
i2cset -y 0 0x2c 0xbc 0xff
i2cset -y 0 0x2c 0xbd 0xff
i2cset -y 0 0x2c 0xbf 0xff


> >> Is there a chance that you have test hardware available with the
> >> w83792d chip where you could try to run the same commands that I
did?
> >>
> > Yes, I have a board on hand; it's a C version chip.
> 
> Your chip seems to behave differently from mine, but then again it is
has '12'
> as revision ID where my chip has '13'. So I guess we still need to
wait for
> that updated datasheet to understand if there are programming
differences.
>
Yes, yours is different from mine. But I can not find more useful
comments from the new datasheet... can you?

> The picture attached is a very simple drawing showing the south bridge
in one
> box and the w83792d in another box. There is one arrow from the south
> bridge to
> the w83792d labelled "SMI bus" and the there is one arrow from the
w83792d to
> the south bridge labelled interrupt.
>

Sorry I don't know how and why the arrow is from south bridge to w83792d
:(


Best Regards
Yuan Mu


===========================================================================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such  a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.
===========================================================================================If your computer is unable to decode Chinese font, please ignore the following message.It essentially repeats the statement in English given above.???H???????t?????q?l???]???????K?????T, ?????v???o?H?H???w?????H?H???\\????. ?????z???D?Q???w?????H?H???]???????]?b???g???v?????????U???????H??, ???z?i?????o?H?H?????Y?N?H???q?q???P???????A???????H????. ?????z???X?@, ?????????P??. ?S??????, ???????g???v?????????????q?l?????K???T???????O?Q?Y???T????. ?H???P?????q?l???~?L???????e,???o?????????q?l?????????N??.




[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux